 |
[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.1Qaw - Management of data-driven and data-dependent connectivity faults
The full title of this PAR is "IEEE Standard for Local and Metropolitan Area Networks---Virtual Bridged Local Area Networks - Amendment: Management of data-driven and data-dependent connectivity faults.".
This standard specifies connectivity fault management protocols, procedures, and managed objects that provide confirmation of successful transmission of frames conveying specified data. This capability supports diagnosis of faults sensitive to, or caused by, particular data patterns, and their isolation to part of the data path. Connectivity verification can be carried out from any single point with bridged connectivity to maintenance points on the data path, can isolate failures to communicate in a specific direction, and can be carried out while service is being provided to other users of the data path. Security considerations are addressed by the use of the mechanisms defined in IEEE Std 802.1X - "Standard for Local and metropolitan area networks - Port-Based Network Access Control", IEEE Std 802.1AE - "Standard for Local and metropolitan area networks - Media Access Control (MAC) Security", and IEEE P802.1af - "Standard for Local and metropolitan area networks - Port-Based Network Access Control - Amendment 1: Authenticated Key Agreement for Media Access Control (MAC) Security".
While bridged networks are notionally transparent to the users’ data, they are often deployed as part of a service offering that selectively filters data frames (e.g. firewall functionality), automatically configures some aspect of service in response to data frames (e.g. IGMP snooping), or is supported by transmission in a data-sensitive way (e.g. IEEE Std 802.3ad Clause 43 - Link Aggregation). This standard defines the protocols (including CFM OpCodes) and managed objects required for data-sensitive connectivity verification that is multi-vendor, interoperable, and uses the framework provided by IEEE P802.1ag Connectivity Fault Management.
There is considerable demand, from the service providers that currently use or plan to use IEEE 802.1 bridging standards, for diagnostic functionality equivalent to that provided by reflecting all data frames (as used by other network technologies) and operates in a broadly similar way. A straight forward application of reflection to IEEE 802.1Q networks is known to cause problems that can be hard to diagnose while not addressing complex fault scenarios, but is likely to be widely implemented in the absence of a better standard solution. The proposed amendment offers that solution, and includes additional capabilities required in bridged networks.
| Status | PAR approved February 27th, 2007, Working Group Ballot |
| Document | 802.1Qaw draft 2.1 |
| Dispositions | Draft 2.0 Comment Dispositions |
| Editor | Linda Dunbar |
| Date | Document |
|---|---|
| 15 Mar 2007 | 802.1Qaw, Editor's draft 0.0 |
| 27 Apr 2007 | 802.1Qaw, Draft 0.2 |
| 27 Jun 2007 | 802.1Qaw, Draft 0.2 comment dispositions |
| 10 Aug 2007 | 802.1Qaw, Draft 1.0 |
| 26 Oct 2007 | 802.1Qaw, Draft 1.0 comment dispositions |
| 26 Oct 2007 | 802.1Qaw, Draft 1.1 |
| 07 Jan 2008 | 802.1Qaw, Draft 1.1 comment dispositions |
| 07 Jan 2008 | 802.1Qaw, Draft 2.0 |
| 21 Jan 2008 | 802.1Qaw, Draft 2.0 MIB |
| 08 Apr 2008 | 802.1Qaw, Draft 2.1 MIB |
| 08 Apr 2008 | 802.1Qaw, Draft 2.1 |
| 08 Apr 2008 | 802.1Qaw, Draft 2.0 comment dispositions |
| Date | Document |
|---|---|
| 08 Mar 2006 | Presentation new-seaman-ddcfm-0306-01.pdf |
| 12 Mar 2006 | Presentation new-seaman-ddcfm-0306-02.pdf |
| 15 Mar 2006 | Presentation new-seaman-ddcfm-note-0306-01.pdf |
| 08 Aug 2006 | Presentation new-seaman-ddcfm-draft-par-0606-01.htm |
| 20 Sep 2006 | Presentation new-dunbar-ddcfm-contrib-0906-01.pdf |
| 08 Mar 2007 | Presentation aw-dunbar-operation-of-ddcfm-0307.pdf |
| 11 Jun 2007 | Presentation aw-bhassink-ddcfm-security-0607-v01.doc |
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.
