ISO/IEC/IEEE 8802-1Q:2016/Amd 2:2018

Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 1Q: Bridges and bridged networks - Amendment 2: Application virtual local area network (VLAN) type, length, value (TLV)

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseaux locaux et métropolitains — Exigences spécifiques — Partie 1Q: Ponts et réseaux pontés — Amendement 2: Type, longueur, valeur (TLV) pour applications de réseaux locaux virtuels (VLAN)

General Information

• Status: Withdrawn
• Publication Date: 07-Jan-2018
• Withdrawal Date: 07-Jan-2018
• ICS: 35.110 - Networking
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 21-Aug-2020
• Completion Date: 30-Oct-2025

Relations

• Amends: ISO/IEC/IEEE 8802-1Q:2016 - Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 1Q: Bridges and bridged networks
• Effective Date: 14-Aug-2021
• Revised: ISO/IEC/IEEE 8802-1Q:2020 - Telecommunications and exchange between information technology systems - Requirements for local and metropolitan area networks - Part 1Q: Bridges and bridged networks
• Effective Date: 23-Apr-2020

Standards Content (Sample)

INTERNATIONAL ISO/IEC/IEEE
STANDARD 8802-1Q
First edition
2016-03-15
AMENDMENT 2
2018-01
Information technology —
Telecommunications and information
exchange between systems — Local
and metropolitan area networks —
Specific requirements —
Part 1Q:
Bridges and bridged networks
AMENDMENT 2: Application virtual
local area network (VLAN) type, length,
value (TLV)
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseaux locaux et métropolitains —
Exigences spécifiques —
Partie 1Q: Ponts et réseaux pontés
AMENDEMENT 2: Type, longueur, valeur (TLV) pour applications de
réseaux locaux virtuels (VLAN)
Reference number
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
©
IEEE 2015
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)

© IEEE 2015
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm,
without permission in writing from ISO, IEC or IEEE at the respective address below.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
CH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USA
Tel. [phone]
Fax [phone]
[e-mail] [e-mail]
www.iso.org www.ieee.org
Published in Switzerland
© IEEE 2015 – All rights reserved
ii
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
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.
In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1.
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.
The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards
adopted by the joint technical committee are circulated to national bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is called to the possibility that implementation of this standard may require the use of subject
matter covered by patent rights. By publication of this standard, no position is taken with respect to the
existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for
identifying essential patents or patent claims for which a license may be required, for conducting inquiries
into the legal validity or scope of patents or patent claims or determining whether any licensing terms or
conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and
Licensing Declaration Form, 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 ISO or the IEEE Standards Association.
ISO/IEC/IEEE 8802-1Q:2016/Amd.2 was prepared by the LAN/MAN of the IEEE Computer Society
(as IEEE Std 802.1Qcd-2015). It was adopted by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 6, Telecommunications and information exchange between
systems, in parallel with its approval by the ISO/IEC national bodies, under the “fast-track procedure”
defined in the Partner Standards Development Organization cooperation agreement between ISO and
IEEE. IEEE is responsible for the maintenance of this document with participation and input from
ISO/IEC national bodies.
© IEEE 2015 – All rights reserved iii

IEEE Std 802.1Qcd™-2015
(Amendment to
IEEE Std 802.1Q™-2014)
IEEE Standard for
Local and metropolitan area networks—
Bridges and Bridged Networks
Amendment 23: Application Virtual Local Area
Network (VLAN) Type, Length, Value (TLV)
Sponsor
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 16 February 2015
IEEE SA-Standards Board
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
Abstract: Enhancements to the set of TLVs used by the Data Center Bridging eXchange protocol
(DCBX) for the purpose of simplifying the management of networks utilizing Data Center Bridging
(DCB) features are defined in this amendment to IEEE Std 802.1Q-2014.
Keywords: Bridged Networks, Data Center Bridging (DCB), Data Center Bridging eXchange ®
protocol (DCBX), IEEE 802 , IEEE 802.1Q™, IEEE 802.1Qcd™, local area networks (LANs), MAC
Bridges, metropolitan area networks, Virtual Bridged Networks (virtual LANs), VLAN Bridges
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 13 March 2015. 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.
Print: ISBN 978-0-7381-9565-0 STD20128
PDF: ISBN 978-0-7381-9566-7 STDPD20128
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.
ii Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
Important Notices and Disclaimers Concerning IEEE Standards Documents
IEEE documents are made available for use subject to important notices and legal disclaimers. These notices
and disclaimers, or a reference to this page, appear in all standards and may be found under the heading
“Important Notice” or “Important Notices and Disclaimers Concerning IEEE Standards Documents.”
Notice and Disclaimer of Liability Concerning the Use of IEEE Standards
Documents
IEEE Standards documents (standards, recommended practices, and guides), both full-use and trial-use, are
developed within IEEE Societies and the Standards Coordinating Committees of the IEEE Standards
Association (“IEEE-SA”) Standards Board. IEEE (“the Institute”) develops its standards through a
consensus development process, approved by the American National Standards Institute (“ANSI”), which
brings together volunteers representing varied viewpoints and interests to achieve the final product.
Volunteers are not necessarily members of the Institute 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 does not warrant or represent the accuracy or content of the material contained in its standards, and
expressly disclaims all warranties (express, implied and statutory) not included in this or any other
document relating to the standard, including, but not limited to, the warranties of: merchantability; fitness
for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of
material. In addition, 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 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 his
or her 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:
PROCUREMENT OF 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 8802-1Q:2016/Amd.2:2018(E)
Translations
The IEEE consensus development 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 should be considered 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, or 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 his or her views should be considered the personal views of that individual rather than the
formal position of IEEE.
Comments on standards
Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of
membership affiliation with IEEE. However, IEEE does not provide 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
Standards Coordinating Committees 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 revisions to an IEEE
standard is welcome to join the relevant IEEE working group.
Comments on standards should be submitted to the following address:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854 USA
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 imply 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.
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, IEEE does not waive any rights in copyright to the
documents.
iv Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
Photocopies
Subject to payment of the appropriate fee, 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; [phone]. 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 ten years. When a document is more than ten 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 the IEEE-SA Website at http://
ieeexplore.ieee.org/xpl/standards.jsp or contact IEEE at the address listed previously. For more information
about the IEEE SA or IOWA’s 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://
standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata
periodically.
Patents
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
filed 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/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.
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
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, Working Group Chair
John Messenger, Working Group Vice Chair
Patricia Thaler, Chair, Data Center Bridging Task Group
Eric Multanen, Editor
Ting Ao Hitosh Hayakawa Karen Randall
Christian Boiger Jeremy Hitt Dan Romascanu
Paul Bottorff Rahil Hussain Jessy V. Rouyer
David Chen Anthony Jeffree Panagiotis Saltsidis
Peter Jones
Feng Chen Behcet Sarikaya
Weiying Cheng Hal Keen Daniel Sexton
Diego Crupnicoff Marcel Kiessling Johannes Specht
Rodney Cummings Yongbum Kim Kevin B. Stanton
Patrick Diamond Philippe Klein Wilfried Steiner
Aboubacar Kader Diarra Jouni Korhonen Vahid Tabatabaee
Janos Farkas Jeff Lynch Jeremy Touve
Norman Finn Karl Weber
Ben Mack-Crane
Geoffrey Garner Christophe Mangin Yuehua Wei
Anoop Ghanwani James McIntosh Brian Weis
Mark Gravel Eric Multanen Jordon Woods
Craig Gunther Donald Pannell Juan-Carlos Zuniga
vi Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
Thomas Alexander Anthony Jeffree Maximilian Riegel
Nancy Bravin Shinkyo Kaku Robert Robinson
William Byrd Piotr Karocki Dan Romascanu
Juan Carreon Stuart Kerry Jessy V. Rouyer
Rodney Cummings Morteza Khodaie Peter Saunderson
Veselin Skendzic
Yezid Donoso Bruce Kraemer
Richard Edgar Yasushi Kudoh Kapil Sood
Yukihiro Fujimoto Michael Lynch Thomas Starai
Eugene Stoudenmire
Devon Gayle Elvis Maculuba
Walter Struppler
Anoop Ghanwani Richard Mellitz
Patricia Thaler
Joel Goergen Jose Morales
Randall Groves Eric Multanen Dmitri Varsanofiev
Prabodh Varshney
Michael Gundlach Michael Newman
George Vlantis
Werner Hoelzl Nick S.A. Nikjoo
Hung-Yu Wei
C. Huntley Satoshi Obara
Noriyuki Ikeuchi Andreas Wolf
Jean Pierre Picard
Oren Yuen
Atsushi Ito R. K. Rannow
Daidi Zhong
Raj Jain Alon Regev
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
When the IEEE-SA Standards Board approved this standard on 16 February 2015, it had the following
membership:
John Kulick, Chair
Jon Walter Rosdahl, Vice Chair
Richard H. Hulett, Past Chair
Konstantinos Karachalios, Secretary
Peter Balma Michael Janezic Ron Peterson
Farooq Bari Jeffrey Katz Adrian Stephens
Peter Sutherland
Ted Burse Joseph L. Koepfinger*
Yatin Trivedi
Clint Chaplain David J. Law
Hung Ling Phil Winston
Stephen Dukes
Oleg Logvinov Don Wright
Jean-Phillippe Faure
Yu Yuan
T. W. Olsen
Gary Hoffman
Glenn Parsons
*Member Emeritus
Also included are the following nonvoting IEEE-SA Standards Board liaisons:
Richard DeBlasio, DOE Representative
Michael Janezic, NIST Representative
Michelle Turner
IEEE-SA Content Production and Management
Kathryn Bennett
IEEE-SA Technical Program Operations
viii Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
Introduction
This introduction is not part of IEEE Std 802.1Qcd™-2015, IEEE Standard for Local and metropolitan area
networks—Bridges and Bridged Networks—Amendment 23: Application Virtual Local Area Network (VLAN)
Type, Length, Value (TLV).
This amendment specifies the protocols, procedures, and management objects for an Application Virtual
Local Area Network (VLAN) identifier (ID) Type, Length, Value (TLV) within the Data Center Bridging
eXchange protocol (DCBX) defined in IEEE Std 802.1Q. This standard also specifies minor extensions and
editorial corrections to the Application Priority TLV.
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 8802-1Q:2016/Amd.2:2018(E)
x Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
Contents
2. Normative references . 2
5. Conformance . 3
38. Data Center Bridging eXchange protocol (DCBX) . 4
38.1 Overview. 4
Annex A (normative) PICS proforma—Bridge implementations . 5
A.35 Data Center Bridging eXchange protocol (DCBX). 5
Annex B (normative) PICS proforma—End station implementations . 6
B.14 Data Center Bridging eXchange protocol (DCBX). 6
Annex D (normative) IEEE 802.1 Organizationally Specific TLV. 7
D.1 Requirements of the IEEE 802.1 Organizationally Specific TLV sets. 7
D.2 Organizationally Specific TLV definitions. 8
D.4 PICS proforma for IEEE 802.1 Organizationally Specific TLV extensions . 12
D.5 IEEE 802.1/LLDP extension MIB. 12
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
List of figures
Figure D-12—Application Priority TLV format . 8
Figure D-15—Application VLAN TLV format . 9
xii Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
List of tables
Table D-1— IEEE 802.1 Organizationally Specific TLVs specified in this standard . 7
Table D-8—Application Priority Table Entry format . 8
Table D-9—Sel field values . 9
Table D-12—Application VLAN Table Entry format .10
Table D-13—Sel field values . 11
Table D-14—IEEE 802.1 extension MIB object group conformance requirements. 12
Table D-15—IEEE 802.1/LLDP extension MIB object cross reference. 12
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)


IEEE Standard for 
Local and metropolitan area networks—
Bridges and Bridged Networks
Amendment 23: Application Virtual Local Area
Network (VLAN) Type, Length, Value (TLV)
IMPORTANT NOTICE: IEEE Standards documents are not intended to ensure safety, health, or
environmental protection, or ensure against interference with or from other devices or networks.
Implementers 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.
This IEEE document is made available for use subject to important notices and legal disclaimers. These
notices and disclaimers appear in all publications containing this document and may be found under the
heading “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.org/IPR/
disclaimers.html.
(This amendment is based on IEEE Std 802.1Q-2014.)
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 italic. 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. 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 8802-1Q:2016/Amd.2:2018(E)
IEEE LOCAL AND METROPOLITAN AREA NETWORKS
Std 802.1Qcd-2015
2. Normative references
Insert the following reference after IETF RFC 2205 and before IETF RFC 2578 in the list in Clause 2.
IETF RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers,
Nichols, K., Blake, S., Baker, F. and Black, D.
2 Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
AMENDMENT 23: APPLICATION VLAN TLV IEEE
Std 802.1Qcd-2015
5. Conformance
5.4.1.7 DCBX Bridge requirements
Insert item g) into the lettered list in 5.4.1.7 as follows:
A device supporting DCBX shall
a) Support Link Layer Discovery Protocol (LLDP) transmit and receive mode (IEEE Std 802.1AB).
b) Support the DCBX ETS Configuration Type, Length, Value (TLV) (D.2.9).
c) Support the ETS Recommendation TLV (D.2.10).
d) Support the Priority-based Flow Control Configuration TLV (D.2.11).
e) Support the Application Priority TLV (D.2.12).
f) Support the asymmetric and symmetric DCBX state machines (38.4).
g) Support the Application VLAN TLV (D.2.15).
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
IEEE LOCAL AND METROPOLITAN AREA NETWORKS
Std 802.1Qcd-2015
38. Data Center Bridging eXchange protocol (DCBX)
Change items e) and f) and insert a new item g), as follows:
38.1 Overview
This clause details DCBX, which is used by DCB devices to exchange configuration information with
directly connected peers. The protocol may also be used for misconfiguration detection and for
configuration of the peer.
This standard describes the base protocol, which comprises state machines and TLVs for capability
exchange. For each feature that is supported by DCBX, the attributes that are to be exchanged specify
a) The attributes to be exchanged;
b) How the attributes are used for detecting misconfiguration; and
c) What action needs to be taken when a misconfiguration is detected.
The information listed above is specified for the following:
d) ETS;
e) PFC; and
f) Application Priority Configuration TLV.; and
g) Application VLAN TLV.
4 Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
AMENDMENT 23: APPLICATION VLAN TLV IEEE
Std 802.1Qcd-2015
Annex A
(normative)
PICS proforma—Bridge implementations
A.35 Data Center Bridging eXchange protocol (DCBX)
Insert the following entry for the Application VLAN TLV at the end of the table in A.35.
Item Feature Status References Support
DCBX-8 Support the Application VLAN TLV DCBX:M D.2.15 Yes [ ]
Copyright release for PICS proformas: Users of this standard may freely reproduce the PICS proforma in this annex so that it can be
used for its intended purpose and may further publish the completed PICS.
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
IEEE LOCAL AND METROPOLITAN AREA NETWORKS
Std 802.1Qcd-2015
Annex B
(normative)
PICS proforma—End station implementations
B.14 Data Center Bridging eXchange protocol (DCBX)
Insert the following entry for the Application VLAN TLV at the end of the table in B.14.
Item Feature Status References Support
DCBX-8 Support the Application VLAN TLV DCBX:M D.2.15 Yes [ ]
Copyright release for PICS proformas: Users of this standard may freely reproduce the PICS proforma in this annex so that it can be
used for its intended purpose and may further publish the completed PICS.
6 Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
AMENDMENT 23: APPLICATION VLAN TLV IEEE
Std 802.1Qcd-2015
Annex D
(normative)
IEEE 802.1 Organizationally Specific TLVs
D.1 Requirements of the IEEE 802.1 Organizationally Specific TLV sets
The IEEE 802.1 Organizationally Specific TLVs may be supported in conjunction with any of the
destination MAC addresses identified in 7.1 of IEEE Std 802.1AB-2009.
If any IEEE 802.1 Organizationally Specific TLV set is supported, all IEEE 802.1 Organizationally Specific
TLVs that are identified as members of that TLV set shall be supported. All IEEE 802.1 Organizationally
Specific TLVs shall conform to the LLDPDU bit and octet ordering conventions of 8.1 of
IEEE Std 802.1AB-2009.
The currently defined IEEE 802.1 Organizationally Specific TLVs specified in this standard are listed in
Table D-1. Other standards can also define IEEE 802.1 Organizationally Specific TLVs. The “TLV set
name” column identifies the TLV set to which each TLV belongs. Any additions or changes to these TLVs
will be included in this annex.
Insert the following entry for the Application VLAN TLV at the end of Table D-1.
Table D-1— IEEE 802.1 Organizationally Specific TLVs specified in this standard
IEEE 802.1 TLV set TLV
TLV name Feature clause reference
subtype name reference
10 Application VLAN TLV dcbxSet D.2.15 Clause 38
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
IEEE LOCAL AND METROPOLITAN AREA NETWORKS
Std 802.1Qcd-2015
D.2 Organizationally Specific TLV definitions
Change D.2.12 as follows:
D.2.12 Application Priority TLV
The TLV illustrated in Figure D-12 is encoded into each IEEE Std 802.1AB-2009 LLDP message and may
be transmitted by a system in order to indicate the application priority table. This TLV is informational and
used to indicate to a peer station the local configuration.
TLV type = TLV information 802.1 OUI 802.1 Reserved Application Priority Table
127 string length = X 00-80-C2 subtype = 12
7 bits 9 bits 3 octets 1 octet 8 bits Multiple of 3 octets
TLV header TLV information string
Figure D-12—Application Priority TLV format
D.2.12.1 TLV type
A 7-bit integer value occupying the most-significant bits of the first octet of the TLV. Always contains the
value 127.
D.2.12.2 TLV information string length
A 9-bit unsigned integer, occupying the LSB of the first octet of the TLV (the MSB of the TLV information
string length) and the entire second octet of the TLV, containing the total number of octets in the TLV
information string of the Application Priority TLV. This does not count the TLV type and TLV information
string length fields. The length for the Application Priority TLV is variable depending on the number of
Application Priorities specified. The length shall be 5 plus a multiple of 3 octets.
D.2.12.3 Application Priority Table
Table D-8 shows the layout of a 3 octet entry in the Application Priority Table.
Table D-8—Application Priority Table Entry format
Octets: 1 2 3
Priority Reserved Sel Protocol ID
Bits: 8       6 5       4 3       1 8                  1 8                   1
The priority field is a 3-bit unsigned integer indicating the priority for which the Protocol ID is being used.
8 Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
AMENDMENT 23: APPLICATION VLAN TLV IEEE
Std 802.1Qcd-2015
The meaning of the Protocol ID field is determined by the Sel field. Allowed values for the Sel field are
shown in Table D-9.
Table D-9—Sel field values
Sel Value Protocol ID value
0 Reserved
0: Default application priority. For use when application priority is not
otherwise specified.
1–1535: Reserved
1536–65535: An EtherType.
Well Known Port number over TCP, or Steam Control Transmission
Protocol (SCTP).
Well Known Port number over UDP, or Datagram Congestion Control
Protocol (DCCP).
4 Well Known Port number over TCP, SCTP, UDP, or DCCP.
Differentiated Services Code Point (DSCP) value. The 6-bit DSCP
value is stored in bits 1–6 of the low order octet of the Protocol ID field
5 (octet 3 of the Application Priority Table Entry). Bits 7 and 8 and the
high order octet of the Protocol ID field are set to zero. 
(See IETF RFC 2474 for the definition of the DSCP value.)
56–7 Reserved
NOTE—The port numbers shown are for identification (i.e., as assigned by IANA) instead of the actual port numbers
being used in a particular deployment.
Insert a new sublcause D.2.15 after D.2.14. Renumber subsequent tables and figures appropriately.
D.2.15 Application VLAN TLV
The TLV illustrated in Figure D-15 is encoded into each IEEE Std 802.1AB-2009 LLDP message and may
be transmitted by a system in order to indicate the application VLAN table. This TLV is informational and
used to indicate to a peer station the local configuration.
TLV type = TLV information 802.1 OUI 802.1 Application VLAN Table
127 string length = X 00-80-C2 subtype = 16
7 bits 9 bits 3 octets 1 octet Multiple of 4 octets
TLV header TLV information string
Figure D-15—Application VLAN TLV format
D.2.15.1 TLV type
A 7-bit integer value occupying the most significant bits of the first octet of the TLV. Always contains the
value 127.
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
IEEE LOCAL AND METROPOLITAN AREA NETWORKS
Std 802.1Qcd-2015
D.2.15.2 TLV information string length
A 9-bit unsigned integer, occupying the LSB of the first octet of the TLV (the MSB of the TLV information
string length) and the entire second octet of the TLV, containing the total number of octets in the TLV
information string of the Application VLAN TLV. This does not count the TLV type and TLV information
string length fields. The length for the Application VLAN TLV is variable depending on the number of
Application VLANs specified. The length shall be 4 plus a multiple of 4 octets.
D.2.15.3 Application VLAN Table
Table D-12 shows the layout of a 4 octet entry in the Application VLAN Table.
Table D-12—Application VLAN Table Entry format
Octets: 1 2 3 4
Field: VID Reserved Sel Protocol ID
Bits: 8       1 8       5 4 3       1 8                   1 8                   1
The VID field is a 12-bit unsigned integer indicating the VID of the VLAN for which the Protocol ID is
being used.
The meaning of the Protocol ID field is determined by the Sel field. Allowed values for the Sel field are
shown in Table D-13.
The Application VLAN TLV may be exchanged between EVB station ERs (5.24.1) and EVB Bridges (5.23)
with LLDP using the Nearest Customer Bridge address. This allows ERs sharing a LAN using S-channels
(40.2) to use different VLANs for the same application.
NOTE 1—The Application VLAN TLV allows multiple VLANs to be associated with an application on a port. Issues
involved with using multiple VLANs for an application on a port, such as resolving which IP subnetwork corresponds to
which VLAN, are beyond the scope of this standard.
NOTE 2—Selection of different IEEE 802.1 paths may use different VLANs, which could be associated with different
quality of service levels. This TLV may not apply to deployment cases where the VID is implied by other attributes of
the frame, for example, by the IP subnet of the source IP address.
10 Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
AMENDMENT 23: APPLICATION VLAN TLV IEEE
Std 802.1Qcd-2015
Table D-13—Sel field values
Sel Value Protocol ID value
0 Reserved
0: PVID. For use when an application VLAN is not otherwise specified.
1 1–1535: Reserved
1536–65535: An EtherType.
2 Well Known Port number over TCP, or SCTP.
3 Well Known Port number over UDP, or DCCP.
4 Well Known Port number over TCP, SCTP, UDP, or DCCP.
Differentiated Services Code Point (DSCP) value. The 6-bit DSCP
value is stored in bits 1–6 of the low order octet of the Protocol ID field
5 (octet 4 of the Application VLAN Table Entry). Bits 7 and 8 and the
high order octet of the Protocol ID field are set to zero. 
(See IETF RFC 2474 for the definition of the DSCP value.)
6–7 Reserved
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
IEEE LOCAL AND METROPOLITAN AREA NETWORKS
Std 802.1Qcd-2015
D.4 PICS proforma for IEEE 802.1 Organizationally Specific TLV extensions
D.4.3 Major capabilities and options
Change the dcbxtlv entry in the table in D.4.3 as follows:
Item Feature Status References Support
dcbxtlv Is each TLV in the IEEE 802.1
DCBX TLV set
implemented?
ETS Configuration TLV dcbxSet:M D.2.9 Yes [ ]
ETS Recommendation TLV dcbxSet:M D.2.10 Yes [ ]
Priority-based Flow Control  dcbxSet:M D.2.11 Yes [ ]
Configuration TLV
Application Priority TLV dcbxSet:M D.2.12 Yes [ ]
Application VLAN TLV dcbxSet:M D.2.15 Yes [ ]
D.5 IEEE 802.1/LLDP extension MIB
D.5.2 Structure of the IEEE 802.1/LLDP extension MIB
Insert the following entry at the end of Table D-14 (renumbered from Table D-12) for the MIB group
lldpXdot1dcbxApplicationVlanGroup.
Table D-14—IEEE 802.1 extension MIB object group conformance requirements
MIB group Rx mode Tx mode Tx/Rx mode
lldpXdot1dcbxApplicationVlanGroup DCBX:M DCBX:M DCBX:M
Change Table D-15 (renumbered from Table D-13) by adding the following entries for the Application
VLAN TLV MIB objects at the end of each dcbx extension group section as shown. (Only the dcbx
extension group sections of the table are shown here.)
Table D-15—IEEE 802.1/LLDP extension MIB object cross reference
MIB table MIB object LLDP reference
a
lldpXdot1dcbxConfig extension group
lldpXdot1dcbxConfigETSConfigurationEntry
lldpXdot1dcbxConfigETSConfigurationTxEnable D.2.9
lldpXdot1dcbxConfigETSRecommendationTable
lldpXdot1dcbxConfigETSRecommendationTxEnable D.2.10
lldpXdot1dcbxConfigPFCTable
lldpXdot1dcbxConfigPFCTxEnable D.2.11
lldpXdot1dcbxConfigApplicationPriorityTable
12 Copyright © 2015 IEEE. All rights reserved.

ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
AMENDMENT 23: APPLICATION VLAN TLV IEEE
Std 802.1Qcd-2015
Table D-15—IEEE 802.1/LLDP extension MIB object cross reference (continued)
MIB table MIB object LLDP reference
lldpXdot1dcbxConfigApplicationPriorityTxEnable
lldpXdot1dcbxConfigApplicationVlanTable
lldpXdot1dcbxConfigApplicationVlanTxEnable D.2.15
a
lldpXdot1dcbxLocalData extension group
lldpXdot1dcbxLocETSBasicConfigurationTable
lldpXdot1dcbxLocETSConCreditBasedShaperSupport D.2.9.4
lldpXdot1dcbxLocETSConMaxTC D.2.9.5
lldpXdot1dcbxLocETSConWilling D.2.9.3
lldpXdot1dcbxLocETSConTrafficClassBandwidthTable D.2.9.7
lldpXdot1dcbxLocETSConTrafficSelectionAlgorithmTable D.2.9.8
lldpXdot1dcbxLocETSConPriorityAssignmentTable
lldpXdot1dcbxLocETSConPriority D.2.9.6
lldpXdot1dcbxLocETSConTrafficClass D.2.9.6
lldpXdot1dcbxLocETSRecommendationTable
lldpXdot1dcbxLocETSRecoTrafficClassBandwidthTable D.2.10.4
lldpXdot1dcbxLocETSRecoTrafficSelectionAlgorithmTable
lldpXdot1dcbxLocETSRecoTSAPriority D.2.10.5
lldpXdot1dcbxLocETSRecoTrafficSelectionAlgorithm D.2.10.5
lldpXdot1dcbxLocPFCBasicTable
lldpXdot1dcbxLocPFCWilling D.2.11.3
lldpXdot1dcbxLocPFCMBC D.2.11.4
lldpXdot1dcbxLocPFCCap D.2.11.5
lldpXdot1dcbxLocPFCEnableTable
lldpXdot1dcbxLocPFCEnablePriority D.2.11.6
lldpXdot1dcbxLocPFCEnableEnabled D.2.11.6
lldpXdot1dcbxLocApplicationPriorityAppTable
lldpXdot1dcbxLocApplicationPriorityAESelector D.2.12.3
lldpXdot1dcbxLocApplicationPriorityAEProtocol D.2.12.3
lldpXdot1dcbxLocApplicationPriorityAEPriority D.2.12.3
lldpXdot1dcbxLocApplicationVlanAppTable
lldpXdot1dcbxLocApplicationVlanAESelector D.2.15.3
lldpXdot1dcbxLocApplicationVlanAEProtocol D.2.15.3
ISO/IEC/IEEE 8802-1Q:2016/Amd.2:2018(E)
IEEE LOCAL AND METROPOLITAN AREA NETWORKS
Std 802.1Qcd-2015
Table D-15—IEEE 802.1/LLDP extension MIB object cross reference (continued)
MIB table MIB object LLDP reference
lldpXdot1dcbxLocApplicationVlanAEVlanId D.2.15.3
a
lldpXdot1dcbxRemoteData extension group
lldpXdot1dcbxRemETSBasicConfigurationTable
lldpXdot1dcbxRemETSConCreditBasedShaperSupport D.2.9.4
lldpXdot1dcbxRemETSConMaxTC D.2.9.5
lldpXdot1dcbxRemETSConWilling D.2.9.3
lldpXdot1dcbxRemETSConTrafficClassBandwidthTable D.2.9.7
lldpXdot1dcbxRemETSConTrafficSelectionAlgorithm- D.2.9.8
Table
lldpXdot1dcbxRemETSConPriorityAssignmentTable
lldpXdot1dcbxRemETSConPriority D.2.9.6
lldpXdot1dcbxRemETSConTrafficClass D.2.9.6
lldpXdot1dcbxRemETSRecommendationTable
lldpXdot1dcbxRemETSRecoTrafficClassBandwidthTable D.2.10.4
lldpXdot1dcbxRemETSRecoTrafficSelectionAlgorithmTable
lldpXdot1dcbxRemETSRecoTSAPriority D.2.10.5
lldpXdot1dcbxRemETSRecoTrafficSelectionAlgorithm D.2.10.5
lldpXdot1dcbxRemPFCBasicTable
lldpXdot1dcbxRemPFCWilling D.2.11.3
lldpXdot1dcbxRemPFCMBC D.2.11.4
lldpXdo
...