IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters Independent
2386 Panoramic Circle Apopka Florida 32703 United States of America +1-508-333-2270 d3e3e3@gmail.com donald.eastlake@futurewei.com
Cloudflare
Amsterdam The Netherlands +31 45 56 36 34 jabley@strandkip.nl
Huawei Technologies
101 Software Avenue Nanjing Jiangsu 210012 China +86-13809002299 liyizhou@huawei.com
int intarea Ethernet EtherType 802 OUI EUI LSAP AFN CBOR LLC SLAP SNAP CID Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses several aspects of such parameters and their use in IETF protocols, specifies IANA considerations for assignment of points under the IANA Organizationally Unique Identifier (OUI), and provides some values for use in documentation. This document obsoletes RFC 7042.
Status of This Memo This memo documents an Internet Best Current Practice. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .
Copyright Notice Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.
Table of Contents
  • .  Introduction
    • .  Notations Used in This Document
    • .  The IEEE Registration Authority
    • .  The IANA Organizationally Unique Identifier
    • .  CFM Code Points
  • .  Ethernet Identifier Parameters
    • .  48-Bit MAC Identifiers, OUIs, and Other Prefixes
      • .  Special First Octet Bits
      • .  OUIs and CIDs
      • .  48-Bit MAC Assignments under the IANA OUI
      • .  48-Bit MAC Documentation Values
      • .  48-Bit IANA MAC Assignment Considerations
    • .  64-Bit MAC Identifiers
      • .  IPv6 Use of Modified EUI‑64 Identifiers
      • .  EUI‑64 IANA Assignment Considerations
      • .  EUI‑64 Documentation Values
    • .  Other 48-Bit MAC Identifiers Used by the IETF
      • .  Identifiers with a '33-33' Prefix
      • .  The CF Series
    • .  CBOR Tags
  • .  Ethernet Protocol Parameters
    • .  Ethernet Protocol Assignment under the IANA OUI
    • .  Documentation Protocol Number
  • .  Other OUI/CID-Based Parameters
    • .  LLDP IETF Organizationally Specific TLV Type
  • .  IANA Considerations
    • .  Expert Review and IESG Ratification
      • .  Expert Review Guidance
      • .  Expert Review and IESG Ratification Procedure
    • .  IANA Registry Group (Web Page) Name Changes
    • .  MAC Address AFNs and RRTYPEs
    • .  Informational IANA Registry Group Material
    • .  EtherType Assignment Process
    • .  OUI Exhaustion
    • .  IANA OUI MAC Address Table
    • .  IANA LLDP TLV Subtypes
    • .  CBOR Tag Assignments
  • .  Security Considerations
  • .  References
    • .  Normative References
    • .  Informative References
  • .  Templates
    • .  EUI‑48/EUI‑64 Identifier or Identifier Block Template
    • .  IANA OUI/CID-Based Protocol Number Template
    • .  Other IANA OUI/CID-Based Parameter Template
  • .  EtherTypes
    • .  IESG Statement on EtherTypes
  • .  Changes from RFC 7042
  • Acknowledgements
  • Authors' Addresses
Introduction Some IETF protocols use Ethernet or other communication frame formats and parameters related to IEEE 802 . These include Media Access Control (MAC) addresses and protocol identifiers. The IEEE Registration Authority manages the assignment of identifiers used in IEEE 802 networks, in some cases assigning blocks 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 tutorials concerning these parameters . IANA has been assigned an Organizationally Unique Identifier (OUI) by the IEEE RA and an associated set of MAC addresses and other organizationally unique code points based on that OUI. This document specifies IANA considerations for the assignment of code points under that IANA OUI, including MAC addresses and protocol identifiers, and provides some values for use in documentation. As noted in and , the use of designated code values reserved for documentation and examples reduces the likelihood of conflicts and confusion arising from such code points conflicting with code points assigned for some deployed use. This document also discusses several other uses by the IETF of IEEE 802 code points, including IEEE 802 Connectivity Fault Management (CFM) code points and IEEE 802 Link Local Discovery Protocol (LLDP) Vendor-Specific TLV Sub-Types . It also specifies Concise Binary Object Representation (CBOR) tags for MAC addresses and OUIs / Company Identifiers (CIDs). Descriptions herein of policies and procedures are authoritative, but descriptions of IEEE registration policies, procedures, and standards are only informative; for authoritative IEEE information, consult the IEEE sources. is incorporated herein except where there are contrary provisions in this document. In this document, "IESG Ratification", specified in , refers to a combination of Expert Review and IESG Approval as those are defined in , where IESG Approval is required only if the Expert does not reject the request. It is NOT the same as just "IESG Approval" in .
Notations Used in This Document This document uses hexadecimal notation. Each octet (that is, 8-bit byte) is represented by two hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen. This document consistently uses IETF ("network") bit ordering although the physical order of bit transmission within an octet on an IEEE link is from the lowest order bit to the highest order bit (i.e., the reverse of the IETF's ordering). In this document:
"AFN"
Address Family Number .
"CBOR"
Concise Binary Object Representation .
"CFM"
Connectivity Fault Management .
"CID"
Company Identifier. See .
"DSAP"
Destination Service Access Point. See .
"EUI"
Extended Unique Identifier.
"EUI-48"
48-bit EUI
"IEEE"
Institute of Electrical and Electronics Engineers .
"IEEE 802"
The LAN/MAN Standards Committee .
"IEEE RA"
IEEE Registration Authority .
"IEEE SA"
IEEE Standards Association .
"LLC"
Logical Link Control. The type of frame header where the protocol is identified by source and destination LSAP fields. See .
"LSAP"
Link-Layer Service Access Point. See .
"MA-L"
MAC Address Block Large.
"MA-M"
MAC Address Block Medium.
"MA-S"
MAC Address Block Small.
"MAC"
Media Access Control, not Message Authentication Code.
"MAC-48"
A 48-bit MAC address. This term is obsolete. If globally unique, use EUI‑48.
"OUI"
Organizationally Unique Identifier. See .
"RRTYPE"
A DNS Resource Record type .
"SLAP"
IEEE 802 Structured Local Address Plan . See .
"SNAP"
Subnetwork Access Protocol. See .
"SSAP"
Source Service Access Point. See .
"tag"
"Tag" is used in two contexts in this document. For "Ethernet tag", see . For "CBOR tag", see .
"TLV"
Type-Length-Value.
"**"
The double asterisk symbol indicates exponentiation. For example, 2**24 is two to the twenty-fourth power.
The IEEE Registration Authority Originally the responsibility of the Xerox Corporation, the registration authority for Ethernet parameters since 1986 has been the IEEE Registration Authority, available on the Web at . The IEEE Registration Authority operates under the direction of the IEEE Standards Association (IEEE SA) Board of Governors, with oversight by the IEEE Registration Authority Committee (IEEE RAC). The IEEE RAC is a committee of the Board of Governors. Anyone may apply to that authority for parameter assignments. The IEEE Registration Authority may impose fees or other requirements but commonly waives fees for applications from standards development organizations. Lists of assignments and their holders are downloadable from the IEEE Registration Authority site.
The IANA Organizationally Unique Identifier The Organizationally Unique Identifier (OUI) 00‑00‑5E has been assigned to IANA by the IEEE Registration Authority. There is no OUI value reserved at this time for documentation, but there are documentation code points under the IANA OUI specified below.
CFM Code Points IEEE Std 802.1Q allocates two blocks of 802 Connectivity Fault Management (CFM) code points to the IETF, one for CFM OpCodes and one for CFM TLV Types. For further information, see . The IANA "Connectivity Fault Management (CFM) OAM IETF Parameters" registry has subregistries for these code points. This document does not further discuss these blocks of code points.
Ethernet Identifier Parameters This section includes information summarized from that is being provided for context. The definitive information, which prevails in case of any discrepancy, is in . discusses 48-bit MAC identifiers, their relationship to OUIs and other prefixes, and assignment under the IANA OUI. extends this to 64-bit identifiers. discusses other IETF MAC identifier uses not under the IANA OUI. specifies CBOR tags for MAC addresses and OUIs/CIDs.
48-Bit MAC Identifiers, OUIs, and Other Prefixes 48-bit MAC "addresses" are the most commonly used Ethernet interface identifiers. Those that are globally unique are also called EUI‑48 identifiers (Extended Unique Identifier 48). An EUI‑48 is structured into an initial prefix assigned by the IEEE Registration Authority and additional bits assigned by the prefix owner. As of 2024, there are three lengths of prefixes assigned, as shown in the table below; however, some prefix bits can have special meaning, as shown in .
Prefix Length in Bits Name Owner Supplied Bits for 48‑bit MAC Addresses
24 MA-L 24
28 MA-M 20
36 MA-S 12
The bottom (least significant) four bits of the first octet of the 6-octet 48-bit MAC have special meaning, as shown in , and are referred to below as the M, X, Y, and Z bits.
48-Bit MAC Address Structure 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | . . . . Z Y X M| . . . . . . . .| octets 0+1 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | . . . . . . . .| . . . . . . . .| octets 2+3 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | . . . . . . . .| . . . . . . . .| octets 4+5 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
For global addresses, X = 0 and a MAC address begins with 3 octets or a larger initial prefix indicating the assignee of the block of MAC addresses. This prefix is followed by a sequence of additional octets so as to add up to the total MAC address length. For example, 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 MA-S one and a half octets (12 bits) they can control in constructing 48-bit MAC addresses; other prefix lengths are also available . An AFN, a DNS RRTYPE, and a CBOR tag have been assigned for 48-bit MAC addresses, as discussed in Sections , , and . IEEE Std 802 describes assignment procedures and policies for identifiers related to IEEE 802 . IEEE RA documentation on EUIs, OUIs, and CIDs is available at .
Special First Octet Bits There are bits within the initial octet of an IEEE MAC address that have special significance , as described as follows:
M bit -
This bit is frequently referred to as the "group" or "multicast" bit. If it is zero, the MAC address is unicast. If it is a one, the address is groupcast (multicast or broadcast). 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 (formerly called the Local/Global bit). If it is zero, the MAC address is a global address under the control of the owner of the IEEE-assigned prefix. Previously, if it was a one, the MAC address was considered "local" and under the assignment and control of the local network operator (but see ). If it is a one and if the IEEE 802 Structured Local Address Plan (SLAP) is in effect, 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 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 formerly uniform "local" MAC address space into four quadrants as follows and further described below:
Y bit Z bit Quadrant
0 0 Administratively Assigned
0 1 Extended Local
1 0 Reserved
1 1 Standard Assigned
While a local network administrator can assign any addresses with the X bit a one, the optional SLAP characterizes the four quadrants of the "local" address space using the Y and Z bits as follows:
Administratively Assigned -
MAC addresses in this quadrant are called Administratively Assigned Identifiers. This is intended for arbitrary local assignment, such as random assignment; however, see .
Extended Local -
MAC addresses in this quadrant are called Extended Local Identifiers. These addresses are not actually "local" under SLAP. They are available to the organization that has been assigned the CID (see ) specifying the other 20 bits of the 24-bit prefix with X, Y, and Z bits having the values 1, 0, and 1, respectively.
Reserved -
MAC addresses in this quadrant are reserved for future use under the SLAP. Until such future use, they could be locally assigned as Administratively Assigned Identifiers are assigned, but there is a danger that future SLAP use would conflict with such local assignments.
Standard Assigned -
MAC addresses in this quadrant are called Standard Assigned Identifiers (SAIs). An SAI is assigned by a protocol specified in an IEEE 802 standard, for example, (but see the first NOTE below).
NOTE: While the SLAP has MAC addresses assigned through a local protocol in the SAI quadrant and assigned by a protocol specified in an IEEE 802 standard, the SLAP is optional. Local network administrators may use the IETF protocol provisions in and , which support assignment of a MAC address in the local MAC address space using DHCPv6 or other protocol methods. NOTE: There isn't any automated way to determine if or to what extent a local network is configured for and/or operating according to SLAP.
OUIs and CIDs 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 group MAC addresses by extending a modified version of the assigned OUI in which the M bit (see ) is set to 1 . 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 bit is a one, the identifier has historically been a local identifier under the control of the local network administrator; however, there are now recommendations on optional management of the local address space, as discussed in . If the Local bit is a one, the holder of an OUI has no special authority over MAC identifiers whose first 3 octets correspond to their OUI or the beginning of their longer prefix. A CID is a 24-bit Company Identifier. It is assigned for 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. A CID has X and Z bits equal to 1 and its Y bit equal to 0 (see ). An AFN and a CBOR tag have been assigned for OUIs/CIDs, as discussed in Sections , , and .
48-Bit MAC Assignments under the IANA OUI The OUI 00‑00‑5E has been assigned to IANA, as stated in 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 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 are as follows:
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 ).
00‑00‑5E‑00‑01‑00 through 00‑00‑5E‑00‑01‑FF:
assigned for the Virtual Router Redundancy Protocol (VRRP) .
00‑00‑5E‑00‑02‑00 through 00‑00‑5E‑00‑02‑FF:
assigned for the IPv6 Virtual Router Redundancy Protocol (IPv6 VRRP) .
00‑00‑5E‑00‑52‑00 through 00‑00‑5E‑00‑52‑FF:
used for very small assignments. As of 2024, 4 out of these 256 values have been assigned. See .
00‑00‑5E‑00‑53‑00 through 00‑00‑5E‑00‑53‑FF:
assigned for use in documentation by this document.
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 addresses. As of 2024, 1 out of these 256 values has been assigned. See .
Multicast:
01‑00‑5E‑00‑00‑00 through 01‑00‑5E‑7F‑FF‑FF:
2**23 addresses assigned for IPv4 multicast .
01‑00‑5E‑80‑00‑00 through 01‑00‑5E‑8F‑FF‑FF:
2**20 addresses assigned for MPLS multicast .
01‑00‑5E‑90‑00‑00 through 01‑00‑5E‑90‑00‑FF:
2**8 addresses being used for very small assignments. As of 2024, 4 out of these 256 values have been assigned. See .
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 addresses. As of 2024, 1 out of these 256 values has been assigned. See .
01‑00‑5E‑90‑10‑00 through 01‑00‑5E‑90‑10‑FF:
2**8 addresses assigned for use in documentation by this document.
For more detailed and up-to-date information, see the "IANA OUI Ethernet Numbers" registry at .
48-Bit MAC Documentation Values 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
  • 01‑00‑5E‑90‑10‑00 through 01‑00‑5E‑90‑10‑FF for multicast.
48-Bit IANA MAC Assignment Considerations 48-bit assignments under the current or a future IANA OUI (see ) must meet the following requirements:
  • must be for standards purposes (either for an IETF Standard or other standard related to IETF work),
  • must be for a power-of-two-sized block of identifiers starting at a boundary that is an equal or greater power of two, including the assignment of one (2**0) identifier,
  • must not be used to evade the requirement for network interface vendors to obtain their own block of identifiers from the IEEE, and
  • must be documented in an Internet-Draft or RFC.
In addition, approval must be obtained as follows (see the procedure in ):
  • 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 require Expert Review (see ).
  • Large assignments of 131072 (2**17) or more EUI‑48 identifiers require IESG Ratification (see ).
64-Bit MAC Identifiers IEEE also defines a system of 64-bit MAC identifiers, including EUI‑64s. EUI‑64 identifiers are used as follows:
  • In IEEE Std 1394 (also known as FireWire and i.Link)
  • In IEEE Std 802.15.4 (also known as Zigbee)
  • In
  • In a modified form to construct some IPv6 Interface Identifiers, as described in , although this use is now deprecated
Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) assignment, or a shorter extension to longer assigned prefixes so as to 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 special low-order bits. An AFN, a DNS RRTYPE, and CBOR tag have been assigned for 64-bit MAC addresses, as discussed in Sections , , and . The discussion below is almost entirely in terms of the "Modified" form of EUI‑64 identifiers; however, anyone assigned such an identifier can also use the unmodified form as a MAC identifier on any link that uses such 64-bit identifiers for interfaces.
IPv6 Use of Modified EUI‑64 Identifiers The approach described below for constructing IPv6 Interface Identifiers is now deprecated, and the method specified in is recommended. EUI‑64 identifiers have been used to form the lower 64 bits of some IPv6 addresses (Section and Appendix of and ). When so used, the EUI‑64 is modified by inverting the X (universal/local) bit to form an IETF "Modified EUI‑64 identifier". Below is an illustration of a Modified EUI‑64 unicast identifier under the IANA OUI, where aa-bb-cc-dd-ee is the extension. 02-00-5E-aa-bb-cc-dd-ee 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‑48 identifiers. It is the globally unique values (universal 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 typically locally assigned and out of scope for global assignment. The X (universal/local) bit was inverted to make it easier for network operators to type in local-scope identifiers. Thus, such Modified EUI‑64 identifiers as 1, 2, etc. (ignoring leading zeros) 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. As with 48-bit MAC identifiers, the M bit (0x01) on in the first octet indicates a group identifier (multicast or broadcast). 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 value, as assigned by the OUI owner for an EUI‑48. For example: 02-00-5E-FF-FE-yy-yy-yy or 03-00-5E-FF-FE-yy-yy-yy 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 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 can be formed by inserting FF-FE in the middle of their EUI‑48 identifiers and inverting the universal/local bit. In addition, certain Modified EUI‑64 identifiers under the IANA OUI are reserved for holders of IPv4 addresses as follows: 02-00-5E-FE-xx-xx-xx-xx 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. Modified EUI‑64 identifiers from 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" addresses . However, for Modified EUI‑64 identifiers based on an IPv4 address, the universal/local bit should be set to correspond to whether the IPv4 address is local or global. (Keep in mind that the sense of the Modified EUI‑64 identifier universal/local bit is reversed from that in (unmodified) EUI‑64 identifiers.)
EUI‑64 IANA Assignment Considerations The following table shows which Modified EUI‑64 identifiers under the IANA OUI are reserved, assigned, or available as indicated. As noted above, the corresponding MAC addresses can be determined by complementing the 02 bit in the first octet. In all cases, the corresponding multicast 64-bit MAC addresses formed by complementing the 01 bit in the first octet have the same status as the modified 64-bit unicast address blocks listed below. These values are prefixed with 02-00-5E to form unicast modified EUI-64 addresses. IANA 64-bit MAC Addresses
Addresses Usage Reference
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 Holders RFC 9542
FF-FF-00-00-00 to FF-FF-FF-FF-FF Reserved RFC 9542
The reserved identifiers above require IESG Ratification (see ) for assignment. IANA EUI‑64 identifier assignments under the IANA OUI must meet the following requirements:
  • must be for standards purposes (either for an IETF Standard or other standard related to IETF work),
  • must be for a power-of-two-sized block of identifiers starting at a boundary that is an equal or greater power of two, including the assignment of one (2**0) identifier,
  • must not be used to evade the requirement for network interface vendors to obtain their own block of identifiers from the IEEE, and
  • must be documented in an Internet-Draft or RFC.
In addition, approval must be obtained as follows (see the procedure in ):
  • Small to medium assignments of a block of 1, 2, 4, ..., 134217728, 268435456 (2**0, 2**1, 2**2, ..., 2**27, 2**28) EUI‑64 identifiers require Expert Review (see ).
  • Large assignments of 536870912 (2**29) or more EUI‑64 identifiers require IESG Ratification (see ).
EUI‑64 Documentation Values The following blocks of unmodified 64-bit MAC addresses are for documentation use. The IPv4-derived addresses are based on the IPv4 documentation addresses , and the MAC-derived addresses are based on the EUI‑48 documentation addresses above. 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‑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‑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‑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 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‑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‑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‑CB‑00‑71 IPv4 multicast derived from IPv4 unicast 01‑00‑5E‑FF‑FE‑90‑10‑00 to 01‑00‑5E‑FF‑FE‑90‑10‑FF EUI‑48 derived
Other 48-Bit MAC Identifiers Used by the IETF There are two other blocks of 48-bit MAC identifiers that are used by the IETF as described below.
Identifiers with a '33-33' Prefix All 48-bit multicast MAC identifiers prefixed with "33-33" (that is, the 2**32 multicast MAC identifiers in the range from 33-33-00-00-00-00 to 33-33-FF-FF-FF-FF) are used as specified in for IPv6 multicast. In all of these identifiers, the Group bit (the bottom bit of the first octet) is on, as is required to work properly with existing hardware as a multicast identifier. They also have the Local bit on, but any Ethernet using standard IPv6 multicast should note that these addresses will be used for that purpose. These multicast MAC addresses fall into the Administratively Assigned SLAP quadrant (see ).
The CF Series The Informational declared the 3-octet values from CF‑00‑00 through CF‑FF‑FF to be "OUIs" available for assignment by IANA to software vendors for use in PPP or for other uses where 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) and M (Group) special bits at the bottom of the first octet equal to one, while all IEEE-assigned OUIs thus far have the X and M bits as zero and all CIDs have the Y and M bits as zero; thus, there can be no conflict between CF series "OUIs" and IEEE-assigned OUIs/CIDs. Multicast MAC addresses constructed with a CF series OUI would fall into the Standard Assigned SLAP quadrant (see ). The Group bit is meaningless in PPP. To quote : "The 'CF0000' series was arbitrarily chosen to match the PPP NLPID 'CF', as a matter of mnemonic convenience." (For further information on Network Layer Protocol Identifiers (NLPIDs), see .) CF‑00‑00 is reserved. CF‑00‑00‑00‑00‑00 is a multicast identifier listed by IANA as used for Ethernet loopback tests. In over a decade of availability, only a handful of values in the CF series have been assigned. (See the "IANA OUI Ethernet Numbers" and "Point-to-Point (PPP) Protocol Field Assignments" registry groups.)
Changes to RFC 2153 The IANA Considerations in were updated as follows by the approval of and remain so updated (no technical changes have been made):
  • Use of these CF series identifiers based on IANA assignment was deprecated.
  • IANA was instructed not to assign any further values in the CF series.
CBOR Tags The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of very small code size, fairly small message size, and extensibility. In CBOR, a data item can be enclosed by a CBOR tag to give it some additional semantics identified by that tag. CBOR-tagged data items (fields) are not used in actual IEEE 802 address fields but may be used in CBOR-encoded parts of protocol messages. IANA has assigned 48 as the CBOR tag to indicate a MAC address. The 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 address is encoded. Should some other multiple of 8 bits be used in the future for the length of MAC addresses, such as a 128-bit (16-octet) MAC address, the 48 tag will be used. IANA has assigned 1048 as the CBOR tag to indicate an OUI, CID, or CF series organizational identifier. The enclosed data item is an octet string of length 3 to hold the 24-bit OUI or CID (see ).
Ethernet Protocol Parameters Ethernet protocol parameters provide a means of indicating, near the beginning of a frame, the contents of that frame -- for example, that it contains IPv4 or IPv6. There are two types of protocol identifier parameters (see ) that can occur in Ethernet frames:
EtherTypes:
These are 16-bit identifiers that, when considered as an unsigned integer, are equal to or larger than 0x0600. shows the simplest case where the EtherType of the protocol data in the frame appears immediately after the destination and source MAC addresses. specifies two EtherTypes for local, experimental use: 0x88B5 and 0x88B6.
LSAPs:
These are 8-bit protocol identifiers that occur in pairs after a field that gives the frame length. Such a length must, when considered as an unsigned integer, be less than 0x5DD, or it could be mistaken as an EtherType. However, the LLC encapsulation EtherType 0x8870 may also be used in place of such a length as a "length indication" of nonspecific length. LSAPs occur in pairs, where one is intended to indicate the source protocol handler (SSAP) and the other the destination protocol handler (DSAP); however, use cases where the two are different have been relatively rare. See for the simplest case where the length field appears immediately after the destination and source MAC addresses. In that figure, the CTL (control) field value of 3 indicates datagram service. This type of protocol identification is sometimes called "LLC" (Logical Link Control).
EtherType Frame Protocol Labeling 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | Destination MAC Address /// +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | Source MAC Address /// +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | EtherType, greater than or equal to 0x0600 | +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | Protocol Data /// +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
LSAP Frame Protocol Labeling 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | Destination MAC Address /// +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | Source MAC Address /// +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | Frame length (or 0x8870) | +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | DSAP | SSAP | +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ | CTL = 0x03 | Protocol Data /// +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
The concept of EtherType labeling has been extended to labeling by Ethernet "tags". An Ethernet tag in this sense is a prefix whose type is identified by an EtherType that is then followed by either another tag, an EtherType, or an LLC Link-Layer Service Access Point (LSAP) protocol indicator for the "main" body of the frame. Customarily, in the world of , tags are a fixed length and do not include any encoding of their own length. An example is the C-Tag (formerly the Q-Tag) . It provides customer VLAN and priority information for a frame. Any device that is processing a frame cannot, in general, safely process anything in the frame past an EtherType it does not understand. Neither EtherTypes nor LSAPs are assigned by IANA; they are assigned by the IEEE Registration Authority (see and ). However, both LSAPs and EtherTypes have extension mechanisms so that they can be used with five-octet Ethernet protocol identifiers under an OUI, including those assigned by IANA under the IANA OUI. When using the IEEE 802 Logical Link Control (LLC) format (Subnetwork Access Protocol (SNAP)) for a frame, an OUI-based protocol identifier can be expressed as follows: xx‑xx‑AA‑AA‑03‑yy‑yy‑yy‑zz‑zz where xx‑xx is the frame length and, as above, must be small enough not to be confused with an EtherType; "AA" is the LSAP that indicates this use and is sometimes referred to as the SNAP Service Access Point (SNAP SAP); "03" is the LLC control octet indicating datagram service; yy‑yy‑yy is an OUI; and zz‑zz is a protocol number, under that OUI, assigned by the OUI owner. The five-octet length for such OUI-based protocol identifiers results, with the LLC control octet ("0x03"), in the preservation of 16-bit alignment. When using an EtherType to indicate the main type for a frame body, the special "OUI Extended EtherType" 0x88B7 is available. Using this EtherType, a frame body can begin with 88‑B7‑yy‑yy‑yy‑zz‑zz where yy‑yy‑yy and zz‑zz have the same meaning as in the SNAP format described above; however, this format with EtherType 0x88B7 does not preserve 16-bit alignment. It is also possible, within the SNAP format, to use an arbitrary EtherType. Putting the EtherType as the zz‑zz field after an all-zeros OUI (00‑00‑00) does this. It looks like xx‑xx‑AA‑AA‑03‑00‑00‑00‑zz‑zz where zz‑zz is the EtherType. As well as labeling frame contents, IEEE 802 protocol types appear within Non-Broadcast Multi-Access (NBMA) Next Hop Resolution Protocol messages. Such messages have provisions for both two-octet EtherTypes and OUI-based protocol types. 16-bit EtherTypes also occur in the Generic Routing Encapsulation (GRE) header and in the Generic Network Virtualization Encapsulation (Geneve) encapsulation header.
Ethernet Protocol Assignment under the IANA OUI Two-octet protocol numbers under the IANA OUI are available, as in 88‑B7‑00‑00‑5E‑qq‑qq or xx‑xx‑AA‑AA‑03‑00‑00‑5E‑qq‑qq where qq‑qq is the protocol number. A number of such assignments have been made out of the 2**16 protocol numbers available from 00‑00‑5E‑00‑00 to 00‑00‑5E‑FF‑FF (see ). The extreme values of this range, 00‑00‑5E‑00‑00 and 00‑00‑5E‑FF‑FF, are reserved and require IESG Ratification for assignment (see ). New assignments of protocol numbers (qq‑qq) under the IANA OUI must meet the following requirements:
  • the assignment must be for standards use (either for an IETF Standard or other standard related to IETF work),
  • the protocol must include a version field at a fixed offset or an equivalent marking such that later versions can be indicated in a way recognizable by earlier versions,
  • the protocol must be documented in an Internet-Draft or RFC, and
  • such protocol numbers are not to be assigned for any protocol that has an EtherType. (That EtherType can be used directly, or -- in the LSAPs case -- it can be used with the SNAP SAP by putting an all-zero "OUI" before the EtherType as described above.)
In addition, the Expert Review (or IESG Ratification for the two reserved values) must be obtained using the procedure specified in .
Documentation Protocol Number 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.
Other OUI/CID-Based Parameters Some IEEE 802 and other protocols provide for parameters based on an OUI or CID beyond those discussed above. Such parameters commonly consist of an OUI or CID plus one octet of additional value. They are called Organizationally Specific parameters (sometimes informally and less accurately referred to as "vendor specific"). They would look like yy‑yy‑yy‑zz where yy‑yy‑yy is the OUI/CID and zz is the additional specifier. An example is the Cipher Suite Selector in . Values may be assigned under the IANA OUI for other OUI-based parameter usage by Expert Review, except that, for each use, the 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 specifier) are reserved and require IESG Ratification (see ) for assignment; also, the additional specifier value 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 octet) is assigned for use as an example in documentation. Assignments of other IANA OUI-based parameters must be for standards use (either for an IETF Standard or other standard related to IETF work) and be documented in an Internet-Draft or RFC. The first time a value is assigned for a particular parameter of this type, an IANA registry will be created to contain that assignment and any subsequent assignments of values for that parameter under the IANA OUI. The Expert may specify the name of the registry. If different policies from those above are required for such a parameter, a BCP or Standards Track RFC should be adopted to update this BCP and specify the new policy and parameter.
LLDP IETF Organizationally Specific TLV Type An example of an "other IANA OUI-based parameter" is specified in . This provides for an Organizationally Specific TLV type for announcing a Manufacturer Usage Description (MUD) Uniform Resource Locator (URL) in the IEEE Link Local Discovery Protocol (LLDP) . Additional IETF use of code points in this space have been proposed . (See also .)
IANA Considerations This document concerns IANA considerations for the assignment of Ethernet parameters in connection with the IANA OUI and related matters. Note: The "IANA OUI Ethernet Numbers" registry group (web page) is for registries of numbers assigned under the IANA OUI, while the "IEEE 802 Numbers" registry group has informational lists of numbers assigned by the IEEE Registration Authority. This document does not create any new IANA registries. The MAC address values assigned for documentation and the protocol number for documentation were both assigned by . No existing assignment is changed by this document.
Expert Review and IESG Ratification This section specifies the procedures for Expert Review and IESG Ratification of MAC, protocol, and other IANA OUI-based identifiers. 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.
Expert Review Guidance The procedure described for Expert Review assignments in this document is consistent with the IANA Expert Review policy described in . While finite, the universe of MAC code points from which Expert-judged assignments will be made is considered to be large enough that the requirements given in this document and the Experts' good judgment are sufficient guidance. The idea is for the Expert to provide a light reasonableness check for small assignments of MAC identifiers, with increased scrutiny by the Expert for medium-sized assignments of MAC identifiers and assignments of protocol identifiers and other IANA OUI-based parameters.
Expert Review and IESG Ratification Procedure It can make sense to assign very large portions of the MAC identifier code point space. (Note that existing assignments include 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 in cases of the assignment of "reserved" values, IESG Ratification of an Expert Review approval recommendation is required as described below. This can be viewed as a combination of Expert Review and IESG Approval as defined in . IESG Approval is required only when the Expert does not reject the request. The procedure is as follows: The applicant always completes the appropriate template from below and sends it to IANA <iana@iana.org>. IANA always sends the template to an appointed Expert. If the Expert recuses themselves or is non-responsive, IANA may choose an alternative appointed Expert or, if none is available, will contact the IESG. In all cases, if IANA receives a disapproval from an Expert selected to review an application template, the application will be denied. The Expert should provide a reason for refusal, which IANA will communicate back to the applicant. If the assignment is based on Expert Review: If IANA receives approval and code points are available, IANA will make the requested assignment. If the assignment is based on IESG Ratification: The procedure starts with the first steps above for Expert Review. If the Expert disapproves the application, they simply inform IANA, who in turn informs the applicant that their request is denied; however, if the Expert believes the application should be approved or is uncertain and believes that the circumstances warrant the attention of the IESG, the Expert will inform IANA about their advice, and IANA will forward the application, together with the reasons provided by the Expert for approval or uncertainty, to the IESG. The IESG must decide whether the assignment will be granted. This can be accomplished by a management item in an IESG telechat, as is done for other types of requests. If the IESG decides not to ratify a favorable opinion by the Expert or decides against an application where the Expert is uncertain, the application is denied; otherwise, it is granted. The IESG will communicate its decision to the Expert and to IANA. In case of refusal, the IESG should provide a reason, which IANA will communicate to the applicant.
IANA Registry Group (Web Page) Name Changes For clarity and parallelism with the IANA "IEEE 802 Numbers" registry group, the IANA "Ethernet Numbers" registry group has been renamed the "IANA OUI Ethernet Numbers" registry. As this document replaces , references to in IANA registries in both the "IEEE 802 Numbers" and the "IANA OUI Ethernet Numbers" registry groups have been replaced by references to this document. Other IANA registry references to are not changed.
MAC Address AFNs and RRTYPEs IANA has assigned Address Family Numbers (AFNs) for MAC addresses as follows:
AFN Decimal Hex Reference
48-bit MAC 16389 0x4005
64-bit MAC 16390 0x4006
OUI 16391 0x4007
Lower 24 bits of a 48-bit MAC address:
MAC/24 16392 0x4008
Lower 40 bits of a 64-bit MAC address:
MAC/40 16393 0x4009
IANA has assigned DNS RRTYPEs for MAC addresses as follows:
RRTYPE Code
Data Mnemonic Decimal Hex Reference
48-bit MAC EUI48 108 0x006C
64-bit MAC EUI64 109 0x006D
Informational IANA Registry Group Material IANA maintains an informational registry group, currently implemented as a web page, concerning EtherTypes, OUIs, and multicast addresses assigned under OUIs other than the IANA OUI. The title of this informational registry group is "IEEE 802 Numbers". IANA updates that informational registry group when changes are provided by or approved by the Expert(s).
EtherType Assignment Process Applying to the IEEE Registration Authority for an EtherType needed by an IETF protocol requires IESG Approval, as stated in . To minimize confusion, this process will normally be done by the primary expert for the informational "EtherType" registry within the "IEEE 802 Numbers" registry group, as described below (see also ). After IESG Approval of the requirement for an EtherType, the IESG should refer the matter to IANA. In any case, IANA will ask the "EtherType" registry expert to execute the IEEE Registration Authority EtherType request process. This path is specified because the IESG usually deals with IANA for assignment actions and because IANA should be aware of which "EtherType" registry expert(s) are available, normally referring the making of the EtherType assignment request to the primary expert. Here is sample text for an Internet-Draft where both IANA and IEEE assignments are required, where "YYY" would be replaced by an explanation of for what/why the EtherType is needed in whatever level of detail is necessary and would normally include a reference or references to other appropriate parts of the Internet-Draft:
X. Assignment Considerations X.1. IEEE Assignment Considerations The IESG is requested to approve applying to the IEEE Registration Authority for an EtherType for YYY. (The IESG should communicate its approval to IANA and to those concerned with this document. IANA will forward the IESG Approval to the registry expert of the "EtherType" registry from the "IEEE 802 Numbers" registry group who will make the application to the IEEE Registration Authority, keeping IANA informed.) X.2. IANA Considerations ...
OUI Exhaustion When the available space for either multicast or unicast EUI‑48 identifiers under OUI 00‑00‑5E has been 90% or more exhausted, IANA should request an additional OUI from the IEEE Registration Authority for further IANA assignment. The appointed Expert(s) should monitor for this condition and notify IANA.
IANA OUI MAC Address Table 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 Addresses", and the "IANA 64-bit MAC Addresses" registries. In addition, the references in those registries are updated, as specified in . The Notes for the "IANA Unicast 48-bit MAC Addresses" registry and for the "IANA Multicast 48-bit MAC Addresses" registry are changed to the following:
These values are prefixed with 00-00-5E. See of RFC 9542.
The Note for the "IANA 64-bit MAC Addresses" registry is changed to the following:
These values are prefixed with 00-00-5E to form unicast MAC addresses, with 01-00-5E to form multicast MAC addresses, with 02-00-5E to form unicast modified EUI-64 addresses, and with 03-00-5E to form multicast modified EUI-64 addresses. See RFC 9542, particularly , for more details.
IANA LLDP TLV Subtypes IANA has moved the "IANA Link Layer Discovery Protocol (LLDP) TLV Subtypes" registry from the "IEEE 802 Numbers" registry group to the "IANA OUI Ethernet Numbers" registry group, since code points within it are assigned by IANA, and has added RFC 9542 as an additional reference for that registry. In addition, IANA has updated three entries in that registry as follows:
Value Description Reference
0 Reserved RFC 9542
42 Example for use in documentation RFC 9542
255 Reserved RFC 9542
The entries for 1 (MUD), 2-41 (unassigned), and 43-254 (unassigned) are unchanged.
CBOR Tag Assignments IANA has assigned two CBOR Tags as shown below in the "Concise Binary Object Representation (CBOR) Tags" registry.
Tag Data Item Semantics Reference
48 byte string IEEE MAC Address RFC 9542
1048 byte string IEEE OUI/CID RFC 9542
Security Considerations This document is concerned with assignment of IEEE 802 parameters allocated to IANA, particularly those under the IANA OUI, and closely related matters. It is not directly concerned with security except as follows: Confusion and conflict can be caused by the use of MAC addresses or other OUI-derived protocol parameters as examples in documentation. Examples that are "only" to be used in documentation can end up being coded and released or cause conflicts due to later real use and the possible acquisition of intellectual property rights in such addresses or parameters. The reservation herein of MAC addresses and parameters for documentation purposes will minimize such confusion and conflict. MAC addresses are identifiers provided by a device to the network. On certain devices, MAC addresses are not static and can be configured. The network should exercise caution when using these addresses to enforce policy because addresses can be spoofed and previously seen devices can return to the network with a new address. MAC addresses identify a physical or virtual interface and can be used for tracking the device with that interface. Thus, they can be used to track users associated with that device. See for related privacy considerations and a discussion of MAC address randomization to partially mitigate this threat. Also, see for the security and privacy considerations of publishing MAC addresses in DNS.
References Normative References IEEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks IEEE This standard specifies how the Media Access Control (MAC) Service is supported by Bridged Networks, the principles of operation of those networks, and the operation of MAC Bridges and VLAN Bridges, including management, protocols, and algorithms IEEE Standard for Local and metropolitan area networks - Station and Media Access Control Connectivity Discovery IEEE IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture IEEE IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture -- Amendment 2: Local Medium Access Control (MAC) Address Usage IEEE Guidelines for Writing an IANA Considerations Section in RFCs Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226. Informative References BGP Logical Link Discovery Protocol (LLDP) Peer Discovery LabN Consulting, L.L.C. Arrcus, Inc LinkedIn Juniper Networks, Inc China Mobile Link Layer Discovery Protocol (LLDP) or IEEE Std 802.1AB is implemented in networking equipment from many vendors. It is natural for IETF protocols to avail this protocol for simple discovery tasks. This document describes how BGP would use LLDP to discover directly connected and 2-hop peers when peering is based on loopback addresses. Work in Progress IANA OUI Ethernet Numbers IANA Internet Assigned Numbers Authority IANA Institute of Electrical and Electronics Engineers IEEE IEEE Standard for Information technology--Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications IEEE This revision specifies technical corrections and clarifications to IEEE Std 802.11 for wireless local area networks (WLANS) as well as enhancements to the existing medium access control (MAC) and physical layer (PHY) functions. It also incorporates Amendments 1 to 10 published in 2008 to 2011. IEEE Standard for Ethernet IEEE IEEE Standard for a High-Performance Serial Bus IEEE IEEE 802 LMSC IEEE 802 IEEE Standard for Low-Rate Wireless Networks IEEE IEEE Standard for Local and metropolitan area networks -- Media Access Control (MAC) Service Definition IEEE 802 Draft Standard for Local and Metropolitan Area Networks: Multicast and Local Address Assignment IEEE draft 0.8 Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID) IEEE Registration Authority IEEE IEEE Standards Association IEEE InfiniBand Architecture Specification Volume 1 InfiniBand Trade Association Randomized and Changing MAC Address state of affairs CISCO Universidad Carlos III de Madrid Safespring AB Work in Progress Point-to-Point (PPP) Protocol Field Assignments IANA OUI Registry Restructuring Ericsson The IEEE Registration Authority Committee, which has oversight for the OUI based registries, is seeking IETF community input as it finalizes restructuring the OUI registries. This document provides background on the RAC as well as explaining the proposed restructuring and the rationale. Work in Progress Host extensions for IP multicasting This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Recommended procedure for IP multicasting in the Internet. This RFC obsoletes RFCs 998 and 1054. [STANDARDS-TRACK] The Point-to-Point Protocol (PPP) This document defines the PPP organization and methodology, and the PPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK] PPP Vendor Extensions The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection; and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document provides information for the Internet community. It does not specify an Internet standard of any kind. NBMA Next Hop Resolution Protocol (NHRP) This document describes the NBMA Next Hop Resolution Protocol (NHRP). NHRP can be used by a source station (host or router) connected to a Non-Broadcast, Multi-Access (NBMA) subnetwork to determine the internetworking layer address and NBMA subnetwork addresses of the "NBMA next hop" towards a destination station. [STANDARDS-TRACK] Transmission of IPv6 Packets over Ethernet Networks This document specifies the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on Ethernet networks. It also specifies the content of the Source/Target Link-layer Address option used in Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and Redirect messages when those messages are transmitted on an Ethernet. [STANDARDS-TRACK] Reserved Top Level DNS Names To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Generic Routing Encapsulation (GRE) This document specifies a protocol for encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol. [STANDARDS-TRACK] Etymology of "Foo" Approximately 212 RFCs so far, starting with RFC 269, contain the terms `foo', `bar', or `foobar' as metasyntactic variables without any proper explanation or definition. This document rectifies that deficiency. This memo provides information for the Internet community. IP Version 6 Addressing Architecture This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture". [STANDARDS-TRACK] Multiprotocol Extensions for BGP-4 This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, L3VPN, etc.). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK] Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects dual-stack (IPv6/IPv4) nodes over IPv4 networks. ISATAP views the IPv4 network as a link layer for IPv6 and supports an automatic tunneling abstraction similar to the Non-Broadcast Multiple Access (NBMA) model. This memo provides information for the Internet community. MPLS Multicast Encapsulations RFC 3032 established two data link layer codepoints for MPLS, used to distinguish whether the data link layer frame is carrying an MPLS unicast or an MPLS multicast packet. However, this usage was never deployed. This specification updates RFC 3032 by redefining the meaning of these two codepoints. Both codepoints can now be used to carry multicast packets. The second codepoint (formerly the "multicast codepoint") is now to be used only on multiaccess media, and it is to mean "the top label of the following label stack is an upstream-assigned label". RFC 3032 does not specify the destination address to be placed in the "MAC DA" (Medium Access Layer Destination Address) field of an ethernet frame that carries an MPLS multicast packet. This document provides that specification. This document updates RFC 3032 and RFC 4023. [STANDARDS-TRACK] IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses some use of such parameters in IETF protocols and specifies IANA considerations for allocation of code points under the IANA OUI (Organizationally Unique Identifier). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. IPv4 Address Blocks Reserved for Documentation Three IPv4 unicast address blocks are reserved for use in examples in specifications and other documents. This document describes the use of these blocks. This document is not an Internet Standards Track specification; it is published for informational purposes. Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 This memo defines the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It is version three (3) of the protocol, and it is based on VRRP (version 2) for IPv4 that is defined in RFC 3768 and in "Virtual Router Redundancy Protocol for IPv6". VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IPv4 or IPv6 address(es) associated with a virtual router is called the Master, and it forwards packets sent to these IPv4 or IPv6 addresses. VRRP Master routers are configured with virtual IPv4 or IPv6 addresses, and VRRP Backup routers infer the address family of the virtual addresses being carried based on the transport protocol. Within a VRRP router, the virtual routers in each of the IPv4 and IPv6 address families are a domain unto themselves and do not overlap. The election process provides dynamic failover in the forwarding responsibility should the Master become unavailable. For IPv4, the advantage gained from using VRRP is a higher-availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. For IPv6, the advantage gained from using VRRP for IPv6 is a quicker switchover to Backup routers than can be obtained with standard IPv6 Neighbor Discovery mechanisms. [STANDARDS-TRACK] Unicast-Prefix-Based IPv4 Multicast Addresses This specification defines an extension to the multicast addressing architecture of the IP Version 4 protocol. The extension presented in this document allows for unicast-prefix-based assignment of multicast addresses. By delegating multicast addresses at the same time as unicast prefixes, network operators will be able to identify their multicast addresses without needing to run an inter-domain allocation protocol. [STANDARDS-TRACK] IANA Considerations for Network Layer Protocol Identifiers Some protocols being developed or extended by the IETF make use of the ISO/IEC (International Organization for Standardization / International Electrotechnical Commission) Network Layer Protocol Identifier (NLPID). This document provides NLPID IANA considerations. This memo documents an Internet Best Current Practice. Domain Name System (DNS) IANA Considerations This document specifies Internet Assigned Numbers Authority (IANA) parameter assignment considerations for the allocation of Domain Name System (DNS) resource record types, CLASSes, operation codes, error codes, DNS protocol message header bits, and AFSDB resource record subtypes. It obsoletes RFC 6195 and updates RFCs 1183, 2845, 2930, and 3597. IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses several uses of such parameters in IETF protocols, specifies IANA considerations for assignment of points under the IANA OUI (Organizationally Unique Identifier), and provides some values for use in documentation. This document obsoletes RFC 5342. Resource Records for EUI-48 and EUI-64 Addresses in the DNS 48-bit Extended Unique Identifier (EUI-48) and 64-bit Extended Unique Identifier (EUI-64) are address formats specified by the IEEE for use in various layer-2 networks, e.g., Ethernet. This document describes two new DNS resource record types, EUI48 and EUI64, for encoding Ethernet addresses in the DNS. This document describes potentially severe privacy implications resulting from indiscriminate publication of link-layer addresses in the DNS. EUI-48 or EUI-64 addresses SHOULD NOT be published in the public DNS. This document specifies an interoperable encoding of these address types for use in private DNS namespaces, where the privacy concerns can be constrained and mitigated. IANA Considerations for Connectivity Fault Management (CFM) Code Points IEEE 802.1 has specified Connectivity Fault Management (CFM) Operations, Administration, and Maintenance (OAM) facilities. CFM messages are structured with an OpCode field and have provision for the inclusion of TLV-structured information. IEEE 802.1 has allocated blocks of CFM OpCodes and TLV Types to the IETF. This document specifies the IANA considerations for the assignment of values from these blocks. Transparent Interconnection of Lots of Links (TRILL): Interface Addresses APPsub-TLV This document specifies a TRILL (Transparent Interconnection of Lots of Links) IS-IS application sub-TLV that enables the reporting by a TRILL switch of sets of addresses. Each set of addresses reports all of the addresses that designate the same interface (port) and also reports the TRILL switch by which that interface is reachable. For example, a 48-bit MAC (Media Access Control) address, IPv4 address, and IPv6 address can be reported as all corresponding to the same interface reachable by a particular TRILL switch. Such information could be used in some cases to synthesize responses to, or bypass the need for, the Address Resolution Protocol (ARP), the IPv6 Neighbor Discovery (ND) protocol, or the flooding of unknown MAC addresses. Recommendation on Stable IPv6 Interface Identifiers This document changes the recommended default Interface Identifier (IID) generation scheme for cases where Stateless Address Autoconfiguration (SLAAC) is used to generate a stable IPv6 address. It recommends using the mechanism specified in RFC 7217 in such cases, and recommends against embedding stable link-layer addresses in IPv6 IIDs. It formally updates RFC 2464, RFC 2467, RFC 2470, RFC 2491, RFC 2492, RFC 2497, RFC 2590, RFC 3146, RFC 3572, RFC 4291, RFC 4338, RFC 4391, RFC 5072, and RFC 5121. This document does not change any existing recommendations concerning the use of temporary addresses as specified in RFC 4941. Dynamic Host Configuration Protocol for IPv6 (DHCPv6) This document describes the Dynamic Host Configuration Protocol for IPv6 (DHCPv6): an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly, or in combination with stateful assignment of one or more IPv6 addresses and/or IPv6 prefixes. DHCPv6 can operate either in place of or in addition to stateless address autoconfiguration (SLAAC). This document updates the text from RFC 3315 (the original DHCPv6 specification) and incorporates prefix delegation (RFC 3633), stateless DHCPv6 (RFC 3736), an option to specify an upper bound for how long a client should wait before refreshing information (RFC 4242), a mechanism for throttling DHCPv6 clients when DHCPv6 service is not available (RFC 7083), and relay agent handling of unknown messages (RFC 7283). In addition, this document clarifies the interactions between models of operation (RFC 7550). As such, this document obsoletes RFC 3315, RFC 3633, RFC 3736, RFC 4242, RFC 7083, RFC 7283, and RFC 7550. Manufacturer Usage Description Specification This memo specifies a component-based architecture for Manufacturer Usage Descriptions (MUDs). The goal of MUD is to provide a means for end devices to signal to the network what sort of access and network functionality they require to properly function. The initial focus is on access control. Later work can delve into other aspects. This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, a Link Layer Discovery Protocol (LLDP) TLV, a URL, an X.509 certificate extension, and a means to sign and verify the descriptions. Geneve: Generic Network Virtualization Encapsulation Network virtualization involves the cooperation of devices with a wide variety of capabilities such as software and hardware tunnel endpoints, transit fabrics, and centralized control clusters. As a result of their role in tying together different elements of the system, the requirements on tunnels are influenced by all of these components. Therefore, flexibility is the most important aspect of a tunneling protocol if it is to keep pace with the evolution of technology. This document describes Geneve, an encapsulation protocol designed to recognize and accommodate these changing capabilities and needs. Link-Layer Address Assignment Mechanism for DHCPv6 In certain environments, e.g., large-scale virtualization deployments, new devices are created in an automated manner. Such devices may have their link-layer addresses assigned in an automated fashion. With sufficient scale, the likelihood of a collision using random assignment without duplication detection is not acceptable. Therefore, an allocation mechanism is required. This document proposes an extension to DHCPv6 that allows a scalable approach to link-layer address assignments where preassigned link-layer address assignments (such as by a manufacturer) are not possible or are unnecessary. Structured Local Address Plan (SLAP) Quadrant Selection Option for DHCPv6 The IEEE originally structured the 48-bit Media Access Control (MAC) address space in such a way that half of it was reserved for local use. In 2017, the IEEE published a new standard (IEEE Std 802c) with a new optional Structured Local Address Plan (SLAP). It specifies different assignment approaches in four specified regions of the local MAC address space. The IEEE is developing protocols to assign addresses (IEEE P802.1CQ). There is also work in the IETF on specifying a new mechanism that extends DHCPv6 operation to handle the local MAC address assignments. This document proposes extensions to DHCPv6 protocols to enable a DHCPv6 client or a DHCPv6 relay to indicate a preferred SLAP quadrant to the server so that the server may allocate MAC addresses in the quadrant requested by the relay or client. A new DHCPv6 option (QUAD) is defined for this purpose. Concise Binary Object Representation (CBOR) The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack. This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.
Templates This appendix provides the specific templates for IANA assignments of parameters. Explanatory words in parentheses in the templates below may be deleted in a completed template as submitted to IANA.
EUI‑48/EUI‑64 Identifier or Identifier Block Template Applicant Name: Applicant Email: Applicant Telephone: (starting with the country code) Use Name: (brief name of Parameter use, such as "Foo Protocol" ) Document: (I-D or RFC specifying use to which the identifier or block of identifiers will be put) Specify whether this is an application for EUI‑48 or EUI‑64 identifiers: Size of Block requested: (must be a power-of-two-sized block, can be a block of size one (2**0)) Specify multicast, unicast, or both:
IANA OUI/CID-Based Protocol Number Template Applicant Name: Applicant Email: Applicant Telephone: (starting with the country code) Use Name: (brief name of use of code point, such as "Foo Protocol") Document: (I-D or RFC specifying use to which the protocol identifier will be put) Note: (any additional note)
Other IANA OUI/CID-Based Parameter Template Applicant Name: Applicant Email: Applicant Telephone: (starting with the country code) Protocol where the OUI/CID-Based Parameter for which a value is being 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 "Foo Cipher Suite" ) Document: (I-D or RFC specifying use to which the other IANA OUI-based parameter value will be put) Note: (any additional note)
EtherTypes This appendix provides a copy of the IESG Statement issued in May 2023 on obtaining new IETF EtherTypes in . Note that there is an informational IANA registry of some important EtherTypes specified for IETF protocols or by IEEE 802 available, currently at . The IEEE Registration Authority page on EtherTypes may also be useful. See above.
IESG Statement on EtherTypes
From:
IESG
Date:
1 May 2023
The IEEE Registration Authority (IEEE RA) assigns EtherTypes with oversight from the IEEE Registration Authority Committee (IEEE RAC). (See .) Some IETF protocol specifications make use of EtherTypes. All EtherType applications are subject to IEEE RA technical review for consistency with policy. 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 protocol specification until the IESG has approved the protocol specification for publication as an RFC. In exceptional cases, the IEEE RA is willing to consider "early allocation" of an EtherType for an IETF protocol that is still under development as long as the request comes from and has been vetted by the IESG. 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 assignment of EtherTypes for IETF protocols will be made by the IESG. Note that Local Experimental ("playpen") EtherTypes have been assigned in IEEE 802 [1] use during protocol development and experimentation. [1] IEEE Std 802. IEEE standard for Local and Metropolitan Area Networks: Overview and Architecture.
Changes from RFC 7042 This document obsoletes and makes the changes listed below. However, the completed application template based upon which an IANA OUI-based protocol number value was assigned for document use remains that in .
  • Add information on MA-M (28-bit) and MA-S (36-bit) EUI prefixes that the IEEE Registration Authority assigns.
  • Add information on the restructuring of the "local" MAC address space into four quadrants under the Structured Local Address Plan (SLAP) .
  • Include the IESG Statement on EtherTypes (see ) and more detailed IETF procedures for applying to the IEEE Registration Authority for an EtherType for use in an IETF protocol (see ).
  • Mention that IEEE 802 CFM code points have been allocated to the IETF (see ).
  • Mention the Organizationally Specific LLDP data element that has been assigned under the IANA OUI and the registry set up for future such assignments (see ).
  • Clarify minor details in on Expert Review and IESG Ratification.
  • Specify CBOR tags for MAC addresses and OUIs/CIDs (see ).
  • Add a version field requirement for the allocation of protocol numbers under the IANA OUI (see ).
  • Mention that EtherTypes are used in the Geneve encapsulation header (see ).
  • Add "a combination of Expert Review and IESG Approval" as part of the specification for "IESG Ratification".
Acknowledgements The comments and suggestions of the following persons and organizations are gratefully acknowledged: Comments and suggestions leading to this document: , , the IEEE 802.1 Working Group, , , and Comments and suggestions leading to (which is obsoleted by this document): , , , , , , , and
Authors' Addresses Independent
2386 Panoramic Circle Apopka Florida 32703 United States of America +1-508-333-2270 d3e3e3@gmail.com donald.eastlake@futurewei.com
Cloudflare
Amsterdam The Netherlands +31 45 56 36 34 jabley@strandkip.nl
Huawei Technologies
101 Software Avenue Nanjing Jiangsu 210012 China +86-13809002299 liyizhou@huawei.com