IEEE Std 802.1Qcp-2018 pdf free downlaod – IEEE Standard for Local and m etropolitan area ne tworks— Brid ge s and Brid ge d Ne two rks— Amendment 30: YAN G Da ta Model.
8. Principles of Bridge operation
Change the text of 8.12 as follows:
8.12 Bridge Management Entity
Remote management capabilities (as opposed to management via a console or other device attached directly to a Bridge) are modeled as performed by a Bridge Management Entity supported by a protocol stack as described in 8.13.7. To facilitate interoperable remote management, the Bridge Management Entity should use either the SMIv2 MIB modules specified in Clause 17 with SNMP or the YANG modules specified in Clause 48 with a network configuration protocol, e.g., NETCONF, RESTCONF.
8.13 Addressing
Change the text of 8.13.7 as follows:
8.13.7 Bridge Management Entities
Network configuration and management protocols typically use IP as a network layer protocol. SNMP can also be supported directly over an IEEE 802 LAN, as specified in IETF RFC 4789. If implemented, the The management protocol stack and address used shall be supported by a single LLC Entity attached to a Bridge Port. The Port should be a Management Port for the Bridge, as described in 8.3 and Figure 8-8, but may be a Port attached to a LAN, as described in 8.13.9, Figure 8-21, and Figure 8-22.
12. Bridge management
12.10 Bridge VLAN managed objects
Change the first paragraph of 12.10.1 as follows:
12.10.1 Bridge VLAN Configuration managed object
The Bridge VLAN Configuration managed object models operations that modify, or inquire about, the overall configuration of the Bridge’s VLAN resources. There is a single Bridge VLAN Configuration managed object per Bridge Component.
48. YANG Data Model
This clause specifies YANG data models that provide control and status monitoring of IEEE 802.1Q Bridges. Specifically,
a) Two-Port MAC Relays,
b) Customer VLAN bridges, and
c) Provider bridges.
The YANG bridge data management models are derived from UML models specified in 48.3. The UML models are based on Clause 12.
NOTE 1—OMG UML 2.5 [B78] conventions together with C++ language constructs are used in this clause as a representation to convey model structure and relationships.
NOTE 2—The MIB modules specified in Clause 17 were also derived from Clause 12. Consequently, the capabilities and structure of the YANG data models should closely aligned with that represented by the MIBs. However the YANG data model has not been derived from the MIB, and there has been no attempt to include data or modeling constructs that might appear in the MIB but not in the information model.
48.1 YANG Framework
This clause has been developed according to the YANG guidelines published in IETF RFC 6087 [B68] as applicable to IEEE standards.
The YANG framework applies hierarchy in the following areas:
1) The uniform resource name (URN), as specified in IEEE Std 802d. The structure of the URN is such that ieee is the root (i.e., name-space identifier), followed by the standard, then the working group developing the standard.
2) The YANG objects form a hierarchy of configuration and operational data structures that define the YANG model. These hierarchical relationships are described in 48.3.
The general YANG framework hierarchy is illustrated in Figure 48-1.IEEE Std 802.1Qcp pdf download.