ISO/IEC/IEEE 8802-A:2026

• Abstract:

  This document contains descriptions of the IEEE 802® standards published by the IEEE for frame-based data networks as well as a reference model (RM) for protocol standards. A specification for the identification of public, private, and standard protocols is included.

• Status: Published
• Publication Date: 23-Aug-2026
• 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: 6060 - International Standard published
• Start Date: 24-Aug-2026
• Due Date: 26-Jun-2028
• Completion Date: 24-Aug-2026

• Revises: ISO/IEC/IEEE 8802-A:2015 - Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Part A: Overview and architecture
• Effective Date: 28-Jun-2025
• Revises: ISO/IEC/IEEE 8802-A:2015/Amd 1:2018 - Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Part A: Overview and architecture — Amendment 1: Allocation of Uniform Resource Name (URN) values in IEEE 802® standards
• Effective Date: 28-Jun-2025
• Revises: ISO/IEC/IEEE 8802-A:2015/Amd 3:2025 - Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Part A: Overview and architecture — Amendment 3: YANG data model for EtherTypes
• Effective Date: 28-Jun-2025
• Revises: ISO/IEC/IEEE 8802-A:2015/Amd 2:2019 - Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Part A: Overview and architecture — Amendment 2: Local medium access control (MAC) address usage
• Effective Date: 28-Jun-2025

ISO/IEC/IEEE 8802-A:2026 is an International Standard from ISO, IEC and IEEE for the IEEE 802 family of frame-based local and metropolitan area network standards. ISO/IEC/IEEE 8802-A:2026 gives the overview and architecture for that family, including the IEEE 802 reference model, the relationship to higher-layer protocols, and the rules used to identify public, private and standard protocols. It is the common architectural reference for people who need to understand how IEEE 802 networks, addressing and protocol identification fit together.

What does ISO/IEC/IEEE 8802-A:2026 specify?

ISO/IEC/IEEE 8802-A:2026 specifies the common structure used across IEEE 802 standards for LANs, MANs, PANs and RANs. It describes the IEEE 802 standards family, the reference model for protocol standards, and the identification of public, private and standard protocols.

The document is organized into Clauses 1 to 11 and informative Annexes A to G.

Annex	What it covers
A	Bibliography
B	Reference models for IEEE 802 standards
C	Examples of bit ordering for addresses
D	List of IEEE 802 standards
E	History
F	EtherType listing subset
G	Wake-on-LAN

Clauses 1 to 3 set the scope, the required references, and the terms and abbreviations. Clauses 4 to 11 then cover the IEEE 802 family overview, reference models, general network requirements, network management, MAC addresses, protocol identifiers, OID allocation and URN allocation.

What are the key requirements of ISO/IEC/IEEE 8802-A:2026?

Architecture and interworking

ISO/IEC/IEEE 8802-A:2026 defines the IEEE 802 reference model as the architectural base for end stations and for the wider IEEE 802 family. In practice, this gives implementers the layer boundaries that have to match when equipment from different vendors is expected to interoperate.

• Clause 5 maps the IEEE 802 reference model to the OSI/RM, with the LLC sublayer above the MAC sublayer and the PHY below it. This matters because products have to place functions on the correct side of the service access points.
• Clause 5.3 groups interworking into three cases: PHY interconnection with repeaters, MAC-sublayer interconnection with bridges, and network-layer interconnection with routers. This helps designers choose whether forwarding happens at Layer 1, Layer 2 or above the data link layer.
• Clause 5.3.2 explains bridge operation for bridged networks, including transparent bridging and special cases such as virtual and provider bridging, Time-Sensitive Networking (TSN) and data center networking bridging. That is the part to read when planning a bridged deployment.

Network service and error behavior

ISO/IEC/IEEE 8802-A:2026 sets the baseline service expectations for a bridgeable IEEE 802 network and states the error-performance expectations for wired, optical and wireless media. This is the practical part that matters when a network must carry user traffic with predictable interoperability.

• Clause 6.1 says a bridgeable IEEE 802 network must support the MAC service defined in IEEE Std 802.1AC between MSAPs and, at minimum, the MAC Internal Sublayer Service. For a buyer or engineer, that is the check that a network can participate in IEEE 802 bridging.
• Clause 6.2 distinguishes wired or optical media from wireless media. Wired and optical implementations are held to defined error-performance expectations, while wireless performance is described as variable over time, which affects how testing and acceptance are approached.

Management

ISO/IEC/IEEE 8802-A:2026 separates general-purpose network management from special-purpose management protocols. This matters because not every management need is served by the same protocol stack.

• Clause 7.2 introduces general-purpose IEEE 802 network management, including management functions, management architecture and managed object definitions. In practice, this is the basis for building or evaluating standard management support.
• Clause 7.3 names special-purpose examples such as the Connectivity Fault Management Protocol, the Operations, Administration, and Maintenance (OAM) Protocol, and the Link Layer Discovery Protocol (LLDP). These examples matter when a product needs protocol-specific diagnostics or discovery rather than a generic management framework.

MAC addresses and local allocation

ISO/IEC/IEEE 8802-A:2026 treats MAC addresses as 48-bit or 64-bit identifiers and ties the addressing choice to interoperability and address-space planning. This is one of the main operational sections for network and product designers.

• Clause 8 states that 48-bit MAC addressing is required when interoperability through bridges is needed, while 64-bit addressing may be used when bridged connectivity is not required. That distinction affects whether a product can fit into existing bridged IEEE 802 networks.
• Clause 8.4 says local MAC addresses shall be assigned only as valid Extended Local Identifiers (ELIs), Standard Assigned Identifiers (SAIs) or Administratively Assigned Identifiers (AAIs) under the Structured Local Address Plan (SLAP). This gives a controlled way to assign local addresses without colliding with universal ones.
• Clause 8.6 requires bit-serial transmission to use least-significant-bit-first ordering for each octet of a source or destination address field. That matters for interoperability and for validating captured frames.

Protocol identification

ISO/IEC/IEEE 8802-A:2026 specifies how IEEE 802 networks identify higher-layer protocols in the LLC sublayer. This is the part that lets a receiver know which upper-layer protocol a frame carries.

• Clause 9 recognizes three protocol identifier types: E-Type, L-Type and O-Type. In practice, that gives a product three different ways to map a frame to the correct higher-layer protocol.
• Clause 9.5 defines protocol identification field (PIF) encodings that allow the receiver to identify the field, the identifier type and the identifier value. That matters because the encoding has to be understood even if a bridge transforms the frame format.
• Clause 9.6 introduces context-dependent identifiers, which are intended to be unique only within a well-specified context. This is useful for local or scoped identification schemes such as NUI-48 and NUI-64.

OID and URN allocation

ISO/IEC/IEEE 8802-A:2026 sets common naming rules for management and data-model identifiers used across IEEE 802. This is important for keeping MIBs, registries and YANG models consistent.

• Clause 10 defines an OID hierarchy for IEEE 802 standards under the ISO tree and gives the IEEE 802 working groups responsibility for later arcs. In practice, this avoids clashes when different IEEE 802 standards define their own managed objects.
• Clause 10.4 identifies the older iso(1) std(0) iso8802(8802) root as deprecated. That tells users which OID tree to treat as current.
• Clause 11 defines the IEEE URN form for standards use as urn:ieee:std:{ResourceSpecificString}, with the resourceType value yang for YANG modules. This gives a uniform naming pattern for data models and other standard resources.

What terms does ISO/IEC/IEEE 8802-A:2026 define?

• access domain - A set of stations, media and functional units that use the same MAC protocol to access a common communications channel.
• bridge - A functional unit that interconnects two or more access domains, and in IEEE 802 practice it forwards between bridgeable networks using Layer 2 information.
• bridgeable network - A network that provides the MAC service specified in IEEE Std 802.1AC between two or more MSAPs.
• end station - A functional unit that acts as a source or destination for link-layer data traffic on an IEEE 802 network.
• EtherType - A 2-octet value assigned by the IEEE Registration Authority to provide protocol context for MAC frame interpretation.
• protocol identification field (PIF) - The initial octets prepended to a higher-layer protocol data unit to identify the protocol carried by the frame.
• Structured Local Address Plan (SLAP) - The local MAC address structure that divides local address space into defined identifier types such as ELI, SAI and AAI.
• Uniform Resource Name (URN) - The naming form used in Clause 11 for IEEE standards resources, including YANG-related resources.

Who uses ISO/IEC/IEEE 8802-A:2026?

ISO/IEC/IEEE 8802-A:2026 is used by IEEE 802 working groups, network architects, protocol designers and equipment vendors who need a common architectural basis for IEEE 802 systems. It is also used by teams building bridges, access points, repeaters, routers, management systems, address assignment tools and protocol registries.

In practice, it is relevant in consumer, commercial, educational, governmental and industrial environments, including office automation, multimedia, vehicular communication, process control, robotics, telecommunications and IoT deployments. Buyers and quality managers use it to check whether a product or specification fits a bridged IEEE 802 environment, a local-address scheme, or a YANG, OID or URN naming framework.

What changed in ISO/IEC/IEEE 8802-A:2026 from the previous edition?

• ISO/IEC/IEEE 8802-A:2026 is the second edition and cancels and replaces ISO/IEC/IEEE 8802-A:2015.
• ISO/IEC/IEEE 8802-A:2026 is technically revised.
• ISO/IEC/IEEE 8802-A:2026 revises ISO/IEC/IEEE 8802-A:2015/Amd 1:2018, ISO/IEC/IEEE 8802-A:2015/Amd 2:2019 and ISO/IEC/IEEE 8802-A:2015/Amd 3:2025.
• The introduction states that the revision integrates IEEE Std 802d-2017, IEEE Std 802c-2017 and IEEE Std 802f-2023 into the previous edition.

Which standards are used with ISO/IEC/IEEE 8802-A:2026?

Standard	What it contributes
IEEE Std 802.1Q	Bridges and bridged networks, and related protocol and management uses named in the document
IEEE Std 802.1AC	MAC Service Definition and the MAC Internal Sublayer Service
ISO/IEC/IEEE 8802-2:1998	Logical Link Control (LLC) requirements
IETF RFC 2578	SMIv2 structure for management information and OID use
IETF RFC 3406	URN namespace definition mechanisms
IETF RFC 8069	URN namespace for IEEE
ITU-T Recommendation X.660	OID registration authority procedures and top arcs

Annex B also uses the IEEE 802.3, IEEE 802.11, IEEE 802.15, IEEE 802.16, IEEE 802.21 and IEEE 802.22 reference models as companion material for the different IEEE 802 parts.

What does the ISO/IEC/IEEE 8802-A:2026 document contain?

ISO/IEC/IEEE 8802-A:2026 contains architectural figures for the IEEE 802 reference model, including end-station structure and interconnection models for bridges and routers. It also contains the address architecture, including examples and explanatory material for bit ordering, universal and local MAC addresses, SLAP and group addresses.

The document includes protocol-identification material for EtherTypes, LSAP addresses, O-Type identifiers and PIF encodings. It also contains the OID hierarchy and URN naming rules used by IEEE 802 standards and YANG models.

Annex B collects reference models for IEEE 802.3, 802.11, 802.15, 802.16, 802.21 and 802.22. Annex F provides a tabular EtherType subset and a YANG module view for that subset, while Annex C gives address bit-order examples and Annex D lists the IEEE 802 standards current when the document was completed.

International
Standard
ISO/IEC/IEEE
8802-A
Second edition
Information technology —
2026-08
Telecommunications and
information exchange between
systems — Local and metropolitan
area networks —
Part A:
Overview and architecture
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
Reference number
© IEEE 2025
© IEEE 2025
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: [e-mail]
Website: www.ieee.org
Published in Switzerland
© IEEE 2025 – All rights reserved
ii
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members
of ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
document should be noted.
IEEE Standards documents are developed within 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.
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 was prepared by the LAN/MAN of the IEEE Computer Society (as IEEE Std
802®-2024) 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.
This second edition cancels and replaces the first edition (ISO/IEC/IEEE 8802-A:2015), which has been
technically revised. It also revises the Amendments ISO/IEC/IEEE 8802-A:2015/Amd 1:2018, ISO/IEC/IEEE
8802-A:2015/Amd 2:2019, ISO/IEC/IEEE 8802-A:2015/Amd 3:2025.
A list of all parts in the ISO/IEC/IEEE 8802 series can be found on the ISO and IEC websites.
© IEEE 2025 – All rights reserved
iii
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 2025 – All rights reserved
iv

IEEE Std 802 -2024
(Revision of IEEE Std 802-2014 as amended by
IEEE Std 802d™-2017, IEEE Std 802c™-2017,
and IEEE Std 802f™-2023)
Title Page
IEEE Standard for Local and
Metropolitan Area Networks:
Overview and Architecture
Developed by the
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 11 December 2024
IEEE SA Standards Board ®
Abstract: An overview to the family of IEEE 802 standards is provided in this standard. I t
describes the reference models for the IEEE 802 standards and explains the relationship of these
standards to the higher layer protocols; it specifies the structure of IEEE 802 MAC addresses; i t
specifies identification of public, private, prototype, and standard protocols; it specifies an object
identifier hierarchy used within IEEE 802 for uniform allocation of object identifiers used in IEEE 802
standards; and it specifies a method for higher layer protocol identification. ®
Keywords: BANs, body area networks, EtherTypes, IEEE 802 , 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 identifiers, protocol types
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 21 March 2025. 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.
Object Management Group®, OMG®, UML® and Unified Modeling Language™ are either registered
trademarks or trademarks of Object Management Group, Inc. in the United States and/or other countries.
PDF: ISBN 979-8-8557-1960-4 STD27775
Print: ISBN 979-8-8557-1961-1 STDPD27775
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.

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 (https://standards.ieee.org/ipr/disclaimers.html), 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 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 al l
warranties, express or implied, concerning this standard, including but not limited to the warranties o f
merchantability, fitness for a particular purpose and non-infringement. In addition, IEEE does not warrant o r
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 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.
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 the presenter’s views should be considered the personal views of that individual rather
than the formal position of IEEE, IEEE SA, the Standards Committee, or the Working Group. Statements
made by volunteers may not represent the formal position of their employer(s) or affiliation(s).
Comments on standards
Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of
membership affiliation with IEEE or IEEE SA. However, IEEE does not provide interpretations,
consulting information or advice pertaining to IEEE Standards documents.
Suggestions for changes in documents should be in the form of a proposed change of text, together with
appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is
important that any responses to comments and questions also receive the concurrence of a balance of
interests. For this reason, IEEE and the members of its Societies and subcommittees of the IEEE SA Board
of Governors are not able to provide an instant response to comments, or questions except in those cases
where the matter has previously been addressed. For the same reason, IEEE does not respond to
interpretation requests. Any person who would like to participate in evaluating comments or in revisions to
an IEEE standard is welcome to join the relevant IEEE working group. You can indicate interest in a
working group using the Interests tab in the Manage Profile & Interests area of the IEEE SA myProject
system. An IEEE Account is needed to access the application.
Comments on standards should be submitted using the Contact Us form.
Laws and regulations
Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the
provisions of any IEEE Standards document does not 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.
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.
Copyrights
IEEE draft and approved standards are copyrighted by IEEE under US 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 or 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; [phone]; 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 t o
periodically check for errata .
Patents
IEEE Standards are developed in compliance with the IEEE SA Patent Policy.
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the
Available at: https://ieeexplore.ieee.org/browse/standards/collection/ieee.
Available at: https://standards.ieee.org/standard/index.html.
Available at: https://standards.ieee.org/about/sasb/patcom/materials.html.
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 o r
under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair
discrimination to applicants desiring to obtain such licenses.
Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not
responsible for identifying Essential Patent Claims for which a license may be required, for conducting
inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or
conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing
agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that
determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their
own responsibility. Further information may be obtained from the IEEE Standards Association.
IMPORTANT NOTICE
IEEE Standards do not guarantee or ensure safety, security, health, or environmental protection, or ensure
against interference with or from other devices or networks. IEEE Standards development activities consider
research and information presented to the standards development group in developing any safety
recommendations. Other information about safety practices, changes in technology or technology
implementation, or impact by peripheral systems also may be pertinent to safety considerations durin g
implementation of the standard. Implementers and users of IEEE Standards documents are responsible fo r
determining and complying with all appropriate safety, security, environmental, health, and interference
protection practices and all applicable laws and regulations.
Participants
At the time this standard was completed, the IEEE 802.1 Working Group had the following membership:
Glenn Parsons, Chair
Jessy V. Rouyer, Vice Chair and Recording Secretary
James P. K. Gilb, IEEE 802-REVc Technical Editor
Mark Hantel, Maintenance TG Chair
Mahin Ahmed Woojung Huh Silvana Rodrigues
Satoko Itaya
Katsuyuki Akizuki Rajeev Roy
Venkat Arunarthi Yoshihiro Ito Atsushi Sato
Ralf Assmann Michael Karl Frank Schewe
Rudy Belliardi Stephan Kehrer Michael Seaman
Christian Boiger Marcel Kiessling Maik Seewald
Paul Bottorff Gavin Lai Ramesh Sivakolundu
Radhakrishna Canchi Yunping (Lily) Lyu Johannes Specht
Feng Chen Christophe Mangin Nemanja Stamenic
Lihao Chen Scott Mansfield Marius Stanica
Abhijit Choudhury Olaf Mater Guenter Steindl
Anna Engelmann David McCall Karim Traore
Martin Mittelberger
János Farkas Max Turner
Donald Fedyk Hiroki Nakano Balazs Varga
Norman Finn Takumi Nomura Ganesh Venkatesan
Geoffrey Garner Donald R. Pannell Leon Wessels
Craig Gunther Dieter Proell Ludwig Winkel
Stephen Haddock Karen Randall Jordon Woods
Marc Holness Maximilian Riegel Takahiro Yamaura
Daniel Hopf Nader Zein
In addition to the members of the IEEE 802.1 Working Group, significant contributions were received from
the following individuals:
Ralf Assman Mark Hamilton Geoffrey O. Thompson
Harry Bims Marco Hernandez Benjamin A. Rolfe
Robert M. Grow Joseph S. Levy Karl Weber
Roger Marks
The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
Iwan Adhicandra C. Huntley Arumugam Paventhan
Thomas Alexander Abdul Jabbar Richie Pearn
Johann Amsenga Raj Jain Cam Posani
Boon Chong Ang SangKwon Jeong Dieter Proell
Pranav Jha
Carol Ansley Adee Ran
Butch Anton Lokesh Kabra R. K. Rannow
Danilo Antonelli Piotr Karocki Alon Regev
Stefan Aust Stephan Kehrer Maximilian Riegel
Harry Bims Stuart Kerry Benjamin Rolfe
Marcel Kiessling
Christian Boiger Jon Rosdahl
Rich Boyer Yongbum Kim Jessy Rouyer
Travis Breitkreutz Hyeong Ho Lee Michael Seaman
Vern Brethour James Lepp Jhony Sembiring
William Byrd Joseph Levy Johannes Specht
Ru Lin
Radhakrishna Canchi Dorothy Stanley
Paul Cardinal Greg Luri Guenter Steindl
Pin Chang Michael Lynch Walter Struppler
Baw Chng Yongsen Ma Mitsutoshi Sugawara
Rodney Cummings Valerie Maguire Bo Sun
Sajeev Manikkoth Peng Sun
Marc Emmelmann
János Farkas Scott Mansfield Bin Tian
Donald Fedyk William Rogelio Marchand- Max Turner
Andrew Fieldsend Niño Masood Ur Rehman
Avraham Freedman Ignacio Marin Garcia Ganesh Venkatesan
Matthias Fritsche Pedro Martinez-Julia John Vergis
James P. K. Gilb Jonathon Mclendon James Weaver
Sachin Goel Richard Mellitz Karl Weber
Fabrizio Granelli Martin Mittelberger Scott Willy
Stephen Haddock Michael Montemurro Ludwig Winkel
Marek Hajduczenia Ronald Murias Andreas Wolf
Mark Hamilton Rick Murphy Forrest Wright
Mark Hantel Rajesh Murthy James Yee
Adam Healey Yukimasa Nagai Yu Yuan
Jerome Henry Paul Nikolich Oren Yuen
Marco Hernandez John Notor Janusz Zalewski
Werner Hoelzl Satoshi Obara Sven Zeisberg
Oliver Holland Satoshi Oyama Ke Zhong
Russell Housley Glenn Parsons Tian Zhou
David Hunter Bansi Patel Juan Carlos Zuniga
Dev Paul
When the IEEE SA Standards Board approved this standard on 11 December 2024, it had the following
membership:
David J. Law, Chair
Jon W. Rosdahl, Vice Chair
Gary Hoffman, Past Chair
Alpesh Shah, Secretary
Sara R. Biyabani Hao Hu Hiroshi Mano
Paul Nikolich
Ted Burse Yousef Kimiagar
Robby Robson
Stephen Dukes Joseph L. Koepfinger*
Lei Wang
Doug Edwards Howard Li
F. Keith Waters
J. Travis Griffith Xiaohui Liu
Sha Wei
Guido R. Hiertz John Haiying Lu
Philip B. Winston
Ronald W. Hotchkiss Kevin W. Lu
Don Wright
*Member Emeritus
Historical participants
When the IEEE Std 802-1990 was approved on 31 May 1990, the IEEE 802.1 Working Group had the
following officer:
William P. Lidinsky, Chair
When the IEEE Std 802-2001 was approved on 6 December 2001, the IEEE 802.1 Working Group had the
following officers:
William P. Lidinsky, Chair
Tony Jeffree, Vice Chair and Editor
Alan Chambers, Tony Jeffree, Editors
When the IEEE Std 802a-2003 was approved on 12 June 2003, the IEEE 802.1 Working Group had the
following officers:
Tony Jeffree, Chair and Editor
Neil Jarvis, Vice Chair
When the IEEE Std 802b-2004 was approved on 25 March 2004, the IEEE 802.1 Working Group had the
following officers:
Tony Jeffree, Chair and Editor
Neil Jarvis, Vice Chair
When the IEEE Std 802-2014 was approved on 12 June 2014, the IEEE 802.1 Working Group had the
following officers:
Glenn Parsons, Chair
John Messenger, Vice Chair
Eric Gray, Recording Secretary
James P. K. Gilb, IEEE 802-2014 Technical Editor
When the IEEE Std 802c-2017 was approved on 15 June 2017, the IEEE 802.1 Working Group had the
following officers:
Glenn Parsons, Chair
John Messenger, Vice Chair
Pat Thaler, Chair, Data Center Bridging Task Group
Roger B. Marks, IEEE 802c Technical Editor
When the IEEE Std 802d-2017 was approved on 14 February 2017, the IEEE 802.1 Working Group had the
following officers:
Glenn Parsons, Chair
John Messenger, Vice Chair
János Farkas, Chair, Time-Sensitive Networking Task Group
Tony Jeffree, Editor
When the IEEE Std 802f-2023 was approved on 21 September 2023, the IEEE 802.1 Working Group had
the following officers:
Glenn Parsons, Chair
Jessy Rouyer, Vice Chair
János Farkas, Chair, Time-Sensitive Networking Task Group
Craig Gunther, Vice Chair, Time-Sensitive Networking Task Group
Marc Holness, IEEE 802f Technical Editor
The following individuals participated in the IEEE 802.1 working group during various stages of the
standard’s development. Since the initial publication, many IEEE standards have added functionality or
provided updates to material included in this standard. The following is a historical list of participants who
have dedicated their valuable time, energy, and knowledge to the creation of this standard:
Pat Gonia
Steve Adams Krishna Narayanaswamy
Fumio Akashi Gerard Goubert
Lawrence Ng
Paul D. Amer Richard Graham Henry Ngai
Charles Arnold Michael A. Gravel Satoshi Obara
Floyd Backes Steve Haddock Don O’Connor
Ann Ballard Sharam Hakimi Jerry O’Keefe
Mogens Hansen
Richard Bantel Toshio Ooka
Harold Harrington
John Bartlett Jorg Ottensmeyer
Sy Bederman John Hart
Richard Patti
Les Bell Mike Harvey Luc Pariseau
Amatzia Ben-Artzi Richard Hausman Glenn Parsons
Michael Berger David Head Roger Pfister
James S. Binder Deepak Hegde Thomas L. Phinney
Ariel Hendel
Robert Bledsoe John Pickens
Bob Herbst
Kwame Boakye Dinel Pitt
Paul Bottorff Steve Horowitz
Ron L. G. Prince
Laura Bridge Robert W. Hott Steve Ramberg
Juan Bulnes Jack R. Hung Nigel Ramsden
Bill Bunch Altaf Hussain Shlomo Reches
Fred Burg Thomas Hytry Frank Reichstein
Ran Ish-Shalom
Jim Burns Trudy Reusser
Jay Israel
Peter Carbone James Richmond
Paul Carroll Vipin K. Jain Anil Rijsinghani
Jeffrey Catlin Neil Jarvis Eduoard Rocher
Dirceu Cavendish Tony Jeffree John Roese
Alan Chambers Shyam Kaluve Allyn Romanow
David W. Chang Toyoyuki Kato Dan Romascanu
Ken Chapman Hal Keen Paul Rosenblum
Kevin Ketchum
Alice Chen Dolors Sala
Jade Chien Alan Kirby John Salter
Hon Wah Chin Kimberly Kirkpatrick Alan Sarsby
Chris Christ Keith Klamm Ayman Sayed
Paul Congdon Steve Kleiman Susan Schannning
Glenn Connery Bruce Kling Mick Seaman
Jim Corrigan Dan Krent Gerry Segal
James Kristof
Paul Cowell Rich Seifert
David Cullerot H. Eugene Latham Lee Sendelbach
Ted Davies Bing Liao Himanshu Shah
Peter Dawe William P. Lidinsky Howard Sherry
Stan Degen George Lin Wu-Shi Shung
Fred Deignan Paul Lachapelle Phil Simmons
David Delaney Bill Lane Curtis Simonson
Ron Dhondy Paul Langille Paramjeet Singh
Jeffrey Dietz Roger Lapuh Rosemary V. Slager
Eiji Doi Loren Larsen Alexander Smith
Barbara J. Don Carlos Johann Lindmeyr Andrew Smith
Peter Ecclesine Andy Luque M. Soha
J. J. Ekstrom Philip Magnuson Larry Stefani
Bruce McClure
Hesham Elbakoury Dan Stokesberry
Walder Eldon Tom McGowan Stuart Soloway
Norman W. Finn Milan Merhar Sundar Subramaniam
David Frattura Margaret A. Merrick Lennart Swartz
Lars Henrik Frederiksen John Messenger Kazuo Takagi
Eldon D. Feist Colin Mick Kenta Takumi
Len Fishler Dinesh Mohan Robin Tasker
John Montrose
Kevin Flanagan Angus Telfer
Anoop Ghanwani Bob Moskowitz Pat Thaler
James P. K. Gilb Yaron Nachman Dave Thompson
Geoffrey O. Thompson John Wakerly Keith Willette
Michael Witkowski
Michel Thorsen Peter Wang
Edward Wong
Nathan Tobol Y. C. Wang
Michael D. Wright
Wendell Turner Trevor Warwick
Michele Wright
Steve Van Seters Scott Wasson
Allen Yu
Dono van-Mierop Daniel Watts
Wayne Zakowski
Paul Videcrantz Karl Weber
Igor Zhovnirovosky
Dennis Volpano Alan Weissberger
Carolyn Zimmer
Paul Wainright Deborah Wilbert
Nick Zucchero
Introduction
This introduction is not part of IEEE Std 802-2024, IEEE Standard for Local and Metropolitan Area Networks:
Overview and Architecture. ®
This document is the third major revision of the IEEE 802 overview and architecture. This revision
integrates into the previous revision of the standard, IEEE Std 802-2014, the three subsequent amendments:
— IEEE Std 802d™-2017, which specifies a Uniform Resource Name (URN) root identifier for YANG
data models
— IEEE Std 802c™-2017, which specifies an optional local medium access control (MAC) address
space structure
— IEEE Std 802f™-2023, which specifies a YANG module that contains EtherType information
Contents
1. Overview. 16
1.1 Scope. 16
1.2 Purpose. 16
1.3 Word usage . 16
2. Normative references. 17
3. Definitions, acronyms, and abbreviations. 18
3.1 Definitions . 18
3.2 Acronyms and abbreviations . 20
4. Family of IEEE 802 standards . 23
4.1 Key concepts. 23
4.2 Application and support. 24
4.3 An international family of standards . 25
4.4 IEEE 802 standards. 25
5. Reference models (RMs) . 27
5.1 Introduction. 27
5.2 RM description for end stations. 28
5.2.1 SAPs. 29
5.2.2 LLC sublayer . 29
5.2.3 MAC sublayer.29
5.2.4 PHY . 30
5.2.5 Layer and sublayer management . 30
5.3 Interconnection and interworking.30
5.3.1 Interconnection at the PHY. 31
5.3.2 MAC-sublayer interconnection: Bridges . 31
5.3.3 Network-layer interconnection: Routers. 35
6. General requirements for an IEEE 802 network. 36
6.1 Services supported . 36
6.2 Error ratios . 36
7. IEEE 802 network management . 37
7.1 General. 37
7.2 General-purpose IEEE 802 network management. 37
7.2.1 Management functions. 37
7.2.2 Management architecture. 37
7.2.3 Managed object definitions. 38
7.3 Special-purpose IEEE 802 network management standards . 38
MAC addresses . 39
8.
8.1 Terms and notational conventions . 39
8.2 Universal addresses. 39
8.2.1 Concept and overview . 39
8.2.2 Assignment of universal addresses . 40
8.2.3 Assignment by organizations. 42
8.2.4 Uniqueness of address assignment . 42
8.3 Interworking with 48-bit and 64-bit MAC addresses . 42
8.4 Local MAC addresses. 43
8.4.1 Concept and overview . 43
8.4.2 Local MAC address assignment protocols . 43
8.4.3 Structured Local Address Plan (SLAP) . 43
8.4.4 SLAP local identifier types. 45
8.4.5 Network Unique Identifier (NUI) . 48
8.5 Group MAC addresses. 48
8.6 Bit-ordering within octets . 48
9. Protocol identifiers and context-dependent identifiers . 49
9.1 Introduction. 49
9.2 EtherTypes and E-Type protocol identifiers. 50
9.2.1 Format, function, and administration. 50
9.2.2 Public EtherType assignments subset. 50
9.2.3 EtherType sub-protocol encoding. 51
9.2.4 Local Experimental EtherTypes . 52
9.3 LSAP addresses and L-Type protocol identifiers . 53
9.4 O-Type protocol identifiers . 53
9.5 PIF encoding . 53
9.5.1 Type 2 PIF encoding. 53
9.5.2 Type 3 PIF encoding. 54
9.5.3 Encoding type and PIF length. 56
9.6 Context-dependent identifiers. 56
10. Allocation of OID values in IEEE 802 standards .57
10.1 General. 57
10.2 OIDs and ISO standards . 57
10.3 The OID hierarchy for IEEE 802 standards. 58
10.4 The OID hierarchy under iso(1) std(0) iso8802(8802). 59
10.5 Migration from previous OID allocations . 59
11. Allocation of Uniform Resource Name (URN) values in IEEE 802 standards. 60
11.1 Introduction. 60
11.2 IEEE Namespace ID and Namespace Specific String . 60
11.3 ResourceSpecificString values in IEEE 802 standards. 60
Annex A (informative) Bibliography . 62
Annex B (informative) Reference models for IEEE 802 standards. 64
B.1 IEEE 802.3 reference models . 64
B.2 IEEE 802.11 reference model. 66
B.3 IEEE 802.15™ reference models . 68
B.3.1 IEEE 802.15.3™ RM. 68
B.3.2 IEEE 802.15.4™ RM. 70
B.3.3 IEEE 802.15.6™ RM. 70
B.3.4 IEEE 802.15.7™ RM. 70
B.4 IEEE 802.16™ reference model . 71
B.4.1 Protocol RM. 71
B.4.2 Network RM .72
B.5 IEEE 802.21™ reference model . 73
B.6 IEEE 802.22™ reference model . 74
B.6.1 Data plane . 75
B.6.2 Management/control plane . 75
B.6.3 Cognitive plane . 75
Annex C (informative) Examples of bit ordering for addresses. 76
Annex D (informative) List of IEEE 802 standards . 77
Annex E (informative) History . 79
E.1 Universal addresses. 79
E.2 IEEE RA address block products. 79
E.3 Local MAC addresses. 80
Annex F (informative) EtherType listing subset . 81
F.1 Introduction. 81
F.2 Tabular format . 81
F.3 YANG module for EtherType subset . 84
F.3.1 YANG framework . 84
,
F.3.2 Definition for ieee802-ethertype YANG module . 85
...