RSS feed
[Home] . [What's New?] . [Active Ballots] . [Minutes] . [Public Docs] . [Committee Docs]
[802 Architecture Group] . [Audio/Video Bridging Task Group] . [Data Center Bridging Task Group]
[Email] . [Ancient Email] . [Meetings] . [802.1 MIBs] . [802.1 OIDs] . [802.1 Interpretations] . [IEEE 802] . [IEEE 802 PARs]
[802] . [802-REV] . [802a] . [802b] . [802.1D] . [802.1D-2004] . [802.1G] . [802.1Q] . [802.1Q-REV] . [802.1s] . [802.1v] . [802.1w] . [802.1AB] . [802.1AB-REV] . [802.1AC] . [802.1ad] . [802.1ag] . [802.1ah] . [802.1aj] . [802.1ak] . [802.1ap] . [802.1aq] . [802.1Qaw] . [802.1Qay]
Security: [802.1X-2001] . [802.1X-2004] . [802.1X-REV] . [802.1AE] . [802.1af] . [802.1AR]
AVB: [802.1AS] . [802.1Qat] . [802.1Qav] . DCB: [802.1Qau] . [802.1Qaz]


802.1AB-REV - Station and Media Access Control Connectivity Discovery

The scope of this standard is to define a protocol and management elements, suitable for advertising information to stations attached to the same IEEE 802 LAN, for the purpose of populating physical topology and device discovery management information databases. The protocol facilitates the identification of stations connected by IEEE 802 LANs/MANs, their points of interconnection, and access points for management protocols. This standard defines a protocol that:

An IETF Standard MIB (IETF RFC 2922 [B15]), as well as a number of vendor specific MIBs, have been created to describe a network's physical topology and associated systems within that topology. However, there is no standard protocol for populating these MIBs or communicating this information among stations on the IEEE 802 LAN.

This standard specifies the necessary protocol and management elements to:

New destination addresses and explicit forwarding rules for LLDP frames are needed to accurately determine the toplogy over transparent forwarding devices such as those defined by 802.1ad and 802.1aj. Additionally, new and developing 802 standards, such as 802.3at, 802.1at and 802.1au, have the need to rapidly discover the boundary in the topology for which particular capabilities are operating. New information elements and a more rapid exchange of LLDP frames is necessary to support the timely discovery of this boundary. Users of this standard will be able to accurately exchange information on a greater set of 802.1 topologies and will experience a more rapid convergence of information.

Status
StatusPAR approved February 27th, 2007
DocumentDraft 0.0
EditorTony Jeffree

Archive
DateDocument
04 Jan 2007802.1AB-REV, Draft 0.0
02 Apr 2007802.1ab, Draft 1 d1-0
22 May 2007802.1ab, Draft 1 proposed comment dispositions
26 May 2007802.1ab, Draft 1 proposed comment dispositions
08 Jun 2007802.1ab, Draft 1 comment dispositions
02 Jul 2007802.1ab, Draft 2 d2-0
01 Nov 2007802.1ab, Draft 2 d2-1
05 Dec 2007802.1ab, Draft 2 d2-2
23 Jan 2008802.1ab, Draft 2 proposed comment dispositions
08 May 2008802.1ab, Draft 2 proposed comment dispositions

<-- Automatic paper updates are turned off for 802.1AB-rev because of a bug in the web page scripts which matches every new paper to 802.1AB-rev. --> Presentations
DateDocument

Pages copyright © Institute of Electrical and Electronics Engineers, Inc. Please read the rules on Confidentiality Statements and Copyright Notices on Communications. If you have any comments on these pages, please send them to me.

Valid XHTML 1.0 Transitional Valid CSS!

Last status: 0
Last modified by jmesseng, at 2:39PM on Thu, 08 May 2008