Requested revision
| Standard: | IEEE Std 802.1Q-2022 | Clause: | 48.6.4 |
| Clause title: | The ieee802-dot1q-bridge YANG module | ||
Rationale for revision
There is a compatibility issue with the ieee802-dot1q-bridge YANG module when it is used in a solution with other YANG modules. The "when" statement associated with bridge-port (augments IETF interface) evaluates true when the interface type is either a bridge, ethernetCsmacd, ieee802adLag, or iLan. The issue is that there are some cases when the interface type is ethernetCsmacd, but the solution does not want or need the bridge-port information included. Therefore, the suggestion is to change the augment statement for bridge-port so that it is possible to enable or disable the use of the bridge-port information.
A further discussion of the issue and rationale for the solution is found here: https://www.ieee802.org/1/files/public/docs2024/yangsters-smansfield-axdz-augmentation-issue-0524-v01.pdf
Proposed text
Add a presence container:
augment "/if:interfaces/if:interface" {
container no-bridge-port {
presence "Indicates if the bridge-port container should be available or not";
description "no-bridge-port indicator";
}
}
Change the augment for bridge-port to the following:
augment "/if:interfaces/if:interface" {
when "(derived-from-or-self(if:type,'ianaif:bridge') or "+
"derived-from-or-self(if:type,'ianaif:ethernetCsmacd') or "+
"derived-from-or-self(if:type,'ianaif:ieee8023adLag') or "+
"derived-from-or-self(if:type,'ianaif:ilan')) and " +
"not(dot1q:no-bridge-port)"
Editorial license is encouraged to add descriptions/change the name of the presence container based on editors style and group consensus.
Impact on existing networks
The change is backwards compatible with existing solutions.
Originator
| Name: | Scott Mansfield | Email: | scott.mansfield@ericsson.com |
| Affiliation: | Ericsson | ||
| Submitted: | 2024-06-19 | ||