1、IEEE Std 802.1Qaw-200g28(Amendment toIEEE Std 802.1Q-2005)IEEE Standard forLocal and metropolitan area networksVirtual Bridged Local Area NetworksAmendment 9: Management of DataDriven and Data DependentConnectivity FaultsIEEE3 Park AvenueNew York, NY 10016-5997, USA25 July 2009IEEE Computer SocietyS
2、ponsored by theLAN/MAN Standards Committee802.1QawTMIEEE Std 802.1Qaw-2009(Amendment to IEEE Std 802.1Q-2005)IEEE Standard for Local and metropolitan area networksVirtual Bridged Local Area NetworksAmendment 9: Management of Data Driven and Data Dependent Connectivity FaultsSponsorLAN/MAN Standards
3、Committeeof theIEEE Computer SocietyApproved 17 June 2009IEEE-SA Standards BoardAbstract: This amendment extends the connectivity fault management capabilities introduced inIEEE Std 802.1ag-2007 to include tools to facilitate diagnosis and isolation of faults sensitive to, orcaused by, particular da
4、ta patterns in frames transmitted by a service user.Keywords: fault management, LANs, local area networks, MAC Bridges, MANs, metropolitan areanetworks, OAM, transparent bridging, VLANSThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 200
5、9 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 25 July 2009. Printed in the United States of America.IEEE and 802 are registered trademarks in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard foreducationalcl
6、assroom use can also be obtained through the Copyright Clearance Center.iv Copyright 2009 IEEE. All rights reserved.IntroductionIEEE Std 802.1Qaw provides additional capability to Connectivity Fault Management (Clause 18 throughClause 22) to achieve data driven and data dependent connectivity fault
7、management.Notice to usersLaws and regulationsUsers of these documents should consult all applicable laws and regulations. Compliance with theprovisions of this standard does not imply compliance to any applicable regulatory requirements.Implementers of the standard are responsible for observing or
8、referring to the applicable regulatoryrequirements. IEEE does not, by the publication of its standards, intend to urge action that is not incompliance with applicable laws, and these documents may not be construed as doing so. CopyrightsThis document is copyrighted by the IEEE. It is made available
9、for a wide variety of both public and privateuses. These include both use, by reference, in laws and regulations, and use in private self-regulation,standardization, and the promotion of engineering practices and methods. By making this documentavailable for use and adoption by public authorities an
10、d private users, the IEEE does not waive any rights incopyright to this document.Updating of IEEE documentsUsers of IEEE standards should be aware that these documents may be superseded at any time by theissuance of new editions or may be amended from time to time through the issuance of amendments,
11、corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of thedocument together with any amendments, corrigenda, or errata then in effect. In order to determine whethera given document is the current edition and whether it has been amended through the is
12、suance ofamendments, corrigenda, or errata, visit the IEEE Standards Association website athttp:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously.For more information about the IEEE Standards Association or the IEEE standards development process,visit the I
13、EEE-SA website at http:/standards.ieee.org.ErrataErrata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL forerrata periodically.This introduction is not part of IEEE
14、 Std 802.1Qaw-2009, IEEE Standards for Local and Metropolitan AreaNetworksVirtual Bridged Local Area NetworksAmendment 9: Management of Data Driven and Data DependentConnectivity Faults.Copyright 2009 IEEE. All rights reserved. vInterpretationsCurrent interpretations can be accessed at the following
15、 URL: http:/standards.ieee.org/reading/ieee/interp/index.html.PatentsAttention is called to the possibility that implementation of this amendment may require use of subjectmatter covered by patent rights. By publication of this amendment, no position is taken with respect to theexistence or validity
16、 of any patent rights in connection therewith. The IEEE is not responsible for identifyingEssential Patent Claims for which a license may be required, for conducting inquiries into the legal validityor scope of Patents Claims or determining whether any licensing terms or conditions provided in conne
17、ctionwith submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this amendment are expressly advised that determination of the validity of anypatent rights, and the risk of infringement of such rights, is entirely their own respons
18、ibility. Furtherinformation may be obtained from the IEEE Standards Association.vi Copyright 2009 IEEE. All rights reserved.ParticipantsAt the time this amendment was submitted to the IEEE-SA Standards Board for approval, the IEEE 802.1Working Group had the following membership: Tony Jeffree, Chair
19、Paul Congdon, Vice ChairStephen Haddock, Chair, Interworking Task GroupLinda Dunbar, EditorOsama Aboul-MagdZehavit AlonCaitlin BestlerJan BialkowskiRob BoatrightJean-Michel BonnamyPaul BottorffRudolf BrandnerCraig W. CarlsonWeiying ChengRao CherukuriDiego CrupnicoffClaudio DesantiZhemin DingHesham M
20、 ElbakouryDavid Elie-Dit-CosaqueJanos FarkasDonald FedykNorman FinnRobert FrazierJohn FullerGeoffrey GarnerAnoop GhanwaniFranz GoetzEric GrayKaranvir GrewalCraig GuntherMitch GusatAsif HazarikaCharles HudsonRomain InslerMichael Johas TeenerAbhay KarandikarPrakash KashyapHal KeenKeti KilcreaseYongbu
21、m KimPhilippe KleinMike KoVinod KumarBruce KwanKari LaihonenYannick Le GoffMichael LererGael MaceBen Mack-CraneDavid MartinRiccardo MartinottiAlan McGuireJames McIntoshMenucher MenucheryJohn MessengerMatthew MoraEric MultanenKevin NolishHiroshi OhtaDavid OlsenDonald PannellGlenn ParsonsJoseph Peliss
22、ierDavid PetersonHayim PoratMax PritikinAnanda RajagopalKaren RandallGuenter RoeckJosef RoeseDerek J. RohdeDan RomascanuMoran RothJessy V. RouyerHyunsurk RyuJonathan SadlerAli SajassiJoseph SaloweyPanagiotis SaltsidisSatish SatheJohn SauerMichael SeamanKoichiro SetoHimanshu ShahNurit SprecherKevin B
23、 StantonRobert A. SultanMuneyoshi SuzukiGeorge SwallowAttila TakacsPatricia ThalerOliver ThorpManoj WadekarYuehua WeiBrian Weis Bert WijnenMichael D. WrightChien-Hsien WuKen YoungGlen ZornCopyright 2009 IEEE. All rights reserved. viiThe following members of the individual balloting committee voted
24、on this standard. Balloters may havevoted for approval, disapproval, or abstention. When the IEEE-SA Standards Board approved this standard on 17 June 2009, it had the followingmembership:Robert M. Grow, ChairThomas Prevost, Vice ChairSteve M. Mills, Past ChairJudith Gorman, Secretary*Member Emeritu
25、sAlso included are the following nonvoting IEEE-SA Standards Board liaisons:Howard L. Wolfman, TAB RepresentativeMichael Janezic, NIST RepresentativeSatish Aggarwal, NRC RepresentativeMichelle D. TurnerIEEE Standards Program Manager, Document DevelopmentKathryn CushIEEE Standards Program Manager, Te
26、chnical Program DevelopmentThomas Alexander Butch Anton Danilo Antonelli Edward Carley James Carlo Juan Carreon Keith Chow Charles Cook Russell Dietz Thomas Dineen Linda Dunbar Sourav Dutta David Elie-Dit-Cosaque Donald Fedyk Yukihiro Fujimoto Devon Gayle Reinhard Gloger Sergiu Goma Randall Groves C
27、 Guy John Hawkins Atsushi Ito Raj Jain Tony Jeffree Shinkyo Kaku Piotr Karocki Stuart J. Kerry Yongbum Kim John Lemon Michael Lerer Li LiWilliam Lumpkins Ben Mack-Crane David Martin Jonathon Mclendon Richard Mellitz Gary Michel Wade Midkiff Michael S. Newman Nick S. A. Nikjoo Paul Nikolich Kevin No
28、lish Satoshi Obara Glenn Parsons Maximilian Riegel Robert Robinson Jessy V. Rouyer Randall Safier Behcet Sarikaya Bartien Sayogo Michael Seaman Kapil Sood Nurit Sprecher Thomas Starai Walter Struppler Robert A. Sultan William Taylor Michael Johas Teener Prabodh Varshney Maarten Vissers Oren Yuen Joh
29、n BarrKaren BartlesonVictor BermanTed BurseRichard DeBlasioAndy DrozdMark EpsteinAlexander GelmanJim HughesRichard H. HulettYoung Kyun KimJoseph L. Koepfinger*John KulickDavid J. LawTed OlsenGlenn ParsonsRonald C. PetersenNarayanan RamachandranJon Walter RosdahlSam SciaccaCopyright 2009 IEEE. All ri
30、ghts reserved. ixContents1. Overview 21.1 Scope 23. Definitions . 34. Abbreviations. 55. Conformance 712. Bridge management . 912.2 Managed objects 912.18 DDCFM entities. 915. Support of the MAC Service by Provider Bridged Networks . 2115.11 Data driven and data dependent connectivity fault manageme
31、nt (DDCFM) 2117. Management Information Base (MIB) 2317.2 Structure of the MIB 2317.2.9Structure of the IEEE8021-DDCFM MIBs . 2317.3.9Relationship of the IEEE8021-DDCFM to other MIB modules . 2517.4.9Security considerations of the IEEE8021-DDCFM MIB 2517.7.9Definitions for the DDCFM MIBs 2719. CFM E
32、ntity operation 4320. Connectivity Fault Management protocols 4721. Encoding of CFM Protocol Data Units 4929. DDCFM operations and protocols. 5129.1 Principles of DDCFM operation 5129.2 DDCFM Entity operation 5429.3 DDCFM protocols . 5929.4 Encoding of DDCFM Protocol Data Units 69Annex A (normative)
33、PICS proforma. 73A.5 Major capabilities . 73A.14 Bridge management . 73A.24 Management Information Base (MIB) 74A.27 Data driven and data dependent connectivity fault management 74Copyright 2009 IEEE. All rights reserved. xiList of figuresFigure 19-2 Maintenance association End Point (MEP) . 44Figur
34、e 19-3 MIP Half Function . 46Figure 29-1 Forward path test (FPT) . 52Figure 29-2 Return path test 53Figure 29-3 Combination of forward path test and return path test. 54Figure 29-4 Detailed Functions of Reflection Responder . 55Figure 29-5 RFM Receiver on an non-MP 58Figure 29-6 Return Path Decapsul
35、ator Responder 59Figure 29-7 RR Filter state machine 64Figure 29-8 RR Encapsulation state machine 65Figure 29-9 RR Transmit state machine 65Figure 29-10 RFM Receiver state machine . 67Figure 29-11 Decapsulator Responder state machine 69Copyright 2009 IEEE. All rights reserved. xiiiList of tablesTabl
36、e 17-1 Structure of the MIB modules. 23Table 17-14 IEEE8021-DDCFM MIB structure and relationship to this standard. 23Table 17-16 Sensitive managed objects (of DDCFM) for read. 26Table 17-15 Sensitive managed objects (of DDCFM): tables and notifications. 26Table 19-1 Actions taken by MP OpCode Demult
37、iplexers. 45Table 21-4 OpCode Field range assignments 49Table 21-6 Type Field values 49Table 29-1 RFM format. 70Table 29-2 SFM format . 71Copyright 2009 IEEE. All rights reserved. 1IEEE Standard for Local and metropolitan area networksVirtual Bridged Local Area NetworksAmendment 9: Management of Dat
38、a Driven and Data Dependent Connectivity FaultsIMPORTANT NOTICE: This standard is not intended to ensure safety, security, health, orenvironmental protection in all circumstances. Implementers of the standard are responsible fordetermining appropriate safety, security, environmental, and health prac
39、tices or regulatory requirements.This IEEE document is made available for use subject to important notices and legal disclaimers. Thesenotices and disclaimers appear in all publications containing this document and may be found under theheading “Important Notice” or “Important Notices and Disclaimer
40、s Concerning IEEE Documents.”They can also be obtained on request from IEEE or viewed at http:/standards.ieee.org/IPR/disclaimers.html.Editorial NoteThis amendment specifies changes to be applied to the base text of IEEE Std 802.1Q-2005 as amended byIEEE Std 802.1adTM-2005, IEEE Std 802.1agTM-2007,
41、IEEE802.1akTM-2007, IEEE Std 802.1ahTM-2008, andIEEE Std 802.1apTM-2008. Text shown in bold italics in this amendment defines the editing instructionsnecessary to changes to this base text. Three editing instructions are used: change, delete, and insert.Change is used to make a change to existing ma
42、terial. The editing instruction specifies the location of thechange and describes what is being changed. Changes to existing text may be clarified using strikeoutmarkings to indicate removal of old material, and underscore markings to indicate addition of new material).Delete removes existing materi
43、al. Insert adds new material without changing the existing material.Insertions may require renumbering. If so, renumbering instructions are given in the editing instruction.Editorial notes will not be carried over into future editions of IEEE Std 802.1Q.IEEE IEEE STANDARD FOR LOCAL AND METROPOLITAN
44、AREA NETWORKSStd 802.1Qaw-20092 Copyright 2009 IEEE. All rights reserved.1. OverviewInsert the following after the initial paragraphs of Clause 1:The data driven and data dependent connectivity fault management capabilities include tools to facilitatediagnosis and isolation of faults sensitive to, o
45、r caused by, particular data patterns in transmitted frames.1.1 ScopeInsert the following at end of subclause 1.1, relettering the bullet points so that they follow in order fromthose in the existing text.This standard specifies connectivity fault management protocols, procedures, and managed object
46、s thatprovide confirmation of successful transmission of frames conveying specified data. This capabilitysupports diagnosis of faults sensitive to, or caused by, particular data patterns, and their isolation to part ofthe transmission path. Connectivity verification can be carried out from any singl
47、e point with bridgedconnectivity to maintenance points on the 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. To this end ita) Defines the extensions to connectivity fault management capabilitie
48、s defined by Clause 18 throughClause 22 to facilitate diagnosis and isolation of faults sensitive to, or caused by, particular datapatterns in frames transmitted by a service user;b) Describes the protocols and procedures for data driven and data dependent connectivity faultmanagement (DDCFM).AMENDM
49、ENT 9: MANAGEMENT OF DATA DRIVEN AND DATA DEPENDENT CONNECTIVITY FAULTS IEEEStd 802.1Qaw-2009Copyright 2009 IEEE. All rights reserved. 33. DefinitionsInsert the following definitions, renumbering to place them in the appropriate collating order.3.1 data driven and data dependent connectivity fault management (DDCFM): DDCFM comprisescapabilities to facilitate detecting and isolating data driven and data dependent faults in Virtual BridgedLocal Area Networks.3.2 data driven and data dependent fault (DDF): A fault that is sensitive to, or caused by, partic
