<?xml version="1.0"encoding="utf-8"?>encoding="UTF-8"?> <?xml-model href="rfc7991bis.rnc"?><!-- Required for schema validation and schema-aware editing --><!DOCTYPE rfc [ <!ENTITY filename "draft-ietf-intarea-rfc7042bis-11"> <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> --> <!-- This third-party XSLT can be enabled for direct transformations in XML processors, including most browsers --> <!-- If further character entities are required then they should be added to the DOCTYPE above. Use of an external entity file is not recommended. --> <?rfc strict="yes" ?> <!-- give errors regarding ID-nits and DTD validation --> <!-- control the table of contents (ToC) --> <?rfc toc="yes"?><rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category="bcp"docName="&filename;"consensus="true" docName="draft-ietf-intarea-rfc7042bis-11" number="9542" ipr="trust200902" updates="" obsoletes="7042"submissionType="IETF"xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3"><!-- * docName should be the name of your draft * category should be one of std, bcp, info, exp, historic * ipr should be one of trust200902, noModificationTrust200902, noDerivativesTrust200902, pre5378Trust200902 * updates can be an RFC number as NNNN * obsoletes can be an RFC number as NNNN --> <!-- ____________________FRONT_MATTER____________________ --><front> <title abbrev="IANA/IETF and IEEE 802 Parameters">IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters</title><!-- The abbreviated title is required if the full title is longer than 39 characters --><seriesInfoname="Internet-Draft" value="&filename;"/>name="RFC" value="9542"/> <seriesInfo name="BCP" value="141"/> <author fullname="Donald E. Eastlake 3rd" initials="D."surname="Eastlake"> <organization>Futurewei Technologies</organization>surname="Eastlake 3rd"> <organization>Independent</organization> <address> <postal> <street>2386 Panoramic Circle</street> <city>Apopka</city> <region>Florida</region> <code>32703</code><country>US</country><country>United States of America</country> </postal> <phone>+1-508-333-2270</phone> <email>d3e3e3@gmail.com</email> <email>donald.eastlake@futurewei.com</email> </address> </author> <author fullname="Joe Abley"initials="J.N."initials="J." surname="Abley"> <organization>Cloudflare</organization> <address> <postal><city>Amsterdam</city> <country>Netherlands</country><postalLine>Amsterdam</postalLine> <postalLine>The Netherlands</postalLine> </postal> <phone>+31 45 56 36 34</phone> <email>jabley@strandkip.nl</email> </address> </author> <author fullname="Yizhou Li" initials="Y." surname="Li"> <organization>Huawei Technologies</organization> <address> <postal> <street>101 Software Avenue</street> <city>Nanjing</city> <region>Jiangsu</region> <code>210012</code> <country>China</country> </postal> <phone>+86-13809002299</phone> <email>liyizhou@huawei.com</email> </address> </author> <dateyear="2023" month="11" day="6"/> <area>Internet</area> <workgroup>INTAREA Working Group</workgroup> <!-- "Internet Engineering Task Force" is fine for individual submissions. If this element is not present, the default is "Network Working Group", which is used by the RFC Editor as a nod to the history of the RFC Series. --> <keyword></keyword> <!-- Multiple keywords are allowed. Keywords are incorporated into HTML output files for use by search engines. -->year="2024" month="April"/> <area>int</area> <workgroup>intarea</workgroup> <keyword>Ethernet</keyword> <keyword>EtherType</keyword> <keyword>802</keyword> <keyword>OUI</keyword> <keyword>EUI</keyword> <keyword>LSAP</keyword> <keyword>AFN</keyword> <keyword>CBOR</keyword> <keyword>LLC</keyword> <keyword>SLAP</keyword> <keyword>SNAP</keyword> <keyword>CID</keyword> <abstract> <t>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 IANAOUI (OrganizationallyOrganizationally UniqueIdentifier),Identifier (OUI), and provides some values for use in documentation. This document obsoletes RFC 7042.</t> </abstract> </front><!-- ____________________MIDDLE_MATTER____________________ --><middle> <section> <!-- 1. --> <name>Introduction</name> <t>Some IETF protocols use Ethernet or otherIEEE 802-relatedcommunication frame formats and parameters related to IEEE 802 <xref target="IEEE802"/>. These includeMAC (MediaMedia AccessControl)Control (MAC) addresses and protocol identifiers. The IEEE Registration Authority <xref target="IEEE_RA"/> 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 <xref target="IEEEtutorials"/>.</t> <t>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 <xref target="RFC2606"/> and <xref target="RFC5737"/>, 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 <xref target="RFC7319"/> and IEEE 802 Link Local Discovery Protocol(LLDP(LLDP) <xreftarget="IEEE802.1AB"/>) Vendor Specifictarget="IEEE802.1AB"/> Vendor-Specific TLV Sub-Types <xref target="RFC8520"/>. It also specifiesCBORConcise Binary Object Representation (CBOR) tags for MAC addresses andOUI/CIDs.</t>OUIs / Company Identifiers (CIDs).</t> <t>Descriptions herein of <xref target="IANA"/> policies and procedures areauthoritativeauthoritative, but descriptions of IEEE registration policies, procedures, and standards are only informative; for authoritative IEEE information, consult the IEEE sources.</t> <t><xref target="RFC8126"/> is incorporated herein except where there are contrary provisions in this document. In this document, "IESG Ratification", specified inSection 5.1,<xref target="ex-rev-iesg-rat"/>, refers to a combination of Expert Review and IESG Approval as those are defined in <xreftarget="RFC8126"/>target="RFC8126"/>, where IESG Approval is required only if the Expert does not reject the request. It is NOT the same as just "IESG Approval" in <xref target="RFC8126"/>.</t> <section> <!-- 1.1 --> <name>Notations Used in This Document</name> <t>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 <xref target="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).</t> <t>In this document:</t><dl><dl newline="false" indent="12"> <dt>"AFN"</dt><dd>Address Family Number <xref target="RFC4760"/>.</dd> <dt>"CBOR"</dt><dd>Concise Binary Object Representation <xref target="RFC8949"/>.</dd> <dt>"CFM"</dt><dd>Connectivity Fault Management <xref target="RFC7319"/>.</dd> <dt>"CID"</dt><dd>Company Identifier.(See Section 2.1.2.)</dd>See <xref target="oui-cid"/>.</dd> <dt>"DSAP"</dt><dd>Destination Service Access Point. SeeSection 3.</dd><xref target="eth-pro-param"/>.</dd> <dt>"EUI"</dt><dd>Extended Unique Identifier.</dd> <dt>"EUI-48"</dt><dd>48-bit EUI</dd> <dt>"IEEE"</dt><dd>Instituteforof Electrical and Electronics Engineers <xref target="IEEE"/>.</dd> <dt>"IEEE 802"</dt><dd>The LAN/MAN Standards Committee <xref target="IEEE802"/>.</dd> <dt>"IEEE RA"</dt><dd>IEEE Registration Authority <xref target="IEEE_RA"/>.</dd> <dt>"IEEE SA"</dt><dd>IEEE Standards Association <xref target="IEEE_SA"/>.</dd> <dt>"LLC"</dt><dd>Logical Link Control. The type of frame header where the protocol is identified by source and destination LSAP fields. SeeSection 3.</dd><xref target="eth-pro-param"/>.</dd> <dt>"LSAP"</dt><dd>Link-Layer Service Access Point. SeeSection 3.</dd><xref target="eth-pro-param"/>.</dd> <dt>"MA-L"</dt><dd>MAC Address Block Large.</dd> <dt>"MA-M"</dt><dd>MAC Address Block Medium.</dd> <dt>"MA-S"</dt><dd>MAC Address Block Small.</dd> <dt>"MAC"</dt><dd>Media Access Control, not Message Authentication Code.</dd> <dt>"MAC-48"</dt><dd>A 48-bit MAC address. This term is obsolete. If globally unique, use EUI&nbhy;48.</dd> <dt>"OUI"</dt><dd>Organizationally Unique Identifier.(See Section 2.1.2.)</dd>See <xref target="oui-cid"/>.</dd> <dt>"RRTYPE"</dt><dd>A DNS Resource Record type <xref target="RFC6895"/>.</dd> <dt>"SLAP"</dt><dd>IEEE 802 Structured Local Address Plan <xref target="IEEE802_OandA"/>. SeeSection 2.1.1.</dd><xref target="first-oct-bit"/>.</dd> <dt>"SNAP"</dt><dd>Subnetwork Access Protocol. SeeSection 3.</dd><xref target="eth-pro-param"/>.</dd> <dt>"SSAP"</dt><dd>Source Service Access Point. SeeSection 3.</dd><xref target="eth-pro-param"/>.</dd> <dt>"tag"</dt><dd>"Tag" is used in two contexts in this document. For "Ethernet tag", seeSection 3.<xref target="eth-pro-param"/>. For "CBOR tag", seeSection 2.4.</dd> <dt>"TLV"</dt><dd>Type, Length, Value.</dd><xref target="cbor-tags"/>.</dd> <dt>"TLV"</dt><dd>Type-Length-Value.</dd> <dt>"**"</dt><dd>The double asterisk symbol indicates exponentiation. For example, 2**24 is two to the twenty-fourth power.</dd> </dl> </section> <section anchor="IEEEregAuth"> <!-- 1.2 --> <name>The IEEE Registration Authority</name> <t>Originally the responsibility of the Xerox Corporation, the registration authority for Ethernet parameters since 1986 has been the IEEE Registration Authority, available on thewebWeb at <xref target="IEEE_RA"/>.</t> <t>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(RAC).(IEEE RAC). The IEEE RAC is a committee of the Board of Governors.</t> <t>Anyone may apply to thatAuthorityauthority 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.</t> </section> <section anchor="IANAOUI"> <!-- 1.3 --> <name>The IANA Organizationally Unique Identifier</name> <t>The Organizationally Unique Identifier (OUI) 00&nbhy;00&nbhy;5E has been assigned to IANA by the IEEE Registration Authority.</t> <t>There is no OUI value reserved at this time for documentation, but there are documentation code points under the IANA OUI specified below.</t> </section> <section anchor="CFM"> <!-- 1.4 --> <name>CFM Code Points</name> <t>IEEE Std 802.1Q <xref target="IEEE.802.1Q_2014"/> 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 furtherinformationinformation, see <xref target="RFC7319"/>. The IANA "Connectivity Fault Management (CFM) OAM IETF Parameters"Registryregistry has subregistries for these code points. This document does not further discuss these blocks of code points.</t> </section> </section> <!-- end 1. Introduction --> <section> <!-- 2. --> <name>Ethernet Identifier Parameters</name> <t>This section includes information summarized from <xref target="IEEE802_OandA"/> that is being provided for context. The definitive information, which prevails in case of any discrepancy, is in <xref target="IEEE802_OandA"/>.</t><t>Section 2.1<t><xref target="bit-48"/> discusses 48-bit MAC identifiers, their relationship to OUIs and other prefixes, and assignment under the IANA OUI.Section 2.2<xref target="bit-64"/> extends this to 64-bit identifiers.Section 2.3<xref target="bit-48-ietf"/> discusses other IETF MAC identifieruseuses not under the IANA OUI.Section 2.4<xref target="cbor-tags"/> specifies CBOR tags for MAC addresses andOUI/CIDs.</t> <t indent="3">HistoricalOUIs/CIDs.</t> <aside> <t>Historical Note: <xreftarget="RAC_OUI"/>target="I-D.ieee-rac-oui-restructuring"/> is an expireddraftInternet-Draft that provides additional historic information on <xref target="IEEE802"/> registries.</t><section></aside> <section anchor="bit-48"> <!-- 2.1 --> <name>48-Bit MAC Identifiers, OUIs, and Other Prefixes</name> <t>48-bit MAC "addresses" are the most commonly used Ethernet interface identifiers. Those that are globally unique are also called EUI&nbhy;48 identifiers (Extended Unique Identifier 48). An EUI&nbhy;48 is structured into an initial prefix assigned by the IEEE Registration Authority and additional bits assigned by the prefix owner. As of20232024, there are three lengths of prefixes assigned, as shown in the table below; however, some prefix bits can have specialmeaningmeaning, as shown in <xref target="MACaddr"/>.</t> <table align="center"> <thead> <tr><th>Prefix Length inbits</th><th>Name</th><th>OwnerBits</th><th>Name</th><th>Owner Supplied Bits for 48&nbhy;bit MAC Addresses</th></tr> </thead> <tbody> <tr><td align="center">24</td><td>MA-L</td><td align="center">24</td></tr> <tr><td align="center">28</td><td>MA-M</td><td align="center">20</td></tr> <tr><td align="center">36</td><td>MA-S</td><td align="center">12</td></tr> </tbody> </table> <t>The bottom (least significant) four bits of the first octet of the 6-octet 48-bit MAC have special meaning, as shown in <xref target="MACaddr"/>, and are referred to below as the M, X, Y, and Z bits.</t> <figure anchor="MACaddr"><name>48-bit<name>48-Bit MAC Address Structure</name> <artwork type="ascii-art" align="center"> <![CDATA[ 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 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ ]]> </artwork> </figure> <t>For global addresses,X=0X = 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 assignsMA-S (MACMAC Address BlockSmall),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 <xref target="IEEEtutorials"/>.</t> <t>An AFN, a DNS RRTYPE, and a CBOR tag have been assigned for 48-bit MACaddressesaddresses, as discussed in Sections2.4, 5.3<xref target="cbor-tags" format="counter"/>, <xref target="mac-addresses" format="counter"/>, and5.9.</t><xref target="cbor-tag-assign" format="counter"/>.</t> <t>IEEE Std 802 describes assignment procedures and policies forIEEE 802-relatedidentifiers related to IEEE 802 <xref target="IEEE802_OandA"/>. IEEE RA documentation on EUIs, OUIs, and CIDs is available at <xref target="IEEEtutorials"/>. </t><section><section anchor="first-oct-bit"> <!-- 2.1.1 --> <name>Special First Octet Bits</name> <t>There are bits within the initial octet of an IEEE MAC address that have special significance <xreftarget="IEEE802_OandA"/>target="IEEE802_OandA"/>, as described as follows:</t> <dl> <dt>Mbit</dt><dd>- Thisbit -</dt><dd>This bit is frequently referred to as thegroup"group" ormulticast"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.</dd> <dt>Xbit</dt><dd>- Thisbit -</dt><dd>This bit is also called the "universal/local"bit.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 theIEEE assignedIEEE-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 seeSection 2.3).<xref target="bit-48-ietf"/>). 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 Zbitsbits, as described below.</dd><dt>Y+Z bits</dt><dd>- These<dt>Y&Z bits -</dt><dd>These two bits have no special meaning if the X bit is zero. If the X bit is onethen,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 fourquadrants,quadrants as follows and further described below:</dd> </dl> <table align="center"> <thead> <tr><th>Y bit</th><th>Z bit</th><th>Quadrant</th></tr> </thead> <tbody> <tr><td align="center">0</td><td align="center">0</td><td>Administratively Assigned</td></tr> <tr><td align="center">0</td><td align="center">1</td><td>Extended Local</td></tr> <tr><td align="center">1</td><td align="center">0</td><td>Reserved</td></tr> <tr><td align="center">1</td><td align="center">1</td><td>Standard Assigned</td></tr> </tbody> </table> <t>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:</t> <dl> <dt>Administratively Assigned -</dt> <dd>MAC addresses in this quadrant are called Administratively Assigned Identifiers. This is intended for arbitrary local assignment, such as random assignment; however, seeSection 2.3.1.</dd><xref target="id-33-33"/>.</dd> <dt>Extended Local -</dt> <dd>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 (seeSection 2.1.2)<xref target="oui-cid"/>) specifying the other 20 bits of the 24-bit prefix with X, Y, and Z bits having the values 1, 0, and11, respectively.</dd> <dt>Reserved -</dt> <dd>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 areassignedassigned, but there is a danger that future SLAP use would conflict with such local assignments.</dd> <dt>Standard Assigned -</dt> <dd>MAC addresses in this quadrant are called Standard Assigned Identifiers (SAIs). An SAI is assigned by a protocol specified in an IEEE 802 standard, forexampleexample, <xref target="IEEE802.1CQ"/> (but see the first NOTE below).</dd> </dl> <t indent="6">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 <xref target="RFC8947"/> and <xreftarget="RFC8948"/>target="RFC8948"/>, which support assignment of a MAC address in the local MAC address space using DHCPv6 <xref target="RFC8415"/> or other protocol methods.</t><t indent="3">NOTE:<t>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.</t> </section> <!-- 2.1.1 --><section><section anchor="oui-cid"> <!-- 2.1.2 --> <name>OUIs and CIDs</name> <t>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 <xref target="MACaddr"/>) is set to 1 <xref target="IEEEtutorials"/>.</t> <t>The Local bit is zero for globally unique EUI&nbhy;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 addressspacespace, as discussed inSection 2.1.1.<xref target="first-oct-bit"/>. 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.</t> <t>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 anOUI,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 <xref target="MACaddr"/>).</t> <t>An AFN and a CBOR tag have been assigned forOUI/CIDsOUIs/CIDs, as discussed in Sections2.4, 5.3<xref target="cbor-tags" format="counter"/>, <xref target="mac-addresses" format="counter"/>, and5.9.</t><xref target="cbor-tag-assign" format="counter"/>.</t> </section><section><section anchor="bit-48-MAC"> <!-- 2.1.3 --> <name>48-Bit MAC Assignments under the IANA OUI</name> <t>The OUI 00&nbhy;00&nbhy;5E has been assigned toIANAIANA, as stated in <xref target="IANAOUI"/> above. This includes 2**24 48&nbhy;bit multicast identifiers from 01&nbhy;00&nbhy;5E&nbhy;00&nbhy;00&nbhy;00 to 01&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FF&nbhy;FF and 2**24 EUI&nbhy;48 unicast identifiers from 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;00&nbhy;00 to 00&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FF&nbhy;FF. </t> <t>Of these identifiers, the sub-blocks reserved or thus far assigned are as follows: </t><t>Unicast,<dl newline="true" spacing="normal"> <dt>Unicast, all blocks of 2**8 addresses thus far:</t></dt> <dd> <dl> <dt>00&nbhy;00&nbhy;5E&nbhy;00&nbhy;00&nbhy;00 through 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;00&nbhy;FF:</dt> <dd>reserved and require IESG Ratification for assignment (seeSection 5.1).</dd><xref target="ex-rev-iesg-rat"/>).</dd> <dt>00&nbhy;00&nbhy;5E&nbhy;00&nbhy;01&nbhy;00 through 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;01&nbhy;FF:</dt> <dd>assigned for the Virtual Router Redundancy Protocol (VRRP) <xref target="RFC5798"/>.</dd> <dt>00&nbhy;00&nbhy;5E&nbhy;00&nbhy;02&nbhy;00 through 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;02&nbhy;FF:</dt> <dd>assigned for the IPv6 Virtual Router Redundancy Protocol (IPv6 VRRP) <xref target="RFC5798"/>.</dd> <dt>00&nbhy;00&nbhy;5E&nbhy;00&nbhy;52&nbhy;00 through 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;52&nbhy;FF:</dt> <dd>used for very small assignments. As of2023,2024, 4 out of these 256 values have been assigned. See <xref target="EthernetNum"/>.</dd> <dt>00&nbhy;00&nbhy;5E&nbhy;00&nbhy;53&nbhy;00 through 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;53&nbhy;FF:</dt><dd>assigned for use in documentation by this document.</dd> <dt>00&nbhy;00&nbhy;5E&nbhy;90&nbhy;01&nbhy;00 through 00&nbhy;00&nbhy;5E&nbhy;90&nbhy;01&nbhy;FF:</dt> <dd>used for very small assignments that need parallel unicast and multicast MAC addresses. As of2023,2024, 1 out of these 256 values has been assigned. See <xref target="EthernetNum"/>.</dd> </dl><t>Multicast:</t></dd> <dt>Multicast:</dt> <dd> <dl> <dt>01&nbhy;00&nbhy;5E&nbhy;00&nbhy;00&nbhy;00 through 01&nbhy;00&nbhy;5E&nbhy;7F&nbhy;FF&nbhy;FF:</dt> <dd>2**23 addresses assigned for IPv4 multicast <xref target="RFC1112"/>.</dd> <dt>01&nbhy;00&nbhy;5E&nbhy;80&nbhy;00&nbhy;00 through 01&nbhy;00&nbhy;5E&nbhy;8F&nbhy;FF&nbhy;FF:</dt> <dd>2**20 addresses assigned for MPLS multicast <xref target="RFC5332"/>. </dd> <dt>01&nbhy;00&nbhy;5E&nbhy;90&nbhy;00&nbhy;00 through 01&nbhy;00&nbhy;5E&nbhy;90&nbhy;00&nbhy;FF:</dt> <dd>2**8 addresses being used for very small assignments. As of2023,2024, 4 out of these 256 values have been assigned. See <xref target="EthernetNum"/>.</dd> <dt>01&nbhy;00&nbhy;5E&nbhy;90&nbhy;01&nbhy;00 through 01&nbhy;00&nbhy;5E&nbhy;90&nbhy;01&nbhy;FF:</dt> <dd>used for very small assignments that need parallel unicast and multicast MAC addresses. As of2023,2024, 1 out of these 256 values has been assigned. See <xref target="EthernetNum"/>.</dd> <dt>01&nbhy;00&nbhy;5E&nbhy;90&nbhy;10&nbhy;00 through 01&nbhy;00&nbhy;5E&nbhy;90&nbhy;10&nbhy;FF:</dt> <dd>2**8 addresses assigned for use in documentation by this document.</dd> </dl> </dd> </dl> <t>For more detailed and up-to-date information, see the"Ethernet"IANA OUI Ethernet Numbers" registry at <xref target="EthernetNum"/>.</t> </section> <section> <!-- 2.1.4 --> <name>48-Bit MAC Documentation Values</name> <t>The following values have been assigned for use in documentation:</t> <ul> <li>00&nbhy;00&nbhy;5E&nbhy;00&nbhy;53&nbhy;00 through 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;53&nbhy;FF for unicast and</li> <li>01&nbhy;00&nbhy;5E&nbhy;90&nbhy;10&nbhy;00 through 01&nbhy;00&nbhy;5E&nbhy;90&nbhy;10&nbhy;FF for multicast.</li> </ul> </section><section><section anchor="bit-48-assign-con"> <!-- 2.1.5 --> <name>48-Bit IANA MAC Assignment Considerations</name> <t>48-bit assignments under the current or a future IANA OUI (seeSection 5.6)<xref target="oui-ex"/>) must meet the following requirements:</t> <ul> <li>must be for standards purposes (either for an IETF Standard or other standard related to IETF work),</li> <li>must be for apower-of-two sizepower-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, </li> <li>must not be used to evade the requirement for network interface vendors to obtain their own block of identifiers from the IEEE, and </li> <li>must be documented in an Internet-Draft or RFC. </li> </ul> <t>In addition, approval must be obtained as follows (see the procedure inSection 5.1):</t><xref target="ex-rev-iesg-rat"/>):</t> <ul> <li>Small to medium assignments of a block of 1, 2, 4, ..., 32768, 65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI&nbhy;48 identifiers require Expert Review (seeSection 5.1).</li><xref target="ex-rev-iesg-rat"/>).</li> <li>Large assignments of 131072 (2**17) or more EUI&nbhy;48 identifiers require IESG Ratification (seeSection 5.1).</li><xref target="ex-rev-iesg-rat"/>).</li> </ul> </section> </section><section><section anchor="bit-64"> <!-- 2.2 --> <name>64-Bit MAC Identifiers</name> <t>IEEE also defines a system of 64-bit MACidentifiersidentifiers, including EUI&nbhy;64s. EUI&nbhy;64 identifiers are used as follows:</t> <ul> <li>In IEEE Std 1394 <xref target="IEEE1394"/> (also known as FireWire and i.Link)</li> <li>In IEEE Std 802.15.4 <xref target="IEEE802.15.4"/> (also known asZigBee)</li>Zigbee)</li> <li>In <xref target="InfiniBand"/></li> <li>In a modified form to construct some IPv6interface identifiersInterface Identifiers, as described inSection 2.2.1,<xref target="ipv6"/>, although this use is now deprecated</li> </ul> <t>Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) assignment, or a shorter extension to longer assigned prefixes <xreftarget="RAC_OUI"/>target="I-D.ieee-rac-oui-restructuring"/> so as to total 64 bits, produces an EUI&nbhy;64 identifier under that OUI or longer prefix. As with EUI&nbhy;48 identifiers, the first octet has the same speciallow orderlow-order bits.</t> <t>An AFN, a DNS RRTYPE, and CBOR tag have been assigned for 64-bit MACaddressesaddresses, as discussed in Sections2.4, 5.3,<xref target="cbor-tags" format="counter"/>, <xref target="mac-addresses" format="counter"/>, and5.9.<xref target="cbor-tag-assign" format="counter"/>. </t> <t>The discussion below is almost entirely in terms of the "Modified" form of EUI&nbhy;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. </t><section><section anchor="ipv6"> <!-- 2.2.1 --> <name>IPv6 Use of Modified EUI&nbhy;64 Identifiers</name> <t>The approach described below for constructing IPv6 Interface Identifiers is nowdeprecateddeprecated, and the method specified in <xref target="RFC8064"/> is recommended.</t> <t>EUI&nbhy;64 identifiers have been used to form the lower 64 bits of some IPv6 addresses (Section2.5.1<xref target="RFC4291" section="2.5.1" sectionFormat="bare"/> and AppendixA<xref target="RFC4291" section="A" sectionFormat="bare"/> of <xref target="RFC4291"/> andAppendix A of<xreftarget="RFC5214"/>).target="RFC5214" sectionFormat="of" section="A"/>). When so used, the EUI&nbhy;64 is modified by inverting the X(Local/Global)(universal/local) bit to form an IETF "Modified EUI&nbhy;64 identifier". Below is an illustration of a Modified EUI&nbhy;64 unicast identifier under the IANA OUI, where aa-bb-cc-dd-ee is the extension. </t> <t indent="3">02-00-5E-aa-bb-cc-dd-ee</t> <t>The first octet is shown as 02 rather than 00 because, in Modified EUI&nbhy;64 identifiers, the sense of the X bit is inverted compared with EUI&nbhy;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. </t> <t>The X(Local/Global)(universal/local) bit was inverted to make it easier for network operators to type in local-scope identifiers. Thus, such Modified EUI&nbhy;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.</t> <t>As with 48-bit MAC identifiers, theM-bitM bit (0x01) on in the first octet indicates a group identifier (multicast or broadcast). </t> <t>When the first two octets of the extension of a Modified EUI&nbhy;64 identifier are FF-FE, the remainder of the extension is a 24-bitvaluevalue, as assigned by the OUI owner for an EUI&nbhy;48. For example: </t> <t indent="3">02-00-5E-FF-FE-yy-yy-yy</t> <t>or</t> <t indent="3">03-00-5E-FF-FE-yy-yy-yy</t> <t>where yy-yy-yy is the portion (of an EUI&nbhy;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&nbhy;48 identifiers under the IANA OUI also has an equal number of Modified EUI&nbhy;64 identifiers that can be formed by inserting FF-FE in the middle of their EUI&nbhy;48 identifiers and inverting theLocal/Globaluniversal/local bit.</t> <t>In addition, certain Modified EUI&nbhy;64 identifiers under the IANA OUI are reserved for holders of IPv4 addresses as follows:</t> <t indent="3">02-00-5E-FE-xx-xx-xx-xx</t> <t>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&nbhy;64 address. Modified EUI&nbhy;64 identifiers from </t> <t indent="3">02-00-5E-FE-F0-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF</t> <t>are effectively reserved pending the specification of IPv4 "Class E" addresses <xref target="RFC1112"/>. However, for Modified EUI&nbhy;64 identifiers based on an IPv4 address, theLocal/Globaluniversal/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&nbhy;64 identifierLocal/Globaluniversal/local bit is reversed from that in (unmodified) EUI&nbhy;64 identifiers.)</t> </section><section><section anchor="eui-64-assign-con"> <name>EUI&nbhy;64 IANA Assignment Considerations</name> <t>The following table shows which Modified EUI&nbhy;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 listedbelow.</t> <dl> <dt>02&nbhy;00&nbhy;5E&nbhy;00&nbhy;00&nbhy;00&nbhy;00&nbhy;00 to 02&nbhy;00&nbhy;5E&nbhy;0F&nbhy;FF&nbhy;FF&nbhy;FF&nbhy;FF</dt> <dd>reserved</dd> <dt>02&nbhy;00&nbhy;5E&nbhy;10&nbhy;00&nbhy;00&nbhy;00&nbhy;00 to 02&nbhy;00&nbhy;5E&nbhy;10&nbhy;00&nbhy;00&nbhy;00&nbhy;FF</dt> <dd>assigned for documentation use</dd> <dt>02&nbhy;00&nbhy;5E&nbhy;10&nbhy;00&nbhy;00&nbhy;01&nbhy;00 to 02&nbhy;00&nbhy;5E&nbhy;EF&nbhy;FF&nbhy;FF&nbhy;FF&nbhy;FF</dt> <dd>available for assignment</dd> <dt>02&nbhy;00&nbhy;5E&nbhy;F0&nbhy;00&nbhy;00&nbhy;00&nbhy;00 to 02&nbhy;00&nbhy;5E&nbhy;FD&nbhy;FF&nbhy;FF&nbhy;FF&nbhy;FF</dt> <dd>reserved</dd> <dt>02&nbhy;00&nbhy;5E&nbhy;FE&nbhy;00&nbhy;00&nbhy;00&nbhy;00 to 02&nbhy;00&nbhy;5E&nbhy;FE&nbhy;FF&nbhy;FF&nbhy;FF&nbhy;FF</dt> <dd>assigned to IPv4 address holders as described above</dd> <dt>02&nbhy;00&nbhy;5E&nbhy;FF&nbhy;00&nbhy;00&nbhy;00&nbhy;00 to 02&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FD&nbhy;FF&nbhy;FF&nbhy;FF</dt> <dd>reserved</dd> <dt>02&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FE&nbhy;00&nbhy;00&nbhy;00below. These values are prefixed with 02-00-5E to02&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FE&nbhy;FF&nbhy;FF&nbhy;FF</dt> <dd>assigned for holders of EUI&nbhy;48 identifiers under the IANA OUI as described above</dd> <dt>02&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FF&nbhy;00&nbhy;00&nbhy;00form unicast modified EUI-64 addresses.</t> <table anchor="table_iana_64_bit_macs"> <name>IANA 64-bit MAC Addresses </name> <thead> <tr> <th>Addresses</th> <th>Usage</th> <th>Reference</th> </tr> </thead> <tbody> <tr> <td>00-00-00-00-00 to02&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FF&nbhy;FF&nbhy;FF&nbhy;FF</dt> <dd>reserved</dd> </dl>0F-FF-FF-FF-FF</td> <td>Reserved</td> <td>RFC 9542</td> </tr> <tr> <td>10-00-00-00-00 to 10-00-00-00-FF </td> <td>Documentation</td> <td>RFC 9542</td> </tr> <tr> <td>10-00-00-01-00 to EF-FF-FF-FF-FF</td> <td>Unassigned</td> <td></td> </tr> <tr> <td>FD-00-00-00-00 to FD-FF-FF-FF-FF</td> <td>Reserved</td> <td>RFC 9542</td> </tr> <tr> <td>FE-00-00-00-00 to FE-FF-FF-FF-FF</td> <td>IPv4 Addr Holders</td> <td>RFC 9542</td> </tr> <tr> <td>FF-00-00-00-00 to FF-FD-FF-FF-FF</td> <td>Reserved</td> <td>RFC 9542</td> </tr> <tr> <td>FF-FE-00-00-00 to FF-FE-FF-FF-FF</td> <td>IANA EUI-48 Holders</td> <td>RFC 9542</td> </tr> <tr> <td>FF-FF-00-00-00 to FF-FF-FF-FF-FF</td> <td>Reserved</td> <td>RFC 9542</td> </tr> </tbody> </table> <t>The reserved identifiers above require IESG Ratification (seeSection 5.1)<xref target="ex-rev-iesg-rat"/>) for assignment. IANA EUI&nbhy;64 identifier assignments under the IANA OUI must meet the following requirements:</t> <ul> <li>must be for standards purposes (either for an IETF Standard or other standard related to IETF work), </li> <li>must be for apower-of-two sizepower-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, </li> <li>must not be used to evade the requirement for network interface vendors to obtain their own block of identifiers from the IEEE, and </li> <li>must be documented in an Internet-Draft or RFC. </li> </ul> <t>In addition, approval must be obtained as follows (see the procedure inSection 5.1):</t><xref target="ex-rev-iesg-rat"/>):</t> <ul> <li>Small to medium assignments of a block of 1, 2, 4, ..., 134217728, 268435456 (2**0, 2**1, 2**2, ..., 2**27, 2**28) EUI&nbhy;64 identifiers require Expert Review (seeSection 5.1).</li><xref target="ex-rev-iesg-rat"/>).</li> <li>Large assignments of 536870912 (2**29) or more EUI&nbhy;64 identifiers require IESG Ratification (seeSection 5.1).</li><xref target="ex-rev-iesg-rat"/>).</li> </ul> </section> <section> <name>EUI&nbhy;64 Documentation Values</name> <t>The following blocks of unmodified 64-bit MAC addresses are for documentation use. The IPv4-derived addresses are based on the IPv4 documentation addresses <xref target="RFC5737"/>, and the MAC-derived addresses are based on the EUI&nbhy;48 documentation addresses above.</t> <t>Unicast values forDocumentation Use:</t>documentation use:</t> <t indent="3">00&nbhy;00&nbhy;5E&nbhy;EF&nbhy;10&nbhy;00&nbhy;00&nbhy;00 to 00&nbhy;00&nbhy;5E&nbhy;EF&nbhy;10&nbhy;00&nbhy;00&nbhy;FF general</t> <t indent="3">00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;C0&nbhy;00&nbhy;02&nbhy;00 to 00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;C0&nbhy;00&nbhy;02&nbhy;FF and 00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;C6&nbhy;33&nbhy;64&nbhy;00 to 00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;C6&nbhy;33&nbhy;64&nbhy;FF and 00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;CB&nbhy;00&nbhy;71&nbhy;00 to 00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;CB&nbhy;00&nbhy;71&nbhy;FF IPv4 derived</t> <t indent="3">00&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FE&nbhy;00&nbhy;53&nbhy;00 to 00&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FE&nbhy;00&nbhy;53&nbhy;FF EUI&nbhy;48 derived</t> <t indent="3">00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;EA&nbhy;C0&nbhy;00&nbhy;02 and 00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;EA&nbhy;C6&nbhy;33&nbhy;64 and 00&nbhy;00&nbhy;5E&nbhy;FE&nbhy;EA&nbhy;CB&nbhy;00&nbhy;71 IPv4 multicast derived from IPv4 unicast <xref target="RFC6034"/></t> <t>Multicast values forDocumentation Use:</t>documentation use:</t> <t indent="3">01&nbhy;00&nbhy;5E&nbhy;EF&nbhy;10&nbhy;00&nbhy;00&nbhy;00 to 01&nbhy;00&nbhy;5E&nbhy;EF&nbhy;10&nbhy;00&nbhy;00&nbhy;FF general</t> <t indent="3">01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;C0&nbhy;00&nbhy;02&nbhy;00 to 01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;C0&nbhy;00&nbhy;02&nbhy;FF and 01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;C6&nbhy;33&nbhy;64&nbhy;00 to 01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;C6&nbhy;33&nbhy;64&nbhy;FF and 01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;CB&nbhy;00&nbhy;71&nbhy;00 to 01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;CB&nbhy;00&nbhy;71&nbhy;FF IPv4 derived</t> <t indent="3">01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;EA&nbhy;C0&nbhy;00&nbhy;02 and 01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;EA&nbhy;C6&nbhy;33&nbhy;64 and 01&nbhy;00&nbhy;5E&nbhy;FE&nbhy;EA&nbhy;CB&nbhy;00&nbhy;71 IPv4 multicast derived from IPv4 unicast <xref target="RFC6034"/></t> <t indent="3">01&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FE&nbhy;90&nbhy;10&nbhy;00 to 01&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FE&nbhy;90&nbhy;10&nbhy;FF EUI&nbhy;48 derived</t> </section> </section> <!-- 2.2 --><section><section anchor="bit-48-ietf"> <name>Other48-bit48-Bit MAC Identifiers Used by the IETF</name> <t>There are two other blocks of 48-bit MAC identifiers that are used by the IETF as described below.</t><section><section anchor="id-33-33"> <name>Identifiers with a '33-33' Prefix</name> <t>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 <xref target="RFC2464"/> 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 bitonon, 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 (seeSection 2.1.1).</t> <t indent="3">Historical notes:<xref target="first-oct-bit"/>).</t> <aside> <t>Historical Notes: It was the custom during IPv6 design to use "3" for unknown or examplevaluesvalues, and 3333 Coyote Hill Road, Palo Alto,California,California is the address of PARC (Palo Alto ResearchCenter,Center), formerly "XeroxPARC").PARC." Ethernet was originally specified by the Digital Equipment Corporation, Intel Corporation, and Xerox Corporation. The pre-IEEE <xref target="IEEE.802.3_2012"/> Ethernet protocol has sometimes been known as "DIX" Ethernet from the first letters of the names of these companies.</t> </aside> </section> <section> <name>The'CF Series'</name>CF Series</name> <t>The Informational <xref target="RFC2153"/> declared the 3-octet values from CF&nbhy;00&nbhy;00 through CF&nbhy;FF&nbhy;FF to be "OUIs" available for assignment by IANA to software vendors for use in PPP <xref target="RFC1661"/> 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),(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 havebitsthe Y and M bits as zero; thus, there can be no conflict between CFSeries "OUI"sseries "OUIs" andIEEE assigned OUI/CIDs.IEEE-assigned OUIs/CIDs. Multicast MAC addresses constructed with a"CF"CF series OUI would fall into the Standard Assigned SLAP quadrant (seeSection 2.1.1).<xref target="first-oct-bit"/>). The Group bit is meaningless in PPP. To quote <xref target="RFC2153"/>: "The 'CF0000' series was arbitrarily chosen to match the PPP NLPID 'CF', as a matter of mnemonic convenience." (For further information onNLPIDs,Network Layer Protocol Identifiers (NLPIDs), see <xref target="RFC6328"/>.)</t> <t indent="3">CF&nbhy;00&nbhy;00 isreserved, and IANA listsreserved. CF&nbhy;00&nbhy;00&nbhy;00&nbhy;00&nbhy;00 is a multicastidentifier</t> <t indent="3">CF&nbhy;00&nbhy;00&nbhy;00&nbhy;00&nbhy;00identifier listed by IANA as used for Ethernet loopback tests.</t> <t>In over a decade of availability, only a handful of values in the CFSeriesseries have been assigned. (See the "IANA OUI Ethernet Numbers" <xref target="EthernetNum"/> and"PPP Numbers""Point-to-Point (PPP) Protocol Field Assignments" <xref target="PPPNum"/>).</t>registry groups.)</t> <section> <name>Changes to RFC 2153</name> <t>The IANA Considerations in <xref target="RFC2153"/> were updated as follows by the approval of <xref target="RFC5342"/> and remain so updated (no technical changes have been made):</t> <ul> <li>Use of these'CF Series'CF series identifiers based on IANA assignment was deprecated.</li> <li>IANA was instructed not to assign any further values in the'CF Series'.</li>CF series.</li> </ul> </section> </section> </section> <!-- 2.3 --><section><section anchor="cbor-tags"> <name>CBOR Tags</name> <t>The Concise Binary Object Representation(CBOR(CBOR) <xreftarget="RFC8949"/>)target="RFC8949"/> 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 taggedCBOR-tagged data items (fields) are not used in actual IEEE 802 address fields but may be used inCBOR encodedCBOR-encoded parts of protocol messages.</t> <t>IANA has assignedTBD148 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 bitslength MAC addressesbe used in thefuture,future for the length of MAC addresses, such as a 128-bit(16 octet)(16-octet) MAC address, theTBD148 tag will be used.</t> <t>IANA has assignedTDB21048 as the CBOR tag to indicate an OUI, CID, or"CF"CF series organizational identifier. The enclosed data item is an octet string of length 3 to hold the 24-bit OUI or CID (seeSection 2.1.2).</t><xref target="oui-cid"/>).</t> </section> <!-- 2.4 --> </section> <!-- 2. Ethernet Identifier Parameters --><section><section anchor="eth-pro-param"> <!-- 3. --> <name>Ethernet Protocol Parameters</name> <t>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.</t> <t>There are two types of protocol identifier parameters(See(see <xref target="EthernetNum"/>) that can occur in Ethernetframes as follows:</t> <dl>frames:</t> <dl newline="true"> <dt>EtherTypes:</dt> <dd>These are 16-bit identifierswhich,that, when considered as an unsigned integer, are equal to or larger than 0x0600. <xref target="EtherType"/> shows the simplest case where the EtherType of the protocol data in the frame appears immediately after the destination and source MAC addresses. <xref target="IEEE802_OandA"/> specifies two EtherTypes for local, experimental use: 0x88B5 and 0x88B6.</dd> <dt>LSAPs:</dt> <dd>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 <xref target="IEEE802.1AC"/> may also be used in place of such a length as a "length indication" of nonspecific length. LSAPs occur inpairspairs, where one is intended to indicate the source protocol handler (SSAP) andonethe other the destination protocol handler (DSAP); however, use cases where the two are different have been relatively rare. See <xref target="LSAP"/> 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).</dd> </dl> <figure anchor="EtherType"> <name>EtherType Frame Protocol Labeling</name> <artwork type="ascii-art" align="center"> <![CDATA[ 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 /// +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ ]]> </artwork> </figure> <figure anchor="LSAP"> <name>LSAP Frame Protocol Labeling</name> <artwork type="ascii-art" align="center"> <![CDATA[ 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 /// +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ ]]> </artwork> </figure> <t>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 LLCLSAP (Link-LayerLink-Layer Service AccessPoint)Point (LSAP) protocol indicator for the "main" body of the frame. Customarily, in the world of <xreftarget="IEEE802_OandA"/> world,target="IEEE802_OandA"/>, 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) <xref target="IEEE.802.1Q_2014"/>. 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. </t> <t>Neither EtherTypes nor LSAPs are assigned by IANA; they are assigned by the IEEE Registration Authority <xref target="IEEE_RA"/> (see <xref target="IEEEregAuth"/>aboveandAppendix B).<xref target="ethertypes"/>). 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.</t> <t>When using the IEEE 802 Logical Link Control (LLC) format (Subnetwork Access Protocol (SNAP)) <xref target="IEEE802_OandA"/> for a frame, an OUI-based protocol identifier can be expressed as follows:</t> <t indent="3">xx&nbhy;xx&nbhy;AA&nbhy;AA&nbhy;03&nbhy;yy&nbhy;yy&nbhy;yy&nbhy;zz&nbhy;zz </t> <t>where xx&nbhy;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&nbhy;yy&nbhy;yy is an OUI; and zz&nbhy;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.</t> <t>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 </t> <t indent="3">88&nbhy;B7&nbhy;yy&nbhy;yy&nbhy;yy&nbhy;zz&nbhy;zz</t> <t>where yy&nbhy;yy&nbhy;yy and zz&nbhy;zz have the same meaning as in the SNAP format described above; however, this format with EtherType 0x88B7 does not preserve 16-bit alignment. </t> <t>It is also possible, within the SNAP format, to use an arbitrary EtherType. Putting the EtherType as the zz&nbhy;zz field after an all-zeros OUI (00&nbhy;00&nbhy;00) does this. It looks like </t> <t indent="3">xx&nbhy;xx&nbhy;AA&nbhy;AA&nbhy;03&nbhy;00&nbhy;00&nbhy;00&nbhy;zz&nbhy;zz </t> <t>where zz&nbhy;zz is the EtherType.</t> <t>As well as labeling frame contents, IEEE 802 protocol types appear withinNBMA (Non-Broadcast Multi-Access)Non-Broadcast Multi-Access (NBMA) Next Hop Resolution Protocol <xref target="RFC2332"/> messages. Such messages have provisions for both two-octet EtherTypes and OUI-based protocol types. 16-bit EtherTypes also occur in the GenericRouterRouting Encapsulation(GRE(GRE) <xreftarget="RFC2784"/>)target="RFC2784"/> header and in theGENEVE (GenericGeneric Network Virtualization Encapsulation (Geneve) <xreftarget="RFC8926"/>)target="RFC8926"/> encapsulation header.</t><section><section anchor="eth-pro-iana-oui"> <name>Ethernet Protocol Assignment under the IANA OUI</name> <t>Two-octet protocol numbers under the IANA OUI are available, as in </t> <t indent="3">88&nbhy;B7&nbhy;00&nbhy;00&nbhy;5E&nbhy;qq&nbhy;qq </t> <t>or</t> <t indent="3">xx&nbhy;xx&nbhy;AA&nbhy;AA&nbhy;03&nbhy;00&nbhy;00&nbhy;5E&nbhy;qq&nbhy;qq </t> <t>where qq&nbhy;qq is the protocol number. </t> <t>A number of such assignments have been made out of the 2**16 protocol numbers available from 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;00 to 00&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FF (see <xref target="EthernetNum"/>). The extreme values of this range, 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;00 and 00&nbhy;00&nbhy;5E&nbhy;FF&nbhy;FF, are reserved and require IESG Ratification for assignment (seeSection 5.1).<xref target="ex-rev-iesg-rat"/>). New assignments of protocol numbers (qq&nbhy;qq) under the IANA OUI must meet the following requirements: </t> <ul> <li>the assignment must be for standards use (either for an IETF Standard or other standard related to IETF work), </li> <li>the protocol must include a version field at a fixed offset or an equivalent marking such that laterversionversions can be indicated in a way recognizable by earlier versions, </li><li>it<li>the protocol must be documented in an Internet-Draft or RFC, and </li> <li>such protocol numbers are not to be assigned for any protocol that has an EtherType.(Either that(That EtherType can be useddirectly or,directly, or -- in the LSAPscase, usingcase -- it can be used with the SNAP SAPandby putting anall-zerosall-zero "OUI" before the EtherType as describedabove.) </li>above.)</li> </ul> <t>In addition, the Expert Review (or IESG Ratification for the two reserved values) must be obtained using the procedure specified inSection 5.1.</t><xref target="ex-rev-iesg-rat"/>.</t> </section> <!-- 3.1 --> <section> <name>Documentation Protocol Number</name> <t>0x0042 is a protocol number under the IANA OUI (that is, 00&nbhy;00&nbhy;5E&nbhy;00&nbhy;42) to be used as an example for documentation purposes.</t> </section> <!-- 3.2 --> </section> <!-- 3. Ethernet Protocol Paraeeters --> <section> <!-- 4. --> <name>Other OUI/CID-Based Parameters</name> <t>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 calledOrganizationally-SpecificOrganizationally Specific parameters (sometimes informally and less accurately referred to as "vendor specific"). They would look like</t> <t indent="3">yy&nbhy;yy&nbhy;yy&nbhy;zz</t> <t>where yy&nbhy;yy&nbhy;yy is the OUI/CID and zz is the additional specifier. An example is the Cipher Suite Selector in <xref target="IEEE.802.11_2012"/>.</t> <t>Values may be assigned under the IANA OUI forsuchother OUI-based parameter usage by ExpertReviewReview, except that, for each use, the additional specifier values consisting of all zero bits and all one bits (0x00 (00&nbhy;00&nbhy;5E&nbhy;00) and 0xFF (00&nbhy;00&nbhy;5E&nbhy;FF) for a one-octet specifier) are reserved and require IESG Ratification (seeSection 5.1)<xref target="ex-rev-iesg-rat"/>) for assignment; also, the additional specifier value 0x42 (00&nbhy;00&nbhy;5E&nbhy;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.</t> <t>Assignments ofsuchother 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.</t> <t>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.</t><section><section anchor="lldp-ietf-tlv"> <name>LLDP IETFOrganizationally-SpecificOrganizationally Specific TLV Type</name> <t>An example ofsuchan "other IANAOUI basedOUI-based parameter" is specified in <xref target="RFC8520"/>. This provides for anOrganizationally-SpecificOrganizationally Specific TLV type for announcing a Manufacturer Usage Description (MUD) Uniform Resource Locator (URL) in the IEEE Link Local Discovery Protocol(LLDP(LLDP) <xreftarget="IEEE802.1AB"/>).target="IEEE802.1AB"/>. Additional IETF use of code points in this space have been proposed <xreftarget="BGP11dp"/>.target="I-D.acee-idr-lldp-peer-discovery"/>. (See alsoSection 5.8.)</t><xref target="lldp-tlv"/>.)</t> </section> <!-- 4.1 --> </section> <!-- 4. Other OUI-Based Parameters --> <section> <!-- 5. --> <name>IANA Considerations</name> <t>This document concerns IANA considerations for the assignment of Ethernet parameters in connection with the IANA OUI and related matters.</t> <t indent="3">Note: The"IETF"IANA OUI Ethernet Numbers"IANA Registry Groupregistry group (web page) is for registries of numbers assigned under the IANAOUIOUI, while the "IEEE 802 Numbers"IANA Registry Groupregistry group has informational lists of numbers assigned by the IEEE Registration Authority.</t> <t>This document does not create any new IANA registries.</t> <t>The MAC address values assigned for documentation and the protocol number for documentation were both assigned by <xref target="RFC7042"/>. </t> <t>No existing assignment is changed by this document.</t><section><section anchor="ex-rev-iesg-rat"> <!-- 5.1 --> <name>Expert Review and IESG Ratification</name> <t>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. </t> <section> <!-- 5.1.1 --> <name>Expert Review Guidance</name> <t>The procedure described for Expert Review assignments in this document is consistent with the IANA Expert Review policy described in <xref target="RFC8126"/>. </t> <t>While finite, the universe of MAC code points from which Expert-judged assignments will be made isfeltconsidered 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 lightsanityreasonableness 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.</t> </section> <section> <!-- 5.1.2 --> <name>Expert Review and IESG Ratification Procedure</name> <t>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&nbhy;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 <xref target="RFC8126"/>. IESG Approval is required only when the Expert does not reject the request. The procedure is as follows: </t> <t indent="3">The applicant always completes the appropriate template fromAppendix A<xref target="templates"/> below and sends it to IANA <iana@iana.org>.</t> <t indent="3">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.</t> <t indent="3">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 forrefusalrefusal, which IANA will communicate back to the applicant.</t> <t indent="3">If the assignment is based on Expert Review:</t> <tindent="9">Ifindent="6">If IANA receives approval and code points are available, IANA will make the requested assignment.</t> <t indent="3">If the assignment is based on IESG Ratification:</t> <tindent="9">Theindent="6">The procedure starts with the first steps above for Expert Review. If the Expert disapproves the application, they simply informIANAIANA, who in turn informs the applicant that their request is denied; however, if the Expert believes the application should beapproved,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 IESGtelechattelechat, 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 areasonreason, which IANA will communicate to the applicant.</t> </section> <!-- 5.1.2 --> </section> <!-- 5.1 --><section><section anchor="iana-name-changes"> <!-- 5.2 --> <name>IANA Registry Group (Web Page) Name Changes</name> <t>For clarity and parallelism with the IANA "IEEE 802 Numbers" registry group, the IANA "Ethernet Numbers" registry groupis re-namedhas been renamed the "IANA OUI Ethernet Numbers"web page.registry. </t> <t>As this document replaces <xref target="RFC7042"/>, references to <xref target="RFC7042"/> in IANA registries in both theIANA IEEE"IEEE 802NumbersNumbers" and theIANA IETF"IANA OUI EthernetNumbersNumbers" registry groupswill behave been replaced by references to[this document].this document. Other IANA registry references to <xref target="RFC7042"/> are not changed. </t> </section> <!-- 5.2 --><section><section anchor="mac-addresses"> <!-- 5.3 --> <name>MAC Address AFNs and RRTYPEs</name> <t>IANA has assigned Address Family Numbers (AFNs) for MAC addresses as follows:</t> <table> <thead> <tr><th>AFN</th><th>Decimal</th><th>Hex</th><th>Reference</th></tr> </thead> <tbody> <tr><td>48-bit MAC</td><td>16389</td><td>0x4005</td><td><xref target="RFC7042"/></td></tr> <tr><td>64-bit MAC</td><td>16390</td><td>0x4006</td><td><xref target="RFC7042"/></td></tr><tr><td>24-bit OUI</td><td>16391</td><td>0x4007</td><td><xref<tr><td>OUI</td><td>16391</td><td>0x4007</td><td><xref target="RFC7961"/></td></tr><tr><td colspan="4"></td></tr> <tr><td<tr><th colspan="4">Lower 24 bits of a 48-bit MACaddress:</td></tr>address:</th></tr> <tr><td>MAC/24</td><td>16392</td><td>0x4008</td><td><xref target="RFC7961"/></td></tr><tr><td colspan="4"></td></tr> <tr><td<tr><th colspan="4">Lower 40 bits of a 64-bit MACaddress:</td></tr>address:</th></tr> <tr><td>MAC/40</td><td>16393</td><td>0x4009</td><td><xref target="RFC7961"/></td></tr> </tbody> </table> <t>IANA has assigned DNS RRTYPEs <xref target="RFC6895"/> for MAC addresses as follows:</t> <table> <thead> <tr><th></th><th></th><th colspan="2" align="center">RRTYPE Code</th><th></th></tr> <tr><th>Data</th><th>Mnemonic</th><th>Decimal</th><th>Hex</th><th> Reference</th></tr> </thead> <tbody> <tr><td>48-bit MAC</td><td align="center">EUI48</td><td align="center">108</td><td>0x006C</td><td><xref target="RFC7043"/></td></tr> <tr><td>64-bit MAC</td><td align="center">EUI64</td><td align="center">109</td><td>0x006D</td><td><xref target="RFC7043"/></td></tr> </tbody> </table> </section> <!-- 5.3 --><section><section anchor="info-iana"> <!-- 5.4 --> <name>Informational IANA Registry Group Material</name> <t>IANA maintains an informational registry group, currently implemented as awebpage,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". IANAwill updateupdates that informational registry group when changes are provided by or approved by the Expert(s).</t> </section> <!-- 5.4 --><section><section anchor="ethertype-assign-pro"> <!-- 5.5 --> <name>EtherType Assignment Process</name> <t>Applying to the IEEE Registration Authority for an EtherType needed by an IETF protocol requires IESGapprovalApproval, as stated inAppendix B.<xref target="ethertypes"/>. To minimize confusion, this process will normally be done by the primary expert for the informationalIANA"EtherType" registry within the "IEEE 802Numbers EtherTypeNumbers" registry group, as described below (see alsoSection 5.4).</t><xref target="info-iana"/>).</t> <t>After IESGapprovalApproval of the requirement for an EtherType, the IESG should refer the matter to IANA. In any case, IANA will ask theIANA IEEE 802 Numbers EtherType"EtherType" registry expert to execute the IEEE Registration Authority <xref target="IEEE_RA"/> EtherType request process. This path is specified because the IESG usually deals with IANA for assignment actions and because IANA should be aware of whichIANA IEEE 802 Numbers EtherType"EtherType" registry expert(s) are available, normallyreferingreferring the making of theEthertypeEtherType assignment request to the primary expert.</t> <t>Here is sample text for anInternet DraftInternet-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 theInternet Draft:</t>Internet-Draft:</t> <blockquote> <t>X. Assignment Considerations</t> <t>X.1. IEEE Assignment Considerations</t> <t indent="3">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 IESGapprovalApproval to theIANA IEEE 802 Numbers EtherTyperegistry expert of the "EtherType" registry from the "IEEE 802 Numbers" registry group who will make the application to the IEEE Registrationauthority,Authority, keeping IANA informed.)</t> <t>X.2. IANA Considerations</t> <t indent="3">...</t> </blockquote> </section> <!-- 5.5 --><section><section anchor="oui-ex"> <!-- 5.6 --> <name>OUI Exhaustion</name> <t>When the available space for either multicast or unicast EUI&nbhy;48 identifiers under OUI 00&nbhy;00&nbhy;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.</t> </section> <!-- 5.6 --> <section> <!-- 5.7 --> <name>IANA OUI MAC Address Table</name> <t>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 areupdatedupdated, as specified inSection 5.2.</t><xref target="iana-name-changes"/>.</t> <t>The Notes for theIANA"IANA Unicast 48-bit MACAddressesAddresses" registry and for theIANA"IANA Multicast 48-bit MACAddressesAddresses" registry are changed to the following:</t><t indent="3">"These<blockquote> <t>These values are prefixed with 00-00-5E. SeeSection 2.1.5<xref target="bit-48-MAC"/> of[this document]."</t>RFC 9542.</t> </blockquote> <t>The Note for theIANA"IANA 64-bit MACAddressesAddresses" registry is changed to the following:</t><t indent="3">"These<blockquote> <t>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[this document],RFC 9542, particularlySection 2.2.2,<xref target="eui-64-assign-con"/>, for moredetails."</t>details.</t> </blockquote> </section> <!-- 5.7 --><section><section anchor="lldp-tlv"> <name>IANA LLDP TLV Subtypes</name> <t>IANAis requested to movehas moved the "IANA Link Layer Discovery Protocol (LLDP) TLV Subtypes"Registryregistry from theIANA IEEE"IEEE 802NumbersNumbers" registry group to theIANA"IANA OUI EthernetNumbersNumbers" registry group, since code points within it are assigned by IANA, andto add [this document]has added RFC 9542 as an additional reference for that registry.</t> <t>In addition, IANAis requested to updatehas updated three entries in thatRegistryregistry as follows:</t> <table> <thead> <tr><th>Value</th><th>Description</th><th>Reference</th></tr> </thead> <tbody> <tr><tdalign="right">0</td><td>Reserved</td><td>[this document]</td></tr>align="right">0</td><td>Reserved</td><td>RFC 9542</td></tr> <tr><td align="right">42</td><td>Example for use indocumentation</td><td>[this document]</td></tr>documentation</td><td>RFC 9542</td></tr> <tr><tdalign="right">255</td><td>Reserved</td><td>[this document]</td></tr>align="right">255</td><td>Reserved</td><td>RFC 9542</td></tr> </tbody> </table> <t>The entries for 1 (MUD), 2-41 (unassigned), and 43-254 (unassigned) are unchanged.</t> </section> <!-- 5.8 --><section><section anchor="cbor-tag-assign"> <name>CBOR Tag Assignments</name> <t>IANAis requested to assignhas assigned two CBOR Tags as shown below in theConcise"Concise Binary Object Representation (CBOR)Tags registry. [The values of 48 and 49 are requested for TBD1 and TBD2 respectively.]</t>Tags" registry.</t> <table> <thead> <tr><th>Tag</th><th>Data Item</th><th>Semantics</th><th>Reference</th></tr> </thead> <tbody><tr><td>TBD1</td><td>byte<tr><td>48</td><td>byte string</td><td>IEEE MACAddress</td><td>[this document]</td></tr> <tr><td>TBD2</td><td>byteAddress</td><td>RFC 9542</td></tr> <tr><td>1048</td><td>byte string</td><td>IEEEOUI/CID</td><td>[this document]</td></tr>OUI/CID</td><td>RFC 9542</td></tr> </tbody> </table> </section> <!-- 5.9 --> </section> <!-- 5. IANA Considerations --> <section> <!-- 6. --> <name>Security Considerations</name> <t>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:</t> <t indent="3">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.</t> <t>MAC addresses arean identifieridentifiers provided by a device to the network. On certain devices, MAC addresses are notstatic,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.</t> <t>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 usersasociatedassociated with that device. See <xreftarget="madinas"/>target="I-D.ietf-madinas-mac-address-randomization"/> for related privacy considerations and a discussion of MAC address randomization to partially mitigate this threat. Also, see <xref target="RFC7043"/> for the security and privacy considerations of publishing MAC addresses in DNS.</t> </section> <!-- end 6. Security Considerations --> </middle><!-- ____________________BACK_MATTER____________________ --><back> <displayreference target="I-D.acee-idr-lldp-peer-discovery" to="BGP11dp"/> <displayreference target="I-D.ietf-madinas-mac-address-randomization" to="madinas"/> <displayreference target="I-D.ieee-rac-oui-restructuring" to="RAC_OUI"/> <references> <name>References</name> <references> <name>Normative References</name> <referencegroup anchor="IEEE802_OandA"> <reference anchor="x"> <front> <title>IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture</title> <author><organization>IEEE 802</organization><organization>IEEE</organization> </author> <date year="2014"month="June" day="12"/>month="June"/> </front> <seriesInfo name="IEEE Std" value="802-2014"/> <seriesInfo name="DOI" value="10.1109/IEEESTD.2014.6847097"/> </reference> <reference anchor="y"> <front> <title>IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture--- Amendment 2: Local Medium Access Control (MAC) Address Usage</title> <author><organization>IEEE 802</organization><organization>IEEE</organization> </author> <date year="2017"month="April"/>month="August"/> </front> <seriesInfo name="IEEE Std" value="802c-2017"/> <seriesInfo name="DOI" value="10.1109/IEEESTD.2017.8016709"/> </reference> </referencegroup> <reference anchor="IEEE802.1AB"> <front> <title>IEEE Standard for Local and metropolitan area networks -StatinStation and Media Access Control Connectivity Discovery</title> <author><organization>IEEE 802</organization><organization>IEEE</organization> </author> <date year="2016"month="January" day="29"/>month="March"/> </front> <seriesInfo name="IEEE Std" value="802.1AB-2016"/> <seriesInfo name="DOI" value="10.1109/IEEESTD.2016.7433915"/> </reference> <xi:include href="https://www.rfc-editor.org/refs/bibxml6/reference.IEEE.802.1Q_2014.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8126.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/> </references> <references> <name>Informative References</name><reference anchor="BGP11dp" target="https://datatracker.ietf.org/doc/draft-acee-idr-lldp-peer-discovery/"> <front> <title>BGP Logical Link Discovery Protocol (LLDP) Peer Discovery</title> <author initials="A." surname="Lindem"/> <author initials="K." surname="Patel"/> <author initials="S." surname="Zandi"/> <author initials="J." surname="Haas"/> <author initials="X." surname="Xu"/> <date year="2022" month="December" day="6"/> </front> <seriesInfo name="work" value="in Progress"/> </reference><xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.acee-idr-lldp-peer-discovery.xml"/> <reference anchor="EthernetNum" target="https://www.iana.org/assignments/ethernet-numbers"> <front><title>Ethernet<title>IANA OUI Ethernet Numbers</title> <author> <organization>IANA</organization> </author> </front> </reference> <reference anchor="IANA" target="https://www.iana.org"> <front> <title>Internet Assigned Numbers Authority</title> <author> <organization>IANA</organization> </author> </front> </reference> <reference anchor="IEEE" target="https://www.ieee.org"> <front> <title>Instituteforof Electrical and Electronics Engineers</title> <author> <organization>IEEE</organization> </author> </front> </reference> <reference anchor="IEEE1394"> <front> <title>IEEE Standard for a High-Performance Serial Bus</title> <author> <organization>IEEE</organization> </author> <date year="2008"month="10" day="21"/>month="October"/> </front> <seriesInfo name="IEEE Std" value="1394-2008"/> <seriesInfo name="DOI" value="10.1109/IEEESTD.2008.4659233"/> </reference> <reference anchor="IEEE802" target="https://www.ieee802.org"> <front> <title>IEEE 802LAN/MAN Standards Committee</title>LMSC</title> <author> <organization>IEEE 802</organization> </author> </front> </reference> <reference anchor="IEEE802.15.4"> <front> <title>IEEE Standard for Low-Rate Wireless Networks</title> <author><organization>IEEE 802</organization><organization>IEEE</organization> </author> <dateyear="2020"/>year="2020" month="July"/> </front> <seriesInfo name="IEEE Std"value="802.14.4"/>value="802.15.4-2020"/> <seriesInfo name="DOI" value="10.1109/IEEESTD.2020.9144691"/> </reference> <reference anchor="IEEE802.1AC"> <front> <title>IEEE Standard for Local andMetropolitan Area Networks -metropolitan area networks -- Media Access Control (MAC) Service Definition</title> <author> <organization>IEEE 802</organization> </author> <dateyear="2016" month="December" day="7"/>year="2017" month="March"/> </front> <seriesInfo name="IEEE Std" value="802.1AC-2016"/> <seriesInfo name="DOI" value="10.1109/IEEESTD.2017.7875381"/> </reference> <reference anchor="IEEE802.1CQ"> <front><title>IEEE<title>Draft Standard for Local and Metropolitan AreaNetworks -Networks: Multicast and Local Address Assignment</title> <author><organization>IEEE 802</organization><organization>IEEE</organization> </author> <date year="2022"month="July" day="31"/>month="July"/> </front><seriesInfo name="draft" value="0.8"/><refcontent>draft 0.8</refcontent> <seriesInfo name="IEEE Std" value="802.1CQ/D0.8"/> </reference> <xi:include href="https://www.rfc-editor.org/refs/bibxml6/reference.IEEE.802.11_2012.xml"/><xi:include href="https://www.rfc-editor.org/refs/bibxml6/reference.IEEE.802.3_2012.xml"/><reference anchor="IEEE.802.3_2012" target="http://ieeexplore.ieee.org/servlet/opac?punumber=6419733"> <front> <title>IEEE Standard for Ethernet</title> <author> <organization>IEEE</organization> </author> <date day="24" month="January" year="2013"/> </front> <seriesInfo name="IEEE" value="802.3-2012"/> <seriesInfo name="DOI" value="10.1109/ieeestd.2012.6419735"/> </reference> <reference anchor="IEEE_RA" target="https://standards.ieee.org/products-programs/regauth/"> <front><title>IEEE Standards Association Registration<title>Registration Authority</title> <author><organization>IEEE RA</organization><organization>IEEE</organization> </author> </front> </reference> <reference anchor="IEEE_SA" target="https://standards.ieee.org"> <front> <title>IEEE Standards Association</title> <author><organization>IEEE SA</organization><organization>IEEE</organization> </author> </front> </reference> <reference anchor="IEEEtutorials" target="https://standards.ieee.org/wp-content/uploads/import/documents/tutorials/eui.pdf"> <front> <title>Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)</title> <author> <organization>IEEE</organization> </author> <date year="2017"month="August" day="3"/>month="August"/> </front> </reference> <reference anchor="InfiniBand" target="https://www.infinibandta.org/"> <front> <title>InfiniBand Architecture Specification Volume 1</title> <author> <organization>InfiniBand Trade Association</organization> </author> <date year="2007" month="November"/> </front> </reference> <referenceanchor="madinas" target="https://datatracker.ietf.org/doc/draft-ietf-madinas-mac-address-randomization/">anchor="I-D.ietf-madinas-mac-address-randomization" target="https://datatracker.ietf.org/doc/html/draft-ietf-madinas-mac-address-randomization-12"> <front> <title>Randomized and Changing MACAddress</title>Address state of affairs</title> <author initials="JC."surname="Zuniga"/>surname="Zúñiga" fullname="Juan-Carlos Zúñiga"> <organization>CISCO</organization> </author> <author initials="CJ."surname="Bernardos"/>surname="Bernardos" fullname="Carlos J. Bernardos" role="editor"> <organization>Universidad Carlos III de Madrid</organization> </author> <authorinitials="A" surname="Andersdotter"/>initials="A." surname="Andersdotter" fullname="Amelia Andersdotter"> <organization>Safespring AB</organization> </author> <dateyear="2023" month="September" day="13"/>month="February" day="28" year="2024" /> </front> <seriesInfoname="work" value="in Progress"/>name="Internet-Draft" value="draft-ietf-madinas-mac-address-randomization-12" /> </reference> <reference anchor="PPPNum" target="https://www.iana.org/assignments/ppp-numbers"> <front><title>PPP Numbers</title><title>Point-to-Point (PPP) Protocol Field Assignments</title> <author> <organization>IANA</organization> </author> </front> </reference><reference anchor="RAC_OUI" target="https://www.ietf.org/archive/id/draft-ieee-rac-oui-restructuring-01.txt"> <front> <title>OUI Registry Restructuring</title> <author fullname="Glenn Parsons" initials="G." surname="Parsons"/> <date year="2013" month="September"/> </front> <seriesInfo name="work in" value="Progress"/> </reference><xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.1112.xml"/>href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ieee-rac-oui-restructuring.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.1661.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1112.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2153.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1661.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2332.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2153.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2464.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2332.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2606.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2464.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2784.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2606.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.3092.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2784.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.4291.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3092.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.4760.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4291.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5214.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4760.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5332.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5214.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5342.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5332.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5737.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5342.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5798.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5737.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.6034.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5798.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.6328.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6034.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.6895.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6328.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.7042.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6895.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.7043.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7042.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.7319.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7043.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.7961.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7319.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8064.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7961.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8415.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8064.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8520.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8415.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8926.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8520.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8947.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8926.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8948.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8947.xml"/> <xi:includehref="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8949.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8948.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8949.xml"/> </references><section></references> <section anchor="templates"> <name>Templates</name> <t>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.</t> <section> <name>EUI&nbhy;48/EUI&nbhy;64 Identifier or Identifier Block Template</name> <t>Applicant Name:</t> <t>Applicant Email: </t> <t>Applicant Telephone: (starting with the country code) </t> <t>Use Name: (brief name of Parameteruseuse, such as "Foo Protocol" <xref target="RFC3092"/>)</t> <t>Document:(ID(I-D or RFC specifying use to which the identifier or block of identifiers will beput.)</t>put)</t> <t>Specify whether this is an application for EUI&nbhy;48 or EUI&nbhy;64 identifiers:</t> <t>Size of Block requested: (must be a power-of-two-sized block, can be a block of size one (2**0))</t> <t>Specify multicast, unicast, or both:</t> </section> <section> <name>IANA OUI/CID-Based Protocol Number Template</name> <t>Applicant Name: </t> <t>Applicant Email: </t> <t>Applicant Telephone: (starting with the country code) </t> <t>Use Name: (brief name of use of codepointpoint, such as "Foo Protocol") </t> <t>Document:(ID(I-D or RFC specifying use to which the protocol identifier will beput.)put) </t> <t>Note: (any additional note) </t> </section> <section> <name>Other IANA OUI/CID-Based Parameter Template</name> <t>Applicant Name: </t> <t>Applicant Email: </t> <t>Applicant Telephone: (starting with the country code) </t> <t>Protocol where the OUI/CID-Based Parameter for which a value is being requested appears: (suchas:as Cipher Suite selection in IEEE 802.11) </t> <t>Use Name: (brief name of use of code point to be assigned, such as "Foo Cipher Suite"[RFC3092])<xref target="RFC3092"/>) </t> <t>Document:(ID(I-D or RFC specifying use to which the other IANA OUI-based parameter value will beput.)put) </t> <t>Note: (any additional note) </t> </section> </section> <!-- Appendix A --><section><section anchor="ethertypes"> <name>EtherTypes</name> <t>This appendix provides a copy of the IESG Statement issued in May 2023 on obtaining new IETF EtherTypes inSection B.1.<xref target="iesg-ethertypes"/>. Note that there is an informational IANA registry of some important EtherTypes specified for IETF protocols or by IEEE 802 available, currently at <xref target="IANA"/>. The IEEE Registration Authority pageof EtherTypes, https://standards.ieee.org/regauth/ethertype/eth.txt,on EtherTypes <eref target="https://standards.ieee.org/regauth/ethertype/eth.txt" brackets="angle"/> may also be useful. SeeSection 3<xref target="eth-pro-param"/> above. </t><section><section anchor="iesg-ethertypes"> <name>IESG Statement onEthertypes</name> <t>From: IESG Date: 1EtherTypes</name> <dl newline="false" spacing="compact"> <dt>From:</dt> <dd>IESG</dd> <dt>Date:</dt> <dd>1 May2023</t>2023</dd> </dl> <t>The IEEE Registration Authority (IEEE RA) assigns EtherTypes with oversight from the IEEE Registration Authority Committee (IEEERAC)</t>RAC).</t> <t>(Seehttps://standards.ieee.org/products-programs/regauth/ethertype/.)<eref target="https://standards.ieee.org/products-programs/regauth/ethertype/"/>.) Some IETF protocol specifications make use of EtherTypes. All EtherType applications are subject to IEEE RA technical review for consistency with policy.</t> <t>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.</t> <t>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.</t> <t>Note that Local Experimental ("playpen") EtherTypes have been assigned in IEEE 802 [1]foruse during protocol development and experimentation.</t><t indent="4"> [1]<t>[1] IEEE Std 802. IEEE standard for Local and Metropolitan Area Networks: Overview and Architecture.</t> </section> </section> <!-- Appendix B --> <section> <!-- Appendix C --> <name>Changes from RFC 7042</name> <t>This document obsoletes <xref target="RFC7042"/> 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 inAppendix C of RFC 7042.</t><xref target="RFC7042" sectionFormat="of" section="C"/>.</t> <ul> <li>Add information on MA-M (28-bit) and MA-S (36-bit) EUI prefixes that the IEEE Registration Authority assigns.</li> <li>Add information on the restructuring of the "local" MAC address space into four quadrants under the Structured Local Address Plan(SLAP(SLAP) <xreftarget="IEEE802_OandA"/>).</li>target="IEEE802_OandA"/>.</li> <li>Include the IESG Statement on EtherTypes(See Appendix B.1)(see <xref target="iesg-ethertypes"/>) and more detailed IETF procedures for applying to the IEEE Registration Authority for an EtherType for use in an IETF protocol (seeSection 5.5).<xref target="ethertype-assign-pro"/>). </li> <li>Mention that IEEE 802 CFMCodepoints thatcode points have been allocated to the IETF (see <xref target="CFM"/>).</li> <li>Mention theorganizationally specificOrganizationally Specific LLDP data element that has been assigned under the IANA OUI and the registry set up for future such assignments (seeSection 4.1).</li><xref target="lldp-ietf-tlv"/>).</li> <li>Clarify minor details inSection 5.1<xref target="ex-rev-iesg-rat"/> on Expert Review and IESG Ratification.</li> <li>Specify CBOR tags for MAC addresses andOUI/CIDsOUIs/CIDs (seeSection 2.4).</li><xref target="cbor-tags"/>).</li> <li>Add a version field requirement for the allocation of protocol numbers under the IANA OUI (seeSection 3.1).</li><xref target="eth-pro-iana-oui"/>).</li> <li>Mention that EtherTypes are used in theGENEVEGeneve <xref target="RFC8926"/> encapsulation header (seeSection 3).</li><xref target="eth-pro-param"/>).</li> <li>Add "a combination of Expert Review and IESGApproal"Approval" as part of the specification for "IESG Ratification".</li> </ul> </section> <section anchor="Acknowledgements" numbered="false"> <name>Acknowledgements</name> <t>The comments and suggestions of the followingpeoplepersons and organizations are gratefully acknowledged:</t> <t indent="3">Comments and suggestions leading to thisDocument:</t>document:</t> <tindent="6">Carsten Bormann, Bob Hinden, Theindent="6"><contact fullname="Carsten Bormann"/>, <contact fullname="Bob Hinden"/>, the IEEE 802.1 Working Group,Éric Vyncke, Dale Worley, and Amanda Baber</t><contact fullname="Éric Vyncke"/>, <contact fullname="Dale Worley"/>, and <contact fullname="Amanda Baber"/></t> <t indent="3">Comments and suggestions leading toRFC 7042<xref target="RFC7042"/> (which is obsoleted by this document):</t> <tindent="6">David Black, Adrian Farrel, Bob Grow, Joel Jaeggli, Pearl Liang, Glenn Parsons, Pete Resnick, and Dan Romascanu.</t>indent="6"><contact fullname="David Black"/>, <contact fullname="Adrian Farrel"/>, <contact fullname="Bob Grow"/>, <contact fullname="Joel Jaeggli"/>, <contact fullname="Pearl Liang"/>, <contact fullname="Glenn Parsons"/>, <contact fullname="Pete Resnick"/>, and <contact fullname="Dan Romascanu"/></t> </section> </back> </rfc>