1、IEEE Std 802.1Q-2005/Cor 1-2008(Corrigendum to IEEE Std 802.1Q-2005) IEEE Standard forLocal and metropolitan area networks Virtual Bridged Local Area NetworksCorrigendum 1: Corrections to the Multiple Registration ProtocolIEEE3 Park Avenue New York, NY 10016-5997, USA15 October 2008IEEE Computer Soc
2、ietySponsored by theLAN/MAN Standards Committee802.1QTM-2005/Cor1-2008IEEE Std 802.1Q-2005/Cor 1-2008(Corrigendum toIEEE Std 802.1Q-2005)IEEE Standard forLocal and metropolitan area networksVirtual Bridged Local Area NetworksCorrigendum 1: Corrections to the Multiple Registration ProtocolSponsorLAN/
3、MAN Standards Committeeof theIEEE Computer SocietyApproved 26 September 2008IEEE-SA Standards BoardThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2008 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. P
4、ublished 15 October 2008. 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 foreducational classroom use can also be obtained through the Copyright Clearance Center.ivCopyrigh
5、t 2008 IEEE. All rights reserved.IntroductionThis standard contains state-of-the-art material. The area covered by this standard is undergoing evolution.Revisions are anticipated within the next few years to clarify existing material, to correct possible errors, andto incorporate new related materia
6、l. Information on the current revision state of this and other IEEE 802standards may be obtained fromSecretary, IEEE-SA Standards Board445 Hoes LaneP.O. Box 1331Piscataway, NJ 08855-1331USANotice to usersLaws and regulationsUsers of these documents should consult all applicable laws and regulations.
7、 Compliance with theprovisions of this standard does not imply compliance to any applicable regulatory requirements.Implementers of the standard are responsible for observing or referring to the applicable regulatoryrequirements. IEEE does not, by the publication of its standards, intend to urge act
8、ion 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 for a wide variety of both public and privateuses. These include both use, by reference, in laws and regulations, and use
9、in private self-regulation,standardization, and the promotion of engineering practices and methods. By making this documentavailable for use and adoption by public authorities and private users, the IEEE does not waive any rights incopyright to this document.Updating of IEEE documentsUsers of IEEE s
10、tandards 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,corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of thedocument toget
11、her 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 issuanceof amendments, corrigenda, or errata, visit the IEEE Standards Association website at http:/ieeexplore.ieee.org/xpl/
12、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 IEEE-SA website at http:/standards.ieee.org.This introduction is not part of P802.1Q-2005/Cor 1-2008, IEEE Standards for L
13、ocal and metropolitan areanetworksVirtual Bridged Local Area Networks Corrigendum 1: Multiple Registration Protocol.vCopyright 2008 IEEE. All rights reserved.ErrataErrata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/updates/err
14、ata/index.html. Users are encouraged to check this URL forerrata periodically.InterpretationsCurrent interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/index.html.PatentsAttention is called to the possibility that implementation of this standard may re
15、quire use of subject mattercovered by patent rights. By publication of this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith. A patent holder or patent applicant has filed a statementof assurance that it will grant licenses under th
16、ese rights without compensation or under reasonable rates,with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicantsdesiring to obtain such licenses. Other Essential Patent Claims may exist for which a statement of assurancehas not been received. The I
17、EEE is not responsible for identifying Essential Patent Claims for which alicense may be required, for conducting inquiries into the legal validity or scope of Patents Claims, ordetermining whether any licensing terms or conditions are reasonable or non-discriminatory. Furtherinformation may be obta
18、ined from the IEEE Standards Association.ParticipantsAt the time this corrigendum was submitted to the IEEE-SA Standards Board for approval, the IEEE 802.1Working Group had the following membership:Anthony Jeffree, ChairPaul Congdon, Vice-ChairStephen Haddock, Vice-ChairOsama Aboul-MagdZehavit AlonC
19、aitlin BestlerJan BialkowskiRob BoatrightJean-Michel BonnamyPaul BottorffRudolf BrandnerCraig CarlsonFrank ChaoRao CherukuriTaesik CheungAlex ContaDiego Crupnicoff Claudio DesantiLinda DunbarHesham ElbakouryDavid Elie-Dit-CosaqueJanos FarkasDonald FedykFeifei Feng FelixNorman FinnRobert FrazierJohn
20、FullerGeoffrey GarnerAnoop GhanwaniFranz GoetzYannick GoffEric GrayKaranvir GrewalCraig GuntherMitch GusatBrian HausauerAsif HazarikaRomain InslerAbhay KarandikarPrakash KashyapHal KeenKeti KilcreaseYongbum KimPhilippe KleinMike KoRaghu KondapalliBruce KwanKari LaihonenGael MaceThomas Mack-CraneDavi
21、d MartinRiccardo MartinottiMarco MascittoAlan McGuireMenucher MenucheryJohn MessengerDinesh MohanMatthew MoraKevin NolishHiroshi OhtaDavid OlsenDon PannellGlenn ParsonsKen PattonJoseph PelissierDavid PetersonHayim PoratMax PritkinAnanda RajagopelviCopyright 2008 IEEE. All rights reserved.The followi
22、ng members of the individual balloting committee voted on this standard. Balloters may havevoted for approval, disapproval, or abstention. When the IEEE-SA Standards Board approved this standard on 26 September 2008, it had the followingmembership:Robert M. Grow, ChairThomas Prevost, Vice ChairSteve
23、 M. Mills, Past ChairJudith Gorman, Secretary*Member EmeritusKaren RandallRobert RodenGuenter RoeckJosef RoeseDan RomascanuMoran RothJessy V. RouyerAli SajassiJoseph SaloweyPanagiotis SaltsidisSatish SatheJohn SauerMichael SeamanKoichiro SetoHimanshu ShahRavi ShenoyNurit SprecherKevin StantonRobert
24、Sultan Muneyoshi SuzukiGeorge SwallowAttila TakacsFrancois TalletMichael Johas TeenerJohn TerryPatricia ThalerOliver ThorpFred TuckMaarten VissersManoj WadekarYan WangBrian WeisWijnen BertLudwig WinkelMichael D. WrightChien-Hsien WuKen YoungGlen ZornButch AntonParag BhattMichael BouchetJames CarloJu
25、an CarreonClint ChaplinKeith ChowCharles CookArjan De HeerCarlo DonatiDonald FedykRobert FrazierYukihiro FujimotoJohn FullerDevon GayleMichael GeipelRandall GrovesC. GuyStephen HaddockJohn HawkinsAtsushi ItoRaj Jain Anthony JeffreeShinkyo KakuPiotr KarockiJuan L. LazaroMichael LererShen LohThomas Ma
26、ck-CraneJonathon MclendonJohn MessengerGary MichelDinesh MohanMichael S. NewmanKevin NolishSatoshi ObaraMaximilian RiegelJessy V. RouyerRandall SafierBartien SayogoMichael SeamanKapil SoodWalter StrupplerAlourdes SullyRobert SultanJoseph TardoMichael Johas TeenerPrabodh VarshneyMichael D. WrightOren
27、 YuenWenhao ZhuVictor BermanRichard DeBlasioAndy DrozdMark EpsteinAlexander GelmanWilliam R. GoldbachArnold M. GreenspanKenneth S. HanusJim HughesRichard H. HulettYoung Kyun KimJoseph L. Koepfinger*John KulickDavid J. LawGlenn ParsonsRonald C. PetersenChuck PowersNarayanan RamachandranJon Walter Ros
28、dahlRobby RobsonAnne-Marie SahazizianMalcolm V. ThadenHoward L. WolfmanDon WrightviiCopyright 2008 IEEE. All rights reserved.Also included are the following nonvoting IEEE-SA Standards Board liaisons:Satish K. Aggarwal, NRC RepresentativeMichael H. Kelly, NIST RepresentativeMichelle TurnerIEEE Stand
29、ards Program Manager, Document DevelopmentKathryn CushIEEE Standards Program Manager, Technical Program DevelopmentviiiCopyright 2008 IEEE. All rights reserved.CONTENTS10. Multiple Registration Protocol (MRP) and Multiple MAC Registration Protocol (MMRP) 210.8 Structure and encoding of MRP Protocol
30、Data Units 210.8.1 Structure. 210.8.1.2 Structure definition 210.8.2 Encoding of MRPDU parameters 310.8.2.2 Encoding of AttributeType 310.8.2.3 Encoding of AttributeLength. 410.8.2.4 Encoding of AttributeEvent . 410.8.2.5 Encoding of LeaveAllEvent. 410.8.2.6 Encoding of FirstValue 410.8.2.7 Encoding
31、 of VectorHeader 510.8.2.8 Encoding of EndMark 510.8.2.9 Encoding of Vector 510.12 Definition of the MMRP application .610.12.1 Definition of MRP protocol elements. 610.12.1.8 MMRP AttributeLength definitions 611. VLAN topology management 611.2 Multiple VLAN Registration Protocol 611.2.3 Definition
32、of the MVRP application 611.2.3.1 Definition of MRP protocol elements 611.2.3.1.8 MVRP AttributeLength definitions 61Copyright 2008 IEEE. All rights reserved.IEEE Standard forLocal and metropolitan area networksVirtual Bridged Local Area NetworksCorrigendum 1: Corrections to the Multiple Registratio
33、n ProtocolIMPORTANT NOTICE: This standard is not intended to assure safety, security, health, or environmental protectionin all circumstances. Implementers of the standard are responsible for determining appropriate safety, security,environmental, and health practices or regulatory requirements.This
34、 IEEE document is made available for use subject to important notices and legal disclaimers. These notices anddisclaimers appear in all publications containing this document and may be found under the heading “ImportantNotice” or “Important Notices and Disclaimers Concerning IEEE Documents.” They ca
35、n also be obtained on requestfrom IEEE or viewed at http:/standards.ieee.org/IPR/disclaimers.html.NOTEThis corrigendum specifies corrections to the MRP protocol specification introduced by IEEE Std 802.1ak-2007 Amendment 7 to IEEE Std 802.1Q-2005. The editing instructions contained in this corrigend
36、um define how tomerge the material contained herein into the existing base standard and its amendments to form the comprehensivestandard.1The editing instructions are shown in bold italic. Three editing instructions are used: change, delete, and insert. Changeis used to make corrections in existing
37、material. The editing instruction specifies the location of the change and describeswhat is being changed by using strikethrough (to remove old material) and underscore (to add new material). Deleteremoves existing material. Insert adds new material without disturbing the existing material. Insertio
38、ns may requirerenumbering. If so, renumbering instructions are given in the editing instructions. Editorial notes will not be carried overinto future editions because the changes will be incorporated into the base standard.1Notes in text, tables, and figures are given for information only, and do no
39、t contain requirements needed to implement the standard.IEEE Std 802.1Q-2005/Cor 1-2008Virtual Bridged Local Area NetworksCorrigendum 1: Corrections to the Multiple Registration Protocol2Copyright 2008 IEEE. All rights reserved.10. Multiple Registration Protocol (MRP) and Multiple MAC Registration P
40、ro-tocol (MMRP)10.8 Structure and encoding of MRP Protocol Data Units10.8.1 Structure10.8.1.2 Structure definitionChange the text of 10.8.1.2, and Figure 10-5, as shown:MRP makes use of an EtherType value as the means of identifying the MRP application that has transmitted,and that will receive, a g
41、iven MRPDU. Table 10-2 lists the set of MRP applications that are defined, and theEtherType values that correspond to them. A protocol version field is included in the structure of the MRPDU, in order to provide the ability to identifyfuture enhancements to MRP applications.MRPDUs exchanged accordin
42、g to the protocol specified in this clause shall have the following structure:a) The first octet contains the ProtocolVersion.b) Following the Protocol Version are one or more Messages. The last element in the PDU is anEndMark.c) Each Message consists of an AttributeType, an AttributeLength, and an
43、AttributeList, in that order.d) An Attribute List consists of one or more VectorAttributes. The last element in the AttributeList is anEndMark.e) A VectorAttribute consists of a VectorHeader, a FirstValue, and a Vector, in that order. TheVectorHeader is able to encode both a LeaveAllEvent and the nu
44、mber of attribute events encoded inthe vector.f) If the end of an MRPDU is encountered before an EndMark is reached, then processing of the PDUis terminated as if an EndMark had been reached.The following BNF productions give the formal description of the MRPDU structure:MRPDU := ProtocolVersion, Me
45、ssage , Message, EndMarkProtocolVersion BYTE := Defined by the specific MRP applicationMessage := AttributeType, AttributeLength, AttributeListAttributeType BYTE := Non-zero integer defined by the specific MRP applicationAttributeLength BYTE := Non-zero integer defined by the specific MRP applicatio
46、nAttributeList := VectorAttribute , VectorAttribute, EndMarkVectorAttribute := VectorHeader, FirstValue, VectorVectorHeader SHORT := (LeaveAllEvent * 8192) + NumberOfValuesFirstValue := Defined by the specific MRP applicationVector := ThreePackedEvents , ThreePackedEventsThreePackedEvents BYTE := (A
47、ttributeEvent) *6) + AttributeEvent) *6) + AttributeEvent)AttributeEvent BYTE := New | JoinIn | In | JoinMt | Mt | LvLeaveAllEvent BYTE := NullLeaveAllEvent | LeaveAllNumberOfValues SHORT := Number of events encoded in the vectorEndMark BYTE SHORT := 0x0000 | End of PDUNullLeaveAllEvent := 0LeaveAll
48、 := 1New := 0IEEE Std 802.1Q-2005/Cor 1-2008Virtual Bridged Local Area NetworksCorrigendum 1: Corrections to the Multiple Registration Protocol3Copyright 2008 IEEE. All rights reserved.JoinIn := 1In := 2JoinMt := 3Mt := 4Lv := 5The parameters carried in MRPDUs, as identified in this structure defini
49、tion, shall be encoded as specified in10.8.2.Figure 5 illustrates the structure of the MRPDU and its components.10.8.2 Encoding of MRPDU parameters10.8.2.2 Encoding of AttributeTypeChange the text of 10.8.2.2 as shown:An AttributeType shall be encoded as a single octet, taken to represent an unsigned binary number. TheAttributeType identifies the type of Attribute to which the message applies. The range of values that can betaken by the AttributeType, and the meanings of those values, are defined by the application concerned. Thev
