IEEE 802 1QCA-2015 en Local and metropolitan area networks-Bridges and Bridged Networks Amendment 24 Path Control and Reservation (IEEE Computer Society)《局域网和城域.pdf

1、 IEEE Standard for Local and metropolitan area networks Bridges and Bridged Networks Amendment 24: Path Control and Reservation Sponsored by the LAN/MAN Standards Committee IEEE 3 Park Avenue New York, NY 10016-5997 USA IEEE Computer Society IEEE Std 802.1Qca-2015 (Amendment to IEEE Std 802.1Q-2014

2、as amended by IEEE Std 802.1Qcd-2015 and IEEE Std 802.1Q-2014/Cor 1-2015) IEEE Std 802.1Qca-2015(Amendment toIEEE Std 802.1Q-2014as amended byIEEE Std 802.1Qcd-2015 andIEEE Std 802.1Q-2014/Cor 1-2015)IEEE Standard for Local and metropolitan area networksBridges and Bridged NetworksAmendment 24: Path

3、 Control and ReservationSponsorLAN/MAN Standards Committee of the IEEE Computer SocietyApproved 3 September 2015IEEE-SA Standards BoardThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2016 by The Institute of Electrical and Electronics E

4、ngineers, Inc.All rights reserved. Published 11 March 2016. Printed in the United States of America.IEEE and IEEE 802 are registered trademarks in the U.S. Patent fitnessfor a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness ofmaterial. In additio

5、n, IEEE disclaims any and all conditions relating to: results; and workmanlike effort.IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.”Use of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that thereare no other ways to produce, test, measur

6、e, purchase, market, or provide other goods and services related tothe scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved andissued is subject to change brought about through developments in the state of the art and commentsreceived from users of the

7、standard. In publishing and making its standards available, IEEE is not suggesting or rendering professional or otherservices for, or on behalf of, any person or entity nor is IEEE undertaking to perform any duty owed by anyother person or entity to another. Any person utilizing any IEEE Standards d

8、ocument, should rely upon hisor her own independent judgment in the exercise of reasonable care in any given circumstances or, asappropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEEstandard.IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRE

9、CT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO:PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGL

10、IGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPONANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE ANDREGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.Translations The IEEE consensus development process involves the review of documents in English

11、only. In the eventthat an IEEE standard is translated, only the English version published by IEEE should be considered theapproved IEEE standard.Official statements A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards BoardOperations Manual shall not be consid

12、ered or inferred to be the official position of IEEE or any of itscommittees and shall not be considered to be, or be relied on as, a formal position of IEEE. At lectures,symposia, seminars, or educational courses, an individual presenting information on IEEE standards shallmake it clear that his or

13、 her views should be considered the personal views of that individual rather than theformal position of IEEE. Comments on standardsComments for revision of IEEE Standards documents are welcome from any interested party, regardless ofmembership affiliation with IEEE. However, IEEE does not provide co

14、nsulting information or advicepertaining to IEEE Standards documents. Suggestions for changes in documents should be in the form of aproposed change of text, together with appropriate supporting comments. Since IEEE standards represent aconsensus of concerned interests, it is important that any resp

15、onses to comments and questions also receivethe concurrence of a balance of interests. For this reason, IEEE and the members of its societies andStandards Coordinating Committees are not able to provide an instant response to comments or questionsexcept in those cases where the matter has previously

16、 been addressed. For the same reason, IEEE does notrespond to interpretation requests. Any person who would like to participate in revisions to an IEEEstandard is welcome to join the relevant IEEE working group.Comments on standards should be submitted to the following address:Secretary, IEEE-SA Sta

17、ndards Board 445 Hoes Lane Piscataway, NJ 08854 USALaws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with theprovisions of any IEEE Standards document does not imply compliance to any applicable regulatoryrequirements. Implementers

18、of the standard are responsible for observing or referring to the applicableregulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is notin compliance with applicable laws, and these documents may not be construed as doing so.CopyrightsIEEE draft and

19、approved standards are copyrighted by IEEE under U.S. and international copyright laws.They are made available by IEEE and are adopted for a wide variety of both public and private uses. Theseinclude both use, by reference, in laws and regulations, and use in private self-regulation, standardization

20、,and the promotion of engineering practices and methods. By making these documents available for use andadoption by public authorities and private users, IEEE does not waive any rights in copyright to thedocuments.Photocopies Subject to payment of the appropriate fee, IEEE will grant users a limited

21、, non-exclusive license tophotocopy portions of any individual standard for company or organizational internal use or individual, non-commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance Center,Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA;

22、+1 978 750 8400. Permission tophotocopy portions of any individual standard for educational classroom use can also be obtained throughthe Copyright Clearance Center.Updating of IEEE Standards documents Users of IEEE Standards documents should be aware that these documents may be superseded at any ti

23、meby the issuance 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 errata then in effect. Every IEEE

24、 standard is subjected to review at least every ten years. When a document is more than ten yearsold and has not undergone a revision process, it is reasonable to conclude that its contents, although still ofsome value, do not wholly reflect the present state of the art. Users are cautioned to check

25、 to determine thatthey have the latest edition of any IEEE standard.In order to determine whether a given document is the current edition and whether it has been amendedthrough the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at http:/ieeexplore.ieee.org/xpl/standards.jsp

26、 or contact IEEE at the address listed previously. For more informationabout the IEEE-SA or IEEEs standards development process, visit the IEEE-SA Website at http:/standards.ieee.org.Errata Errata, if any, for all IEEE standards can be accessed on the IEEE-SA Website at the following URL: http:/stan

27、dards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errataperiodically.PatentsAttention is called to the possibility that implementation of this standard may require use of subject mattercovered by patent rights. By publication of this standard, no position is taken

28、 by the IEEE with respect to theexistence or validity of any patent rights in connection therewith. If a patent holder or patent applicant hasfiled a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website at http:/standards.ieee.org/about/sasb

29、/patcom/patents.html. Letters of Assurance may indicatewhether the Submitter is willing or unwilling to grant licenses under patent rights without compensation orunder reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfairdiscrimination to applicants desiring

30、 to obtain such licenses.Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is notresponsible for identifying Essential Patent Claims for which a license may be required, for conductinginquiries into the legal validity or scope of Patents Claims, or det

31、ermining whether any licensing terms orconditions provided in connection with submission of a Letter of Assurance, if any, or in any licensingagreements are reasonable or non-discriminatory. Users of this standard are expressly advised thatdetermination of the validity of any patent rights, and the

32、risk of infringement of such rights, is entirely theirown responsibility. Further information may be obtained from the IEEE Standards Association. viCopyright 2016 IEEE. All rights reserved.ParticipantsAt the time this amendment was submitted to the IEEE-SA Standards Board for approval, the IEEE 802

33、.1Working Group had the following membership:Glenn Parsons, Chair John Messenger, Vice ChairJnos Farkas, EditorStephen Haddock, Chair, Interworking Task Group The following members of the individual balloting committee voted on this amendment. Balloters may havevoted for approval, disapproval, or ab

34、stention.Ting AoChristian BoigerPaul BottorffDavid ChenFeng ChenWeiying ChengDiego CrupnicoffRodney CummingsPatrick DiamondAboubacar Kader DiarraNorman FinnGeoffrey GarnerAnoop GhanwaniMark GravelEric W. GrayCraig GuntherHitoshi HayakawaJeremy HittRahil HussainMichael Johas TeenerPeter JonesHal Keen

35、Marcel KiesslingYongbum KimPhilippe KleinJouni KorhonenJeff LynchBen Mack-CraneChristophe ManginJames McIntoshEric MultanenDonald PannellKaren RandallMaximilian RiegelDan RomascanuJessy V. RouyerPanagiotis SaltsidisBehcet SarikayaMichael SeamanDaniel SextonJohannes SpechtKevin B. StantonWilfried Ste

36、inerVahid TabatabaeePatricia ThalerJeremy TouveKarl WeberYuehua WeiBrian WeisJordon WoodsJuan-Carlos ZunigaIwan AdhicandraThomas AlexanderRichard AlfvinButch AntonGennaro BoggiaChristian BoigerNancy BravinAshley ButterworthWilliam ByrdRadhakrishna CanchiJuan CarreonCharles CookRodney CummingsYezid D

37、onosoSourav DuttaRichard EdgarLiu FangfangJnos FarkasMichael FischerYukihiro FujimotoDevon GayleJoel GoergenEric W. GrayDavid GregsonRandall GrovesCraig GuntherStephen HaddockMarco HernandezWerner HoelzlDavid HunterNoriyuki IkeuchiSergiu IordanescuAkio IsoAtsushi ItoRaj JainAnthony JeffreeMichael Jo

38、has TeenerPeter JonesAdri JovinShinkyo KakuPiotr KarockiStuart KerryYongbum KimJeff KoftinoffBruce KraemerHyeong Ho LeeArthur H. LightElvis MaculubaJames MarinRoger MarksJonathon MclendonCharles MoorwoodJose MoralesRonald MuriasMichael NewmanNick S. A. NikjooSatoshi ObaraAlon RegevMaximilian RiegelR

39、obert RobinsonBenjamin RolfeDan RomascanuJessy V. RouyerOsman SakrPanagiotis SaltsidisBartien SayogoMichael SeamanKapil SoodThomas StaraiEugene StoudenmireWalter StrupplerPayam TorabJahromiMark-Rene UchidaLorenzo VangelistaDmitri VarsanofievPrabodh VarshneyGeorge VlantisKhurram WaheedStephen WebbHun

40、g-Yu WeiAndreas WolfOren YuenviiCopyright 2016 IEEE. All rights reservedWhen the IEEE-SA Standards Board approved this amendment on 3 September 2015, it had the followingmembership:John Kulick, Chair Jon Walter Rosdahl, Vice Chair Richard H. Hulett, Past Chair Konstantinos Karachalios, Secretary *Me

41、mber EmeritusMasayuki AriyoshiTed Burse Stephen Dukes Jean-Phillippe Faure J. Travis GriffithGary Hoffman Michael Janezic Joseph L. Koepfinger* David J. Law Hung Ling Andrew MylesT. W. Olsen Glenn Parsons Ronald C. Peterson Annette D. ReillyStephen J. ShellhammerAdrian P. Stephens Yatin Trivedi Phil

42、lip Winston Don Wright Yu Yuan Daidi ZhongviiiCopyright 2016 IEEE. All rights reserved.IntroductionThis amendment to IEEE Std 802.1Q-2014 specifies protocol extensions, procedures and managed objectsfor explicit path control, bandwidth reservation, and redundancy (protection, restoration) for data f

43、lows.This 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 material. Information on the current revision s

44、tate of this and other IEEE 802standards may be obtained fromSecretary, IEEE-SA Standards Board445 Hoes LanePiscataway, NJ 08854USAThis introduction is not part of IEEE Std 802.1Qca-2015, IEEE Standard for Local and metropolitan areanetworksBridges and Bridged NetworksAmendment 24: Path Contro l and

45、 Reservation.ixCopyright 2016 IEEE. All rights reserved.Contents1. Overview21.3 Introduction22. Normative references.33. Definitions44. Abbreviations.65. Conformance75.4.6 Path Control and Reservation (PCR) (optional) .77. Principles of Virtual Bridged Network operation87.1 Network overview87.3 Acti

46、ve topology88. Principles of Bridge operation.108.4 Active topologies, learning, and forwarding108.6.1 Active topology enforcement 108.8.9 Querying the FDB .108.9.3 ID to MSTI Allocation Table 1112.Bridge management.1212.25 Shortest Path Bridging managed objects.1212.25.4 The SPB ECT Static Entry ma

47、naged object .1312.28 Path Control and Reservation (PCR) management1312.28.1 The PCR ECT Static Entry managed object .1412.28.2 The PCR Topology ECT Table managed object 1617.Management Information Base (MIB).1817.2 Structure of the MIB1817.2.19 Structure of the IEEE8021-SPB-MIB .1817.3 Relationship

48、 to other MIBs1917.3.22 Relationship of the PCR MIB to other MIB modules 1917.4 Security considerations1917.4.22 Security considerations of the PCR MIB 1917.7 MIB modules.1917.7.19 Definitions for the IEEE8021-SPB-MIB module .1927.Shortest Path Bridging (SPB)6427.1 Protocol design requirements.6427.

49、4 ISIS-SPB VLAN configuration.6428.ISIS-SPB Link State Protocol6628.6 Symmetric ECT framework.6628.7 Symmetric ECT.6628.8 Symmetric ECT Algorithm details.66xCopyright 2016 IEEE. All rights reserved28.12.4 SPB Base VLAN-Identifiers sub-TLV 6728.12.5 SPB Instance sub-TLV 6728.12.10 SPBM Service Identifier and Unicast Address (ISID-ADDR) sub-TLV .6745.Path Control and Reservation (PCR).6845.1 Explicit trees6845.1.1 Tree structures .7245.1.2 Explicit ECT Algorithms 7345.1.3 ISIS-PCR VLAN configuration 7545.1.4 Use of VIDs for strict explicit trees 7945.1.5 MAC addres