ISO/IEC/IEEE 8802-A:2015/Amd 3:2025

International
Standard
ISO/IEC/IEEE
8802-A
First edition
Information technology —
2015-12-15
Telecommunications and
information exchange between
AMENDMENT 3
systems — Local and metropolitan
2025-02
area networks —
Part A:
Overview and architecture
AMENDMENT 3: YANG data model for
EtherTypes
Technologies de l'information — Télécommunications et
échange d'information entre systèmes — Réseaux locaux et
métropolitains —
Partie A: Présentation et architecture
AMENDEMENT 3
Reference number
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
© IEEE 2023
ISO/IEC/IEEE 8802-A:2015/Amd.3: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-A:2015/Amd.3: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 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
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-A:2015/Amd.3 was prepared by the LAN/MAN of the IEEE Computer Society (as IEEE Std
802f-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
IEEE Std 802f™-2023 ®
(Amendment to IEEE Std 802 -2014
as amended by IEEE Std 802c™-2017 and
IEEE Std 802d™-2017)
IEEE Standard for Local and
Metropolitan Area Networks:
Overview and Architecture
Amendment 3: YANG Data Model for
EtherTypes
Developed by the
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 21 September 2023
IEEE SA Standards Board
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
Abstract: The YANG module containing the EtherType information, including a compact human-
readable name and description, for a subset of EtherTypes taken from the IEEE Registration
Authority EtherType public listing is specified in this amendment. This amendment also addresses
errors and omissions in IEEE Std 802 description of existing functionality.
Keywords: BANs, body area networks, EtherTypes, IEEE 802®, IEEE 802f™, IEEE 802
architecture, IEEE 802 reference model, LANs, local area networks, MANs, metropolitan area
networks, object identifiers, PANs, personal area networks, RANs, regional area networks, protocol
development, protocol types, YANG
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 8 December 2023. 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 979-8-8557-0279-8 STD26593
Print: ISBN 979-8-8557-0280-4 STDPD26593
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-A:2015/Amd.3: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.
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.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
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.
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 regu-
latory 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 8802-A:2015/Amd.3: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.
Available at: https://ieeexplore.ieee.org/browse/standards/collection/ieee.
Available at: https://standards.ieee.org/standard/index.html.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
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
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 dis-
crimination 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 determi-
nation 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 recommen-
dations. 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 com-
plying with all appropriate safety, security, environmental, health, and interference protection practices and
all applicable laws and regulations.
Available at: https://standards.ieee.org/about/sasb/patcom/materials.html.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
Participants
At the time this amendment was submitted to the IEEE SA for approval, the IEEE 802.1 Working Group had
the following membership:
Glenn Parsons, Chair
Jessy Rouyer, Vice-Chair
Janos Farkas, Chair, Time-Sensitive Networking Task Group
Craig Gunther, Vice-Chair, Time Sensitive Nwtworking Task Group
Marc Holness, IEEE 802f Technical Editor
Katsuyuki Akizuki Marina Gutierrez Donald R. Pannell
Stephen Haddock Dieter Proell
Konstantinos Alexandris
Venkat Arunarthi Mark Hantel Atsushi Sato
Ralf Assmann Daniel Hopf Frank Schewe
Woojung Huh
Huajie Bao Michael Seaman
Rudy Belliardi Satoko Itaya Maik Seewald
Jeremias Blendin Yoshihiro Ito Ramesh Sivakolundu
Christian Boiger Michael Karl Johannes Specht
Stephan Kehrer
Paul Bottorff Nemanja Stamenic
Radhakrishna Canchi Marcel Kiessling Marius Stanica
Feng Chen Gavin Lai Guenter Steindl
Abhijit Choudhury Yizhou Li Karim Traore
Paul Congdon Joao Lopes Max Turner
Rodney Cummings Lily Lv Balazs Varga
Josef Dorr Christophe Mangin Ganesh Venkatesan
Hesham Elbakoury Scott Mansfield Tongtong Wang
Anna Engelmann Olaf Mater Karl Weber
Thomas Enzinger David McCall Leon Wessels
Donald Fedyk Larry McMillan Ludwig Winkel
Martin Mittelberger
Norman Finn Jordon Woods
Geoffrey Garner Hiroki Nakano Takahiro Yamaura
Craig Gunther Takumi Nomura Nader Zein
Dragan Obradovic
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
The following members of the individual balloting committee voted on this amendment. Balloters may have
voted for approval, disapproval, or abstention.
Piotr Karocki
Thomas Alexander R. K. Rannow
Stephan Kehrer
Butch Anton Maximilian Riegel
Stuart Kerry
Philip E. Beecher Benjamin Rolfe
Christian Boiger Yongbum Kim Jessy Rouyer
William Byrd Jeff Koftinoff Frank Schewe
Paul Cardinal David Kornbau Reinhard Schrage
Steven Carlson David Law Cole Scott
Pin Chang Hyeong Ho Lee Michael Seaman
Aditya Chaudhuri James Lepp Veselin Skendzic
Paul Congdon Joao Lopes Guenter Steindl
Rodney Cummings Greg Luri Walter Struppler
Janos Farkas Michael Lynch Mitsutoshi Sugawara
Donald Fedyk Christophe Mangin Bo Sun
Avraham Freedman Scott Mansfield Max Turner
James Gilb Roger Marks John Vergis
Craig Gunther Jonathon Mclendon James Weaver
Marek Hajduczenia Rajesh Murthy Stephen Webb
Chong Han Satoshi Obara Karl Weber
Xiang He Glenn Parsons Matthias Wendt
Marco Hernandez Bansi Patel Scott Willy
Werner Hoelzl Dev Paul Andreas Wolf
Russell Housley
Arumugam Paventhan Yu Yuan
Yasuhiro Hyakutake Rick Pimpinella Oren Yuen
Pranav Jha Clinton Powell George Zimmerman
Lokesh Kabra Venkatesha Prasad Qiyue Zou
Dieter Proell
When the IEEE SA Standards Board approved this amendment 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 Gui Lin Robby Robson
Guido R. Hiertz Johnny Daozhuang Lin Lei Wang
Yousef Kimiagar Kevin W. Lu F. Keith Waters
Joseph L. Koepfinger* Daleep C. Mohla Karl Weber
Thomas Koshy Andrew Myles Philip B. Winston
John D. Kulick Don Wright
*Member Emeritus
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
Introduction
This introduction is not part of IEEE Std 802f-2023, IEEE Standard for Local and Metropolitan Area Networks:
Overview and Architecture—Amendment 3: YANG Data Model for EtherTypes.
This amendment specifies a YANG module that contains the EtherType information, including a compact
human-readable name and description, for a subset of EtherTypes taken from the IEEE Registration
Authority EtherType public listing. This amendment also addresses errors and omissions in IEEE Std 802
description of existing functionality.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
Contents
2. Normative references. 12
5. Reference models (RMs) . 13
5.3.2.1 Bridges and bridged IEEE 802 networks. 13
5.3.2.3 Resolving topologies with multiple paths. 13
5.3.2.4 Transparent bridging. 13
7. IEEE 802 network management . 14
7.2.2 Management architecture. 14
7.2.3 Managed object definitions. 14
8. MAC addresses . 15
8.2.2 Assignment of universal addresses . 15
8.3 Interworking with 48-bit and 64-bit MAC addresses . 15
9. Protocol identifiers and context-dependent identifiers . 16
9.2 EtherTypes . 16
9.2.1 Format, function, and administration. 16
9.2.1a Public EtherType assignments subset. 16
Annex A (informative) Bibliography . 18
Annex D (informative) List of IEEE standards . 19
Annex F (informative) EtherType listing subset . 20
Annex G (informative) Wake-on-LAN . 34
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Standard for Local and
Metropolitan Area Networks:
Overview and Architecture
Amendment 3: YANG Data Model for
Ethertypes
(This amendment is based on IEEE Std 802®-2014, as previously amended by IEEE Std 802d™-2017 and
IEEE Std 802c™-2017.)
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 either 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
large changes in existing text, subclauses, tables, or figures by removing existing material and replacing it with new ma-
terial. Editorial notes 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-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
2. Normative references
Delete the following normative reference in Clause 2 as follows:
IEEE Std 802.1D™, IEEE Standard for Local and metropolitan area networks—Media Access Control
1,2
(MAC) Bridges.
Insert the following normative reference in the appropriate collating sequence:
IEEE Std 802.1Q™, IEEE Standard for Local and metropolitan area networks—Virtual Bridged Local Area
7, 8
Networks.
The IEEE standards referred to in Clause 2 are trademarks owned by the Institute of Electrical and Electronics Engineers,
Incorporated.
IEEE publications are available from The Institute of Electrical and Electronics Engineers. (https://standards.ieee.org).
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
5. Reference models (RMs)
5.3.2.1 Bridges and bridged IEEE 802 networks
Change the text of the first paragraph in 5.3.2.1 as follows:
Bridges are stations that interconnect multiple access domains. IEEE Std 802.1DQ provides the basic
specification for bridge interworking among IEEE 802 networks. A bridged IEEE 802 network consists of
one or more bridges together with the complete set of access domains that they interconnect. A bridged
IEEE 802 network provides end stations belonging to any of its access domains with the connectivity of a
network that contains the whole set of attached end stations. IEEE Std 802.1Q adds additional capabilities to
the bridge specification in IEEE Std 802.1D including virtual local area networks (VLANs), priorities, and
provider bridging, as described in 5.3.2.5 includes provisions for MAC Bridging, virtual local area networks
(VLANs), priorities and provider bridging.
Change the text in the last paragraph in 5.3.2.1 as follows:
The term switch is often used to refer to some classes of bridge. However, there is no consistent meaning
applied to the distinction between the terms bridge and switch, and IEEE Std 802.1DQ does not make any
such distinction. Hence, this standard only uses the term bridge.
5.3.2.3 Resolving topologies with multiple paths
Change the text in the first paragraph in 5.3.2.3 as follows:
A key aspect of IEEE Std 802.1D and IEEE Std 802.1Q is the specification of the rapid spanning tree
protocol (RSTP), which is used by bridges to configure their interconnections in order to prevent looping
data paths in the bridged IEEE 802 network. If the basic interconnection topology of bridges and networks
contains multiple possible paths between certain points, use of the RSTP blocks some paths in order to
produce a simply connected active topology for the flow of MAC user traffic between end stations. For each
point of attachment of a bridge to a network, the RSTP selects whether MAC user traffic is to be received
and transmitted by the bridge at that point of attachment.
5.3.2.4 Transparent bridging
Change the text in 5.3.2.4 as follows:
IEEE Std 802.1Q specify specifies transparent bridging operation, so called because
IEEE Std 802.1D and
the MAC bridging function does not require the MAC user frames transmitted and received to carry any
additional information relating to the operation of the bridging functions; end-station operation is unchanged
by the presence of bridges.
Information on normative references can be found in Clause 2.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
7. IEEE 802 network management
7.2.2 Management architecture
Change the last paragraph in 7.2.2 as follows:
The Simple Network Management Protocol (SNMP), as described in IETF RFC 3411 [B5], and Network
Configuration Protocol (NETCONF), as described in RFC 6241 [B15], are examples of provides a general-
purpose management protocols that can be used for the management of IEEE 802 network equipment.
7.2.3 Managed object definitions
Change text in 7.2.3 as follows:
In order for an IEEE 802 standard to specify management facilities, it is necessary for it to specify managed
objects that model the operations that can be performed on the communications resources specified in the
standard. The components of a managed object definition are as follows:
a) A definition of the functionality provided by the managed object, and the relationship between this
functionality and the resource to which it relates.
b) A definition of the syntax that is used to convey management operations, and their arguments and
results, in a management protocol.
c) An address that allows the management protocol to specifically communicate with the managed
object in question. In IEEE 802 this is done with an object identifier (OID), as described in
Clause 10, or a Uniform Resource Name (URN), as described in Clause 11.
The functionality of a managed object can be described in a manner that is independent of the protocol that
is used; this abstract definition can then be used in conjunction with a definition of the syntactic elements
required in order to produce a complete definition of the object for use with specific management protocols.
SNMP is used in many cases together with the structure of management information known as SMIv2 (IETF
RFC 2578, IETF RFC 2579 [B3], and IETF RFC 2580 [B4]), which uses a set of macros based on a subset
of ASN.1 for defining managed objects. YANG (IETF RFC 7950) is a data modeling language used to
model configuration data, state data, remote procedure calls, and notifications for network management
protocols.
The choice of notational tools for defining managed objects depends on which of the available management
protocols the standard supports.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
8. MAC addresses
8.2.2 Assignment of universal addresses
Change the last paragraph before Figure 10 in 8.2.2. as follows:
A universal address consists of two parts: the leading bits (24, 28, or 36) are assigned by the IEEE RA with
the U/L bit set to zero and the remaining bits by that assignee. An example of an EUI-48 is shown in
Figure 10. For MA-M and MA-S, the final 4 bits of the assigned number are in a nibble that is not adjacent
to the other bits in the assigned number when displayed with LSB on the left and most significant bit (MSB)
on the right. For example, when using an MA-S to create an EUI-48, the MA-S value is contained in octets
0, 1, 2, 3 and the least most significant nibble four bits of octet 4, and the value assigned by the assignee is
contained in the most least significant nibble four bits of octet 4 and in octet 5.
Change the NOTE in 8.2.4 as follows:
NOTE—While some implementations have used a single EUI-48 or EUI-64 to identify all of the system’s points of
attachment to IEEE 802 networks, this approach does not inherently meet the requirements of IEEE 802.1DQ™ MAC
bridging.
8.3 Interworking with 48-bit and 64-bit MAC addresses
Change the text in 8.3 as follows:
In response to concerns that the EUI-48 space could be exhausted by the breadth of products requiring
unique identifiers, 64-bit MAC addresses were introduced. Initially, new IEEE standards projects that did
not require backward compatibility with EUI-48 were requested to use 64-bit MAC addresses. This led to
some IEEE 802 standards adopting 64-bit MAC addressing, which cannot be bridged onto IEEE 802
networks that use 48-bit MAC addressing. The reason is that the bridging function in IEEE Std 802.1D and
IEEE Std 802.1Q assumes that 48-bit MAC addresses are unique among all the connected networks.
Truncating an 64-bit MAC address into an 48-bit field can lead to two stations having the same 48-bit value.
Instead, traffic between 64-bit and 48-bit MAC addressed networks needs to be routed at a layer above the
DLL.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
9. Protocol identifiers and context-dependent identifiers
9.2 EtherTypes
9.2.1 Format, function, and administration
Change the footnote in the first paragraph of 9.2.1 (the paragraph is shown for convenience of the user)
as follows:
EtherType protocol identification values are assigned by the IEEE RA and are used to identify the
protocol that is to be invoked to process the user data in the frame. An EtherType is a sequence of 2 octets,
interpreted as a 16-bit numeric value with the first octet containing the most significant 8 bits and the second
octet containing the least significant 8 bits. Values in the 0–1535 range are not available for use in order to
retain legacy compatibility with Length field based protocols, e.g., IEEE Std 802.3.
Change the third paragraph in 9.2.1 as follows:
Examples of EtherTypes are 0x0800 and 0x86DD 0x08-00 and 0x86-DD, which are used to identify IPv4
and IPv6, respectively.
Insert the following subclause 9.2.1a, and renumber the existing subclauses accordingly.
9.2.1a Public EtherType assignments subset
The IEEE Registration Authority (RA) provides a public listing of EtherType assignments. Many of these
are for private or proprietary purposes. However, others are incorporated into well-known standards. In
some cases, the IEEE RA Public Listing for an EtherType identifies an assignee without explicitly
identifying the standards in which the use of that EtherType is specified. For ready reference by users and
developers of such standards, Annex F identifies some well-known EtherTypes and the protocols they
identify. This subset is derived by combining the EtherTypes listed in the ietf-ethertypes YANG module
specified in IETF RFC 8519 [B11] with the subset of EtherTypes defined by IEEE 802 Standards (e.g.,
IEEE 802.1Q, 802.3, etc.) and as provided by participants that developed this standard. Information on
products released after that date can be found on the IEEE SA Registration Authority web site: https://
standards.ieee.org/products-programs/regauth/ethertype/ and https://regauth.standards.ieee.org/standards-
ra-web/pub/view.html#registries. The subset in Table F.1 and in F.3 is provided solely for the convenience
of users of this standard and does not constitute an endorsement by IEEE of the listed protocols.
The EtherType public listing includes the following fields, specified by the EtherType assignee:
— Assignment — The hexadecimal representation of the EtherType.
— Assignment Type — The type is EtherType.
— Company Name — The registrant of the Assignment.
— Company Address — The address of the registrant.
— Protocol — A brief protocol description, as provided by the registrant.
This standard includes the following fields in Table F.1 for use by the YANG module:
More information on EtherTypes can be found at http://standards.ieee.org/develop/regauth/llc on the IEEE RA web site, https://stan-
dards.ieee.org/products-programs/regauth/ethertype and https://regauth standards.ieee.org/standards-ra-web/pub/view.html#registries.
The EtherType public listing is the public view of the EtherType registry managed by the Registration Authority (see https://
regauth.standards.ieee.org/).
EtherType is the only assignment type for the records in the EtherType public listing.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
a) Friendly Name — A short alphanumeric name for the Assignment that is unique within the YANG
module in F.2 and is used to enumerate the entry.
b) Short Description — A short description of the assigned protocol per its typical usage.
c) Reference — A reference to a standard associated with the EtherType assignment.
A YANG model representation can be found in F.3.2.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
Annex A
(informative)
Bibliography
Insert the following bibliographical references into Annex A in alphanumeric order:
[B11] IETF RFC 8519, YANG Data Model for Network Access Control Lists (ACLs), March 2019.
[B15] IETF RFC 6241, Network Configuration Protocol (NETCONF), June 2011.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
Annex D
(informative)
List of IEEE 802 standards
Delete the following standard as follows:
IEEE Std 802.1D™, IEEE Standard for Local and metropolitan area networks: Media Access Control
(MAC) Bridges.
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
Insert new Annex F as follow:
Annex F
(informative)
EtherType listing subset
F.1 Introduction
This annex lists the subset of EtherType assignments described in 9.2.1 in tabular form (Table F.1) and in
the form of a YANG module (F.2). This subset is provided solely for the convenience of the users of this
standard and does not constitute an endorsement by IEEE of the listed protocols.
F.2 Tabular format
A subset of EtherType assignments by the IEEE RA is given in Table F.1. Each Friendly Name in Table F.1
is unique and is used as an identifier in the YANG module. The Short Description identifies the protocol,
protocol message, or protocol field that uses the assignment as specified in the Reference, or the EtherType
assignment itself as named in the Reference. Where the Reference specifies more than one name or use
(distinguished for example by sub-type) these are included in the Short Description field.
NOTE—The fields “Friendly Names” and “Short Descriptions” in Table F.1 may include trademarks that are owned by
their respective trademark owners. The information in these fields is provided solely for the convenience of users of this
standard and does not constitute an endorsement by IEEE of those products or the companies producing those products.

a
Table F.1 — EtherType listing subset
EtherType
Assignment Friendly Name Short Description Reference
(HEX)
08-00 ipv4 Internet Protocol version 4 (IPv4) IETF RFC 894
08-06 arp Address Resolution Protocol IETF RFC 826, IETF RFC
(ARP) 7042
08-42 wol Wake-on-LAN IEEE Std 802
22-E2 msp MAC Status Protocol (MSP) IEEE Std 802.1Q
22-E7 cnm Congestion Notification Message IEEE Std 802.1Q
(CNM)
22-E9 cn-tag Congestion Notification Tag (CN- IEEE Std 802.1Q
TAG)
22-EA msrp Multiple Stream Reservation IEEE Std 802.1Q
Protocol (MSRP)
ISO/IEC/IEEE 8802-A:2015/Amd.3:2025(en)
IEEE Std 802f-2023
IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture
Amendment 3: YANG Data Model for EtherTypes
a
Table F.1 — EtherType listing subset  (continued)
EtherType
Assignment Friendly Name Short Description Reference
(HEX)
22-F3 trill Transparent Interconnection of IETF RFC 6325
Lots of Links
60-03 decnet DECnet DNA Routing DECnet DIGITAL Network
Architecture—Ethernet Data
Link Architectural
Specification v1.0.0
80-35 rarp Reverse Address Resolution IETF RFC 903
Protocol
80-9B appletalk Appletalk (Ethertalk) Inside Appletalk, Second
Edition
80-F3 aarp Appletalk Address Resolution Inside Appletalk, Second
Protocol Edition
81-00 c-tag Customer VLAN Tag (C-TAG) IEEE Std 802.1Q
81-37
...