ISO/IEC/IEEE 8802-1Q:2020/Amd 3:2021

INTERNATIONAL ISO/IEC/
STANDARD IEEE
8802-1Q
Second edition
2020-08
AMENDMENT 3
2021-09
Telecommunications and exchange
between information technology
systems — Requirements for local and
metropolitan area networks —
Part 1Q:
Bridges and bridged networks
AMENDMENT 3: Virtual station interface
(VSI) discovery and configuration
protocol (VDP) extension to support
network virtualization overlays over
layer 3 (NVO3)
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 3
Reference number
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
©
IEEE 2019
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)

© IEEE 2019
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
ii © IEEE 2019 – All rights reserved

ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(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.
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 ISO/IEC documents 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.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details
of any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC list of patent
declarations received (see patents.iec.ch).
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:2020/Amd 3 was prepared by the LAN/MAN of the IEEE Computer Society (as
IEEE Std 802.1Qcy-2019) 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 2019 – All rights reserved iii

IEEE Std 802.1Qcy™-2019
(Amendment to IEEE Std 802.1Q™-2018
as amended by IEEE Std 802.1Qcp™-2018
and IEEE Std 802.1Qcc™-2018)
IEEE Standard for 
Local and Metropolitan Area Networks—
Bridges and Bridged Networks
Amendment 32: 
Virtual Station Interface (VSI) Discovery and
Configuration Protocol (VDP) Extension to
Support Network Virtualization Overlays 
Over Layer 3 (NVO3)
Sponsor
LAN/MAN Standards Committee 
of the 
IEEE Computer Society
Approved 21 March 2019
IEEE-SA Standards Board
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
Abstract: Extensions to the Virtual Station Interface (VSI) Discovery and Configuration Protocol
(VDP) to support using the protocol between an end station and a device doing encapsulation/
decapsulation for Network Virtualization Overlays Over Layer 3 (NVO3) are specified in this
amendment to IEEE Std 802.1Q-2018. The extensions include adding format types [e.g., Internet
Protocol (IP) addresses] and enhancing indication of migration events.
Keywords: amendment, IEEE 802.1Q™, IEEE 802.1Qcy™, NVO3, VDP extension, VDP IP
address extension
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 4 June 2019. Printed in the United States of America.
IEEE and IEEE 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by The Institute of Electrical and Electronics
Engineers, Incorporated.
PDF: ISBN 978-1-5044-5669-2 STD23619
Print: ISBN 978-1-5044-5670-8 STDPD23619
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.
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(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 Notices
and Disclaimers Concerning IEEE Standards Documents.” They can also be obtained on request from IEEE or viewed at
https://standards.ieee.org/ipr/disclaimers.html.
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. IEEE Standards are documents developed through scientific, academic, and
industry-based technical working groups. Volunteers in IEEE working groups 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 Standards do not guarantee or ensure safety, security, health, or environmental protection, or ensure against
interference with or from other devices or networks. 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.
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 disclaim s
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 O F
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.
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.
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
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 considere d
to be, or be relied upon as, a formal position of IEEE. At lectures, symposia, seminars, or educational courses, a n
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, IEE E
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, b y
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.
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. T o
arrange for payment of licensing fees, please contact Copyright Clearance Center, Customer Service, 222 Rosewood
Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for
educational classroom use can also be obtained through the Copyright Clearance Center.
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
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. A current 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 no t
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 https://ieeexplore.ieee.org or contact IEEE
at the address listed previously. For more information about the IEEE SA or IEEE’s standards development process,
visit the IEEE-SA Website at https://standards.ieee.org.
Errata
Errata, if any, for all IEEE standards can be accessed on the IEEE-SA Website at the following URL: https://
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 o f
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 https://standards.ieee.org/about/
sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to gran t
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 infringemen t
of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards
Association.
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
Participants
At the time this amendment was submitted to the IEEE-SA Standards Board for approval, the IEEE 802.1
Working Group had the following membership:
Glenn Parsons, Chair
John Messenger, Vice Chair
János Farkas, Chair, Time Sensitive Networking Task Group
Yizhou Li, Editor
Paul Bottorff, Editor
Ralf Assmann Mark Hantel Maximilian Riegel
Shenghua Bao Marc Holness Jessy Rouyer
Jens Bierschenk Satoko Itaya Atsushi Sato
Steinar Bjornstad Lokesh Kabra Frank Schewe
Christian Boiger Michael Karl Michael Seaman
Stephan Kehrer
Radhakrishna Canchi Johannes Specht
David Chen Hajime Koto
Patricia Thaler
Feng Chen Christophe Mangin Paul Unbehagen
Weiying Cheng Scott Mansfield Xinyuan Wang
Paul Congdon Kenichi Maruhashi Tongtong Wang
Rodney Cummings James McIntosh Hao Wang
Hesham Elbakoury Tero Mustala Karl Weber
Tomoki Ohsawa
Norman Finn Brian Weis
Geoffrey Garner Hiroshi Ohue Ludwig Winkel
Eric Gray Donald R. Pannell Jordon Woods
Craig Gunther Walter Pienciak Takahiro Yamaura
Marina Gutierrez Michael Potts Xiang Yu
Stephen Haddock Wei Qiu Nader Zein
Karen Randall
The following members of the individual balloting committee voted on this amendment. Balloters may have
voted for approval, disapproval, or abstention.
Thomas Alexander Noriyuki Ikeuchi Bansi Patel
Butch Anton Atsushi Ito Clinton Powell
Stefan Aust Raj Jain Adee Ran
Harry Bims Sangkwon Jeong Alon Regev
Paul Bottorff Piotr Karocki Maximilian Riegel
Nancy Bravin Stuart Kerry Robert Robinson
Demetrio Bucaneg Yongbum Kim Jessy Rouyer
William Byrd Hyeong Ho Lee Manikantan Srinivasan
Xin Chang Li Li Thomas Starai
De Chen Xiuyan Li Walter Struppler
Keith Chow Xiaohui Liu Patricia Thaler
Marc Emmelmann Michael Lynch Mark-Rene Uchida
Elvis Maculuba
János Farkas Dmitri Varsanofiev
Yukihiro Fujimoto Roger Marks George Vlantis
Eric W. Gray John Messenger Khurram Waheed
Randall Groves Nick S. A. Nikjoo Hung-Yu Wei
Marco Hernandez Satoshi Obara Andreas Wolf
Werner Hoelzl Robert O’Hara Oren Yuen
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
When the IEEE-SA Standards Board approved this amendment on 21 March 2019, it had the following
membership:
Gary Hoffman, Chair
Ted Burse, Vice Chair
Jean-Philippe Faure, Past Chair
Konstantinos Karachalios, Secretary
Masayuki Ariyoshi David J. Law Annette D. Reilly
Stephen D. Dukes Joseph Levy Dorothy Stanley
J. Travis Griffith Howard Li Sha Wei
Guido Hiertz Xiaohui Liu Phil Wennblom
Christel Hunter Kevin Lu Philip Winston
Howard Wolfman
Joseph L. Koepfinger* Daleep Mohla
Feng Wu
Thomas Koshy Andrew Myles
Jingyi Zhou
John D. Kulick
*Member Emeritus
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
Introduction
This introduction is not part of IEEE Std 802.1Qcy-2019, IEEE Standard for Local and Metropolitan Area Networks—
Bridges and Bridged Networks—Amendment 32: Virtual Station Interface (VSI) Discovery and Configuration Protocol
(VDP) Extension to Support Network Virtualization Overlays over Layer 3 (NVO3).
This amendment to IEEE Std 802.1Q-2018 provides extensions to the Virtual Station Interface (VSI)
Discovery and Configuration Protocol (VDP) to support using the protocol between an end station and a
device doing encapsulation/decapsulation for Network Virtualization Overlays Over Layer 3 (NVO3). The
extensions include adding format types [e.g., Internet Protocol (IP) addresses] and enhancing indication of
migration events.
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
USA
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
Contents
1.Overview. 12
1.3 Introduction. 12
2.Normative references. 13
3.Definitions . 14
4.Abbreviations. 15
5.Conformance. 16
5.2 Conformant components and equipment . 16
5.31 VDP-NVO3 requirements.16
5.31.1 VDP-NVO3 nNVE requirements . 16
5.31.2 VDP-NVO3 tNVE requirements . 17
12.Bridge management . 18
12.3 Data types . 18
12.26 Edge Virtual Bridging (EVB) management. 19
12.26.3VSI table entry . 19
40.Edge Virtual Bridging (EVB) . 21
40.4 EVB status parameters. 21
40.4.4 EVBMode = NVO3 . 21
40.5 EVB Status Parameter for NVO3 Mode Support . 21
40.5.1 NVERole = nNVE . 21
40.5.2 NVERole = tNVE . 22
41.VSI Discovery and Configuration Protocol (VDP) . 23
41.2 VDP association TLV definitions. 23
41.2.3 Status . 23
41.2.9 Filter Info field . 25
41.2.10VDP TLV type and Sstatus semantics . 28
Annex A (normative) PICS proforma—Bridge implementations . 29
A.5 Major capabilities . 29
A.51 VDP for NVO3 nNVE Devices . 29
A.52 VDP for NVO3 tNVE Devices. 30
Annex D (normative) IEEE 802.1 Organizationally Specific TLVs . 32
D.2 Organizationally Specific TLV definitions. 32
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
Figures
Figure 41-7 GroupID/VID/IPv4 filter format. 26
Figure 41-8 GroupID/MAC/VID/IPv4 filter format. 27
Figure 41-9 GroupID/VID/IPv6 filter format. 27
Figure 41-10 GroupID/MAC/VID/IPv6 filter format. 28
Figure D-12 EVB TLV format . 32
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
Tables
Table 12-25 VSI table entry . 19
Table 12-26 VSI MAC/VLAN table entry. 20
Table 41-2 Flag values in VDP requests. 24
Table 41-3 Error types in VDP responses. 24
Table 41-4 Flag values in VDP responses . 25
Table 41-6 Filter Info format values . 25
Table D-9 RRSAT flag values and meanings . 35
Table D-10 EVB Mode values. 36
Table D-11 NVE Role values . 36
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Standard for 
Local and Metropolitan Area Networks—
Bridges and Bridged Networks
Amendment 32: 
Virtual Station Interface (VSI) Discovery and
Configuration Protocol (VDP) Extension to
Support Network Virtualization Overlays 
Over Layer 3 (NVO3)
(This amendment is based on IEEE Std 802.1Q™-2018, as amended by IEEE Std 802.1Qcp™-2018 and
IEEE Std 802.1Qcc™-2018.)
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 strike through (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.
1. Overview
1.3 Introduction
Change the second to last paragraph of 1.3 as follows and renumber the subsequent list items
accordingly:
This standard specifies protocols, procedures, and managed objects that
ck) Allow for the filtering and policing of individual traffic streams.
cl) Provide for Network Virtualization Overlays over Layer 3 (NVO3) related port configuration.
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:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
2. Normative references
Insert the following references into Clause 2 in alphanumeric order:
IETF RFC 7365, Framework for Data Center (DC) Network Virtualization, October 2014.
IETF RFC 8394, Split Network Virtualization Edge (Split-NVE) Control Plane Requirements, May 2018.
IETF documents (e.g., RFCs) are available from the Internet Engineering Task Force (https://tools.ietf.org/html/).
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
3. Definitions
Change the following definitions of Clause 3 as specified:
3.70 downlink relay port (DRP): A port of an edge relay (ER) that is capable of supporting at least one
Virtual Station Interface (VSI). For NVO3 a port of a tNVE that is capable of supporting at least one NVO3
Tenant Station Interface (TSI) (see IETF RFC 8394).
3.255 Station-facing Bridge Port (SBP): A Bridge Port that supports the Edge Virtual Bridging (EVB)
status parameters with an EVBMode parameter value of “EVB Bridge”. For NVO3 a port of an nNVE that
supports VDP.
NOTE—See 40.4.
3.296 Virtual Station Interface (VSI): An interface to a virtual station that is attached to a downlink relay
port (DRP) of an edge relay (ER). For NVO3 a VSI is equivalent to an NVO3 Tenant Station Interface (TSI)
(see IETF RFC 8394).
Insert the following definitions into Clause 3 in alphabetic order, number them appropriately, and
renumber the subsequent terms in the clause accordingly:
3.x Network Virtualization Edge (NVE): A term as defined in IETF RFC 7365.
3.x Network Virtualization Overlays over Layer 3 (NVO3): A framework conforming t o
IETF RFC 7365.
3.x nNVE: A term as defined in IETF RFC 8394.
3.x tNVE: A term as defined in IETF RFC 8394.
3.x Virtual Network Instance (VNI): A term as defined in IETF RFC 7365.
3.x Virtual Network Instance Identifier (VNI ID): A 3-octet identifier for a VNI.
Information about references can be found in Clause 2.
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
4. Abbreviations
Insert the following abbreviations into Clause 4 in alphabetic order:
NVE Network Virtualization Edge
NVO3 Network Virtualization Overlays over Layer 3
VNI Virtual Network Instance
VNI ID Virtual Network Instance Identifier
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
5. Conformance
5.2 Conformant components and equipment
Change 5.2 as follows:
This subclause specifies requirements and options for the following core components:
a) VLAN Bridge component (5.4)
b) MAC Bridge component (5.13)
for the following components that use that core functionality:
c) Customer VLAN (C-VLAN) component (5.5)
d) Service VLAN (S-VLAN) component (5.6)
e) I-component (5.7)
f) B-component (5.8)
g) TPMR component (5.15)
h) T-component (5.17)
i) Edge relay (ER) (5.24.1)
and for the following systems that include instances of the above components:
j) C-VLAN Bridge (5.9)
k) S-VLAN Bridge (5.10.1)
l) Provider Edge Bridge (5.10.2)
m) Backbone Edge Bridge (BEB) (5.12)
n) MAC Bridge (5.14)
o) TPMR (5.16)
p) Edge Virtual Bridging (EVB) Bridge (5.23)
q) EVB station (5.24)
r) TSN CNC station (5.29)
s) VDP-NVO3 (5.31)
NOTE—Both S-VLAN Bridges and Provider Edge Bridges are examples of Provider Bridges.
Insert the following subclause (5.31 and its subclauses) after 5.29 (subclause 5.30 is reserved for a future
amendment):
5.31 VDP-NVO3 requirements
In the Split-NVE scenario, the nNVE implements the bridge role VDP and tNVE implements the station role
VDP. While the nNVE and tNVE share the VDP functionality of an EVB Bridge and an EVB Station, their
conformance requirements are different. This clause lists the conformance requirements for nNVE and
tNVE to operate VDP in the Split-NVE scenario.
5.31.1 VDP-NVO3 nNVE requirements
A conformant VDP-NVO3 nNVE implementation shall
a) Support the Bridge role of VDP on each SBP (Clause 41).
b) Support assignment of VIDs to GroupIDs (41.2.9).
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
A conformant VDP-NVO3 nNVE implementation may
c) Support the functionality of a C-VLAN component (5.5).
d) Support at least one SBP on the C-VLAN component (Clause 40).
e) Support an LLDP nearest Customer Bridge database (Clause 40).
f) Support the EVB status parameters for EVBMode = NVO3 Mode (40.4.4) and NVERole = nNVE
(40.5.1).
g) Support the EVB Bridge status parameters about IPv4 and IPv6 address capability (D.2.12.3).
h) Support the EVB TLV on each SBP (D.2.12).
i) Support ECP on each SBP (Clause 43).
j) Support the use of the M, S and N bits in VDP (41.2.3).
k) Support the use of IP addresses in VDP filter info format (41.2.9).
5.31.2 VDP-NVO3 tNVE requirements
A conformant VDP-NVO3 tNVE implementation shall
a) Support the station role of VDP for each URP (Clause 41).
b) Support assignment of VIDs to GroupIDs (41.2.9).
A conformant VDP-NVO3 tNVE implementation may
c) Support one ER (5.23.1, Clause 40).
d) Support an LLDP nearest Customer Bridge database (Clause 40).
e) Support the EVB status parameters for EVBMode = NVO3 Mode (40.4.4) and NVERole = tNVE
(40.5.2).
f) Support the EVB station status parameters about IPv4 and IPv6 address capability (D.2.12.4).
g) Support the EVB TLV on each URP (D.2.12).
h) Support ECP on each URP (Clause 43).
i) Support the use of the M, S and N bits in VDP (41.2.3).
j) Support the use of IP addresses in VDP filter info format (41.2.9).
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
12. Bridge management
12.3 Data types
Change 12.3 as follows:
This subclause specifies the semantics of operations independent of their encoding in management protocol.
The data types of the parameters of operations are defined only as required for that specification.
The following data types are used:
a) Boolean.
b) Enumerated, for a collection of named values.
c) Unsigned, for all parameters specified as “the number of” some quantity, and for spanning tree
priority values that are numerically compared. When comparing spanning tree priority values, the
lower number represents the higher priority value.
d) MAC address.
e) Latin1 String, as defined by ANSI X3.159, for all text strings.
f) Time Interval, an Unsigned value representing a positive integral number of seconds, for all
spanning tree protocol timeout parameters.
g) Counter, for all parameters specified as a “count” of some quantity. A counter increments and wraps
with a modulus of 2 to the power of 64.
h) MRP Time Interval, an Unsigned value representing a positive integral number of centiseconds, fo r
all MRP timeout parameters.
i) Port Number, an Unsigned value assigned to a Port as part of a Port Identifier. Valid Port Numbers
are in the range 1 through 4095.
j) Port Priority, an Unsigned value used to represent the priority component of a Port Identifier. Vali d
Port Priorities are in the range 0 through 240, in steps of 16.
k) Bridge Priority, an Unsigned value used to represent the priority component of a Bridge Identifier.
Valid Bridge Priorities are in the range 0 through 61440, in steps of 4096.
l) ComponentID, an unsigned value used to uniquely identify the management objects for a particular
VLAN Bridge component (12.2, Clause 8, 5.4) within a system (such as a BEB) comprising
multiple such components. ComponentIDs start at 1 and go through 4294967295. If the system has a
single component it will have a ComponentID equal to 1.
m) ComponentType, an enumerated list used to classify a particular VLAN Bridge component within a
system comprising multiple components.
n) Port Index, a handle, unique within a system, that identifies a port.
o) PIP Index, a Port Index for a PIP.
p) Percentage.
q) ECT-ALGORITHM. A 4-byte unsigned identifier. Used as a worldwide unique definition of an
Equal Cost Tree (ECT) Algorithm, the first 3 bytes are expected to be taken from the OUI or CID
space for the organization that has defined the algorithm. The last byte is allocated by that
organization.
r) SPSourceID. A 20-bit Unsigned identifier. Used to represent a node uniquely within an SPT Domain
(27.10).
s) Timer exp, an unsigned value from 0–31 representing a positive integer for the exponent of 2, which
forms the multiplier of 10 µs, used for EVB protocol timeout parameters.
NOTE—For example, a value of 4 represents 2  10 µs, or 160 µs.
t) Boolean array, an array of Boolean values.
u) IP Address, an IPv4 address, IPv6 address, or null for no IP address.
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
12.26 Edge Virtual Bridging (EVB) management
12.26.3 VSI table entry
Change 12.26.3 as follows:
Each EVB system maintains a table of the active VSIs. The structure of a VSI table entry is shown i n
Table 12-25. This read-only table provides the current operation parameters of each VSI along with the VDP
state associated with the VSI. The table is keyed on the SBP’s or URP’s ComponentID and Port Number and
on the VSIID. The operation that can be performed on the VSI table is as follows:
a) Read entry for a ComponentID, Port Number and VSIID
Table 12-25—VSI table entry
Operations
b
Name Data type Conformance References
a
supported
evbVsiComponentID ComponentID R BE 12.4.1.5
evbVsiPortNumber Port Number R BE 12.4.2
evbVsiIDType enumerated R BE 41.2.6,
Table 41-5
evbVsiID Latin1 String R BE 41.2.7
(SIZE(16))
evbVsiTimeSinceCreate time interval R BE Clause 41
evbVsiVdpOperCmd enumerated R BE 41.2.1,
Table 41-1
evbVsiOperRevert Boolean R BE 41.2.3
evbVsiOperHard Boolean R BE 41.2.3
evbVsiOperReason unsigned (0.15) R BE 41.2.3
evbVsiMgrID Latin1 String R BE 41.1.3
(SIZE(1))
evbVsiType Latin1 String R BE 41.2.9
(SIZE(3))
evbVsiTypeVersion Latin1 String R BE 41.2.10
(SIZE(1))
evbVsiMvFormat Latin1 String R BE 41.2.8
(SIZE(1))
evbVsiNumMACs unsigned R BE 41.2.9
evbVdpMachineState enumerated R BE 41.5.5.14
evbVdpCmdsSucceeded counter R BE 41.5
evbVdpCmdsFailed counter R BE 41.5
evbVdpCmdsReverts counter R BE 41.5
a
R = Read-only access; RW = Read/Write access.
b
B = Required for an EVB Bridge system; E = Required for an EVB station system.
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
Each EVB Bridge or EVB station maintains a table of the VID/MACs on each VSI. The structure of a VSI
MAC/VLAN table entry is shown in Table 12-26. This read-only table provides the current GroupID/VID/
MAC assignments for each VSI. The operations that can be performed on the VSI table are as follows:
b) Read entries for a ComponentID, Port Number, and VSIID
c) Read entries for a ComponentID and Port Number
Table 12-26—VSI MAC/VLAN table entry
Operations
b
Name Data type Conformance References
a
supported
evbMvComponentID ComponentID R BE 12.4.1.5
evbMvPortNumber Port Number R BE 12.4.2
evbMvVsiIDType enumerated R BE 41.2.6,
Table 41-5
evbMvVsiID Latin1 String R BE 41.2.7
(SIZE(16))
evbMvVsiGroupID unsigned R BE 41.2.9
evbMvVsiVID unsigned (1.4094) R BE 41.2.9
evbMvVsiMAC MAC address R BE 41.2.9
evbMvVsiIpAddress IP address R 41.2.9
a
R= Read-only access; RW = Read/Write access.
b
B = Required for an EVB Bridge system; E = Required for an EVB station system.
ISO/IEC/IEEE 8802-1Q:2020/Amd.3:2021(E)
IEEE Std 802.1Qcy-2019
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks
Amendment 32: VDP Extension to Support NVO3
40. Edge Virtual Bridging (EVB)
40.4 EVB status parameters
Change 40.4 as follows:
In EVB Bridges and EVB Stations, an EVBMode parameter is associated with each port that provides EVB
functionality. The parameter represent the EVB status of the port.
The EVBMode parameter determines whether EVB functionality is supported, and in what mode. The
parameter can take one of the following three four values:
a) EVB Bridge. The port supports the functionality of an EVB Bridge.
b) EVB station. The port supports the functionality of an EVB station.
c) Not Supported. The port does not support EVB functionality. This value is assumed if the EVB
status parameters are not implemented.
d) NVO3 Mode. The port support
...