Requested revision
Standard: | 802.1Qcp-2018 | Clause: | 48.6.3.2 |
Clause title: | Definition for the ieee802-dot1q-types YANG module |
Rationale for revision
The 'choice map-type' statement as part of the 'dot1q-types:port-map-grouping' is confusing in my opinion and violates some parts of the IEEE 802.1Q standard in Section 8.8. As per the standard, the entire filtering entry could be a 'static-filtering-entry', 'mac-address-registration-entry', etc... Thus it should not be defined per individual port in the port map with the 'choice map-type' per port. (i.e. It is currently possible for a 'filtering-entry' to have a port in the port map to be a 'static-filtering-entry' and another port to be a 'dynamic-filtering-entry').
Proposed text
I believe the port-map should have the 'forward', 'filter' and 'forward-filter' enumeration options per port and have a separate "type" parameter to represent the filtering-entry's type ('static-filtering-entry', 'dynamic-filtering-entry', etc...). For this model, it is important to define 'must' statements that prevent the port in the port-map from being in the 'forward', 'filter', or 'forward-filter' states depending on the 'filtering-entry' type.
Impact on existing networks
YANG upgrade on 'ieee802-dot1q-types.yang' will be required.
Originator
Name: | William Zhao | Email: | william.zhao@siemens.com |
Affiliation: | Siemens | ||
Submitted: | 2018-09-25 |