rfc9542.original   rfc9542.txt 
INTAREA Working Group D. Eastlake Internet Engineering Task Force (IETF) D. Eastlake 3rd
Internet-Draft Futurewei Technologies Request for Comments: 9542 Independent
Obsoletes: 7042 (if approved) J.N. Abley BCP: 141 J. Abley
Intended status: Best Current Practice Cloudflare Obsoletes: 7042 Cloudflare
Expires: 9 May 2024 Y. Li Category: Best Current Practice Y. Li
Huawei Technologies ISSN: 2070-1721 Huawei Technologies
6 November 2023 April 2024
IANA Considerations and IETF Protocol and Documentation Usage for IEEE IANA Considerations and IETF Protocol and Documentation Usage for IEEE
802 Parameters 802 Parameters
draft-ietf-intarea-rfc7042bis-11
Abstract Abstract
Some IETF protocols make use of Ethernet frame formats and IEEE 802 Some IETF protocols make use of Ethernet frame formats and IEEE 802
parameters. This document discusses several aspects of such parameters. This document discusses several aspects of such
parameters and their use in IETF protocols, specifies IANA parameters and their use in IETF protocols, specifies IANA
considerations for assignment of points under the IANA OUI considerations for assignment of points under the IANA
(Organizationally Unique Identifier), and provides some values for Organizationally Unique Identifier (OUI), and provides some values
use in documentation. This document obsoletes RFC 7042. for use in documentation. This document obsoletes RFC 7042.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This memo documents an Internet Best Current Practice.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 7841.
This Internet-Draft will expire on 9 May 2024. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9542.
Copyright Notice Copyright Notice
Copyright (c) 2023 IETF Trust and the persons identified as the Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction
1.1. Notations Used in This Document . . . . . . . . . . . . . 4 1.1. Notations Used in This Document
1.2. The IEEE Registration Authority . . . . . . . . . . . . . 5 1.2. The IEEE Registration Authority
1.3. The IANA Organizationally Unique Identifier . . . . . . . 5 1.3. The IANA Organizationally Unique Identifier
1.4. CFM Code Points . . . . . . . . . . . . . . . . . . . . . 6 1.4. CFM Code Points
2. Ethernet Identifier Parameters . . . . . . . . . . . . . . . 6 2. Ethernet Identifier Parameters
2.1. 48-Bit MAC Identifiers, OUIs, and Other Prefixes . . . . 6 2.1. 48-Bit MAC Identifiers, OUIs, and Other Prefixes
2.1.1. Special First Octet Bits . . . . . . . . . . . . . . 7 2.1.1. Special First Octet Bits
2.1.2. OUIs and CIDs . . . . . . . . . . . . . . . . . . . . 9 2.1.2. OUIs and CIDs
2.1.3. 48-Bit MAC Assignments under the IANA OUI . . . . . . 10 2.1.3. 48-Bit MAC Assignments under the IANA OUI
2.1.4. 48-Bit MAC Documentation Values . . . . . . . . . . . 11 2.1.4. 48-Bit MAC Documentation Values
2.1.5. 48-Bit IANA MAC Assignment Considerations . . . . . . 11 2.1.5. 48-Bit IANA MAC Assignment Considerations
2.2. 64-Bit MAC Identifiers . . . . . . . . . . . . . . . . . 12 2.2. 64-Bit MAC Identifiers
2.2.1. IPv6 Use of Modified EUI-64 Identifiers . . . . . . . 12 2.2.1. IPv6 Use of Modified EUI-64 Identifiers
2.2.2. EUI-64 IANA Assignment Considerations . . . . . . . . 14 2.2.2. EUI-64 IANA Assignment Considerations
2.2.3. EUI-64 Documentation Values . . . . . . . . . . . . . 15 2.2.3. EUI-64 Documentation Values
2.3. Other 48-bit MAC Identifiers Used by the IETF . . . . . . 16 2.3. Other 48-Bit MAC Identifiers Used by the IETF
2.3.1. Identifiers with a '33-33' Prefix . . . . . . . . . . 16 2.3.1. Identifiers with a '33-33' Prefix
2.3.2. The 'CF Series' . . . . . . . . . . . . . . . . . . . 16 2.3.2. The CF Series
2.4. CBOR Tags . . . . . . . . . . . . . . . . . . . . . . . . 17 2.4. CBOR Tags
3. Ethernet Protocol Parameters . . . . . . . . . . . . . . . . 17 3. Ethernet Protocol Parameters
3.1. Ethernet Protocol Assignment under the IANA OUI . . . . . 20 3.1. Ethernet Protocol Assignment under the IANA OUI
3.2. Documentation Protocol Number . . . . . . . . . . . . . . 21 3.2. Documentation Protocol Number
4. Other OUI/CID-Based Parameters . . . . . . . . . . . . . . . 21 4. Other OUI/CID-Based Parameters
4.1. LLDP IETF Organizationally-Specific TLV Type . . . . . . 22 4.1. LLDP IETF Organizationally Specific TLV Type
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 5. IANA Considerations
5.1. Expert Review and IESG Ratification . . . . . . . . . . . 22 5.1. Expert Review and IESG Ratification
5.1.1. Expert Review Guidance . . . . . . . . . . . . . . . 22 5.1.1. Expert Review Guidance
5.1.2. Expert Review and IESG Ratification Procedure . . . . 23 5.1.2. Expert Review and IESG Ratification Procedure
5.2. IANA Registry Group (Web Page) Name Changes . . . . . . . 24 5.2. IANA Registry Group (Web Page) Name Changes
5.3. MAC Address AFNs and RRTYPEs . . . . . . . . . . . . . . 24 5.3. MAC Address AFNs and RRTYPEs
5.4. Informational IANA Registry Group Material . . . . . . . 25 5.4. Informational IANA Registry Group Material
5.5. EtherType Assignment Process . . . . . . . . . . . . . . 25 5.5. EtherType Assignment Process
5.6. OUI Exhaustion . . . . . . . . . . . . . . . . . . . . . 26 5.6. OUI Exhaustion
5.7. IANA OUI MAC Address Table . . . . . . . . . . . . . . . 26 5.7. IANA OUI MAC Address Table
5.8. IANA LLDP TLV Subtypes . . . . . . . . . . . . . . . . . 27 5.8. IANA LLDP TLV Subtypes
5.9. CBOR Tag Assignments . . . . . . . . . . . . . . . . . . 27 5.9. CBOR Tag Assignments
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 6. Security Considerations
7. Normative References . . . . . . . . . . . . . . . . . . . . 28 7. References
8. Informative References . . . . . . . . . . . . . . . . . . . 29 7.1. Normative References
Appendix A. Templates . . . . . . . . . . . . . . . . . . . . . 33 7.2. Informative References
A.1. EUI-48/EUI-64 Identifier or Identifier Block Template . . 33 Appendix A. Templates
A.2. IANA OUI/CID-Based Protocol Number Template . . . . . . . 34 A.1. EUI-48/EUI-64 Identifier or Identifier Block Template
A.3. Other IANA OUI/CID-Based Parameter Template . . . . . . . 34 A.2. IANA OUI/CID-Based Protocol Number Template
Appendix B. EtherTypes . . . . . . . . . . . . . . . . . . . . . 35 A.3. Other IANA OUI/CID-Based Parameter Template
B.1. IESG Statement on Ethertypes . . . . . . . . . . . . . . 35 Appendix B. EtherTypes
Appendix C. Changes from RFC 7042 . . . . . . . . . . . . . . . 36 B.1. IESG Statement on EtherTypes
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 36 Appendix C. Changes from RFC 7042
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Acknowledgements
Authors' Addresses
1. Introduction 1. Introduction
Some IETF protocols use Ethernet or other IEEE 802-related Some IETF protocols use Ethernet or other communication frame formats
communication frame formats and parameters [IEEE802]. These include and parameters related to IEEE 802 [IEEE802]. These include Media
MAC (Media Access Control) addresses and protocol identifiers. The Access Control (MAC) addresses and protocol identifiers. The IEEE
IEEE Registration Authority [IEEE_RA] manages the assignment of Registration Authority [IEEE_RA] manages the assignment of
identifiers used in IEEE 802 networks, in some cases assigning blocks identifiers used in IEEE 802 networks, in some cases assigning blocks
of such identifiers whose sub-assignment is managed by the entity to of such identifiers whose sub-assignment is managed by the entity to
which the block is assigned. The IEEE RA also provides a number of which the block is assigned. The IEEE RA also provides a number of
tutorials concerning these parameters [IEEEtutorials]. tutorials concerning these parameters [IEEEtutorials].
IANA has been assigned an Organizationally Unique Identifier (OUI) by IANA has been assigned an Organizationally Unique Identifier (OUI) by
the IEEE RA and an associated set of MAC addresses and other the IEEE RA and an associated set of MAC addresses and other
organizationally unique code points based on that OUI. This document organizationally unique code points based on that OUI. This document
specifies IANA considerations for the assignment of code points under specifies IANA considerations for the assignment of code points under
that IANA OUI, including MAC addresses and protocol identifiers, and that IANA OUI, including MAC addresses and protocol identifiers, and
provides some values for use in documentation. As noted in [RFC2606] provides some values for use in documentation. As noted in [RFC2606]
and [RFC5737], the use of designated code values reserved for and [RFC5737], the use of designated code values reserved for
documentation and examples reduces the likelihood of conflicts and documentation and examples reduces the likelihood of conflicts and
confusion arising from such code points conflicting with code points confusion arising from such code points conflicting with code points
assigned for some deployed use. This document also discusses several assigned for some deployed use. This document also discusses several
other uses by the IETF of IEEE 802 code points, including IEEE 802 other uses by the IETF of IEEE 802 code points, including IEEE 802
Connectivity Fault Management (CFM) code points [RFC7319] and IEEE Connectivity Fault Management (CFM) code points [RFC7319] and IEEE
802 Link Local Discovery Protocol (LLDP [IEEE802.1AB]) Vendor 802 Link Local Discovery Protocol (LLDP) [IEEE802.1AB] Vendor-
Specific TLV Sub-Types [RFC8520]. It also specifies CBOR tags for Specific TLV Sub-Types [RFC8520]. It also specifies Concise Binary
MAC addresses and OUI/CIDs. Object Representation (CBOR) tags for MAC addresses and OUIs /
Company Identifiers (CIDs).
Descriptions herein of [IANA] policies and procedures are Descriptions herein of [IANA] policies and procedures are
authoritative but descriptions of IEEE registration policies, authoritative, but descriptions of IEEE registration policies,
procedures, and standards are only informative; for authoritative procedures, and standards are only informative; for authoritative
IEEE information, consult the IEEE sources. IEEE information, consult the IEEE sources.
[RFC8126] is incorporated herein except where there are contrary [RFC8126] is incorporated herein except where there are contrary
provisions in this document. In this document, "IESG Ratification", provisions in this document. In this document, "IESG Ratification",
specified in Section 5.1, refers to a combination of Expert Review specified in Section 5.1, refers to a combination of Expert Review
and IESG Approval as those are defined in [RFC8126] where IESG and IESG Approval as those are defined in [RFC8126], where IESG
Approval is required only if the Expert does not reject the request. Approval is required only if the Expert does not reject the request.
It is NOT the same as just "IESG Approval" in [RFC8126]. It is NOT the same as just "IESG Approval" in [RFC8126].
1.1. Notations Used in This Document 1.1. Notations Used in This Document
This document uses hexadecimal notation. Each octet (that is, 8-bit This document uses hexadecimal notation. Each octet (that is, 8-bit
byte) is represented by two hexadecimal digits giving the value of byte) is represented by two hexadecimal digits giving the value of
the octet as an unsigned integer. Successive octets are separated by the octet as an unsigned integer. Successive octets are separated by
a hyphen. This document consistently uses IETF ("network") bit a hyphen. This document consistently uses IETF ("network") bit
ordering although the physical order of bit transmission within an ordering although the physical order of bit transmission within an
octet on an IEEE [IEEE.802.3_2012] link is from the lowest order bit octet on an IEEE [IEEE.802.3_2012] link is from the lowest order bit
to the highest order bit (i.e., the reverse of the IETF's ordering). to the highest order bit (i.e., the reverse of the IETF's ordering).
In this document: In this document:
"AFN" Address Family Number [RFC4760]. "AFN" Address Family Number [RFC4760].
"CBOR" Concise Binary Object Representation [RFC8949]. "CBOR" Concise Binary Object Representation [RFC8949].
"CFM" Connectivity Fault Management [RFC7319]. "CFM" Connectivity Fault Management [RFC7319].
"CID" Company Identifier. (See Section 2.1.2.) "CID" Company Identifier. See Section 2.1.2.
"DSAP" Destination Service Access Point. See Section 3. "DSAP" Destination Service Access Point. See Section 3.
"EUI" Extended Unique Identifier. "EUI" Extended Unique Identifier.
"EUI-48" 48-bit EUI "EUI-48" 48-bit EUI
"IEEE" Institute for Electrical and Electronics Engineers [IEEE]. "IEEE" Institute of Electrical and Electronics Engineers [IEEE].
"IEEE 802" The LAN/MAN Standards Committee [IEEE802]. "IEEE 802" The LAN/MAN Standards Committee [IEEE802].
"IEEE RA" IEEE Registration Authority [IEEE_RA]. "IEEE RA" IEEE Registration Authority [IEEE_RA].
"IEEE SA" IEEE Standards Association [IEEE_SA]. "IEEE SA" IEEE Standards Association [IEEE_SA].
"LLC" Logical Link Control. The type of frame header where the "LLC" Logical Link Control. The type of frame header where the
protocol is identified by source and destination LSAP fields. See protocol is identified by source and destination LSAP
Section 3. fields. See Section 3.
"LSAP" Link-Layer Service Access Point. See Section 3. "LSAP" Link-Layer Service Access Point. See Section 3.
"MA-L" MAC Address Block Large. "MA-L" MAC Address Block Large.
"MA-M" MAC Address Block Medium. "MA-M" MAC Address Block Medium.
"MA-S" MAC Address Block Small. "MA-S" MAC Address Block Small.
"MAC" Media Access Control, not Message Authentication Code. "MAC" Media Access Control, not Message Authentication Code.
"MAC-48" A 48-bit MAC address. This term is obsolete. If globally "MAC-48" A 48-bit MAC address. This term is obsolete. If
unique, use EUI-48. globally unique, use EUI-48.
"OUI" Organizationally Unique Identifier. (See Section 2.1.2.) "OUI" Organizationally Unique Identifier. See Section 2.1.2.
"RRTYPE" A DNS Resource Record type [RFC6895]. "RRTYPE" A DNS Resource Record type [RFC6895].
"SLAP" IEEE 802 Structured Local Address Plan [IEEE802_OandA]. See "SLAP" IEEE 802 Structured Local Address Plan [IEEE802_OandA].
Section 2.1.1. See Section 2.1.1.
"SNAP" Subnetwork Access Protocol. See Section 3. "SNAP" Subnetwork Access Protocol. See Section 3.
"SSAP" Source Service Access Point. See Section 3. "SSAP" Source Service Access Point. See Section 3.
"tag" "Tag" is used in two contexts in this document. For "Ethernet "tag" "Tag" is used in two contexts in this document. For
tag", see Section 3. For "CBOR tag", see Section 2.4. "Ethernet tag", see Section 3. For "CBOR tag", see
Section 2.4.
"TLV" Type, Length, Value. "TLV" Type-Length-Value.
"**" The double asterisk symbol indicates exponentiation. For "**" The double asterisk symbol indicates exponentiation. For
example, 2**24 is two to the twenty-fourth power. example, 2**24 is two to the twenty-fourth power.
1.2. The IEEE Registration Authority 1.2. The IEEE Registration Authority
Originally the responsibility of Xerox Corporation, the registration Originally the responsibility of the Xerox Corporation, the
authority for Ethernet parameters since 1986 has been the IEEE registration authority for Ethernet parameters since 1986 has been
Registration Authority, available on the web at [IEEE_RA]. the IEEE Registration Authority, available on the Web at [IEEE_RA].
The IEEE Registration Authority operates under the direction of the The IEEE Registration Authority operates under the direction of the
IEEE Standards Association (IEEE SA) Board of Governors, with IEEE Standards Association (IEEE SA) Board of Governors, with
oversight by the IEEE Registration Authority Committee (RAC). The oversight by the IEEE Registration Authority Committee (IEEE RAC).
IEEE RAC is a committee of the Board of Governors. The IEEE RAC is a committee of the Board of Governors.
Anyone may apply to that Authority for parameter assignments. The Anyone may apply to that authority for parameter assignments. The
IEEE Registration Authority may impose fees or other requirements but IEEE Registration Authority may impose fees or other requirements but
commonly waives fees for applications from standards development commonly waives fees for applications from standards development
organizations. Lists of assignments and their holders are organizations. Lists of assignments and their holders are
downloadable from the IEEE Registration Authority site. downloadable from the IEEE Registration Authority site.
1.3. The IANA Organizationally Unique Identifier 1.3. The IANA Organizationally Unique Identifier
The Organizationally Unique Identifier (OUI) 00-00-5E has been The Organizationally Unique Identifier (OUI) 00-00-5E has been
assigned to IANA by the IEEE Registration Authority. assigned to IANA by the IEEE Registration Authority.
There is no OUI value reserved at this time for documentation, but There is no OUI value reserved at this time for documentation, but
there are documentation code points under the IANA OUI specified there are documentation code points under the IANA OUI specified
below. below.
1.4. CFM Code Points 1.4. CFM Code Points
IEEE Std 802.1Q [IEEE.802.1Q_2014] allocates two blocks of 802 IEEE Std 802.1Q [IEEE.802.1Q_2014] allocates two blocks of 802
Connectivity Fault Management (CFM) code points to the IETF, one for Connectivity Fault Management (CFM) code points to the IETF, one for
CFM OpCodes and one for CFM TLV Types. For further information see CFM OpCodes and one for CFM TLV Types. For further information, see
[RFC7319]. The IANA "Connectivity Fault Management (CFM) OAM IETF [RFC7319]. The IANA "Connectivity Fault Management (CFM) OAM IETF
Parameters" Registry has subregistries for these code points. This Parameters" registry has subregistries for these code points. This
document does not further discuss these blocks of code points. document does not further discuss these blocks of code points.
2. Ethernet Identifier Parameters 2. Ethernet Identifier Parameters
This section includes information summarized from [IEEE802_OandA] This section includes information summarized from [IEEE802_OandA]
that is being provided for context. The definitive information, that is being provided for context. The definitive information,
which prevails in case of any discrepancy, is in [IEEE802_OandA]. which prevails in case of any discrepancy, is in [IEEE802_OandA].
Section 2.1 discusses 48-bit MAC identifiers, their relationship to Section 2.1 discusses 48-bit MAC identifiers, their relationship to
OUIs and other prefixes, and assignment under the IANA OUI. OUIs and other prefixes, and assignment under the IANA OUI.
Section 2.2 extends this to 64-bit identifiers. Section 2.3 Section 2.2 extends this to 64-bit identifiers. Section 2.3
discusses other IETF MAC identifier use not under the IANA OUI. discusses other IETF MAC identifier uses not under the IANA OUI.
Section 2.4 specifies CBOR tags for MAC addresses and OUI/CIDs. Section 2.4 specifies CBOR tags for MAC addresses and OUIs/CIDs.
Historical Note: [RAC_OUI] is an expired draft that provides | Historical Note: [RAC_OUI] is an expired Internet-Draft that
additional historic information on [IEEE802] registries. | provides additional historic information on [IEEE802]
| registries.
2.1. 48-Bit MAC Identifiers, OUIs, and Other Prefixes 2.1. 48-Bit MAC Identifiers, OUIs, and Other Prefixes
48-bit MAC "addresses" are the most commonly used Ethernet interface 48-bit MAC "addresses" are the most commonly used Ethernet interface
identifiers. Those that are globally unique are also called EUI-48 identifiers. Those that are globally unique are also called EUI-48
identifiers (Extended Unique Identifier 48). An EUI-48 is structured identifiers (Extended Unique Identifier 48). An EUI-48 is structured
into an initial prefix assigned by the IEEE Registration Authority into an initial prefix assigned by the IEEE Registration Authority
and additional bits assigned by the prefix owner. As of 2023 there and additional bits assigned by the prefix owner. As of 2024, there
are three lengths of prefixes assigned, as shown in the table below; are three lengths of prefixes assigned, as shown in the table below;
however, some prefix bits can have special meaning as shown in however, some prefix bits can have special meaning, as shown in
Figure 1. Figure 1.
+=======================+======+=========================+ +=======================+======+=========================+
| Prefix Length in bits | Name | Owner Supplied Bits for | | Prefix Length in Bits | Name | Owner Supplied Bits for |
| | | 48-bit MAC Addresses | | | | 48-bit MAC Addresses |
+=======================+======+=========================+ +=======================+======+=========================+
| 24 | MA-L | 24 | | 24 | MA-L | 24 |
+-----------------------+------+-------------------------+ +-----------------------+------+-------------------------+
| 28 | MA-M | 20 | | 28 | MA-M | 20 |
+-----------------------+------+-------------------------+ +-----------------------+------+-------------------------+
| 36 | MA-S | 12 | | 36 | MA-S | 12 |
+-----------------------+------+-------------------------+ +-----------------------+------+-------------------------+
Table 1 Table 1
skipping to change at page 7, line 18 skipping to change at line 303
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| . . . . Z Y X M| . . . . . . . .| octets 0+1 | . . . . Z Y X M| . . . . . . . .| octets 0+1
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| . . . . . . . .| . . . . . . . .| octets 2+3 | . . . . . . . .| . . . . . . . .| octets 2+3
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| . . . . . . . .| . . . . . . . .| octets 4+5 | . . . . . . . .| . . . . . . . .| octets 4+5
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Figure 1: 48-bit MAC Address Structure Figure 1: 48-Bit MAC Address Structure
For global addresses, X=0 and a MAC address begins with 3 octets or a For global addresses, X = 0 and a MAC address begins with 3 octets or
larger initial prefix indicating the assignee of the block of MAC a larger initial prefix indicating the assignee of the block of MAC
addresses. This prefix is followed by a sequence of additional addresses. This prefix is followed by a sequence of additional
octets so as to add up to the total MAC address length. For example, octets so as to add up to the total MAC address length. For example,
the IEEE assigns MA-S (MAC Address Block Small), where the first four the IEEE assigns MAC Address Block Small (MA-S), where the first four
and a half octets (36 bits) are assigned, giving the holder of the and a half octets (36 bits) are assigned, giving the holder of the
MA-S one and a half octets (12 bits) they can control in constructing MA-S one and a half octets (12 bits) they can control in constructing
48-bit MAC addresses; other prefix lengths are also available 48-bit MAC addresses; other prefix lengths are also available
[IEEEtutorials]. [IEEEtutorials].
An AFN, a DNS RRTYPE, and a CBOR tag have been assigned for 48-bit An AFN, a DNS RRTYPE, and a CBOR tag have been assigned for 48-bit
MAC addresses as discussed in Sections 2.4, 5.3 and 5.9. MAC addresses, as discussed in Sections 2.4, 5.3, and 5.9.
IEEE Std 802 describes assignment procedures and policies for IEEE IEEE Std 802 describes assignment procedures and policies for
802-related identifiers [IEEE802_OandA]. IEEE RA documentation on identifiers related to IEEE 802 [IEEE802_OandA]. IEEE RA
EUIs, OUIs, and CIDs is available at [IEEEtutorials]. documentation on EUIs, OUIs, and CIDs is available at
[IEEEtutorials].
2.1.1. Special First Octet Bits 2.1.1. Special First Octet Bits
There are bits within the initial octet of an IEEE MAC address that There are bits within the initial octet of an IEEE MAC address that
have special significance [IEEE802_OandA] as follows: have special significance [IEEE802_OandA], as described as follows:
M bit - This bit is frequently referred to as the group or multicast M bit - This bit is frequently referred to as the "group" or
bit. If it is zero, the MAC address is unicast. If it is a one, "multicast" bit. If it is zero, the MAC address is unicast. If
the address is groupcast (multicast or broadcast). This meaning it is a one, the address is groupcast (multicast or broadcast).
is independent of the values of the X, Y, and Z bits. This meaning is independent of the values of the X, Y, and Z bits.
X bit - This bit is also called the "universal/local" bit. If it is X bit - This bit is also called the "universal/local" bit (formerly
zero, the MAC address is a global address under the control of the called the Local/Global bit). If it is zero, the MAC address is a
owner of the IEEE assigned prefix. Previously, if it was a one, global address under the control of the owner of the IEEE-assigned
the MAC address was considered "local" and under the assignment prefix. Previously, if it was a one, the MAC address was
and control of the local network operator (but see Section 2.3). considered "local" and under the assignment and control of the
If it is a one and if the IEEE 802 Structured Local Address Plan local network operator (but see Section 2.3). If it is a one and
(SLAP) is in effect, the nature of the MAC address is optionally if the IEEE 802 Structured Local Address Plan (SLAP) is in effect,
determined by the Y and Z bits as described below. the nature of the MAC address is optionally determined by the Y
and Z bits, as described below.
Y+Z bits - These two bits have no special meaning if the X bit is Y&Z bits - These two bits have no special meaning if the X bit is
zero. If the X bit is one then, if the IEEE 802 Structured Local zero. If the X bit is one and if the IEEE 802 Structured Local
Address Plan (SLAP) is in effect, these two bits divide the Address Plan (SLAP) is in effect, these two bits divide the
formerly uniform "local" MAC address space into four quadrants, as formerly uniform "local" MAC address space into four quadrants as
follows and further described below: follows and further described below:
+=======+=======+===========================+ +=======+=======+===========================+
| Y bit | Z bit | Quadrant | | Y bit | Z bit | Quadrant |
+=======+=======+===========================+ +=======+=======+===========================+
| 0 | 0 | Administratively Assigned | | 0 | 0 | Administratively Assigned |
+-------+-------+---------------------------+ +-------+-------+---------------------------+
| 0 | 1 | Extended Local | | 0 | 1 | Extended Local |
+-------+-------+---------------------------+ +-------+-------+---------------------------+
| 1 | 0 | Reserved | | 1 | 0 | Reserved |
skipping to change at page 8, line 46 skipping to change at line 377
Administratively Assigned - MAC addresses in this quadrant are Administratively Assigned - MAC addresses in this quadrant are
called Administratively Assigned Identifiers. This is intended called Administratively Assigned Identifiers. This is intended
for arbitrary local assignment, such as random assignment; for arbitrary local assignment, such as random assignment;
however, see Section 2.3.1. however, see Section 2.3.1.
Extended Local - MAC addresses in this quadrant are called Extended Extended Local - MAC addresses in this quadrant are called Extended
Local Identifiers. These addresses are not actually "local" under Local Identifiers. These addresses are not actually "local" under
SLAP. They are available to the organization that has been SLAP. They are available to the organization that has been
assigned the CID (see Section 2.1.2) specifying the other 20 bits assigned the CID (see Section 2.1.2) specifying the other 20 bits
of the 24-bit prefix with X, Y, and Z bits having the values 1, 0, of the 24-bit prefix with X, Y, and Z bits having the values 1, 0,
and 1 respectively. and 1, respectively.
Reserved - MAC addresses in this quadrant are reserved for future Reserved - MAC addresses in this quadrant are reserved for future
use under the SLAP. Until such future use, they could be locally use under the SLAP. Until such future use, they could be locally
assigned as Administratively Assigned Identifiers are assigned but assigned as Administratively Assigned Identifiers are assigned,
there is a danger that future SLAP use would conflict with such but there is a danger that future SLAP use would conflict with
local assignments. such local assignments.
Standard Assigned - MAC addresses in this quadrant are called Standard Assigned - MAC addresses in this quadrant are called
Standard Assigned Identifiers (SAIs). An SAI is assigned by a Standard Assigned Identifiers (SAIs). An SAI is assigned by a
protocol specified in an IEEE 802 standard, for example protocol specified in an IEEE 802 standard, for example,
[IEEE802.1CQ] (but see NOTE below). [IEEE802.1CQ] (but see the first NOTE below).
NOTE: While the SLAP has MAC addresses assigned through a local NOTE: While the SLAP has MAC addresses assigned through a local
protocol in the SAI quadrant and assigned by a protocol protocol in the SAI quadrant and assigned by a protocol
specified in an IEEE 802 standard, the SLAP is optional. Local specified in an IEEE 802 standard, the SLAP is optional. Local
network administrators may use the IETF protocol provisions in network administrators may use the IETF protocol provisions in
[RFC8947] and [RFC8948] which support assignment of a MAC [RFC8947] and [RFC8948], which support assignment of a MAC
address in the local MAC address space using DHCPv6 [RFC8415] address in the local MAC address space using DHCPv6 [RFC8415]
or other protocol methods. or other protocol methods.
NOTE: There isn't any automated way to determine if or to what NOTE: There isn't any automated way to determine if or to what extent
extent a local network is configured for and/or operating a local network is configured for and/or operating according to SLAP.
according to SLAP.
2.1.2. OUIs and CIDs 2.1.2. OUIs and CIDs
MA-L, MA-M, and MA-S MAC prefixes are assigned with the Local bit MA-L, MA-M, and MA-S MAC prefixes are assigned with the Local bit
zero. The assignee of an OUI is exclusively authorized to assign zero. The assignee of an OUI is exclusively authorized to assign
group MAC addresses by extending a modified version of the assigned group MAC addresses by extending a modified version of the assigned
OUI in which the M bit (see Figure 1) is set to 1 [IEEEtutorials]. OUI in which the M bit (see Figure 1) is set to 1 [IEEEtutorials].
The Local bit is zero for globally unique EUI-48 identifiers assigned The Local bit is zero for globally unique EUI-48 identifiers assigned
by the owner of a MAC-L or owner of a longer prefix. If the Local by the owner of a MAC-L or owner of a longer prefix. If the Local
bit is a one, the identifier has historically been a local identifier bit is a one, the identifier has historically been a local identifier
under the control of the local network administrator; however, there under the control of the local network administrator; however, there
are now recommendations on optional management of the local address are now recommendations on optional management of the local address
space as discussed in Section 2.1.1. If the Local bit is a one, the space, as discussed in Section 2.1.1. If the Local bit is a one, the
holder of an OUI has no special authority over MAC identifiers whose holder of an OUI has no special authority over MAC identifiers whose
first 3 octets correspond to their OUI or the beginning of their first 3 octets correspond to their OUI or the beginning of their
longer prefix. longer prefix.
A CID is a 24-bit Company Identifier. It is assigned for A CID is a 24-bit Company Identifier. It is assigned for
organizations that need such an identifier that can be used in place organizations that need such an identifier that can be used in place
of an OUI, but do not need to assign subsidiary global MAC addresses. of an OUI but do not need to assign subsidiary global MAC addresses.
A CID has X and Z bits equal to 1 and its Y bit equal to 0 (see A CID has X and Z bits equal to 1 and its Y bit equal to 0 (see
Figure 1). Figure 1).
An AFN and a CBOR tag have been assigned for OUI/CIDs as discussed in An AFN and a CBOR tag have been assigned for OUIs/CIDs, as discussed
Sections 2.4, 5.3 and 5.9. in Sections 2.4, 5.3, and 5.9.
2.1.3. 48-Bit MAC Assignments under the IANA OUI 2.1.3. 48-Bit MAC Assignments under the IANA OUI
The OUI 00-00-5E has been assigned to IANA as stated in Section 1.3 The OUI 00-00-5E has been assigned to IANA, as stated in Section 1.3
above. This includes 2**24 48-bit multicast identifiers from above. This includes 2**24 48-bit multicast identifiers from
01-00-5E-00-00-00 to 01-00-5E-FF-FF-FF and 2**24 EUI-48 unicast 01-00-5E-00-00-00 to 01-00-5E-FF-FF-FF and 2**24 EUI-48 unicast
identifiers from 00-00-5E-00-00-00 to 00-00-5E-FF-FF-FF. identifiers from 00-00-5E-00-00-00 to 00-00-5E-FF-FF-FF.
Of these identifiers, the sub-blocks reserved or thus far assigned Of these identifiers, the sub-blocks reserved or thus far assigned
are as follows: are as follows:
Unicast, all blocks of 2**8 addresses thus far: Unicast, all blocks of 2**8 addresses thus far:
00-00-5E-00-00-00 through 00-00-5E-00-00-FF: reserved and require
IESG Ratification for assignment (see Section 5.1).
00-00-5E-00-00-00 through 00-00-5E-00-00-FF: reserved and require 00-00-5E-00-01-00 through 00-00-5E-00-01-FF: assigned for the
IESG Ratification for assignment (see Section 5.1). Virtual Router Redundancy Protocol (VRRP) [RFC5798].
00-00-5E-00-01-00 through 00-00-5E-00-01-FF: assigned for the
Virtual Router Redundancy Protocol (VRRP) [RFC5798].
00-00-5E-00-02-00 through 00-00-5E-00-02-FF: assigned for the IPv6 00-00-5E-00-02-00 through 00-00-5E-00-02-FF: assigned for the
Virtual Router Redundancy Protocol (IPv6 VRRP) [RFC5798]. IPv6 Virtual Router Redundancy Protocol (IPv6 VRRP) [RFC5798].
00-00-5E-00-52-00 through 00-00-5E-00-52-FF: used for very small 00-00-5E-00-52-00 through 00-00-5E-00-52-FF: used for very small
assignments. As of 2023, 4 out of these 256 values have been assignments. As of 2024, 4 out of these 256 values have been
assigned. See [EthernetNum]. assigned. See [EthernetNum].
00-00-5E-00-53-00 through 00-00-5E-00-53-FF: assigned for use in 00-00-5E-00-53-00 through 00-00-5E-00-53-FF: assigned for use in
documentation by this document. documentation by this document.
00-00-5E-90-01-00 through 00-00-5E-90-01-FF: used for very small 00-00-5E-90-01-00 through 00-00-5E-90-01-FF: used for very small
assignments that need parallel unicast and multicast MAC assignments that need parallel unicast and multicast MAC
addresses. As of 2023, 1 out of these 256 values has been addresses. As of 2024, 1 out of these 256 values has been
assigned. See [EthernetNum]. assigned. See [EthernetNum].
Multicast: Multicast:
01-00-5E-00-00-00 through 01-00-5E-7F-FF-FF: 2**23 addresses
assigned for IPv4 multicast [RFC1112].
01-00-5E-00-00-00 through 01-00-5E-7F-FF-FF: 2**23 addresses 01-00-5E-80-00-00 through 01-00-5E-8F-FF-FF: 2**20 addresses
assigned for IPv4 multicast [RFC1112]. assigned for MPLS multicast [RFC5332].
01-00-5E-80-00-00 through 01-00-5E-8F-FF-FF: 2**20 addresses
assigned for MPLS multicast [RFC5332].
01-00-5E-90-00-00 through 01-00-5E-90-00-FF: 2**8 addresses being 01-00-5E-90-00-00 through 01-00-5E-90-00-FF: 2**8 addresses being
used for very small assignments. As of 2023, 4 out of these 256 used for very small assignments. As of 2024, 4 out of these
values have been assigned. See [EthernetNum]. 256 values have been assigned. See [EthernetNum].
01-00-5E-90-01-00 through 01-00-5E-90-01-FF: used for very small 01-00-5E-90-01-00 through 01-00-5E-90-01-FF: used for very small
assignments that need parallel unicast and multicast MAC assignments that need parallel unicast and multicast MAC
addresses. As of 2023, 1 out of these 256 values has been addresses. As of 2024, 1 out of these 256 values has been
assigned. See [EthernetNum]. assigned. See [EthernetNum].
01-00-5E-90-10-00 through 01-00-5E-90-10-FF: 2**8 addresses assigned 01-00-5E-90-10-00 through 01-00-5E-90-10-FF: 2**8 addresses
for use in documentation by this document. assigned for use in documentation by this document.
For more detailed and up-to-date information, see the "Ethernet For more detailed and up-to-date information, see the "IANA OUI
Numbers" registry at [EthernetNum]. Ethernet Numbers" registry at [EthernetNum].
2.1.4. 48-Bit MAC Documentation Values 2.1.4. 48-Bit MAC Documentation Values
The following values have been assigned for use in documentation: The following values have been assigned for use in documentation:
* 00-00-5E-00-53-00 through 00-00-5E-00-53-FF for unicast and * 00-00-5E-00-53-00 through 00-00-5E-00-53-FF for unicast and
* 01-00-5E-90-10-00 through 01-00-5E-90-10-FF for multicast. * 01-00-5E-90-10-00 through 01-00-5E-90-10-FF for multicast.
2.1.5. 48-Bit IANA MAC Assignment Considerations 2.1.5. 48-Bit IANA MAC Assignment Considerations
48-bit assignments under the current or a future IANA OUI (see 48-bit assignments under the current or a future IANA OUI (see
Section 5.6) must meet the following requirements: Section 5.6) must meet the following requirements:
* must be for standards purposes (either for an IETF Standard or * must be for standards purposes (either for an IETF Standard or
other standard related to IETF work), other standard related to IETF work),
* must be for a power-of-two size block of identifiers starting at a * must be for a power-of-two-sized block of identifiers starting at
boundary that is an equal or greater power of two, including the a boundary that is an equal or greater power of two, including the
assignment of one (2**0) identifier, assignment of one (2**0) identifier,
* must not be used to evade the requirement for network interface * must not be used to evade the requirement for network interface
vendors to obtain their own block of identifiers from the IEEE, vendors to obtain their own block of identifiers from the IEEE,
and and
* must be documented in an Internet-Draft or RFC. * must be documented in an Internet-Draft or RFC.
In addition, approval must be obtained as follows (see the procedure In addition, approval must be obtained as follows (see the procedure
in Section 5.1): in Section 5.1):
* Small to medium assignments of a block of 1, 2, 4, ..., 32768, * Small to medium assignments of a block of 1, 2, 4, ..., 32768,
65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI-48 identifiers 65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI-48 identifiers
require Expert Review (see Section 5.1). require Expert Review (see Section 5.1).
* Large assignments of 131072 (2**17) or more EUI-48 identifiers * Large assignments of 131072 (2**17) or more EUI-48 identifiers
require IESG Ratification (see Section 5.1). require IESG Ratification (see Section 5.1).
2.2. 64-Bit MAC Identifiers 2.2. 64-Bit MAC Identifiers
IEEE also defines a system of 64-bit MAC identifiers including IEEE also defines a system of 64-bit MAC identifiers, including
EUI-64s. EUI-64 identifiers are used as follows: EUI-64s. EUI-64 identifiers are used as follows:
* In IEEE Std 1394 [IEEE1394] (also known as FireWire and i.Link) * In IEEE Std 1394 [IEEE1394] (also known as FireWire and i.Link)
* In IEEE Std 802.15.4 [IEEE802.15.4] (also known as ZigBee) * In IEEE Std 802.15.4 [IEEE802.15.4] (also known as Zigbee)
* In [InfiniBand] * In [InfiniBand]
* In a modified form to construct some IPv6 interface identifiers as * In a modified form to construct some IPv6 Interface Identifiers,
described in Section 2.2.1, although this use is now deprecated as described in Section 2.2.1, although this use is now deprecated
Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) assignment, Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) assignment,
or a shorter extension to longer assigned prefixes [RAC_OUI] so as to or a shorter extension to longer assigned prefixes [RAC_OUI] so as to
total 64 bits, produces an EUI-64 identifier under that OUI or longer total 64 bits, produces an EUI-64 identifier under that OUI or longer
prefix. As with EUI-48 identifiers, the first octet has the same prefix. As with EUI-48 identifiers, the first octet has the same
special low order bits. special low-order bits.
An AFN, a DNS RRTYPE, and CBOR tag have been assigned for 64-bit MAC An AFN, a DNS RRTYPE, and CBOR tag have been assigned for 64-bit MAC
addresses as discussed in Sections 2.4, 5.3, and 5.9. addresses, as discussed in Sections 2.4, 5.3, and 5.9.
The discussion below is almost entirely in terms of the "Modified" The discussion below is almost entirely in terms of the "Modified"
form of EUI-64 identifiers; however, anyone assigned such an form of EUI-64 identifiers; however, anyone assigned such an
identifier can also use the unmodified form as a MAC identifier on identifier can also use the unmodified form as a MAC identifier on
any link that uses such 64-bit identifiers for interfaces. any link that uses such 64-bit identifiers for interfaces.
2.2.1. IPv6 Use of Modified EUI-64 Identifiers 2.2.1. IPv6 Use of Modified EUI-64 Identifiers
The approach described below for constructing IPv6 Interface The approach described below for constructing IPv6 Interface
Identifiers is now deprecated and the method specified in [RFC8064] Identifiers is now deprecated, and the method specified in [RFC8064]
is recommended. is recommended.
EUI-64 identifiers have been used to form the lower 64 bits of some EUI-64 identifiers have been used to form the lower 64 bits of some
IPv6 addresses (Section 2.5.1 and Appendix A of [RFC4291] and IPv6 addresses (Section 2.5.1 and Appendix A of [RFC4291] and
Appendix A of [RFC5214]). When so used, the EUI-64 is modified by Appendix A of [RFC5214]). When so used, the EUI-64 is modified by
inverting the X (Local/Global) bit to form an IETF "Modified EUI-64 inverting the X (universal/local) bit to form an IETF "Modified
identifier". Below is an illustration of a Modified EUI-64 unicast EUI-64 identifier". Below is an illustration of a Modified EUI-64
identifier under the IANA OUI, where aa-bb-cc-dd-ee is the extension. unicast identifier under the IANA OUI, where aa-bb-cc-dd-ee is the
extension.
02-00-5E-aa-bb-cc-dd-ee 02-00-5E-aa-bb-cc-dd-ee
The first octet is shown as 02 rather than 00 because, in Modified The first octet is shown as 02 rather than 00 because, in Modified
EUI-64 identifiers, the sense of the X bit is inverted compared with EUI-64 identifiers, the sense of the X bit is inverted compared with
EUI-48 identifiers. It is the globally unique values (universal EUI-48 identifiers. It is the globally unique values (universal
scope) that have the 0x02 bit (also known as the X or universal/local scope) that have the 0x02 bit (also known as the X or universal/local
bit) on in the first octet, while those with this bit off are bit) on in the first octet, while those with this bit off are
typically locally assigned and out of scope for global assignment. typically locally assigned and out of scope for global assignment.
The X (Local/Global) bit was inverted to make it easier for network The X (universal/local) bit was inverted to make it easier for
operators to type in local-scope identifiers. Thus, such Modified network operators to type in local-scope identifiers. Thus, such
EUI-64 identifiers as 1, 2, etc. (ignoring leading zeros) are local. Modified EUI-64 identifiers as 1, 2, etc. (ignoring leading zeros)
Without the modification, they would have to be are local. Without the modification, they would have to be
02-00-00-00-00-00-00-01, 02-00-00-00-00-00-00-02, etc. to be local. 02-00-00-00-00-00-00-01, 02-00-00-00-00-00-00-02, etc. to be local.
As with 48-bit MAC identifiers, the M-bit (0x01) on in the first As with 48-bit MAC identifiers, the M bit (0x01) on in the first
octet indicates a group identifier (multicast or broadcast). octet indicates a group identifier (multicast or broadcast).
When the first two octets of the extension of a Modified EUI-64 When the first two octets of the extension of a Modified EUI-64
identifier are FF-FE, the remainder of the extension is a 24-bit identifier are FF-FE, the remainder of the extension is a 24-bit
value as assigned by the OUI owner for an EUI-48. For example: value, as assigned by the OUI owner for an EUI-48. For example:
02-00-5E-FF-FE-yy-yy-yy 02-00-5E-FF-FE-yy-yy-yy
or or
03-00-5E-FF-FE-yy-yy-yy 03-00-5E-FF-FE-yy-yy-yy
where yy-yy-yy is the portion (of an EUI-48 global unicast or where yy-yy-yy is the portion (of an EUI-48 global unicast or
multicast identifier) that is assigned by the OUI owner (IANA in this multicast identifier) that is assigned by the OUI owner (IANA in this
case). Thus, any holder of one or more EUI-48 identifiers under the case). Thus, any holder of one or more EUI-48 identifiers under the
IANA OUI also has an equal number of Modified EUI-64 identifiers that IANA OUI also has an equal number of Modified EUI-64 identifiers that
can be formed by inserting FF-FE in the middle of their EUI-48 can be formed by inserting FF-FE in the middle of their EUI-48
identifiers and inverting the Local/Global bit. identifiers and inverting the universal/local bit.
In addition, certain Modified EUI-64 identifiers under the IANA OUI In addition, certain Modified EUI-64 identifiers under the IANA OUI
are reserved for holders of IPv4 addresses as follows: are reserved for holders of IPv4 addresses as follows:
02-00-5E-FE-xx-xx-xx-xx 02-00-5E-FE-xx-xx-xx-xx
where xx-xx-xx-xx is a 32-bit IPv4 address. The owner of an IPv4 where xx-xx-xx-xx is a 32-bit IPv4 address. The owner of an IPv4
address has both a unicast- and multicast-derived EUI-64 address. address has both a unicast- and multicast-derived EUI-64 address.
Modified EUI-64 identifiers from Modified EUI-64 identifiers from
02-00-5E-FE-F0-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF 02-00-5E-FE-F0-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF
are effectively reserved pending the specification of IPv4 "Class E" are effectively reserved pending the specification of IPv4 "Class E"
addresses [RFC1112]. However, for Modified EUI-64 identifiers based addresses [RFC1112]. However, for Modified EUI-64 identifiers based
on an IPv4 address, the Local/Global bit should be set to correspond on an IPv4 address, the universal/local bit should be set to
to whether the IPv4 address is local or global. (Keep in mind that correspond to whether the IPv4 address is local or global. (Keep in
the sense of the Modified EUI-64 identifier Local/Global bit is mind that the sense of the Modified EUI-64 identifier universal/local
reversed from that in (unmodified) EUI-64 identifiers.) bit is reversed from that in (unmodified) EUI-64 identifiers.)
2.2.2. EUI-64 IANA Assignment Considerations 2.2.2. EUI-64 IANA Assignment Considerations
The following table shows which Modified EUI-64 identifiers under the The following table shows which Modified EUI-64 identifiers under the
IANA OUI are reserved, assigned, or available as indicated. As noted IANA OUI are reserved, assigned, or available as indicated. As noted
above, the corresponding MAC addresses can be determined by above, the corresponding MAC addresses can be determined by
complementing the 02 bit in the first octet. In all cases, the complementing the 02 bit in the first octet. In all cases, the
corresponding multicast 64-bit MAC addresses formed by complementing corresponding multicast 64-bit MAC addresses formed by complementing
the 01 bit in the first octet have the same status as the modified the 01 bit in the first octet have the same status as the modified
64-bit unicast address blocks listed below. 64-bit unicast address blocks listed below. These values are
prefixed with 02-00-5E to form unicast modified EUI-64 addresses.
02-00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF reserved
02-00-5E-10-00-00-00-00 to 02-00-5E-10-00-00-00-FF assigned for
documentation use
02-00-5E-10-00-00-01-00 to 02-00-5E-EF-FF-FF-FF-FF available for
assignment
02-00-5E-F0-00-00-00-00 to 02-00-5E-FD-FF-FF-FF-FF reserved
02-00-5E-FE-00-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF assigned to IPv4
address holders as described above
02-00-5E-FF-00-00-00-00 to 02-00-5E-FF-FD-FF-FF-FF reserved
02-00-5E-FF-FE-00-00-00 to 02-00-5E-FF-FE-FF-FF-FF assigned for +==================================+===================+===========+
holders of EUI-48 identifiers under the IANA OUI as described | Addresses | Usage | Reference |
above +==================================+===================+===========+
| 00-00-00-00-00 to 0F-FF-FF-FF-FF | Reserved | RFC 9542 |
+----------------------------------+-------------------+-----------+
| 10-00-00-00-00 to 10-00-00-00-FF | Documentation | RFC 9542 |
+----------------------------------+-------------------+-----------+
| 10-00-00-01-00 to EF-FF-FF-FF-FF | Unassigned | |
+----------------------------------+-------------------+-----------+
| FD-00-00-00-00 to FD-FF-FF-FF-FF | Reserved | RFC 9542 |
+----------------------------------+-------------------+-----------+
| FE-00-00-00-00 to FE-FF-FF-FF-FF | IPv4 Addr Holders | RFC 9542 |
+----------------------------------+-------------------+-----------+
| FF-00-00-00-00 to FF-FD-FF-FF-FF | Reserved | RFC 9542 |
+----------------------------------+-------------------+-----------+
| FF-FE-00-00-00 to FF-FE-FF-FF-FF | IANA EUI-48 | RFC 9542 |
| | Holders | |
+----------------------------------+-------------------+-----------+
| FF-FF-00-00-00 to FF-FF-FF-FF-FF | Reserved | RFC 9542 |
+----------------------------------+-------------------+-----------+
02-00-5E-FF-FF-00-00-00 to 02-00-5E-FF-FF-FF-FF-FF reserved Table 3: IANA 64-bit MAC Addresses
The reserved identifiers above require IESG Ratification (see The reserved identifiers above require IESG Ratification (see
Section 5.1) for assignment. IANA EUI-64 identifier assignments Section 5.1) for assignment. IANA EUI-64 identifier assignments
under the IANA OUI must meet the following requirements: under the IANA OUI must meet the following requirements:
* must be for standards purposes (either for an IETF Standard or * must be for standards purposes (either for an IETF Standard or
other standard related to IETF work), other standard related to IETF work),
* must be for a power-of-two size block of identifiers starting at a * must be for a power-of-two-sized block of identifiers starting at
boundary that is an equal or greater power of two, including the a boundary that is an equal or greater power of two, including the
assignment of one (2**0) identifier, assignment of one (2**0) identifier,
* must not be used to evade the requirement for network interface * must not be used to evade the requirement for network interface
vendors to obtain their own block of identifiers from the IEEE, vendors to obtain their own block of identifiers from the IEEE,
and and
* must be documented in an Internet-Draft or RFC. * must be documented in an Internet-Draft or RFC.
In addition, approval must be obtained as follows (see the procedure In addition, approval must be obtained as follows (see the procedure
in Section 5.1): in Section 5.1):
skipping to change at page 15, line 28 skipping to change at line 680
* Large assignments of 536870912 (2**29) or more EUI-64 identifiers * Large assignments of 536870912 (2**29) or more EUI-64 identifiers
require IESG Ratification (see Section 5.1). require IESG Ratification (see Section 5.1).
2.2.3. EUI-64 Documentation Values 2.2.3. EUI-64 Documentation Values
The following blocks of unmodified 64-bit MAC addresses are for The following blocks of unmodified 64-bit MAC addresses are for
documentation use. The IPv4-derived addresses are based on the IPv4 documentation use. The IPv4-derived addresses are based on the IPv4
documentation addresses [RFC5737], and the MAC-derived addresses are documentation addresses [RFC5737], and the MAC-derived addresses are
based on the EUI-48 documentation addresses above. based on the EUI-48 documentation addresses above.
Unicast values for Documentation Use: Unicast values for documentation use:
00-00-5E-EF-10-00-00-00 to 00-00-5E-EF-10-00-00-FF general 00-00-5E-EF-10-00-00-00 to 00-00-5E-EF-10-00-00-FF general
00-00-5E-FE-C0-00-02-00 to 00-00-5E-FE-C0-00-02-FF and 00-00-5E-FE-C0-00-02-00 to 00-00-5E-FE-C0-00-02-FF and
00-00-5E-FE-C6-33-64-00 to 00-00-5E-FE-C6-33-64-FF and 00-00-5E-FE-C6-33-64-00 to 00-00-5E-FE-C6-33-64-FF and
00-00-5E-FE-CB-00-71-00 to 00-00-5E-FE-CB-00-71-FF IPv4 derived 00-00-5E-FE-CB-00-71-00 to 00-00-5E-FE-CB-00-71-FF IPv4 derived
00-00-5E-FF-FE-00-53-00 to 00-00-5E-FF-FE-00-53-FF EUI-48 derived 00-00-5E-FF-FE-00-53-00 to 00-00-5E-FF-FE-00-53-FF EUI-48 derived
00-00-5E-FE-EA-C0-00-02 and 00-00-5E-FE-EA-C6-33-64 and 00-00-5E-FE-EA-C0-00-02 and 00-00-5E-FE-EA-C6-33-64 and
00-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 00-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast
[RFC6034] [RFC6034]
Multicast values for Documentation Use: Multicast values for documentation use:
01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general 01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general
01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and 01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and
01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and 01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and
01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived 01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived
01-00-5E-FE-EA-C0-00-02 and 01-00-5E-FE-EA-C6-33-64 and 01-00-5E-FE-EA-C0-00-02 and 01-00-5E-FE-EA-C6-33-64 and
01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast
[RFC6034] [RFC6034]
skipping to change at page 16, line 4 skipping to change at line 705
01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general 01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general
01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and 01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and
01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and 01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and
01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived 01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived
01-00-5E-FE-EA-C0-00-02 and 01-00-5E-FE-EA-C6-33-64 and 01-00-5E-FE-EA-C0-00-02 and 01-00-5E-FE-EA-C6-33-64 and
01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast
[RFC6034] [RFC6034]
01-00-5E-FF-FE-90-10-00 to 01-00-5E-FF-FE-90-10-FF EUI-48 derived 01-00-5E-FF-FE-90-10-00 to 01-00-5E-FF-FE-90-10-FF EUI-48 derived
2.3. Other 48-bit MAC Identifiers Used by the IETF 2.3. Other 48-Bit MAC Identifiers Used by the IETF
There are two other blocks of 48-bit MAC identifiers that are used by There are two other blocks of 48-bit MAC identifiers that are used by
the IETF as described below. the IETF as described below.
2.3.1. Identifiers with a '33-33' Prefix 2.3.1. Identifiers with a '33-33' Prefix
All 48-bit multicast MAC identifiers prefixed "33-33" (that is, the All 48-bit multicast MAC identifiers prefixed with "33-33" (that is,
2**32 multicast MAC identifiers in the range from 33-33-00-00-00-00 the 2**32 multicast MAC identifiers in the range from
to 33-33-FF-FF-FF-FF) are used as specified in [RFC2464] for IPv6 33-33-00-00-00-00 to 33-33-FF-FF-FF-FF) are used as specified in
multicast. In all of these identifiers, the Group bit (the bottom [RFC2464] for IPv6 multicast. In all of these identifiers, the Group
bit of the first octet) is on, as is required to work properly with bit (the bottom bit of the first octet) is on, as is required to work
existing hardware as a multicast identifier. They also have the properly with existing hardware as a multicast identifier. They also
Local bit on but any Ethernet using standard IPv6 multicast should have the Local bit on, but any Ethernet using standard IPv6 multicast
note that these addresses will be used for that purpose. These should note that these addresses will be used for that purpose.
multicast MAC addresses fall into the Administratively Assigned SLAP These multicast MAC addresses fall into the Administratively Assigned
quadrant (see Section 2.1.1). SLAP quadrant (see Section 2.1.1).
Historical notes: It was the custom during IPv6 design to use "3" | Historical Notes: It was the custom during IPv6 design to use
for unknown or example values and 3333 Coyote Hill Road, Palo | "3" for unknown or example values, and 3333 Coyote Hill Road,
Alto, California, is the address of PARC (Palo Alto Research | Palo Alto, California is the address of PARC (Palo Alto
Center, formerly "Xerox PARC"). Ethernet was originally specified | Research Center), formerly "Xerox PARC." Ethernet was
by the Digital Equipment Corporation, Intel Corporation, and Xerox | originally specified by the Digital Equipment Corporation,
Corporation. The pre-IEEE [IEEE.802.3_2012] Ethernet protocol has | Intel Corporation, and Xerox Corporation. The pre-IEEE
sometimes been known as "DIX" Ethernet from the first letters of | [IEEE.802.3_2012] Ethernet protocol has sometimes been known as
the names of these companies. | "DIX" Ethernet from the first letters of the names of these
| companies.
2.3.2. The 'CF Series' 2.3.2. The CF Series
The Informational [RFC2153] declared the 3-octet values from CF-00-00 The Informational [RFC2153] declared the 3-octet values from CF-00-00
through CF-FF-FF to be "OUIs" available for assignment by IANA to through CF-FF-FF to be "OUIs" available for assignment by IANA to
software vendors for use in PPP [RFC1661] or for other uses where software vendors for use in PPP [RFC1661] or for other uses where
vendors do not otherwise need an IEEE-assigned OUI. When used as vendors do not otherwise need an IEEE-assigned OUI. When used as
48-bit MAC prefixes, these values have all of the Z, Y, X (Local), 48-bit MAC prefixes, these values have all of the Z, Y, X (Local) and
and M (Group) special bits at the bottom of the first octet equal to M (Group) special bits at the bottom of the first octet equal to one,
one, while all IEEE-assigned OUIs thus far have the X and M bits zero while all IEEE-assigned OUIs thus far have the X and M bits as zero
and all CIDs have bits Y and M zero; thus, there can be no conflict and all CIDs have the Y and M bits as zero; thus, there can be no
between CF Series "OUI"s and IEEE assigned OUI/CIDs. Multicast MAC conflict between CF series "OUIs" and IEEE-assigned OUIs/CIDs.
addresses constructed with a "CF" series OUI would fall into the Multicast MAC addresses constructed with a CF series OUI would fall
Standard Assigned SLAP quadrant (see Section 2.1.1). The Group bit into the Standard Assigned SLAP quadrant (see Section 2.1.1). The
is meaningless in PPP. To quote [RFC2153]: "The 'CF0000' series was Group bit is meaningless in PPP. To quote [RFC2153]: "The 'CF0000'
arbitrarily chosen to match the PPP NLPID 'CF', as a matter of series was arbitrarily chosen to match the PPP NLPID 'CF', as a
mnemonic convenience." (For further information on NLPIDs, see matter of mnemonic convenience." (For further information on Network
[RFC6328].) Layer Protocol Identifiers (NLPIDs), see [RFC6328].)
CF-00-00 is reserved, and IANA lists multicast identifier CF-00-00 is reserved. CF-00-00-00-00-00 is a multicast identifier
CF-00-00-00-00-00 as used for Ethernet loopback tests. listed by IANA as used for Ethernet loopback tests.
In over a decade of availability, only a handful of values in the CF In over a decade of availability, only a handful of values in the CF
Series have been assigned. (See "IANA OUI Ethernet Numbers" series have been assigned. (See the "IANA OUI Ethernet Numbers"
[EthernetNum] and "PPP Numbers" [PPPNum] ). [EthernetNum] and "Point-to-Point (PPP) Protocol Field Assignments"
[PPPNum] registry groups.)
2.3.2.1. Changes to RFC 2153 2.3.2.1. Changes to RFC 2153
The IANA Considerations in [RFC2153] were updated as follows by the The IANA Considerations in [RFC2153] were updated as follows by the
approval of [RFC5342] and remain so updated (no technical changes approval of [RFC5342] and remain so updated (no technical changes
have been made): have been made):
* Use of these 'CF Series' identifiers based on IANA assignment was * Use of these CF series identifiers based on IANA assignment was
deprecated. deprecated.
* IANA was instructed not to assign any further values in the 'CF * IANA was instructed not to assign any further values in the CF
Series'. series.
2.4. CBOR Tags 2.4. CBOR Tags
The Concise Binary Object Representation (CBOR [RFC8949]) is a data The Concise Binary Object Representation (CBOR) [RFC8949] is a data
format whose design goals include the possibility of very small code format whose design goals include the possibility of very small code
size, fairly small message size, and extensibility. In CBOR, a data size, fairly small message size, and extensibility. In CBOR, a data
item can be enclosed by a CBOR tag to give it some additional item can be enclosed by a CBOR tag to give it some additional
semantics identified by that tag. CBOR tagged data items (fields) semantics identified by that tag. CBOR-tagged data items (fields)
are not used in actual IEEE 802 address fields but may be used in are not used in actual IEEE 802 address fields but may be used in
CBOR encoded parts of protocol messages. CBOR-encoded parts of protocol messages.
IANA has assigned TBD1 as the CBOR tag to indicate a MAC address. IANA has assigned 48 as the CBOR tag to indicate a MAC address. The
The enclosed data item is an octet string. The length of the octet enclosed data item is an octet string. The length of the octet
string indicates whether a 48-bit (6 octet) or 64-bit (8 octet) MAC string indicates whether a 48-bit (6 octet) or 64-bit (8 octet) MAC
address is encoded. Should some other multiple of 8 bits length MAC address is encoded. Should some other multiple of 8 bits be used in
addresses be used in the future, such as a 128-bit (16 octet) MAC the future for the length of MAC addresses, such as a 128-bit
address, the TBD1 tag will be used. (16-octet) MAC address, the 48 tag will be used.
IANA has assigned TDB2 as the CBOR tag to indicate an OUI, CID, or IANA has assigned 1048 as the CBOR tag to indicate an OUI, CID, or CF
"CF" series organizational identifier. The enclosed data item is an series organizational identifier. The enclosed data item is an octet
octet string of length 3 to hold the 24-bit OUI or CID (see string of length 3 to hold the 24-bit OUI or CID (see Section 2.1.2).
Section 2.1.2).
3. Ethernet Protocol Parameters 3. Ethernet Protocol Parameters
Ethernet protocol parameters provide a means of indicating, near the Ethernet protocol parameters provide a means of indicating, near the
beginning of a frame, the contents of that frame -- for example, that beginning of a frame, the contents of that frame -- for example, that
it contains IPv4 or IPv6. it contains IPv4 or IPv6.
There are two types of protocol identifier parameters (See There are two types of protocol identifier parameters (see
[EthernetNum]) that can occur in Ethernet frames as follows: [EthernetNum]) that can occur in Ethernet frames:
EtherTypes: These are 16-bit identifiers which, when considered as EtherTypes:
an unsigned integer, are equal to or larger than 0x0600. Figure 2 These are 16-bit identifiers that, when considered as an unsigned
shows the simplest case where the EtherType of the protocol data integer, are equal to or larger than 0x0600. Figure 2 shows the
in the frame appears immediately after the destination and source simplest case where the EtherType of the protocol data in the
MAC addresses. [IEEE802_OandA] specifies two EtherTypes for frame appears immediately after the destination and source MAC
local, experimental use: 0x88B5 and 0x88B6. addresses. [IEEE802_OandA] specifies two EtherTypes for local,
experimental use: 0x88B5 and 0x88B6.
LSAPs: These are 8-bit protocol identifiers that occur in pairs LSAPs:
after a field that gives the frame length. Such a length must, These are 8-bit protocol identifiers that occur in pairs after a
when considered as an unsigned integer, be less than 0x5DD, or it field that gives the frame length. Such a length must, when
could be mistaken as an EtherType. However, the LLC encapsulation considered as an unsigned integer, be less than 0x5DD, or it could
be mistaken as an EtherType. However, the LLC encapsulation
EtherType 0x8870 [IEEE802.1AC] may also be used in place of such a EtherType 0x8870 [IEEE802.1AC] may also be used in place of such a
length as a "length indication" of nonspecific length. LSAPs length as a "length indication" of nonspecific length. LSAPs
occur in pairs where one is intended to indicate the source occur in pairs, where one is intended to indicate the source
protocol handler (SSAP) and one the destination protocol handler protocol handler (SSAP) and the other the destination protocol
(DSAP); however, use cases where the two are different have been handler (DSAP); however, use cases where the two are different
relatively rare. See Figure 3 for the simplest case where the have been relatively rare. See Figure 3 for the simplest case
length field appears immediately after the destination and source where the length field appears immediately after the destination
MAC addresses. In that figure, the CTL (control) field value of 3 and source MAC addresses. In that figure, the CTL (control) field
indicates datagram service. This type of protocol identification value of 3 indicates datagram service. This type of protocol
is sometimes called "LLC" (Logical Link Control). identification is sometimes called "LLC" (Logical Link Control).
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Destination MAC Address /// | Destination MAC Address ///
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Source MAC Address /// | Source MAC Address ///
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| EtherType, greater than or equal to 0x0600 | | EtherType, greater than or equal to 0x0600 |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Protocol Data /// | Protocol Data ///
skipping to change at page 19, line 4 skipping to change at line 853
| Destination MAC Address /// | Destination MAC Address ///
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Source MAC Address /// | Source MAC Address ///
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Frame length (or 0x8870) | | Frame length (or 0x8870) |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| DSAP | SSAP | | DSAP | SSAP |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| CTL = 0x03 | Protocol Data /// | CTL = 0x03 | Protocol Data ///
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Figure 3: LSAP Frame Protocol Labeling Figure 3: LSAP Frame Protocol Labeling
The concept of EtherType labeling has been extended to labeling by The concept of EtherType labeling has been extended to labeling by
Ethernet "tags". An Ethernet tag in this sense is a prefix whose Ethernet "tags". An Ethernet tag in this sense is a prefix whose
type is identified by an EtherType that is then followed by either type is identified by an EtherType that is then followed by either
another tag, an EtherType, or an LLC LSAP (Link-Layer Service Access another tag, an EtherType, or an LLC Link-Layer Service Access Point
Point) protocol indicator for the "main" body of the frame. (LSAP) protocol indicator for the "main" body of the frame.
Customarily, in the [IEEE802_OandA] world, tags are a fixed length Customarily, in the world of [IEEE802_OandA], tags are a fixed length
and do not include any encoding of their own length. An example is and do not include any encoding of their own length. An example is
the C-Tag (formerly the Q-Tag) [IEEE.802.1Q_2014]. It provides the C-Tag (formerly the Q-Tag) [IEEE.802.1Q_2014]. It provides
customer VLAN and priority information for a frame. Any device that customer VLAN and priority information for a frame. Any device that
is processing a frame cannot, in general, safely process anything in is processing a frame cannot, in general, safely process anything in
the frame past an EtherType it does not understand. the frame past an EtherType it does not understand.
Neither EtherTypes nor LSAPs are assigned by IANA; they are assigned Neither EtherTypes nor LSAPs are assigned by IANA; they are assigned
by the IEEE Registration Authority [IEEE_RA] (see Section 1.2 above by the IEEE Registration Authority [IEEE_RA] (see Section 1.2 and
and Appendix B). However, both LSAPs and EtherTypes have extension Appendix B). However, both LSAPs and EtherTypes have extension
mechanisms so that they can be used with five-octet Ethernet protocol mechanisms so that they can be used with five-octet Ethernet protocol
identifiers under an OUI, including those assigned by IANA under the identifiers under an OUI, including those assigned by IANA under the
IANA OUI. IANA OUI.
When using the IEEE 802 Logical Link Control (LLC) format (Subnetwork When using the IEEE 802 Logical Link Control (LLC) format (Subnetwork
Access Protocol (SNAP)) [IEEE802_OandA] for a frame, an OUI-based Access Protocol (SNAP)) [IEEE802_OandA] for a frame, an OUI-based
protocol identifier can be expressed as follows: protocol identifier can be expressed as follows:
xx-xx-AA-AA-03-yy-yy-yy-zz-zz xx-xx-AA-AA-03-yy-yy-yy-zz-zz
skipping to change at page 20, line 14 skipping to change at line 909
It is also possible, within the SNAP format, to use an arbitrary It is also possible, within the SNAP format, to use an arbitrary
EtherType. Putting the EtherType as the zz-zz field after an all- EtherType. Putting the EtherType as the zz-zz field after an all-
zeros OUI (00-00-00) does this. It looks like zeros OUI (00-00-00) does this. It looks like
xx-xx-AA-AA-03-00-00-00-zz-zz xx-xx-AA-AA-03-00-00-00-zz-zz
where zz-zz is the EtherType. where zz-zz is the EtherType.
As well as labeling frame contents, IEEE 802 protocol types appear As well as labeling frame contents, IEEE 802 protocol types appear
within NBMA (Non-Broadcast Multi-Access) Next Hop Resolution Protocol within Non-Broadcast Multi-Access (NBMA) Next Hop Resolution Protocol
[RFC2332] messages. Such messages have provisions for both two-octet [RFC2332] messages. Such messages have provisions for both two-octet
EtherTypes and OUI-based protocol types. 16-bit EtherTypes also occur EtherTypes and OUI-based protocol types. 16-bit EtherTypes also occur
in the Generic Router Encapsulation (GRE [RFC2784]) header and in the in the Generic Routing Encapsulation (GRE) [RFC2784] header and in
GENEVE (Generic Network Virtualization Encapsulation [RFC8926]) the Generic Network Virtualization Encapsulation (Geneve) [RFC8926]
encapsulation header. encapsulation header.
3.1. Ethernet Protocol Assignment under the IANA OUI 3.1. Ethernet Protocol Assignment under the IANA OUI
Two-octet protocol numbers under the IANA OUI are available, as in Two-octet protocol numbers under the IANA OUI are available, as in
88-B7-00-00-5E-qq-qq 88-B7-00-00-5E-qq-qq
or or
skipping to change at page 20, line 44 skipping to change at line 939
numbers available from 00-00-5E-00-00 to 00-00-5E-FF-FF (see numbers available from 00-00-5E-00-00 to 00-00-5E-FF-FF (see
[EthernetNum]). The extreme values of this range, 00-00-5E-00-00 and [EthernetNum]). The extreme values of this range, 00-00-5E-00-00 and
00-00-5E-FF-FF, are reserved and require IESG Ratification for 00-00-5E-FF-FF, are reserved and require IESG Ratification for
assignment (see Section 5.1). New assignments of protocol numbers assignment (see Section 5.1). New assignments of protocol numbers
(qq-qq) under the IANA OUI must meet the following requirements: (qq-qq) under the IANA OUI must meet the following requirements:
* the assignment must be for standards use (either for an IETF * the assignment must be for standards use (either for an IETF
Standard or other standard related to IETF work), Standard or other standard related to IETF work),
* the protocol must include a version field at a fixed offset or an * the protocol must include a version field at a fixed offset or an
equivalent marking such that later version can be indicated in a equivalent marking such that later versions can be indicated in a
way recognizable by earlier versions, way recognizable by earlier versions,
* it must be documented in an Internet-Draft or RFC, and * the protocol must be documented in an Internet-Draft or RFC, and
* such protocol numbers are not to be assigned for any protocol that * such protocol numbers are not to be assigned for any protocol that
has an EtherType. (Either that EtherType can be used directly or, has an EtherType. (That EtherType can be used directly, or -- in
in the LSAPs case, using the SNAP SAP and putting an all-zeros the LSAPs case -- it can be used with the SNAP SAP by putting an
"OUI" before the EtherType as described above.) all-zero "OUI" before the EtherType as described above.)
In addition, the Expert Review (or IESG Ratification for the two In addition, the Expert Review (or IESG Ratification for the two
reserved values) must be obtained using the procedure specified in reserved values) must be obtained using the procedure specified in
Section 5.1. Section 5.1.
3.2. Documentation Protocol Number 3.2. Documentation Protocol Number
0x0042 is a protocol number under the IANA OUI (that is, 0x0042 is a protocol number under the IANA OUI (that is,
00-00-5E-00-42) to be used as an example for documentation purposes. 00-00-5E-00-42) to be used as an example for documentation purposes.
4. Other OUI/CID-Based Parameters 4. Other OUI/CID-Based Parameters
Some IEEE 802 and other protocols provide for parameters based on an Some IEEE 802 and other protocols provide for parameters based on an
OUI or CID beyond those discussed above. Such parameters commonly OUI or CID beyond those discussed above. Such parameters commonly
consist of an OUI or CID plus one octet of additional value. They consist of an OUI or CID plus one octet of additional value. They
are called Organizationally-Specific parameters (sometimes informally are called Organizationally Specific parameters (sometimes informally
and less accurately referred to as "vendor specific"). They would and less accurately referred to as "vendor specific"). They would
look like look like
yy-yy-yy-zz yy-yy-yy-zz
where yy-yy-yy is the OUI/CID and zz is the additional specifier. An where yy-yy-yy is the OUI/CID and zz is the additional specifier. An
example is the Cipher Suite Selector in [IEEE.802.11_2012]. example is the Cipher Suite Selector in [IEEE.802.11_2012].
Values may be assigned under the IANA OUI for such other OUI-based Values may be assigned under the IANA OUI for other OUI-based
parameter usage by Expert Review except that, for each use, the parameter usage by Expert Review, except that, for each use, the
additional specifier values consisting of all zero bits and all one additional specifier values consisting of all zero bits and all one
bits (0x00 (00-00-5E-00) and 0xFF (00-00-5E-FF) for a one-octet bits (0x00 (00-00-5E-00) and 0xFF (00-00-5E-FF) for a one-octet
specifier) are reserved and require IESG Ratification (see specifier) are reserved and require IESG Ratification (see
Section 5.1) for assignment; also, the additional specifier value Section 5.1) for assignment; also, the additional specifier value
0x42 (00-00-5E-42 for a one octet specifier, right justified and 0x42 (00-00-5E-42 for a one octet specifier, right justified and
filled with zeros on the left if the specifier is more than one filled with zeros on the left if the specifier is more than one
octet) is assigned for use as an example in documentation. octet) is assigned for use as an example in documentation.
Assignments of such other IANA OUI-based parameters must be for Assignments of other IANA OUI-based parameters must be for standards
standards use (either for an IETF Standard or other standard related use (either for an IETF Standard or other standard related to IETF
to IETF work) and be documented in an Internet-Draft or RFC. The work) and be documented in an Internet-Draft or RFC. The first time
first time a value is assigned for a particular parameter of this a value is assigned for a particular parameter of this type, an IANA
type, an IANA registry will be created to contain that assignment and registry will be created to contain that assignment and any
any subsequent assignments of values for that parameter under the subsequent assignments of values for that parameter under the IANA
IANA OUI. The Expert may specify the name of the registry. OUI. The Expert may specify the name of the registry.
If different policies from those above are required for such a If different policies from those above are required for such a
parameter, a BCP or Standards Track RFC should be adopted to update parameter, a BCP or Standards Track RFC should be adopted to update
this BCP and specify the new policy and parameter. this BCP and specify the new policy and parameter.
4.1. LLDP IETF Organizationally-Specific TLV Type 4.1. LLDP IETF Organizationally Specific TLV Type
An example of such an "other IANA OUI based parameter" is specified An example of an "other IANA OUI-based parameter" is specified in
in [RFC8520]. This provides for an Organizationally-Specific TLV [RFC8520]. This provides for an Organizationally Specific TLV type
type for announcing a Manufacturer Usage Description (MUD) Uniform for announcing a Manufacturer Usage Description (MUD) Uniform
Resource Locator (URL) in the IEEE Link Local Discovery Protocol Resource Locator (URL) in the IEEE Link Local Discovery Protocol
(LLDP [IEEE802.1AB]). Additional IETF use of code points in this (LLDP) [IEEE802.1AB]. Additional IETF use of code points in this
space have been proposed [BGP11dp]. (See also Section 5.8.) space have been proposed [BGP11dp]. (See also Section 5.8.)
5. IANA Considerations 5. IANA Considerations
This document concerns IANA considerations for the assignment of This document concerns IANA considerations for the assignment of
Ethernet parameters in connection with the IANA OUI and related Ethernet parameters in connection with the IANA OUI and related
matters. matters.
Note: The "IETF OUI Ethernet Numbers" IANA Registry Group (web Note: The "IANA OUI Ethernet Numbers" registry group (web page) is
page) is for registries of numbers assigned under the IANA OUI for registries of numbers assigned under the IANA OUI, while the
while the "IEEE 802 Numbers" IANA Registry Group has informational "IEEE 802 Numbers" registry group has informational lists of
lists of numbers assigned by the IEEE Registration Authority. numbers assigned by the IEEE Registration Authority.
This document does not create any new IANA registries. This document does not create any new IANA registries.
The MAC address values assigned for documentation and the protocol The MAC address values assigned for documentation and the protocol
number for documentation were both assigned by [RFC7042]. number for documentation were both assigned by [RFC7042].
No existing assignment is changed by this document. No existing assignment is changed by this document.
5.1. Expert Review and IESG Ratification 5.1. Expert Review and IESG Ratification
skipping to change at page 22, line 46 skipping to change at line 1035
The Expert(s) referred to in this document shall consist of one or The Expert(s) referred to in this document shall consist of one or
more persons appointed by and serving at the pleasure of the IESG. more persons appointed by and serving at the pleasure of the IESG.
5.1.1. Expert Review Guidance 5.1.1. Expert Review Guidance
The procedure described for Expert Review assignments in this The procedure described for Expert Review assignments in this
document is consistent with the IANA Expert Review policy described document is consistent with the IANA Expert Review policy described
in [RFC8126]. in [RFC8126].
While finite, the universe of MAC code points from which Expert- While finite, the universe of MAC code points from which Expert-
judged assignments will be made is felt to be large enough that the judged assignments will be made is considered to be large enough that
requirements given in this document and the Experts' good judgment the requirements given in this document and the Experts' good
are sufficient guidance. The idea is for the Expert to provide a judgment are sufficient guidance. The idea is for the Expert to
light sanity check for small assignments of MAC identifiers, with provide a light reasonableness check for small assignments of MAC
increased scrutiny by the Expert for medium-sized assignments of MAC identifiers, with increased scrutiny by the Expert for medium-sized
identifiers and assignments of protocol identifiers and other IANA assignments of MAC identifiers and assignments of protocol
OUI-based parameters. identifiers and other IANA OUI-based parameters.
5.1.2. Expert Review and IESG Ratification Procedure 5.1.2. Expert Review and IESG Ratification Procedure
It can make sense to assign very large portions of the MAC identifier It can make sense to assign very large portions of the MAC identifier
code point space. (Note that existing assignments include one for code point space. (Note that existing assignments include one for
half of the entire multicast IANA 48-bit code point space and one for half of the entire multicast IANA 48-bit code point space and one for
a sixteenth of that multicast code point space.) In those cases, and a sixteenth of that multicast code point space.) In those cases, and
in cases of the assignment of "reserved" values, IESG Ratification of in cases of the assignment of "reserved" values, IESG Ratification of
an Expert Review approval recommendation is required as described an Expert Review approval recommendation is required as described
below. This can be viewed as a combination of Expert Review and IESG below. This can be viewed as a combination of Expert Review and IESG
skipping to change at page 23, line 28 skipping to change at line 1066
The applicant always completes the appropriate template from The applicant always completes the appropriate template from
Appendix A below and sends it to IANA <iana@iana.org>. Appendix A below and sends it to IANA <iana@iana.org>.
IANA always sends the template to an appointed Expert. If the IANA always sends the template to an appointed Expert. If the
Expert recuses themselves or is non-responsive, IANA may choose an Expert recuses themselves or is non-responsive, IANA may choose an
alternative appointed Expert or, if none is available, will alternative appointed Expert or, if none is available, will
contact the IESG. contact the IESG.
In all cases, if IANA receives a disapproval from an Expert In all cases, if IANA receives a disapproval from an Expert
selected to review an application template, the application will selected to review an application template, the application will
be denied. The Expert should provide a reason for refusal which be denied. The Expert should provide a reason for refusal, which
IANA will communicate back to the applicant. IANA will communicate back to the applicant.
If the assignment is based on Expert Review: If the assignment is based on Expert Review:
If IANA receives approval and code points are available, If IANA receives approval and code points are available, IANA
IANA will make the requested assignment. will make the requested assignment.
If the assignment is based on IESG Ratification: If the assignment is based on IESG Ratification:
The procedure starts with the first steps above for Expert The procedure starts with the first steps above for Expert
Review. If the Expert disapproves the application, they Review. If the Expert disapproves the application, they simply
simply inform IANA who in turn informs the applicant that inform IANA, who in turn informs the applicant that their
their request is denied; however, if the Expert believes the request is denied; however, if the Expert believes the
application should be approved, or is uncertain and believes application should be approved or is uncertain and believes
that the circumstances warrant the attention of the IESG, that the circumstances warrant the attention of the IESG, the
the Expert will inform IANA about their advice, and IANA Expert will inform IANA about their advice, and IANA will
will forward the application, together with the reasons forward the application, together with the reasons provided by
provided by the Expert for approval or uncertainty, to the the Expert for approval or uncertainty, to the IESG. The IESG
IESG. The IESG must decide whether the assignment will be must decide whether the assignment will be granted. This can
granted. This can be accomplished by a management item in be accomplished by a management item in an IESG telechat, as is
an IESG telechat as is done for other types of requests. If done for other types of requests. If the IESG decides not to
the IESG decides not to ratify a favorable opinion by the ratify a favorable opinion by the Expert or decides against an
Expert or decides against an application where the Expert is application where the Expert is uncertain, the application is
uncertain, the application is denied; otherwise, it is denied; otherwise, it is granted. The IESG will communicate
granted. The IESG will communicate its decision to the its decision to the Expert and to IANA. In case of refusal,
Expert and to IANA. In case of refusal, the IESG should the IESG should provide a reason, which IANA will communicate
provide a reason which IANA will communicate to the to the applicant.
applicant.
5.2. IANA Registry Group (Web Page) Name Changes 5.2. IANA Registry Group (Web Page) Name Changes
For clarity and parallelism with the IANA "IEEE 802 Numbers" registry For clarity and parallelism with the IANA "IEEE 802 Numbers" registry
group, the IANA "Ethernet Numbers" registry group is re-named the group, the IANA "Ethernet Numbers" registry group has been renamed
"IANA OUI Ethernet Numbers" web page. the "IANA OUI Ethernet Numbers" registry.
As this document replaces [RFC7042], references to [RFC7042] in IANA As this document replaces [RFC7042], references to [RFC7042] in IANA
registries in both the IANA IEEE 802 Numbers and the IANA IETF OUI registries in both the "IEEE 802 Numbers" and the "IANA OUI Ethernet
Ethernet Numbers registry groups will be replaced by references to Numbers" registry groups have been replaced by references to this
[this document]. Other IANA registry references to [RFC7042] are not document. Other IANA registry references to [RFC7042] are not
changed. changed.
5.3. MAC Address AFNs and RRTYPEs 5.3. MAC Address AFNs and RRTYPEs
IANA has assigned Address Family Numbers (AFNs) for MAC addresses as IANA has assigned Address Family Numbers (AFNs) for MAC addresses as
follows: follows:
+============+=========+========+===========+ +============+=========+========+===========+
| AFN | Decimal | Hex | Reference | | AFN | Decimal | Hex | Reference |
+============+=========+========+===========+ +============+=========+========+===========+
| 48-bit MAC | 16389 | 0x4005 | [RFC7042] | | 48-bit MAC | 16389 | 0x4005 | [RFC7042] |
+------------+---------+--------+-----------+ +------------+---------+--------+-----------+
| 64-bit MAC | 16390 | 0x4006 | [RFC7042] | | 64-bit MAC | 16390 | 0x4006 | [RFC7042] |
+------------+---------+--------+-----------+ +------------+---------+--------+-----------+
| 24-bit OUI | 16391 | 0x4007 | [RFC7961] | | OUI | 16391 | 0x4007 | [RFC7961] |
+------------+---------+--------+-----------+ +============+=========+========+===========+
+-------------------------------------------+
| Lower 24 bits of a 48-bit MAC address: | | Lower 24 bits of a 48-bit MAC address: |
+------------+---------+--------+-----------+ +============+=========+========+===========+
| MAC/24 | 16392 | 0x4008 | [RFC7961] | | MAC/24 | 16392 | 0x4008 | [RFC7961] |
+------------+---------+--------+-----------+ +============+=========+========+===========+
+-------------------------------------------+
| Lower 40 bits of a 64-bit MAC address: | | Lower 40 bits of a 64-bit MAC address: |
+------------+---------+--------+-----------+ +============+=========+========+===========+
| MAC/40 | 16393 | 0x4009 | [RFC7961] | | MAC/40 | 16393 | 0x4009 | [RFC7961] |
+------------+---------+--------+-----------+ +------------+---------+--------+-----------+
Table 3 Table 4
IANA has assigned DNS RRTYPEs [RFC6895] for MAC addresses as follows: IANA has assigned DNS RRTYPEs [RFC6895] for MAC addresses as follows:
+============+==========+==================+===========+ +============+==========+==================+===========+
| | | RRTYPE Code | | | | | RRTYPE Code | |
+============+==========+=========+========+===========+ +============+==========+=========+========+===========+
| Data | Mnemonic | Decimal | Hex | Reference | | Data | Mnemonic | Decimal | Hex | Reference |
+============+==========+=========+========+===========+ +============+==========+=========+========+===========+
| 48-bit MAC | EUI48 | 108 | 0x006C | [RFC7043] | | 48-bit MAC | EUI48 | 108 | 0x006C | [RFC7043] |
+------------+----------+---------+--------+-----------+ +------------+----------+---------+--------+-----------+
| 64-bit MAC | EUI64 | 109 | 0x006D | [RFC7043] | | 64-bit MAC | EUI64 | 109 | 0x006D | [RFC7043] |
+------------+----------+---------+--------+-----------+ +------------+----------+---------+--------+-----------+
Table 4 Table 5
5.4. Informational IANA Registry Group Material 5.4. Informational IANA Registry Group Material
IANA maintains an informational registry group, currently implemented IANA maintains an informational registry group, currently implemented
as a webpage, concerning EtherTypes, OUIs, and multicast addresses as a web page, concerning EtherTypes, OUIs, and multicast addresses
assigned under OUIs other than the IANA OUI. The title of this assigned under OUIs other than the IANA OUI. The title of this
informational registry group is "IEEE 802 Numbers". IANA will update informational registry group is "IEEE 802 Numbers". IANA updates
that informational registry group when changes are provided by or that informational registry group when changes are provided by or
approved by the Expert(s). approved by the Expert(s).
5.5. EtherType Assignment Process 5.5. EtherType Assignment Process
Applying to the IEEE Registration Authority for an EtherType needed Applying to the IEEE Registration Authority for an EtherType needed
by an IETF protocol requires IESG approval as stated in Appendix B. by an IETF protocol requires IESG Approval, as stated in Appendix B.
To minimize confusion, this process will normally be done by the To minimize confusion, this process will normally be done by the
primary expert for the informational IANA 802 Numbers EtherType primary expert for the informational "EtherType" registry within the
registry as described below (see also Section 5.4). "IEEE 802 Numbers" registry group, as described below (see also
Section 5.4).
After IESG approval of the requirement for an EtherType, the IESG After IESG Approval of the requirement for an EtherType, the IESG
should refer the matter to IANA. In any case, IANA will ask the IANA should refer the matter to IANA. In any case, IANA will ask the
IEEE 802 Numbers EtherType registry expert to execute the IEEE "EtherType" registry expert to execute the IEEE Registration
Registration Authority [IEEE_RA] EtherType request process. This Authority [IEEE_RA] EtherType request process. This path is
path is specified because the IESG usually deals with IANA for specified because the IESG usually deals with IANA for assignment
assignment actions and because IANA should be aware of which IANA actions and because IANA should be aware of which "EtherType"
IEEE 802 Numbers EtherType registry expert(s) are available, normally registry expert(s) are available, normally referring the making of
refering the making of the Ethertype assignment request to the the EtherType assignment request to the primary expert.
primary expert.
Here is sample text for an Internet Draft where both IANA and IEEE Here is sample text for an Internet-Draft where both IANA and IEEE
assignments are required, where "YYY" would be replaced by an assignments are required, where "YYY" would be replaced by an
explanation of for what/why the EtherType is needed in whatever level explanation of for what/why the EtherType is needed in whatever level
of detail is necessary and would normally include a reference or of detail is necessary and would normally include a reference or
references to other appropriate parts of the Internet Draft: references to other appropriate parts of the Internet-Draft:
| X. Assignment Considerations | X. Assignment Considerations
| |
| X.1. IEEE Assignment Considerations | X.1. IEEE Assignment Considerations
| |
| The IESG is requested to approve applying to the IEEE | The IESG is requested to approve applying to the IEEE
| Registration Authority for an EtherType for YYY. (The IESG | Registration Authority for an EtherType for YYY. (The IESG
| should communicate its approval to IANA and to those concerned | should communicate its approval to IANA and to those concerned
| with this document. IANA will forward the IESG approval to the | with this document. IANA will forward the IESG Approval to the
| IANA IEEE 802 Numbers EtherType registry expert who will make | registry expert of the "EtherType" registry from the "IEEE 802
| the application to the IEEE Registration authority, keeping | Numbers" registry group who will make the application to the
| IANA informed.) | IEEE Registration Authority, keeping IANA informed.)
| |
| X.2. IANA Considerations | X.2. IANA Considerations
| |
| ... | ...
5.6. OUI Exhaustion 5.6. OUI Exhaustion
When the available space for either multicast or unicast EUI-48 When the available space for either multicast or unicast EUI-48
identifiers under OUI 00-00-5E has been 90% or more exhausted, IANA identifiers under OUI 00-00-5E has been 90% or more exhausted, IANA
should request an additional OUI from the IEEE Registration Authority should request an additional OUI from the IEEE Registration Authority
for further IANA assignment. The appointed Expert(s) should monitor for further IANA assignment. The appointed Expert(s) should monitor
for this condition and notify IANA. for this condition and notify IANA.
5.7. IANA OUI MAC Address Table 5.7. IANA OUI MAC Address Table
The following changes are made by this document to the Notes for the The following changes are made by this document to the Notes for the
"IANA Unicast 48-bit MAC Addresses", the "IANA Multicast 48-bit MAC "IANA Unicast 48-bit MAC Addresses", the "IANA Multicast 48-bit MAC
Addresses", and the "IANA 64-bit MAC Addresses" registries. In Addresses", and the "IANA 64-bit MAC Addresses" registries. In
addition, the references in those registries are updated as specified addition, the references in those registries are updated, as
in Section 5.2. specified in Section 5.2.
The Notes for the IANA Unicast 48-bit MAC Addresses registry and for The Notes for the "IANA Unicast 48-bit MAC Addresses" registry and
the IANA Multicast 48-bit MAC Addresses registry are changed to the for the "IANA Multicast 48-bit MAC Addresses" registry are changed to
following: the following:
"These values are prefixed with 00-00-5E. See Section 2.1.5 of | These values are prefixed with 00-00-5E. See Section 2.1.3 of RFC
[this document]." | 9542.
The Note for the IANA 64-bit MAC Addresses registry is changed to the The Note for the "IANA 64-bit MAC Addresses" registry is changed to
following: the following:
"These values are prefixed with 00-00-5E to form unicast MAC | These values are prefixed with 00-00-5E to form unicast MAC
addresses, with 01-00-5E to form multicast MAC addresses, with | addresses, with 01-00-5E to form multicast MAC addresses, with
02-00-5E to form unicast modified EUI-64 addresses, and with | 02-00-5E to form unicast modified EUI-64 addresses, and with
03-00-5E to form multicast modified EUI-64 addresses. See [this | 03-00-5E to form multicast modified EUI-64 addresses. See RFC
document], particularly Section 2.2.2, for more details." | 9542, particularly Section 2.2.2, for more details.
5.8. IANA LLDP TLV Subtypes 5.8. IANA LLDP TLV Subtypes
IANA is requested to move the "IANA Link Layer Discovery Protocol IANA has moved the "IANA Link Layer Discovery Protocol (LLDP) TLV
(LLDP) TLV Subtypes" Registry from the IANA IEEE 802 Numbers registry Subtypes" registry from the "IEEE 802 Numbers" registry group to the
group to the IANA OUI Ethernet Numbers registry group, since code "IANA OUI Ethernet Numbers" registry group, since code points within
points within it are assigned by IANA, and to add [this document] as it are assigned by IANA, and has added RFC 9542 as an additional
an additional reference for that registry. reference for that registry.
In addition, IANA is requested to update three entries in that In addition, IANA has updated three entries in that registry as
Registry as follows: follows:
+=======+==================================+=================+ +=======+==================================+===========+
| Value | Description | Reference | | Value | Description | Reference |
+=======+==================================+=================+ +=======+==================================+===========+
| 0 | Reserved | [this document] | | 0 | Reserved | RFC 9542 |
+-------+----------------------------------+-----------------+ +-------+----------------------------------+-----------+
| 42 | Example for use in documentation | [this document] | | 42 | Example for use in documentation | RFC 9542 |
+-------+----------------------------------+-----------------+ +-------+----------------------------------+-----------+
| 255 | Reserved | [this document] | | 255 | Reserved | RFC 9542 |
+-------+----------------------------------+-----------------+ +-------+----------------------------------+-----------+
Table 5 Table 6
The entries for 1 (MUD), 2-41 (unassigned), and 43-254 (unassigned) The entries for 1 (MUD), 2-41 (unassigned), and 43-254 (unassigned)
are unchanged. are unchanged.
5.9. CBOR Tag Assignments 5.9. CBOR Tag Assignments
IANA is requested to assign two CBOR Tags as shown below in the IANA has assigned two CBOR Tags as shown below in the "Concise Binary
Concise Binary Object Representation (CBOR) Tags registry. [The Object Representation (CBOR) Tags" registry.
values of 48 and 49 are requested for TBD1 and TBD2 respectively.]
+======+=============+==================+=================+ +======+=============+==================+===========+
| Tag | Data Item | Semantics | Reference | | Tag | Data Item | Semantics | Reference |
+======+=============+==================+=================+ +======+=============+==================+===========+
| TBD1 | byte string | IEEE MAC Address | [this document] | | 48 | byte string | IEEE MAC Address | RFC 9542 |
+------+-------------+------------------+-----------------+ +------+-------------+------------------+-----------+
| TBD2 | byte string | IEEE OUI/CID | [this document] | | 1048 | byte string | IEEE OUI/CID | RFC 9542 |
+------+-------------+------------------+-----------------+ +------+-------------+------------------+-----------+
Table 6 Table 7
6. Security Considerations 6. Security Considerations
This document is concerned with assignment of IEEE 802 parameters This document is concerned with assignment of IEEE 802 parameters
allocated to IANA, particularly those under the IANA OUI, and closely allocated to IANA, particularly those under the IANA OUI, and closely
related matters. It is not directly concerned with security except related matters. It is not directly concerned with security except
as follows: as follows:
Confusion and conflict can be caused by the use of MAC addresses Confusion and conflict can be caused by the use of MAC addresses
or other OUI-derived protocol parameters as examples in or other OUI-derived protocol parameters as examples in
documentation. Examples that are "only" to be used in documentation. Examples that are "only" to be used in
documentation can end up being coded and released or cause documentation can end up being coded and released or cause
conflicts due to later real use and the possible acquisition of conflicts due to later real use and the possible acquisition of
intellectual property rights in such addresses or parameters. The intellectual property rights in such addresses or parameters. The
reservation herein of MAC addresses and parameters for reservation herein of MAC addresses and parameters for
documentation purposes will minimize such confusion and conflict. documentation purposes will minimize such confusion and conflict.
MAC addresses are an identifier provided by a device to the network. MAC addresses are identifiers provided by a device to the network.
On certain devices, MAC addresses are not static, and can be On certain devices, MAC addresses are not static and can be
configured. The network should exercise caution when using these configured. The network should exercise caution when using these
addresses to enforce policy because addresses can be spoofed and addresses to enforce policy because addresses can be spoofed and
previously seen devices can return to the network with a new address. previously seen devices can return to the network with a new address.
MAC addresses identify a physical or virtual interface and can be MAC addresses identify a physical or virtual interface and can be
used for tracking the device with that interface. Thus, they can be used for tracking the device with that interface. Thus, they can be
used to track users asociated with that device. See [madinas] for used to track users associated with that device. See [madinas] for
related privacy considerations and a discussion of MAC address related privacy considerations and a discussion of MAC address
randomization to partially mitigate this threat. Also, see [RFC7043] randomization to partially mitigate this threat. Also, see [RFC7043]
for the security and privacy considerations of publishing MAC for the security and privacy considerations of publishing MAC
addresses in DNS. addresses in DNS.
7. Normative References 7. References
[IEEE802_OandA]
IEEE 802, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture", IEEE Std 802-2014,
12 June 2014.
IEEE 802, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture - Amendment 2: Local
Medium Access Control (MAC) Address Usage", IEEE Std 802c-
2017, April 2017.
[IEEE802.1AB] 7.1. Normative References
IEEE 802, "IEEE Standard for Local and metropolitan area
networks - Statin and Media Access Control Connectivity
Discovery", IEEE Std 802.1AB-2016, 29 January 2016.
[IEEE.802.1Q_2014] [IEEE.802.1Q_2014]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks--Bridges and Bridged Networks", IEEE 802.1Q-2014, networks--Bridges and Bridged Networks", IEEE 802.1Q-2014,
DOI 10.1109/ieeestd.2014.6991462, 18 December 2014, DOI 10.1109/ieeestd.2014.6991462, 18 December 2014,
<http://ieeexplore.ieee.org/servlet/ <http://ieeexplore.ieee.org/servlet/
opac?punumber=6991460>. opac?punumber=6991460>.
[IEEE802.1AB]
IEEE, "IEEE Standard for Local and metropolitan area
networks - Station and Media Access Control Connectivity
Discovery", IEEE Std 802.1AB-2016,
DOI 10.1109/IEEESTD.2016.7433915, March 2016,
<https://doi.org/10.1109/IEEESTD.2016.7433915>.
[IEEE802_OandA]
IEEE, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture", IEEE Std 802-2014,
DOI 10.1109/IEEESTD.2014.6847097, June 2014,
<https://doi.org/10.1109/IEEESTD.2014.6847097>.
IEEE, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture -- Amendment 2: Local
Medium Access Control (MAC) Address Usage", IEEE Std 802c-
2017, DOI 10.1109/IEEESTD.2017.8016709, August 2017,
<https://doi.org/10.1109/IEEESTD.2017.8016709>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
8. Informative References 7.2. Informative References
[BGP11dp] Lindem, A., Patel, K., Zandi, S., Haas, J., and X. Xu, [BGP11dp] Lindem, A., Patel, K., Zandi, S., Haas, J., and X. Xu,
"BGP Logical Link Discovery Protocol (LLDP) Peer "BGP Logical Link Discovery Protocol (LLDP) Peer
Discovery", work in Progress, 6 December 2022, Discovery", Work in Progress, Internet-Draft, draft-acee-
<https://datatracker.ietf.org/doc/draft-acee-idr-lldp- idr-lldp-peer-discovery-17, 4 January 2024,
peer-discovery/>. <https://datatracker.ietf.org/doc/html/draft-acee-idr-
lldp-peer-discovery-17>.
[EthernetNum] [EthernetNum]
IANA, "Ethernet Numbers", IANA, "IANA OUI Ethernet Numbers",
<https://www.iana.org/assignments/ethernet-numbers>. <https://www.iana.org/assignments/ethernet-numbers>.
[IANA] IANA, "Internet Assigned Numbers Authority", [IANA] IANA, "Internet Assigned Numbers Authority",
<https://www.iana.org>. <https://www.iana.org>.
[IEEE] IEEE, "Institute for Electrical and Electronics [IEEE] IEEE, "Institute of Electrical and Electronics Engineers",
Engineers", <https://www.ieee.org>. <https://www.ieee.org>.
[IEEE1394] IEEE, "IEEE Standard for a High-Performance Serial Bus",
IEEE Std 1394-2008, 21 October 2008.
[IEEE802] IEEE 802, "IEEE 802 LAN/MAN Standards Committee",
<https://www.ieee802.org>.
[IEEE802.15.4]
IEEE 802, "IEEE Standard for Low-Rate Wireless Networks",
IEEE Std 802.14.4, 2020.
[IEEE802.1AC]
IEEE 802, "IEEE Standard for Local and Metropolitan Area
Networks - Media Access Control (MAC) Service Definition",
IEEE Std 802.1AC-2016, 7 December 2016.
[IEEE802.1CQ]
IEEE 802, "IEEE Standard for Local and Metropolitan Area
Networks - Multicast and Local Address Assignment",
draft 0.8, IEEE Std 802.1CQ/D0.8, 31 July 2022.
[IEEE.802.11_2012] [IEEE.802.11_2012]
IEEE, "IEEE Standard for Information technology-- IEEE, "IEEE Standard for Information technology--
Telecommunications and information exchange between Telecommunications and information exchange between
systems Local and metropolitan area networks--Specific systems Local and metropolitan area networks--Specific
requirements Part 11: Wireless LAN Medium Access Control requirements Part 11: Wireless LAN Medium Access Control
(MAC) and Physical Layer (PHY) Specifications", (MAC) and Physical Layer (PHY) Specifications",
IEEE 802.11-2012, DOI 10.1109/ieeestd.2012.6178212, 5 IEEE 802.11-2012, DOI 10.1109/ieeestd.2012.6178212, 5
April 2012, <http://ieeexplore.ieee.org/servlet/ April 2012, <http://ieeexplore.ieee.org/servlet/
opac?punumber=6178209>. opac?punumber=6178209>.
[IEEE.802.3_2012] [IEEE.802.3_2012]
IEEE, "802.3-2012", IEEE 802.3-2012, IEEE, "IEEE Standard for Ethernet", IEEE 802.3-2012,
DOI 10.1109/ieeestd.2012.6419735, 24 January 2013, DOI 10.1109/ieeestd.2012.6419735, 24 January 2013,
<http://ieeexplore.ieee.org/servlet/ <http://ieeexplore.ieee.org/servlet/
opac?punumber=6419733>. opac?punumber=6419733>.
[IEEE_RA] IEEE RA, "IEEE Standards Association Registration [IEEE1394] IEEE, "IEEE Standard for a High-Performance Serial Bus",
Authority", IEEE Std 1394-2008, DOI 10.1109/IEEESTD.2008.4659233,
<https://standards.ieee.org/products-programs/regauth/>. October 2008,
<https://doi.org/10.1109/IEEESTD.2008.4659233>.
[IEEE_SA] IEEE SA, "IEEE Standards Association", [IEEE802] IEEE 802, "IEEE 802 LMSC", <https://www.ieee802.org>.
<https://standards.ieee.org>.
[IEEE802.15.4]
IEEE, "IEEE Standard for Low-Rate Wireless Networks", IEEE
Std 802.15.4-2020, DOI 10.1109/IEEESTD.2020.9144691, July
2020, <https://doi.org/10.1109/IEEESTD.2020.9144691>.
[IEEE802.1AC]
IEEE 802, "IEEE Standard for Local and metropolitan area
networks -- Media Access Control (MAC) Service
Definition", IEEE Std 802.1AC-2016,
DOI 10.1109/IEEESTD.2017.7875381, March 2017,
<https://doi.org/10.1109/IEEESTD.2017.7875381>.
[IEEE802.1CQ]
IEEE, "Draft Standard for Local and Metropolitan Area
Networks: Multicast and Local Address Assignment", draft
0.8, IEEE Std 802.1CQ/D0.8, July 2022.
[IEEEtutorials] [IEEEtutorials]
IEEE, "Guidelines for Use of Extended Unique Identifier IEEE, "Guidelines for Use of Extended Unique Identifier
(EUI), Organizationally Unique Identifier (OUI), and (EUI), Organizationally Unique Identifier (OUI), and
Company ID (CID)", 3 August 2017, Company ID (CID)", August 2017,
<https://standards.ieee.org/wp- <https://standards.ieee.org/wp-
content/uploads/import/documents/tutorials/eui.pdf>. content/uploads/import/documents/tutorials/eui.pdf>.
[IEEE_RA] IEEE, "Registration Authority",
<https://standards.ieee.org/products-programs/regauth/>.
[IEEE_SA] IEEE, "IEEE Standards Association",
<https://standards.ieee.org>.
[InfiniBand] [InfiniBand]
InfiniBand Trade Association, "InfiniBand Architecture InfiniBand Trade Association, "InfiniBand Architecture
Specification Volume 1", November 2007, Specification Volume 1", November 2007,
<https://www.infinibandta.org/>. <https://www.infinibandta.org/>.
[madinas] Zuniga, JC., Bernardos, CJ., and A. Andersdotter, [madinas] Zúñiga, JC., Bernardos, CJ., Ed., and A. Andersdotter,
"Randomized and Changing MAC Address", work in Progress, "Randomized and Changing MAC Address state of affairs",
13 September 2023, <https://datatracker.ietf.org/doc/ Work in Progress, Internet-Draft, draft-ietf-madinas-mac-
draft-ietf-madinas-mac-address-randomization/>. address-randomization-12, 28 February 2024,
<https://datatracker.ietf.org/doc/html/draft-ietf-madinas-
mac-address-randomization-12>.
[PPPNum] IANA, "PPP Numbers", [PPPNum] IANA, "Point-to-Point (PPP) Protocol Field Assignments",
<https://www.iana.org/assignments/ppp-numbers>. <https://www.iana.org/assignments/ppp-numbers>.
[RAC_OUI] Parsons, G., "OUI Registry Restructuring", work [RAC_OUI] Parsons, G., "OUI Registry Restructuring", Work in
in Progress, September 2013, Progress, Internet-Draft, draft-ieee-rac-oui-
<https://www.ietf.org/archive/id/draft-ieee-rac-oui- restructuring-01, 9 September 2013,
restructuring-01.txt>. <https://datatracker.ietf.org/doc/html/draft-ieee-rac-oui-
restructuring-01>.
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
RFC 1112, DOI 10.17487/RFC1112, August 1989, RFC 1112, DOI 10.17487/RFC1112, August 1989,
<https://www.rfc-editor.org/info/rfc1112>. <https://www.rfc-editor.org/info/rfc1112>.
[RFC1661] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", [RFC1661] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)",
STD 51, RFC 1661, DOI 10.17487/RFC1661, July 1994, STD 51, RFC 1661, DOI 10.17487/RFC1661, July 1994,
<https://www.rfc-editor.org/info/rfc1661>. <https://www.rfc-editor.org/info/rfc1661>.
[RFC2153] Simpson, W., "PPP Vendor Extensions", RFC 2153, [RFC2153] Simpson, W., "PPP Vendor Extensions", RFC 2153,
skipping to change at page 34, line 5 skipping to change at line 1574
This appendix provides the specific templates for IANA assignments of This appendix provides the specific templates for IANA assignments of
parameters. Explanatory words in parentheses in the templates below parameters. Explanatory words in parentheses in the templates below
may be deleted in a completed template as submitted to IANA. may be deleted in a completed template as submitted to IANA.
A.1. EUI-48/EUI-64 Identifier or Identifier Block Template A.1. EUI-48/EUI-64 Identifier or Identifier Block Template
Applicant Name: Applicant Name:
Applicant Email: Applicant Email:
Applicant Telephone: (starting with country code) Applicant Telephone: (starting with the country code)
Use Name: (brief name of Parameter use such as "Foo Protocol" Use Name: (brief name of Parameter use, such as "Foo Protocol"
[RFC3092]) [RFC3092])
Document: (ID or RFC specifying use to which the identifier or block Document: (I-D or RFC specifying use to which the identifier or block
of identifiers will be put.) of identifiers will be put)
Specify whether this is an application for EUI-48 or EUI-64 Specify whether this is an application for EUI-48 or EUI-64
identifiers: identifiers:
Size of Block requested: (must be a power-of-two-sized block, can be Size of Block requested: (must be a power-of-two-sized block, can be
a block of size one (2**0)) a block of size one (2**0))
Specify multicast, unicast, or both: Specify multicast, unicast, or both:
A.2. IANA OUI/CID-Based Protocol Number Template A.2. IANA OUI/CID-Based Protocol Number Template
Applicant Name: Applicant Name:
Applicant Email: Applicant Email:
Applicant Telephone: (starting with country code) Applicant Telephone: (starting with the country code)
Use Name: (brief name of use of code point such as "Foo Protocol") Use Name: (brief name of use of code point, such as "Foo Protocol")
Document: (ID or RFC specifying use to which the protocol identifier Document: (I-D or RFC specifying use to which the protocol identifier
will be put.) will be put)
Note: (any additional note) Note: (any additional note)
A.3. Other IANA OUI/CID-Based Parameter Template A.3. Other IANA OUI/CID-Based Parameter Template
Applicant Name: Applicant Name:
Applicant Email: Applicant Email:
Applicant Telephone: (starting with country code) Applicant Telephone: (starting with the country code)
Protocol where the OUI/CID-Based Parameter for which a value is being Protocol where the OUI/CID-Based Parameter for which a value is being
requested appears: (such as: Cipher Suite selection in IEEE 802.11) requested appears: (such as Cipher Suite selection in IEEE 802.11)
Use Name: (brief name of use of code point to be assigned, such as Use Name: (brief name of use of code point to be assigned, such as
"Foo Cipher Suite" [RFC3092]) "Foo Cipher Suite" [RFC3092])
Document: (ID or RFC specifying use to which the other IANA OUI-based Document: (I-D or RFC specifying use to which the other IANA OUI-
parameter value will be put.) based parameter value will be put)
Note: (any additional note) Note: (any additional note)
Appendix B. EtherTypes Appendix B. EtherTypes
This appendix provides a copy of the IESG Statement issued in May This appendix provides a copy of the IESG Statement issued in May
2023 on obtaining new IETF EtherTypes in Section B.1. Note that 2023 on obtaining new IETF EtherTypes in Appendix B.1. Note that
there is an informational IANA registry of some important EtherTypes there is an informational IANA registry of some important EtherTypes
specified for IETF protocols or by IEEE 802 available, currently at specified for IETF protocols or by IEEE 802 available, currently at
[IANA]. The IEEE Registration Authority page of EtherTypes, [IANA]. The IEEE Registration Authority page on EtherTypes
https://standards.ieee.org/regauth/ethertype/eth.txt, may also be <https://standards.ieee.org/regauth/ethertype/eth.txt> may also be
useful. See Section 3 above. useful. See Section 3 above.
B.1. IESG Statement on Ethertypes B.1. IESG Statement on EtherTypes
From: IESG Date: 1 May 2023 From: IESG
Date: 1 May 2023
The IEEE Registration Authority (IEEE RA) assigns EtherTypes with The IEEE Registration Authority (IEEE RA) assigns EtherTypes with
oversight from the IEEE Registration Authority Committee (IEEE RAC) oversight from the IEEE Registration Authority Committee (IEEE RAC).
(See https://standards.ieee.org/products-programs/regauth/ (See https://standards.ieee.org/products-programs/regauth/
ethertype/.) Some IETF protocol specifications make use of ethertype/.) Some IETF protocol specifications make use of
EtherTypes. All EtherType applications are subject to IEEE RA EtherTypes. All EtherType applications are subject to IEEE RA
technical review for consistency with policy. technical review for consistency with policy.
Since EtherTypes are a fairly scarce resource, the IEEE RAC has let Since EtherTypes are a fairly scarce resource, the IEEE RAC has let
us know that they will not assign a new EtherType to a new IETF us know that they will not assign a new EtherType to a new IETF
protocol specification until the IESG has approved the protocol protocol specification until the IESG has approved the protocol
specification for publication as an RFC. In exceptional cases, the specification for publication as an RFC. In exceptional cases, the
IEEE RA is willing to consider "early allocation" of an EtherType for IEEE RA is willing to consider "early allocation" of an EtherType for
an IETF protocol that is still under development as long as the an IETF protocol that is still under development as long as the
request comes from and has been vetted by the IESG. request comes from and has been vetted by the IESG.
To let the IEEE RAC know that the IESG has approved the request for To let the IEEE RAC know that the IESG has approved the request for
an Ethernet assignment for an IETF protocol, all future requests for an Ethernet assignment for an IETF protocol, all future requests for
assignment of EtherTypes for IETF protocols will be made by the IESG. assignment of EtherTypes for IETF protocols will be made by the IESG.
Note that Local Experimental ("playpen") EtherTypes have been Note that Local Experimental ("playpen") EtherTypes have been
assigned in IEEE 802 [1] for use during protocol development and assigned in IEEE 802 [1] use during protocol development and
experimentation. experimentation.
[1] IEEE Std 802. IEEE standard for Local and Metropolitan Area [1] IEEE Std 802. IEEE standard for Local and Metropolitan Area
Networks: Overview and Architecture. Networks: Overview and Architecture.
Appendix C. Changes from RFC 7042 Appendix C. Changes from RFC 7042
This document obsoletes [RFC7042] and makes the changes listed below. This document obsoletes [RFC7042] and makes the changes listed below.
However, the completed application template based upon which an IANA However, the completed application template based upon which an IANA
OUI-based protocol number value was assigned for document use remains OUI-based protocol number value was assigned for document use remains
that in Appendix C of RFC 7042. that in Appendix C of [RFC7042].
* Add information on MA-M (28-bit) and MA-S (36-bit) EUI prefixes * Add information on MA-M (28-bit) and MA-S (36-bit) EUI prefixes
that the IEEE Registration Authority assigns. that the IEEE Registration Authority assigns.
* Add information on the restructuring of the "local" MAC address * Add information on the restructuring of the "local" MAC address
space into four quadrants under the Structured Local Address Plan space into four quadrants under the Structured Local Address Plan
(SLAP [IEEE802_OandA]). (SLAP) [IEEE802_OandA].
* Include the IESG Statement on EtherTypes (See Appendix B.1) and * Include the IESG Statement on EtherTypes (see Appendix B.1) and
more detailed IETF procedures for applying to the IEEE more detailed IETF procedures for applying to the IEEE
Registration Authority for an EtherType for use in an IETF Registration Authority for an EtherType for use in an IETF
protocol (see Section 5.5). protocol (see Section 5.5).
* Mention that IEEE 802 CFM Codepoints that have been allocated to * Mention that IEEE 802 CFM code points have been allocated to the
the IETF (see Section 1.4). IETF (see Section 1.4).
* Mention the organizationally specific LLDP data element that has * Mention the Organizationally Specific LLDP data element that has
been assigned under the IANA OUI and the registry set up for been assigned under the IANA OUI and the registry set up for
future such assignments (see Section 4.1). future such assignments (see Section 4.1).
* Clarify minor details in Section 5.1 on Expert Review and IESG * Clarify minor details in Section 5.1 on Expert Review and IESG
Ratification. Ratification.
* Specify CBOR tags for MAC addresses and OUI/CIDs (see * Specify CBOR tags for MAC addresses and OUIs/CIDs (see
Section 2.4). Section 2.4).
* Add a version field requirement for the allocation of protocol * Add a version field requirement for the allocation of protocol
numbers under the IANA OUI (see Section 3.1). numbers under the IANA OUI (see Section 3.1).
* Mention that EtherTypes are used in the GENEVE [RFC8926] * Mention that EtherTypes are used in the Geneve [RFC8926]
encapsulation header (see Section 3). encapsulation header (see Section 3).
* Add "a combination of Expert Review and IESG Approal" as part of * Add "a combination of Expert Review and IESG Approval" as part of
the specification for "IESG Ratification". the specification for "IESG Ratification".
Acknowledgements Acknowledgements
The comments and suggestions of the following people persons and The comments and suggestions of the following persons and
organizations are gratefully acknowledged: organizations are gratefully acknowledged:
Comments and suggestions leading to this Document: Comments and suggestions leading to this document:
Carsten Bormann, Bob Hinden, The IEEE 802.1 Working Group, Éric Carsten Bormann, Bob Hinden, the IEEE 802.1 Working Group, Éric
Vyncke, Dale Worley, and Amanda Baber Vyncke, Dale Worley, and Amanda Baber
Comments and suggestions leading to RFC 7042 (which is obsoleted Comments and suggestions leading to [RFC7042] (which is obsoleted
by this document): by this document):
David Black, Adrian Farrel, Bob Grow, Joel Jaeggli, Pearl David Black, Adrian Farrel, Bob Grow, Joel Jaeggli, Pearl
Liang, Glenn Parsons, Pete Resnick, and Dan Romascanu. Liang, Glenn Parsons, Pete Resnick, and Dan Romascanu
Authors' Addresses Authors' Addresses
Donald E. Eastlake 3rd Donald E. Eastlake 3rd
Futurewei Technologies Independent
2386 Panoramic Circle 2386 Panoramic Circle
Apopka, Florida 32703 Apopka, Florida 32703
United States of America United States of America
Phone: +1-508-333-2270 Phone: +1-508-333-2270
Email: d3e3e3@gmail.com, donald.eastlake@futurewei.com Email: d3e3e3@gmail.com, donald.eastlake@futurewei.com
Joe Abley Joe Abley
Cloudflare Cloudflare
Amsterdam Amsterdam
Netherlands The Netherlands
Phone: +31 45 56 36 34 Phone: +31 45 56 36 34
Email: jabley@strandkip.nl Email: jabley@strandkip.nl
Yizhou Li Yizhou Li
Huawei Technologies Huawei Technologies
101 Software Avenue 101 Software Avenue
Nanjing Nanjing
Jiangsu, 210012 Jiangsu, 210012
China China
Phone: +86-13809002299 Phone: +86-13809002299
 End of changes. 213 change blocks. 
558 lines changed or deleted 578 lines changed or added

This html diff was produced by rfcdiff 1.48.