|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IEEE 802.1AB-2005
|
|
Title:
|
IEEE Standard for Local and metropolitan area networks - Station and Media Access Control Connectivity Discovery IEEE 802.1AB describes the management objects and protocol that can be used for Layer 1 topology discovery in Ethernet LANs.
|
|
|
2.
|
Status of approval:
|
|
|
Approved as standard.
|
|
3.
|
Justification for the specific reference:
|
|
|
G.8011/Y.1307 Corrigendum 1 specifies the correct handling of IEEE 802.1 control frames at the Ethernet transport UNI. IEEE 802.1AB specifies a control frame associated with its protocol.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known issues.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
New standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
New standard.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
G.8011/Y.1307 specifies the Ethernet transport UNI and NNI for Ethernet Private Line services, including how to handle the control frames.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
1. Abstract Syntax Notation One (ASN.1): Specification of Basic Notation, ITU-T Rec. X.680 (2002) ISO/IEC 8824-1:2002.3/
2. IEEE Std 802®-2001, IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture.4, 5/
3. IEEE Std 802a™-2003, IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture-Amendment 1: Ethertypes for Prototype and Vendor-Specific Protocol Development./
4. IEEE Std 802.1D™-2004, Standard for Local and Metropolitan Area Networks: Media Access Control (MAC) Bridges./
5. IEEE Std 802.1Q™-1998, IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks./
6. IEEE Std 802.1X™-2004, IEEE Standard for Local and Metropolitan Area Networks-Port-Based Network Access Control./
7. IEEE Std 802.3™-2002, Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications./
8. IEEE Std 802.3ae™-2002, Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications-Amendment: Media Access Control (MAC) Parameters, Physical Layers, and Management Parameters for 10 Gb/s Operation./
9. IEEE Std 802.3af™-2003, Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications-Amendment: Data Terminal Equipment (DTE) Power via Media Dependent Interface (MDI)./
10. IETF RFC 1493, Definitions of Managed Objects for Bridges, Decker, E., Langille, P., Rijsinghani, A., and McCloghrie, K., July 1993.6/
11. IETF RFC 1812, Requirements for IP Version 4 Routers, Baker, F., June 1995./
12. IETF RFC 2108, Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2, de Graaf, K., and Romascanu, D., February 1997./
13. IETF RFC 2011, SNMPv2 Management Information Base for the Internet Protocol using SMIv2, McCloghrie, K., November 1996./
14. IETF RFC 2021, Remote Network Monitoring Management Information Base Version 2 using SMIv2, Waldbusser, S., January 1997./
15. IETF RFC 2669, DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems, St. Johns, M., August 1999./
16. IETF RFC 2670, Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces, St. Johns, M., August 1999./
17. IETF RFC 2674, Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions, Bell, E., Smith, A., Langille, P., Rijhsinghani, A., and McCloghrie, K., August 1999./
18. IETF RFC 2683, IMAP4 Implementation Recommendations, Leiba, B., September 1999./
19. IETF RFC 2737, Entity MIB (Version 2), McCloghrie, K., and Bierman, A., December 1999./
20. IETF RFC 2863, The Interfaces Group MIB, McCloghrie, K. and Kastenholz, F., June 2000./
21. IETF RFC 3046, DHCP Relay Agent Information Option, Patrick, M., January 2001./
22. IETF RFC 3232, Assigned Numbers: RFC 1700 is Replaced by an On-line Database, Reynolds, J., January 2002.7/
23. IETF RFC 3410, Introduction and Applicability Statements for Internet-Standard Management Framework, Case, J., Mundy, R.,Partain, D., and Stewart, B., December 2002./
24. IETF RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP), Presuhn, R., ED., December 2002./
25. IETF RFC 3621, Power Ethernet MIB, Berger, A. and Romascanu, D., December 2003./
26. IETF RFC 3629, UTF-8, a transformation format of ISO 10646, Yergeau, F. November 2003./
27. IETF RFC 3636, Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs), Flick, J., September 2003.
|
|
9.
|
Qualification of
IEEE:
|
|
|
The IEEE was recognized under the provisions of ITU-T Recommendation A.5 on 1 November 1999. Qualifying information is on file with TSB.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
