1、IEEE Std 802.1ah-2008(Amendment toIEEE Std 802.1Q-2005)IEEE Standard forLocal and metropolitan area networksVirtual Bridged Local Area Networks Amendment 7: Provider Backbone BridgesIEEE3 Park Avenue New York, NY 10016-5997, USA14 August 2008IEEE Computer SocietySponsored by theLAN/MAN Standards Com
2、mittee802.1ahTMIEEE Std 802.1ah-2008(Amendment to IEEE Std 802.1Q-2005)IEEE Standard for Local and metropolitan area networksVirtual Bridged Local Area NetworksAmendment 7: Provider Backbone BridgesSponsorLAN/MAN Standards Committeeof theIEEE Computer SocietyApproved 12 June 2008IEEE-SA Standards Bo
3、ardAbstract: This amendment defines an architecture and bridge protocols for interconnection ofmultiple Provider Bridged Networks, allowing a Provider to support up to 224service instances.Keywords: Bridged Local Area Networks, LANs, local area networks, MAC Bridges, MANs,metropolitan area networks,
4、 MRP, MSTP, Multiple Registration Protocol, Multiple Spanning TreeProtocol, Multiple VLAN Registration Protocol, MVRP, Provider Bridged Local Area Networks,Virtual Bridged Local Area Networks, virtual LANsThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-59
5、97, USACopyright 2008 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 14 August 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 ofany individual stan
6、dard for educational classroom use can also be obtained through the Copyright ClearanceCenter.iv Copyright 2008 IEEE. All rights reserved.IntroductionNotice to usersLaws and regulationsUsers of these documents should consult all applicable laws and regulations. Compliance with theprovisions of this
7、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 action that is not incompliance with appli
8、cable 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 in private self-regulation,standardizat
9、ion, 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 standards should be aware that these doc
10、uments 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 together with any amendments, corrigenda, or
11、 errata then in effect. In order to determine whethera given document is the current edition and whether it has been amended through the issuance ofamendments, corrigenda, or errata, visit the IEEE Standards Association website athttp:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at th
12、e 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.ErrataErrata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/
13、reading/ieee/updates/errata/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.This introduction is not part of IEEE Std 802.1ah-2008, IEEE Stan
14、dards for Local and Metropolitan Area Net-worksVirtual Bridged Local Area NetworksAmendment 7: Provider Backbone Bridges.Copyright 2008 IEEE. All rights reserved. vPatentsAttention is called to the possibility that implementation of this amendment may require use of subjectmatter covered by patent r
15、ights. By publication of this amendment, no position is taken with respect to theexistence or validity 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 validit
16、yor scope of Patents Claims or determining whether any licensing terms or conditions provided in connectionwith 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 va
17、lidity of anypatent rights, and the risk of infringement of such rights, is entirely their own responsibility. Furtherinformation may be obtained from the IEEE Standards Association.ParticipantsAt the time this amendment was submitted, the IEEE 802.1 Working Group had the following membership: Tony
18、Jeffree, ChairPaul Congdon, Vice ChairStephen Haddock, Chair, Interworking Task GroupPaul Bottorff, Stephen Haddock, and Muneyoshi Suzuki, EditorsOsama Aboul-MagdZehavit AlonCaitlin BestlerJan BialkowskiRob BoatrightJean-Michel BonnamyRudolf BrandnerCraig W. CarlsonFrank ChaoRao CherukuriTaesik Cheu
19、ngAlex ContaDiego CrupnicoffClaudio DesantiLinda DunbarHesham ElbakouryDavid Elie-Dit-CosaqueJanos FarkasDon FedykFelix Feifei FengNorm FinnBob FrazierJohn FullerGeoffrey GarnerAnoop GhanwaniFranz GoetzEric GrayKen GrewalCraig GuntherMitch GusatBrian HassinkBrian HausauerAsif HazarikaRomain Insler P
20、aul Hongkyu JeongMichael Johas TeenerPrakash KashyapHal KeenKeti KilcreaseYongbum KimPhilippe KleinMike KoRaghu KondapalliBruce KwanKari LaihonenYannick Le GoffGael MaceBen Mack-CraneDavid MartinRiccardo MartinottiMarco MascittoAlan McGuireMenucher MenucheryJohn MessengerDinesh MohanKevin NolishHiro
21、shi OhtaDavid OlsenShlomo OvadiaDon PannellGlenn ParsonsKen PattonJoe PelissierHayim PoratMax PritikinAnanda RajagopalKaren RandallRobert RodenGuenter RoeckJosef RoeseDan RomascanuMoran RothJessy V. RouyerAli SajassiJoseph SaloweyPanagiotis SaltsidisSatish SatheJohn SauerMick SeamanKoichiro SetoHima
22、nshu ShahRavi ShenoyNurit SprecherKevin B. StantonBob SultanGeorge SwallowAttila TakacsFrancois TalletJohn TerryPat ThalerOliver ThorpFred Tuck Maarten VissersManoj WadekarYan WangBrian Weis Bert WijnenLudwig WinkelMichael D. WrightChien-Hsien WuKen Young vi Copyright 2008 IEEE. All rights reserved.
23、The following 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 12 June 2008, it had the followingmembership:Robert M. Grow, ChairThomas Prevost, Vice Chai
24、rSteve M. Mills, Past ChairJudith Gorman, Secretary*Member EmeritusAlso included are the following nonvoting IEEE-SA Standards Board liaisons:Satish K. Aggarwal, NRC RepresentativeMichael H. Kelly, NIST RepresentativeDon MessinaIEEE Standards Program Manager, Document DevelopmentMichael D. KipnessIE
25、EE Standards Program Manager, Technical Program DevelopmentOsama Aboul-Magd Toru Aihara Butch Anton Danilo Antonelli Hugh Barrass Parag Bhatt Tomo Bogataj Paul Bottorff Michael Bouchet James Carlo Juan Carreon Keith Chow Charles Cook Arjan De Heer Russell Dietz Sourav Dutta Don Fedyk Prince Francis
26、Yukihiro Fujimoto Devon Gayle Sergiu Goma C. GuyStephen Haddock John Hawkins Atsushi Ito Raj Jain Tony Jeffree Piotr Karocki Stuart J. Kerry Yongbum Kim Thomas Kurihara John Lemon William Lumpkins Thomas Mack-Crane David MartinJonathon Mclendon John Messenger Gary Michel Dinesh Mohan Jose MoralesMic
27、hael S. Newman Nick S. A. Nikjoo Glenn Parsons Haim Porat Venkatesha Prasad Maximilian Riegel Jessy V. Rouyer Randall Safier John Sargent John Sauer Veselin Skendzic Kapil Sood Amjad Soomro Nurit Sprecher Manikantan Srinivasan Thomas Starai Marian Stasney Alourdes Sully Bob Sultan Michael Johas Teen
28、er Pat Thaler Oliver Thorp Thomas Tullia Mark-Rene Uchida Ludwig Winkel Derek Woo Ken Young Oren YuenVictor BermanRichard DeBlasioAndy DrozdMark EpsteinAlexander GelmanWilliam R. GoldbachArnold M. GreenspanKenneth S. HanusJim HughesRichard H. HulettYoung Kyun KimJoseph L. Koepfinger*John KulickDavid
29、 J. LawGlenn ParsonsRonald C. PetersenChuck PowersNarayanan RamachandranJon Walter RosdahlRobby RobsonAnne-Marie SahaziziaMalcolm V. ThadenHoward L. WolfmanDon WrightCopyright 2008 IEEE. All rights reserved. viiContents1. Overview 21.1 Scope 22. Normative references. 33. Definitions . 54. Abbreviati
30、ons. 75. Conformance 95.2 Conformant components and equipment . 95.3 Protocol Implementation Conformance Statement (PICS) 95.7 I-component conformance . 95.8 B-component conformance 105.11 Backbone Edge Bridge conformance 116. Support of the MAC Service in VLANs 136.6 Internal Sublayer Service. 136.
31、8 Enhanced Internal Sublayer Service 156.9 Support of the EISS . 176.10 Support of the EISS by Provider Instance Ports 176.11 Support of the EISS by Customer Backbone Ports 206.18 Backbone Service Instance Multiplex Entity. 247. Principles of network operation. 297.4 Locating end stations . 298. Pri
32、nciples of bridge operation 318.8 The Filtering Database. 319. Tagged frame format . 339.5 Tag Protocol Identification 339.8 Backbone Service Instance Tag Control Information 3412. Bridge management . 3712.2 Managed objectsVLAN-aware bridge objects. 3712.3 Data types 3712.7 Filtering Database 3712.8
33、 Bridge Protocol Entity . 3812.14 CFM entities 3912.15 Backbone Core Bridge management . 4312.16 Backbone Edge Bridge management. 4313. The Multiple Spanning Tree Protocol (MSTP) . 5913.12 Port Role assignments 5913.19 Multiple Spanning Tree state machines. 5913.21 State machine timers 6113.25 State
34、 machine conditions and parameters 61viii Copyright 2008 IEEE. All rights reserved.13.26 State machine procedures 6213.27 The Port Timers state machine 6313.28 Port Receive state machine 6313.31 Port Transmit state machine 6313.32 Port Information state machine 6413.37 Port Receive Pseudo Informatio
35、n state machine . 6513.40 Virtual Instance Port Spanning Tree operation 6718. Principles of Connectivity Fault Management operation 6919. CFM Entity operation 7119.4 Maintenance Point addressing . 7120. Connectivity Fault Management protocols 7325. Support of the MAC Service by Provider Backbone Bri
36、dged Networks 7525.1 Service transparency 7725.2 Customer service interface. 7725.3 Port-based service interface . 7725.4 S-tagged service interface 7925.5 I-tagged service interface. 8225.6 Service instance segregation 8425.7 Service instance selection and identification . 8425.8 Service priority a
37、nd drop eligibility selection 8425.9 Service access protection . 8526. Principles of Provider Backbone Bridged Network operation 8926.1 Provider Backbone Bridged Network overview 8926.2 Provider Backbone Bridged Network example . 9026.3 Backbone VLAN connectivity. 9226.4 Backbone addressing . 9326.5
38、 Detection of connectivity loops through attached networks 9526.6 Scaling of Provider Backbone Bridges 9626.7 Network Management 9626.8 Connectivity Fault Management in Provider Backbone Bridges 97Annex A (normative) PICS proforma 105Annex B (informative) Shared and independent VLAN learning . 109Co
39、pyright 2008 IEEE. All rights reserved. ixFiguresFigure 6-2 I-Component Provider Instance Port 18Figure 6-3 B-Component Customer Backbone Port 21Figure 6-6 Two back-to-back Backbone Service Instance Multiplex Entities 24Figure 6-7 Backbone Service Instance Multiplex Entities with example CFM shims 2
40、5Figure 9-3 I-TAG TCI Format. 34Figure 12-1 Relationship among BEB managed objects. 44Figure 13-9 MSTP state machinesoverview and relationships 60Figure 13-11 Port Timers state machine 63Figure 13-13 Port Transmit state machine. 64Figure 13-14 Port Information state machine 65Figure 13-23 Port Recei
41、ve Pseudo Information state machine 66Figure 25-1 Internal organization of the MAC sublayer in a PBBN . 75Figure 25-2 Provider Backbone Bridge terminology 76Figure 25-3 Customer service interface types . 77Figure 25-4 Port-based service interface . 78Figure 25-5 Port-based interface equipment 79Figu
42、re 25-6 Encapsulated service frames at ISS . 80Figure 25-7 S-tagged service interface 81Figure 25-8 S-tagged service interface equipment 81Figure 25-9 I-tagged service interface . 83Figure 25-10 I-tagged service interface equipment . 83Figure 25-11 S-tagged and Port-based service interface access cl
43、assifications 86Figure 25-12 I-tagged service interface access protection classifications. 87Figure 26-1 PBBN example. 91Figure 26-2 CFM Shim Model 98Figure 26-3 CFM example applied to a Port-based and S-tagged Service Interface. 100Figure 26-4 CFM example applied to an I-tagged Service Interface 10
44、1Figure 26-5 CFM example applied to a hierarchal E-NNI, CBP-PIP Demarc 103Figure 26-6 CFM example applied to a peer E-NNI, CBP-PIP. 104x Copyright 2008 IEEE. All rights reserved.TablesTable 6-7 Encapsulated Addresses type 25Table 9-1 IEEE 802.1Q Ethernet Type allocations. 34Table 9-3 Reserved I-SID
45、values 35Table 26-1 Backbone Service Instance Group address OUI. 93Copyright 2008 IEEE. All rights reserved. 1IEEE Standard for Local and metropolitan area networksVirtual Bridged Local Area NetworksAmendment 7: Provider Backbone BridgesIMPORTANT NOTICE: This standard is not intended to assure safet
46、y, security, health, or environmentalprotection in all circumstances. Implementers of the standard are responsible for determiningappropriate safety, security, environmental, and health practices or regulatory requirements.This IEEE document is made available for use subject to important notices and
47、 legal disclaimers. Thesenotices and disclaimers appear in all publications containing this document and may be found under theheading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.”They can also be obtained on request from IEEE or viewed at http:/standards.ieee.
48、org/IPR/disclaimers.html.This amendment is based on IEEE Std 802.1QTM-2005.Editorial NoteThis amendment specifies changes to IEEE Std 802.1Q-2005, as amended by IEEE Std 802.1adTM-2005,IEEE Std 802.1akTM-2007 and IEEE Std 802.1agTM-2007, that enable a provider to scale a Provider BridgedNetwork by i
49、nterconnecting many Provider Bridged Networks over a Provider Backbone Bridged Network.The resulting backbone network can support interconnection of up to 224equivalent of separate LANs,Bridged Local Area Networks, or Virtual Bridged Local Area Networks. Changes are applied to the basetext of IEEE Std 802.1Q-2005 as amended by IEEE Std 802.1ad-2005, IEEE Std 802.1ak-2007, and IEEEStd 802.1ag-2007. Text shown in bold italics in this amendment defines the editing instructions for changesto this base text. Three editing instructions are used: change, del