ISO/IEC/IEEE 8802-1Q:2024/Amd 37:2025

International
Standard
ISO/IEC/IEEE
8802-1Q
Third edition
Telecommunications and exchange
2024-08
between information technology
systems — Requirements for local
AMENDMENT 37
and metropolitan area networks —
2025-03
Part 1Q:
Bridges and bridged networks
AMENDMENT 37: Automatic
Attachment to Provider Backbone
Bridging (PBB) Services
Télécommunications et échange entre systèmes informatiques —
Exigences pour les réseaux locaux et métropolitains —
Partie 1Q: Ponts et réseaux pontés
AMENDEMENT 37: Attachement automatique aux services PBB
(Provider Backbone Bridging)
Reference number
ISO/IEC/IEEE 8802-1Q:2024/
Amd.37:2025(en)
© IEEE 2023
ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2025(en)
© IEEE 2023
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from IEEE at the address below.
Institute of Electrical and Electronics Engineers, Inc
3 Park Avenue, New York
NY 10016-5997, USA
Email: stds.ipr@ieee.org
Website: www.ieee.org
Published in Switzerland
© IEEE 2023 – All rights reserved
ii
ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2025(en)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members
of ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
document should be noted.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards
through a consensus development process, approved by the American National Standards Institute, which
brings together volunteers representing varied viewpoints and interests to achieve the final product.
Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE
administers the process and establishes rules to promote fairness in the consensus development process, the
IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its
standards.
ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of
(a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not received
notice of (a) patent(s) which may be required to implement this document. However, implementers are
cautioned that this may not represent the latest information, which may be obtained from the patent database
available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
ISO/IEC/IEEE 8802-1Q:2024/Amd.37 was prepared by the LAN/MAN of the IEEE Computer Society (as
IEEE 802.1Qcj-2023) and drafted in accordance with its editorial rules. It was adopted, under the “fast-track
procedure” defined in the Partner Standards Development Organization cooperation agreement between
ISO and IEEE, by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 6,
Telecommunications and information exchange between systems.
A list of all parts in the ISO/IEC/IEEE 8802 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html and www.iec.ch/national-
committees.
© IEEE 2023 – All rights reserved
iii
Title page
IEEE Std 802.1Qcj™-2023
(Amendment to IEEE Std 802.1Q™-2022
as amended by IEEE Std 802.1Qcz™-2023
and IEEE Std 802.1Qcw™-2023)
IEEE Standard for
Local and Metropolitan Area Networks—
Bridges and Bridged Networks
Amendment 37:
Automatic Attachment to Provider
Backbone Bridging (PBB) Services
Developed by the
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 21 September 2023
IEEE SA Standards Board
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Abstract: This amendment to IEEE Std 802.1Q-2022 as amended by IEEE Std 802.1Qcz-2023
and IEEE Std 802.1Qcw-2023 specifies protocols, procedures, and management objects for auto
attachment of network devices to Provider Backbone service instances using Type, Length, Value
(TLVs) within the Link Layer Discovery Protocol (LLDP).
Keywords: AAB, AAD, AAP, amendment, Auto Attach, Auto Attach Backbone Edge Bridge, Auto
Attach Device, Auto Attach Protocol, Bridged Network, IEEE 802.1Q™, IEEE 802.1Qcj™, LAN,
local area network, MAC Bridge, metropolitan area network, MSTP, Multiple Spanning Tree
Protocol, PBBN, PBN, Provider Backbone Bridged Network, Provider Bridged Network, Rapid
Spanning Tree Protocol, RSTP, Shortest Path Bridging Protocol, SPB Protocol, Time-Sensitive
Networking, TSN, Virtual Bridged Network, virtual LAN, VLAN Bridge
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 17 November 2023. Printed in the United States of America.
IEEE and 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and
Electronics Engineers, Incorporated.
PDF: ISBN 979-8-8557-0268-2 STD26585
Print: ISBN 979-8-8557-0269-9 STDPD26585
IEEE prohibits discrimination, harassment, and bullying. For more information, visit
http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior
written permission of the publisher.
Copyright © 2023 IEEE. All rights reserved.

ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Important Notices and Disclaimers Concerning IEEE Standards
Documents
IEEE Standards documents are made available for use subject to important notices and legal disclaimers.
These notices and disclaimers, or a reference to this page (https://standards.ieee.org/ipr/disclaimers.html),
appear in all standards and may be found under the heading “Important Notices and Disclaimers Concerning
IEEE Standards Documents.”
Notice and Disclaimer of Liability Concerning the Use of IEEE Standards
Documents
IEEE Standards documents are developed within IEEE Societies and subcommittees of IEEE Standards
Association (IEEE SA) Board of Governors. IEEE develops its standards through an accredited consensus
development process, which brings together volunteers representing varied viewpoints and interests to
achieve the final product. IEEE standards are documents developed by volunteers with scientific, academic,
and industry-based expertise in technical working groups. Volunteers are not necessarily members of IEEE
or IEEE SA and participate without compensation from IEEE. While IEEE administers the process and
establishes rules to promote fairness in the consensus development process, IEEE does not independently
evaluate, test, or verify the accuracy of any of the information or the soundness of any judgments contained
in its standards.
IEEE makes no warranties or representations concerning its standards, and expressly disclaims all
warranties, express or implied, concerning this standard, including but not limited to the warranties of
merchantability, fitness for a particular purpose and non-infringement. IEEE Standards documents do not
guarantee safety, security, health, or environmental protection, or guarantee against interference with or
from other devices or networks. In addition, IEEE does not warrant or represent that the use of the material
contained in its standards is free from patent infringement. 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 there
are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to
the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and
issued is subject to change brought about through developments in the state of the art and comments
received from users of the standard.
In publishing and making its standards available, IEEE is not suggesting or rendering professional or other
services for, or on behalf of, any person or entity, nor is IEEE undertaking to perform any duty owed by any
other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon their
own independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate,
seek the advice of a competent professional in determining the appropriateness of a given IEEE standard.
IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: THE
NEED TO PROCURE SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE
UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND
REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Translations
The IEEE consensus balloting process involves the review of documents in English only. In the event that an
IEEE standard is translated, only the English version published by IEEE is the approved IEEE standard.
Official statements
A statement, written or oral, that is not processed in accordance with the IEEE SA Standards Board
Operations Manual shall not be considered or inferred to be the official position of IEEE or any of its
committees and shall not be considered to be, nor be relied upon as, a formal position of IEEE. At lectures,
symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall
make it clear that the presenter’s views should be considered the personal views of that individual rather
than the formal position of IEEE, IEEE SA, the Standards Committee, or the Working Group. Statements
made by volunteers may not represent the formal position of their employer(s) or affiliation(s).
Comments on standards
Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of
membership affiliation with IEEE or IEEE SA. However, IEEE does not provide interpretations,
consulting information, or advice pertaining to IEEE Standards documents.
Suggestions for changes in documents should be in the form of a proposed change of text, together with
appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is
important that any responses to comments and questions also receive the concurrence of a balance of interests.
For this reason, IEEE and the members of its Societies and subcommittees of the IEEE SA Board of
Governors are not able to provide an instant response to comments, or questions except in those cases where
the matter has previously been addressed. For the same reason, IEEE does not respond to interpretation
requests. Any person who would like to participate in evaluating comments or in revisions to an IEEE standard
is welcome to join the relevant IEEE working group. You can indicate interest in a working group using the
Interests tab in the Manage Profile & Interests area of the IEEE SA myProject system. An IEEE Account is
needed to access the application.
Comments on standards should be submitted using the Contact Us form.
Laws and regulations
Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the
provisions of any IEEE Standards document does not constitute compliance to any applicable regulatory
requirements. Implementers of the standard are responsible for observing or referring to the applicable
regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not
in compliance with applicable laws, and these documents may not be construed as doing so.
Data privacy
Users of IEEE Standards documents should evaluate the standards for considerations of data privacy and
data ownership in the context of assessing and using the standards in compliance with applicable laws and
regulations.
Available at: https://development.standards.ieee.org/myproject-web/public/view.html#landing.
Available at: https://standards.ieee.org/content/ieee-standards/en/about/contact/index.html.
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Copyrights
IEEE draft and 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. 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 these documents available for use and
adoption by public authorities and private users, neither IEEE nor its licensors waive any rights in copyright
to the documents.
Photocopies
Subject to payment of the appropriate licensing fees, IEEE will grant users a limited, non-exclusive license
to photocopy 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; +1 978 750 8400;
https://www.copyright.com/. Permission to photocopy portions of any individual standard for educational
classroom use can also be obtained through the Copyright Clearance Center.
Updating of IEEE Standards documents
Users of IEEE Standards documents should be aware that these documents may be superseded at any time
by 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 the
document together with any amendments, corrigenda, or errata then in effect.
Every IEEE standard is subjected to review at least every 10 years. When a document is more than 10 years
old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of
some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that
they 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 amended
through the issuance of amendments, corrigenda, or errata, visit IEEE Xplore or contact IEEE. For more
information about the IEEE SA or IEEE’s standards development process, visit the IEEE SA Website.
Errata
Errata, if any, for all IEEE standards can be accessed on the IEEE SA Website. Search for standard number
and year of approval to access the web page of the published standard. Errata links are located under the
Additional Resources Details section. Errata are also available in IEEE Xplore. Users are encouraged to
periodically check for errata.
Patents
IEEE standards are developed in compliance with the IEEE SA Patent Policy.
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the
existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has
Available at: https://ieeexplore.ieee.org/browse/standards/collection/ieee.
Available at: https://standards.ieee.org/standard/index.html.
Available at: https://standards.ieee.org/about/sasb/patcom/materials.html.
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the
IEEE SA Website at https://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may
indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without
compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of
any unfair discrimination to applicants desiring to obtain such licenses.
Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not
responsible for identifying Essential Patent Claims for which a license may be required, for conducting
inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or
conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing
agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that
determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their
own responsibility. Further information may be obtained from the IEEE Standards Association.
IMPORTANT NOTICE
Technologies, application of technologies, and recommended procedures in various industries evolve over
time. The IEEE standards development process allows participants to review developments in industries,
technologies, and practices, and to determine what, if any, updates should be made to the IEEE standard.
During this evolution, the technologies and recommendations in IEEE standards may be implemented in
ways not foreseen during the standard’s development. IEEE standards development activities consider
research and information presented to the standards development group in developing any safety
recommendations. Other information about safety practices, changes in technology or technology
implementation, or impact by peripheral systems also may be pertinent to safety considerations during
implementation of the standard. Implementers and users of IEEE Standards documents are responsible for
determining and complying with all appropriate safety, security, environmental, health, and interference
protection practices and all applicable laws and regulations.
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Participants
At the time this standard was submitted to the IEEE SA Standards Board for approval, the IEEE 802.1
Working Group had the following membership:
Glenn Parsons, Chair
Jessy V. Rouyer, Vice Chair
János Farkas, Chair, Time-Sensitive Networking Task Group
Craig Gunther, Vice Chair, Time-Sensitive Networking Task Group
Paul Bottorff, Editor
Katsuyuki Akizuki Marc Holness Maximilian Riegel
Konstantinos Alexandris Daniel Hopf Craig Rodine
Woojung Huh
Venkat Arunarthi Silvana Rodrigues
Satoko Itaya
Ralf Assmann Atsushi Sato
Yoshihiro Ito
Huajie Bao Frank Schewe
Michael Karl
Rudy Belliardi Michael Seaman
Stephan Kehrer
Jeremias Blendin Maik Seewald
Marcel Kiessling
Christian Boiger Ramesh Sivakolundu
Gavin Lai
Radhakrishna Canchi Johannes Specht
Yizhou Li
Nemanja Stamenic
Feng Chen
Joao Lopes
Abhijit Choudhury Marius Stanica
Lily Lyu
Paul Congdon Guenter Steindl
Christophe Mangin
Rodney Cummings Karim Traore
Scott Mansfield
Josef Dorr Max Turner
Olaf Mater
Hesham Elbakoury Balazs Varga
David McCall
Ganesh Venkatesan
Anna Engelmann
Larry McMillan
Thomas Enzinger Tongtong Wang
Martin Mittelberger
Donald Fedyk Karl Weber
Hiroki Nakano
Norman Finn Leon Wessels
Takumi Nomura
Geoffrey Garner Ludwig Winkel
Dragan Obradovic
Marina Gutiérrez Jordon Woods
Donald R. Pannell
Stephen Haddock Dieter Proell Takahiro Yamaura
Mark Hantel Karen Randall Nader Zein
The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
Thomas Alexander Pranav Jha Dieter Proell
Lokesh Kabra
Amelia Andersdotter R. K. Rannow
Butch Anton Piotr Karocki
Maximilian Riegel
Christian Boiger Stuart Kerry
Jessy V. Rouyer
Paul Bottorff Yongbum Kim
Michael Seaman
William Byrd Hyeong Ho Lee
Veselin Skendzic
Paul Cardinal James Lepp
Walter Struppler
Jose Castro Greg Luri
Max Turner
Pin Chang Christophe Mangin
John Vergis
Aditya Chaudhuri Scott Mansfield
James Weaver
Paul Congdon Jonathon McLendon
Stephen Webb
János Farkas Ronald Murias
Karl Weber
Donald Fedyk Rajesh Murthy
Scott Willy
Avraham Freedman Satoshi Obara
Andreas Wolf
Chong Han Glenn Parsons
Yu Yuan
Marco Hernandez Bansi Patel
Oren Yuen
Werner Hoelzl Arumugam Paventhan
Yasuhiro Hyakutake Clinton Powell Qiyue Zou
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

When the IEEE SA Standards Board approved this standard on 21 September 2023, it had the following
membership:
David J. Law, Chair
Ted Burse, Vice Chair
Gary Hoffman, Past Chair
Konstantinos Karachalios, Secretary
Sara R. Biyabani Joseph S. Levy Paul Nikolich
Doug Edwards Howard Li Annette D. Reilly
Ramy Ahmed Fathy Johnny Daozhuang Lin Robby Robson
Guido R. Hiertz Gui Lin Lei Wang
Yousef Kimiagar Xiaohui Liu F. Keith Waters
Joseph L. Koepfinger* Kevin W. Lu Karl Weber
Thomas Koshy Daleep C. Mohla Philip B. Winston
John D. Kulick Andrew Myles Don Wright
*Member Emeritus
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Introduction
This introduction is not part of IEEE Std 802.1Qcj™-2023, IEEE Standard for Local and Metropolitan Area
Networks—Bridges and Bridged Networks—Amendment 37: Automatic Attachment to Provider Backbone Bridging
(PBB) Services.
IEEE Std 802.1Qcj™-2023: Automatic Attachment to Provider Backbone Bridging (PBB) Services
specifies protocols, procedures, and management objects for auto attachment of network devices to Provider
Backbone service instances using Type, Length, Value (TLVs) within the Link Layer Discovery Protocol
(LLDP).
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, and
to incorporate new related material. Information on the current revision state of this and other IEEE 802
standards may be obtained from:
Secretary, IEEE SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854-4141
USA
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Contents
1. Overview. 16
1.3 Introduction. 16
3. Definitions . 17
4. Abbreviations. 18
5. Conformance. 19
5.9 C-VLAN Bridge conformance. 19
5.9.2 C-VLAN Bridge requirements for PBBN Auto Attach (optional) . 19
5.10 Provider Bridge conformance.19
5.10.3 S-VLAN Bridge requirements for PBBN Auto Attach (optional) . 19
5.12 Backbone Edge Bridge (BEB) conformance . 19
5.12.2 Backbone Edge Bridge requirements for PBBN Auto Attach (optional) . 19
5.14 MAC Bridge conformance.20
5.14.2 MAC Bridge requirements for PBBN Auto Attach (optional) . 20
5.33 End station requirements for PBBN Auto Attach (optional). 20
12. Bridge Management. 21
12.34 Managed objects for PBBN Auto Attach . 21
12.34.1 PBBN Auto Attach System objects . 21
12.34.2 PBBN Auto Attach port table . 22
12.34.3 PBBN Discovered Auto Attach Systems table . 23
12.34.4 PBBN Auto Attach assignment table . 24
12.34.5 PBBN Auto Attach statistics table . 25
17. Management Information Base (MIB) . 26
17.2 Structure of the MIB . 26
17.2.26 Structure of the IEEE8021-PBBN-AA-MIB . 26
17.3 MIB module relationships . 28
17.3.26 Relationship of the IEEE8021-PBBN-AA-MIB to other MIB modules . 28
17.4 Security considerations . 28
17.4.26 Security considerations of the IEEE8021-PBBN-AA-MIB . 28
17.7 MIB modules . 29
17.7.26 Definitions for the IEEE8021-PBBN-AA-MIB module . 29
48. YANG Data Models . 39
48.6 YANG modules . 39
48.6.2 The ieee802-dot1q-types YANG module . 39
50. PBBN Auto Attach . 56
50.1 Overview. 56
........ 57
50.2 Service interfaces.
50.2.1 S-tagged service interface . 57
50.2.2 C-tagged service interface . 58
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

50.3 State machine overview . 59
50.3.1 System inactivity . 60
50.3.2 Multiple AAD systems . 60
50.3.3 AAD assignment requests . 60
50.3.4 AAB assignment request processing . 61
50.3.5 Assignment updates . 61
50.4 State machine variables . 62
50.4.1 Structure type definitions . 62
50.4.2 Per AAS variables . 63
50.4.3 Per port variables . 64
50.5 State machine functions . 67
50.5.1 aaBuildSysTlv( SYSstring tlv ) . 67
50.5.2 aaBuildAsgnsTlv( ASGNSstring tlv, VIDISIDpair vidIsidArray[], ASGNSstring
operTlv ) . 67
50.5.3 aaConfigAabAsgn( unsigned vid, unsigned isid ) . 68
50.5.4 aaDisableAabVidIsidAsgns( ASGNSstring tlvNew, ASGNSstring tlvOld ) . 68
50.5.5 aaDisableLldpAaTlvTx() . 69
50.5.6 aaDisableVidIsidAsgns() . 69
50.5.7 aaDiscAssocAabTblCheck( unsigned port, SYSstring tlv ) . 69
50.5.8 aaDiscAssocAadTblCheck( unsigned port, SYSstring tlv ) . 70
50.5.9 aaDiscAssocTblDelete( unsigned port ) . 70
50.5.10 aaDiscAssocTblInsert( unsigned port, SYSstring tlv ) . 70
50.5.11 aaEnableAabVidIsidAsgns( ASGNSstring tlv ) . 70
50.5.12 aaEnableAadVidIsidAsgns( ASGNSstring tlv ) . 71
50.5.13 aaPortClearStats() . 71
50.5.14 aaSetAsgnsTlv( ASGNSstring tlv ) . 71
50.5.15 aaSetSysTlv( SYSstring tlv ) . 71
50.5.16 aaSomethingChangedRemote() . 72
50.5.17 aaSomethingChangeRemoteInit() . 72
50.5.18 aaUpdateReqDelVidIsidStats( ASGNSstring tlvNew, ASGNSstring tlvOld ) . 73
50.5.19 aaUpdateAcptRejVidIsidStats( ASGNSstring tlvNew, ASGNSstring tlvOld ) . 74
50.5.20 SomethingChangedLocal() . 74
50.6 AAD state machine. 75
50.7 AAB state machine . 76
Annex A (normative) PICS proforma—Bridge implementations . 77
A.5 Major capabilities . 77
A.14 Bridge management . 78
A.24 Management Information Base (MIB) . 79
A.47 YANG. 80
A.54 PBBN auto attach. 81
Annex B (normative) PICS proforma—End station implementations . 82
B.5 Major capabilities . 82
B.20 PBBN Auto Attach . 82
Annex D (normative) IEEE 802.1 Organizationally Specific TLVs . 83
D.1 Requirements of the IEEE 802.1 Organizationally Specific TLV sets. 83
D.2 Organizationally Specific TLV definitions. 84
D.2.17 PBBN Auto Attach System TLV . 84
D.2.18 PBBN Auto Attach Assignment TLV . 86
D.3 IEEE 802.1 Organizationally Specific TLV management. 88
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

D.4 PICS proforma for IEEE 802.1 Organizationally Specific TLV extensions . 89
D.4.3 Major capabilities and options . 89
D.5 IEEE 802.1/LLDP extension MIB. 90
D.5.2 Structure of the IEEE 802.1/LLDP extension MIB . 90
D.5.4 Security considerations for IEEE 802.1 LLDP extension MIB module . 91
D.5.6 EVB extensions to the IEEE 802.1 LLDP extension MIB module . 93
D.6 IEEE 802.1/LLDP extension YANG. 104
D.6.2 IEEE 802.1 Organizationally Specific TLV YANG data models . 104
D.6.3 Structure of the IEEE 802.1/LLDP extension YANG models . 104
D.6.4 Security considerations . 105
D.6.5 Definition of the IEEE 802.1/LLDP extension YANG modules . 105
D.6.6 IEEE 802.1/LLDP extension YANG modules . 106
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Figures
Figure 50-1 PBBN Auto Attach model . 56
Figure 50-2 PBBN Auto Attach functions diagram . 57
Figure 50-3 PBBN Auto Attach for customer networks . 58
Figure 50-4 PBBN Auto Attach Device (AAD) state machine. 75
Figure 50-5 PBBN Auto Attach BEB (AAB) state machine. 76
Figure D-17 PBBN Auto Attach System TLV Format . 84
Figure D-18 PBBN Auto Attach Assignment TLV format. 87
Figure D-26 PBBN Auto Attach aaSet TLV model. 104
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

Tables
Table 12-46 PBBN Auto Attach System objects . 21
Table 12-47 PBBN Auto Attach port table . 22
Table 12-48 PBBN Discovered Auto Attach Systems table . 23
Table 12-49 PBBN Auto Attach assignment table. 24
Table 12-50 PBBN Auto Attach statistics table. 25
Table 17-1 IEEE 802.1Q MIB modules. 26
Table 17-32 IEEE8021-PBBN-AA-MIB Structure . 26
Table D-1 IEEE 802.1 Organizationally Specific TLVs . 83
Table D-16 PBBN Auto Attach association states. 85
Table D-17 PBBN Auto Attach System Type values . 85
Table D-18 PBBN Auto Attach Tagging field values . 86
Table D-19 PBBN Auto Attach PortNetId values . 86
Table D-20 PBBN Auto Attach Assignment Status values . 87
Table D-21 IEEE 802.1 extension MIB object group conformance requirements . 90
Table D-22 IEEE 802.1/LLDP extension MIB object cross reference. 90
Table D-23 Summary of the YANG modules. 104
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)

IEEE Standard for
Local and Metropolitan Area Networks—
Bridges and Bridged Networks
Amendment 37:
Automatic Attachment to Provider
Backbone Bridging (PBB) Services
(This amendment is based on IEEE Std 802.1Q™-2022 as amended by IEEE Std 802.1Qcz™-2023 and
IEEE Std 802.1Qcw™-2023.)
NOTE—The editing instructions contained in this amendment define how to merge the material contained therein into
the existing base standard and its amendments to form the comprehensive standard.
The editing instructions are shown in bold italics. Four editing instructions are used: change, delete, insert, and replace.
Change is used to make corrections in existing text or tables. The editing instruction specifies the location of the change
and describes what is being changed by using strikethrough (to remove old material) and underscore (to add new
material). Delete removes existing material. Insert adds new material without disturbing the existing material. Deletions
and insertions may require renumbering. If so, renumbering instructions are given in the editing instruction. Replace is
used to make changes in figures or equations by removing the existing figure or equation and replacing it with a new
one. Editing instructions, change markings, and this note will not be carried over into future editions because the
changes will be incorporated into the base standard.
Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the standard.
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)
IEEE Std 802.1Qcj™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks

Amendment 37: Automatic Attachment to Provider Backbone Bridging (PBB) Services
1. Overview
1.3 Introduction
Insert the following text at the end of 1.3:
This standard specifies the protocols, procedures, and management objects for auto attachment of network
devices to backbone service instances (BSIs) by adding an Auto Attach Protocol (AAP) over the Link Layer
Discovery Protocol (LLDP). The AAP simplifies the deployment and administration of PBB networks by
automatically coupling end stations or Bridges to BSIs.
To this end, it:
cz) Introduces the concepts of Auto Attach Protocol (AAP), Auto Attach System (AAS) on devices
supporting Auto Attach; non-PBB-based Auto Attach Devices (AADs) and PBB-based Auto
Attach BEBs (AABs).
da) Describes the process of discovery and advertising of capabilities for AADs and AABs supporting
the AAP acting as an AAS.
db) Describes the bindings between Backbone Service Instance Identifiers (I-SIDs) and VLAN
Identifiers.
dc) Specifies IEEE 802.1 Organizationally Specific LLDP TLVs for discovery and capabilities
advertising, and attachment of C-VLANs to backbone service instances.
dd) Specifies SNMP MIB support for PBBN Auto Attach.
de) Specifies YANG extensions to the LLDP YANG modules for the PBBN Auto Attach LLDP TLVs.
df) Specifies SNMP MIB extensions to the LLDP EVB extension MIB module for the PBBN Auto
Attach LLDP TLVs.
The term “Auto Attach” is used interchangeably with “PBBN Auto Attach” where it is clear from the context that “PBBN Auto
Attach” is discussed.
ISO/IEC/IEEE ISO/IEC/IEEE 8802-1Q:2024/Amd.37:2024(en)8802-1Q:2024/Amd.37:2025(en)
IEEE Std 802.1Qcj™-2023
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks

Amendment 37: Automatic Attachment to Provider Backbone Bridging (PBB) Services
3. Definitions
Insert the following definitions in the appropriate collating sequence, renumbering accordingly:
3.1 Auto Attach BEB (AAB) Bridge component: A Backbone Edge Bridge ha
...