Closed michbin closed 4 years ago
For VLAN purposes I would agree that an "empty" VLAN should be represented as "empty" ForwardingConstuct. A solution could be: by "pruning-and-refactoring" the min-elements as defined in CoreModel.UML could be "corrected".
@openBackhaul: please comment.
Decision made on the ONF call: https://wiki.opennetworking.org/display/OTCC/2019-10-30+5G-xHaul+Meeting+Notes
Change min-elements from 2 to 0.
Please retest once a new core-model was delivered.
Minimum number of elements changed to 0. Issue can be closed.
list fc-port {
key "local-id";
min-elements 0;
uses fc-port;
description
"The FcPorts define the boundary of the FC.
The FC is accessed via the FcPorts.
Flow within the FC is defined in terms of its FcPorts.";
}
For avoiding warnings during compilation the "min-elements 0;" statement has been removed.
RFC7950: "If no "min-elements" statement is present, it defaults to zero."
The fc-port list in the forwarding-construct grouping is defined with
min-elements 2
, i.e. must have at least 2 elements. This is not true for Forwarding Constructs which represent VLANs. They are usually created without member ports which are added afterwards.