idnits 2.17.1 draft-eastlake-rfc7042bis-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 14, 2021) is 956 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 1320 -- Obsolete informational reference (is this intentional?): RFC 7042 (Obsoleted by RFC 9542) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group D. Eastlake 2 INTERNET-DRAFT Futurewei Technologies 3 Obsoletes: 7042 J. Abley 4 Intended Status: Best Current Practice Hopcount 5 Expires: March 13, 2022 September 14, 2021 7 IANA Considerations and IETF Protocol and Documentation Usage 8 for IEEE 802 Parameters 9 11 Abstract 13 Some IETF protocols make use of Ethernet frame formats and IEEE 802 14 parameters. This document discusses several uses of such parameters 15 in IETF protocols, specifies IANA considerations for assignment of 16 points under the IANA OUI (Organizationally Unique Identifier), and 17 provides some values for use in documentation. This document 18 obsoletes RFC 7042. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Distribution of this document is unlimited. Comments should be sent 26 to the authors. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF), its areas, and its working groups. Note that 30 other groups may also distribute working documents as Internet- 31 Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 https://www.ietf.org/1id-abstracts.html. The list of Internet-Draft 40 Shadow Directories can be accessed at 41 https://www.ietf.org/shadow.html. 43 Table of Contents 45 1. Introduction............................................4 46 1.1 Notations Used in This Document........................4 47 1.2 Changes from RFC 7042..................................5 48 1.3 The IEEE Registration Authority........................6 49 1.4 The IANA Organizationally Unique Identifier............6 50 1.5 CFM Code Points........................................6 52 2. Ethernet Identifier Parameters..........................7 53 2.1 48-Bit MAC Identifiers, OUIs, and Other Prefixes.......7 54 2.1.1 Special First Octet Bits.............................8 55 2.1.2 OUIs and CIDs........................................9 56 2.1.3 EUI-48 Assignments under the IANA OUI...............10 57 2.1.4 EUI-48 Documentation Values.........................11 58 2.1.5 EUI-48 IANA Assignment Considerations...............11 59 2.2 64-Bit MAC Identifiers................................12 60 2.2.1. IPv6 Use of Modified EUI-64 Identifiers............12 61 2.2.2 EUI-64 IANA Assignment Considerations...............14 62 2.2.3 EUI-64 Documentation Values.........................15 63 2.3 Other 48-bit MAC Identifiers Used by the IETF.........16 64 2.3.1 Identifiers Prefixed '33-33'........................16 65 2.3.2 The 'CF Series'.....................................16 66 2.3.2.1 Changes to RFC 2153...............................17 68 3. Ethernet Protocol Parameters...........................18 69 3.1 Ethernet Protocol Assignment under the IANA OUI.......19 70 3.2 Documentation Protocol Number.........................20 72 4. Other OUI-Based Parameters............................21 73 4.1 LLDP IETF Vendor-Specific TLV Type....................21 75 5. IANA Considerations...................................22 76 5.1 Expert Review and IESG Ratification...................22 77 5.2 IANA Web Page Changes.................................23 78 5.3 MAC Address AFNs and RRTYPEs..........................24 79 5.4 Informational IANA Web Page Material..................24 80 5.5 OUI Exhaustion........................................24 81 5.6 IANA OUI MAC Address Table............................25 82 5.7 IANA LLDP TLV Subtypes................................25 84 6. Security Considerations................................26 85 7. Acknowledgements.......................................26 87 Normative References......................................27 88 Informative References....................................27 90 Table of Contents (continued) 92 Appendix A. Templates.....................................31 93 A.1 EUI-48/EUI-64 Identifier or Identifier Block Template.31 94 A.2 IANA OUI-Based Protocol Number Template...............31 95 A.3 Other IANA OUI-Based Parameter Template...............32 97 Appendix B. Ethertypes...................................33 98 B.1 IESG Statement on Ethertypes..........................33 100 Authors' Addresses........................................34 102 1. Introduction 104 Some IETF protocols use Ethernet or other IEEE 802-related 105 communication frame formats and parameters [IEEE802]. These include 106 MAC (Media Access Control) addresses and protocol identifiers. 108 This document specifies IANA considerations for the assignment of 109 code points under the IANA OUI including MAC addresses and protocol 110 identifiers and provides some values for use in documentation. As 111 noted in [RFC2606] and [RFC5737], the use of designated code values 112 reserved for documentation and examples reduces the likelihood of 113 conflicts and confusion arising from their duplication of code points 114 assigned for some deployed use. This document also discusses several 115 other uses by the IETF of IEEE 802 code points, including IEEE 802 116 Connectivity Fault Management (CFM) code points [RFC7319] and IEEE 117 802 Link Local Discovery Protocol (LLDP [802.1AB]) Vaendor-Specific 118 TLV Sub-Types [RFC8520]. 120 [RFC8126] is incorporated herein except where there are contrary 121 provisions in this document. In this document, "IESG Ratification" 122 is used in some cases. IESG Ratification is specified in Section 5.1. 123 It is not the same as "IESG Approval" in [RFC8126]. 125 1.1 Notations Used in This Document 127 This document uses hexadecimal notation. Each octet (that is, 8-bit 128 byte) is represented by two hexadecimal digits giving the value of 129 the octet as an unsigned integer. Successive octets are separated by 130 a hyphen. This document consistently uses IETF ("network") bit 131 ordering although the physical order of bit transmission within an 132 octet on an IEEE [802.3] link is from the lowest order bit to the 133 highest order bit (i.e., the reverse of the IETF's ordering). 135 In this document: 137 "AFN" Address Family Number [RFC4760]. 139 "CFM" Connectivity Fault Management [RFC7319]. 141 "CID" Company Identifier. 143 "EUI" Extended Unique Identifier. 145 "IAB" Individual Address Block, not Internet Architecture Board. 147 "IEEE" Institute for Electrical and Electronics Engineers 148 (www.ieee.org). 150 "IEEE-SA" IEEE Standards Association (standards.ieee.org). 152 "MA-L" MAC Address Block Large, commonly referred to as an OUI. 154 "MA-M" MAC Address Block Medium. 156 "MA-S" MAC Address Block Small. 158 "MAC" Media Access Control, not for Message Authentication Code. 160 "MAC-48" A 48-bit MAC address. This term is obsolete. If globally 161 unique, use EUI-48. 163 "OUI" Organizationally Unique Identifier. An OUI is now officially 164 called an "MA-L" by the IEEE. 166 "RRTYPE" A DNS Resource Record type [RFC6895]. 168 "SLAP" IEEE 802 Structured Local Address Plan [802_O&A]. 170 "TLV" Type, Length, Value. 172 "**" The double asterisk symbol indicates exponentiation. For 173 example, 2**24 is two to the twenty-fourth power. 175 1.2 Changes from RFC 7042 177 This document obsoletes [RFC7042] and makes the changes listed below. 178 However, the completed application template based upon which an IANA 179 OUI-based protocol number value was assigned for document use remains 180 that in Appendix C of RFC 7042. 182 o Adds information on MA-M (28-bit) and MA-S (36-bit) EUI prefixes 183 that the IEEE Registration Authority assigns. 185 o Adds information on the restructuring of the "local" MAC address 186 space into four quadrants under the Structured Local Address Plan 187 (SLAP [802_O&A]). 189 o Includes the IESG Statement on Ethertypes (See Appendix B.1). 191 o Mentions that IEEE 802 CFM Codepoints that have been allocated to 192 the IETF (see Section 1.5). 194 o Mentions the vendor specific LLDP data element that has been 195 assigned under the IANA OUI (see Section 4.1). 197 o Clarifies minor details in Section 5.1 on Expert Review and IESG 198 Ratification. 200 1.3 The IEEE Registration Authority 202 Originally the responsibility of Xerox Corporation, the registration 203 authority for Ethernet parameters is now the IEEE Registration 204 Authority, available on the web at: 206 http://standards.ieee.org/regauth/ 208 The IEEE Registration Authority operates under the direction of the 209 IEEE-SA Board of Governors. Anyone may apply to that Authority for 210 parameter assignments. The IEEE Registration Authority may impose 211 fees or other requirements but commonly waives fees for applications 212 from standards development organizations. 214 Lists of assignments and their holders are downloadable from the IEEE 215 Registration Authority site. 217 1.4 The IANA Organizationally Unique Identifier 219 The Organizationally Unique Identifier (OUI) 00-00-5E has been 220 assigned to IANA by the IEEE Registration Authority. 222 There is no OUI value reserved at this time for documentation, but 223 there are documentation code points under the IANA OUI specified 224 below. 226 1.5 CFM Code Points 228 The IEEE has allocated two blocks of 802 Connectivity Fault 229 Management (CFM) code points to the IETF, one for CFM OpCodes and one 230 for CFM TLV Types. For further information see [RFC7319]. The IANA 231 "Connectivity Fault Management (CFM) OAM IETF Parameters" Registry 232 has subregistries for these code points. This document does not 233 further discuss these blocks of code points. 235 2. Ethernet Identifier Parameters 237 Section 2.1 discusses 48-bit MAC identifiers, their relationship to 238 OUIs and other prefixes, and assignment under the IANA OUI. Section 239 2.2 extends this to 64-bit identifiers. Section 2.3 discusses other 240 IETF MAC identifier use not under the IANA OUI. ([RAC_OUI] indicates 241 that the IEEE Registration Authority Committee was at one time 242 exploring the feasibility of defining 128-bit identifiers. [RAC_OUI] 243 is an expired draft that also provides additional historic 244 information on [IEEE802] registries.) 246 2.1 48-Bit MAC Identifiers, OUIs, and Other Prefixes 248 48-bit MAC "addresses" are the most commonly used Ethernet interface 249 identifiers. Those that are globally unique are also called EUI-48 250 identifiers (Extended Unique Identifier 48). An EUI-48 is structured 251 into an initial prefix assigned by the IEEE Registration Authority 252 and additional bits assigned by the prefix owner. Currently there 253 are three lengths of prefixes assigned as shown in the table below; 254 however, some prefix bits have special meaning as shown in Figure 1. 256 Prefix Length Owner Supplied Bits 257 in bits Name for EUI-48 258 ------------- ------ -------------------- 259 24 MAC-L (OUI) 24 260 28 MAC-M 20 261 36 MAC-S 12 263 The bottom four bits, as shown below, of the first octet of the 264 3-octet 48-bit MAC have special meaning and are referred to below as 265 the M, X, Y, and Z bits. 267 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 268 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 269 | . . . . Z Y X M| . . . . . . . .| octets 0&1 270 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 271 | . . . . . . . .| . . . . . . . .| octets 2&3 272 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 273 | . . . . . . . .| . . . . . . . .| octets 4&5 274 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 276 Figure 1. 48-bit MAC Address Structure 278 A 3-octet OUI (Organizationally Unique Identifier) is followed by an 279 additional 3 octets assigned by the OUI holder or there may be a 280 larger initial prefix assigned to an organization and a shorter 281 sequence of additional bits so as to add up to 48 bits in total. For 282 example, the IEEE has assigned IABs (Individual Address Blocks), 283 where the first 4 1/2 octets (36 bits) are assigned, giving the 284 holder of the IAB 1 1/2 octets (12 bits) they can control; however, 285 IABs have become historic, and a wider range of prefix lengths are 286 available [RAC_OUI]. 288 The IEEE describes its assignment procedures and policies for IEEE 289 802-related identifiers in [802_O&A]. An IEEE tutorial on EUIs, OUIs, 290 and CIDs is available at [IEEEtutorial]. 292 2.1.1 Special First Octet Bits 294 Four bits within the initial octet of an IEEE MAC interface 295 identifier, such as an EUI-48, have special significance [802_O&A] as 296 follows: 298 M bit --- This bit always indicates a group address and is 299 frequently referred to as the group bit. If it is zero, 300 the MAC address is unicast. If it is a one, the address is 301 multicast or broadcast. This meaning is independent of the 302 values of the X, Y, and Z bits. 304 X bit --- This bit was previously called the "local" bit. If it is 305 zero, the MAC address is a global address under the 306 control of the owner of the IEEE assigned prefix. 307 Previously, if it was a one, the MAC address was 308 considered "local" and under the assignment and control of 309 the local network operator (but see Section 2.3). Now, if 310 it is a one, the nature of the MAC address is optionally 311 determined by the Y and Z bits under the IEEE 802 312 Structured Local Address Plan (SLAP) as described below. 314 Y&Z bits - These two bits have no special meaning if the X bit is 315 zero. If the X bit is one, these two bits divide the 316 formerly uniform "local" MAC address space into four 317 quadrants, as follows. These quadrants are further 318 described below. 320 Y bit Z bit Quadrant 321 ----- ----- ----------- 322 0 0 Administratively Assigned 323 0 1 Extended Local 324 1 0 Reserved 325 1 1 Standard Assigned 327 While a local network administrator can assign any addresses with the 328 X bit a one, the optional SLAP characterizes the four quadrants of 329 the "local" address space using the Y and Z bits as follows: 331 Administratively Assigned - MAC addresses in this quadrant are 332 called Administratively Assigned Identifiers. This is 333 intended for arbitrary local assignment such as random 334 assignment; however, see Section 2.3.1. 336 Extended Local - MAC addresses in this quadrant are called Extended 337 Local Identifiers. These addresses are not actually 338 "local" under SLAP. They are available to the 339 organization that has been assigned the CID (see Section 340 2.1.2) specifying the other 20 bits of the 24-bit prefix 341 with X, Y, Z bits 1, 0, 1 respectively. 343 Reserved - MAC addresses in this quadrant are reserved for future 344 use under the SLAP. Until such future use, they could be 345 locally assigned as Administratively Assigned Identifiers 346 are assigned but there is a danger that future SLAP use 347 would conflict with such local assignments. 349 Standard Assigned - MAC addresses in this quadrant are known as 350 Standard Assigned Identifiers. It is intended that such 351 addresses be assigned and possibly revoked through a 352 local protocol. There is work in the IEEE [802.1CQ] and 353 the IETF [RFC8947] [RFC8948] related to such protocols. 355 2.1.2 OUIs and CIDs 357 OUI, MAC-M, and MAC-S MAC prefixes are assigned with the Local bit 358 zero and the Group bit unspecified. Multicast identifiers may be 359 constructed by turning on the Group bit, and unicast identifiers may 360 be constructed by leaving the Group bit zero. 362 The Local bit is zero for globally unique EUI-48 identifiers assigned 363 by the owner of an OUI or owner of a longer prefix. If the Local bit 364 is a one, the identifier has been considered by IEEE 802 to be a 365 local identifier under the control of the local network 366 administrator; however, there are now recommendations on optional 367 management of the local address space as discussed in Section 2.1.1. 368 If the Local bit is on, the holder of an OUI has no special authority 369 over MAC identifiers whose first 3 octets correspond to their OUI or 370 the beginning of their longer prefix. 372 [more info on CIDs needed here] 374 An AFN and a DNS RRTYPE have been assigned for 48-bit MAC addresses 375 (See Section 5.2). 377 2.1.3 EUI-48 Assignments under the IANA OUI 379 The OUI 00-00-5E has been assigned to IANA as stated in Section 1.4 380 above. This includes 2**24 EUI-48 multicast identifiers from 381 01-00-5E-00-00-00 to 01-00-5E-FF-FF-FF and 2**24 EUI-48 unicast 382 identifiers from 00-00-5E-00-00-00 to 00-00-5E-FF-FF-FF. 384 Of these EUI-48 identifiers, the sub-blocks reserved or thus far 385 assigned by IANA for purposes of documentation are as follows: 387 Unicast, all blocks of 2**8 addresses thus far: 389 00-00-5E-00-00-00 through 00-00-5E-00-00-FF: reserved and require 390 IESG Ratification for assignment (see Section 5.1). 392 00-00-5E-00-01-00 through 00-00-5E-00-01-FF: assigned for the 393 Virtual Router Redundancy Protocol (VRRP) [RFC5798]. 395 00-00-5E-00-02-00 through 00-00-5E-00-02-FF: assigned for the IPv6 396 Virtual Router Redundancy Protocol (IPv6 VRRP) [RFC5798]. 398 00-00-5E-00-52-00 through 00-00-5E-00-52-FF: used for very small 399 assignments. Currently, 4 out of these 256 values have been 400 assigned. 402 00-00-5E-00-53-00 through 00-00-5E-00-53-FF: assigned for use in 403 documentation. 405 00-00-5E-90-01-00 through 00-00-5E-90-01-FF: used for very small 406 assignments that need parallel unicast and multicast MAC 407 addresses. Currently 1 out of these 256 values has been 408 assigned. 410 Multicast: 412 01-00-5E-00-00-00 through 01-00-5E-7F-FF-FF: 2**23 addresses 413 assigned for IPv4 multicast [RFC1112]. 415 01-00-5E-80-00-00 through 01-00-5E-8F-FF-FF: 2**20 addresses 416 assigned for MPLS multicast [RFC5332]. 418 01-00-5E-90-00-00 through 01-00-5E-90-00-FF: 2**8 addresses being 419 used for very small assignments. Currently, 4 out of these 256 420 values have been assigned. 422 01-00-5E-90-01-00 through 01-00-5E-90-01-FF: used for very small 423 assignments that need parallel unicast and multicast MAC 424 addresses. Currently 1 out of these 256 values has been 425 assigned. 427 01-00-5E-90-10-00 through 01-00-5E-90-10-FF: 2**8 addresses for 428 use in documentation. 430 For more detailed and up-to-date information, see the "Ethernet 431 Numbers" registry at http://www.iana.org. 433 2.1.4 EUI-48 Documentation Values 435 The following values have been assigned for use in documentation: 437 00-00-5E-00-53-00 through 00-00-5E-00-53-FF for unicast and 439 01-00-5E-90-10-00 through 01-00-5E-90-10-FF for multicast. 441 2.1.5 EUI-48 IANA Assignment Considerations 443 EUI-48 assignments under the current or a future IANA OUI (see 444 Section 5.4) must meet the following requirements: 446 o must be for standards purposes (either for an IETF Standard or 447 other standard related to IETF work), 449 o must be for a power-of-two size block of identifiers starting 450 at a boundary that is an equal or greater power of two, 451 including the assignment of one (2**0) identifier, 453 o must not be used to evade the requirement for vendors to obtain 454 their own block of identifiers from the IEEE, and 456 o must be documented in an Internet-Draft or RFC. 458 In addition, approval must be obtained as follows (see the procedure 459 in Section 5.1): 461 Small to medium assignments of a block of 1, 2, 4, ..., 32768, 462 65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI-48 identifiers 463 require Expert Review (see Section 5.1). 465 Large assignments of 131072 (2**17) or more EUI-48 identifiers 466 require IESG Ratification (see Section 5.1). 468 2.2 64-Bit MAC Identifiers 470 IEEE also defines a system of 64-bit MAC identifiers including 471 EUI-64s. EUI-64 identifiers are currently used as follows: 473 o In a modified form to construct some IPv6 interface identifiers 474 as described in Section 2.2.1 476 o In IEEE Std 1394 (also known as FireWire and i.Link) 478 o In IEEE Std 802.15.4 (also known as ZigBee) 480 o In [InfiniBand] 482 Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) OUI, or a 483 shorter extension to longer assigned prefixes [RAC_OUI] so as to 484 total 64 bits, produces an EUI-64 identifier under that OUI or longer 485 prefix. As with EUI-48 identifiers, the first octet has the same 486 Group and Local bits. 488 An AFN and a DNS RRTYPE have been assigned for 64-bit MAC addresses 489 (See Section 5.2). 491 The discussion below is almost entirely in terms of the "Modified" 492 form of EUI-64 identifiers; however, anyone assigned such an 493 identifier can also use the unmodified form as a MAC identifier on 494 any link that uses such 64-bit identifiers for interfaces. 496 2.2.1. IPv6 Use of Modified EUI-64 Identifiers 498 MAC-64 identifiers are used to form the lower 64 bits of some IPv6 499 addresses (Section 2.5.1 and Appendix A of [RFC4291] and Appendix A 500 of [RFC5214]). When so used, the MAC-64 is modified by inverting the 501 Local/Global bit to form an IETF "Modified EUI-64 identifier". Below 502 is an illustration of a Modified EUI-64 unicast identifier under the 503 IANA OUI, where aa-bb-cc-dd-ee is the extension. 505 02-00-5E-aa-bb-cc-dd-ee 507 The first octet is shown as 02 rather than 00 because, in Modified 508 EUI-64 identifiers, the sense of the Local/Global bit is inverted 509 compared with EUI-48 identifiers. It is the globally unique values 510 (universal scope) that have the 02 bit on in the first octet, while 511 those with this bit off are locally assigned and out of scope for 512 global assignment. 514 The Local/Global bit was inverted to make it easier for network 515 operators to type in local-scope identifiers. Thus, such Modified 516 EUI-64 identifiers as 1, 2, etc. (ignoring leading zeros) are local. 517 Without the modification, they would have to be 518 02-00-00-00-00-00-00-01, 02-00-00-00-00-00-00-02, etc. to be local. 520 As with 48-bit MAC identifiers, the 01 bit on in the first octet 521 indicates a group identifier. 523 When the first two octets of the extension of a Modified EUI-64 524 identifier are FF-FE, the remainder of the extension is a 24-bit 525 value as assigned by the OUI owner for an EUI-48. For example: 527 02-00-5E-FF-FE-yy-yy-yy 528 or 529 03-00-5E-FF-FE-yy-yy-yy 531 where yy-yy-yy is the portion (of an EUI-48 global unicast or 532 multicast identifier) that is assigned by the OUI owner (IANA in this 533 case). Thus, any holder of one or more EUI-48 identifiers under the 534 IANA OUI also has an equal number of Modified EUI-64 identifiers that 535 can be formed by inserting FF-FE in the middle of their EUI-48 536 identifiers and inverting the Local/Global bit. 538 (Note: [EUI-64] defines FF-FF as the bits to be inserted to create 539 an IEEE EUI-64 identifier from a EUI-48 identifier. That document 540 says the FF-FE value is used when starting with an EUI-48 541 identifier. The IETF uses only FF-FE to create Modified EUI-64 542 identifiers from 48-bit Ethernet station identifiers regardless of 543 whether they are EUI-48 or 48-bit local MAC identifiers. EUI-48 544 and local 48-bit MAC identifiers are syntactically equivalent, and 545 this doesn't cause any problems in practice.) 547 In addition, certain Modified EUI-64 identifiers under the IANA OUI 548 are reserved for holders of IPv4 addresses as follows: 550 02-00-5E-FE-xx-xx-xx-xx 552 where xx-xx-xx-xx is a 32-bit IPv4 address. The owner of an IPv4 553 address has both the unicast- and multicast-derived EUI-64 address. 554 Modified EUI-64 identifiers from 556 02-00-5E-FE-F0-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF 558 are effectively reserved pending the specification of IPv4 Class E 559 addresses. However, for Modified EUI-64 identifiers based on an IPv4 560 address, the Local/Global bit should be set to correspond to whether 561 the IPv4 address is local or global. (Keep in mind that the sense of 562 the Modified EUI-64 identifier Local/Global bit is reversed from that 563 in (unmodified) MAC-64 identifiers.) 565 2.2.2 EUI-64 IANA Assignment Considerations 567 The following table shows which Modified EUI-64 identifiers under the 568 IANA OUI are reserved, assigned, or available as indicated. As noted 569 above, the corresponding MAC addresses can be determined by 570 complementing the 02 bit in the first octet. In all cases, the 571 corresponding multicast 64-bit MAC addresses formed by complementing 572 the 01 bit in the first octet have the same status as the modified 573 64-bit unicast address blocks listed below. 575 02-00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF reserved 577 02-00-5E-10-00-00-00-00 to 02-00-5E-10-00-00-00-FF assigned for 578 documentation use 580 02-00-5E-10-00-00-01-00 to 02-00-5E-EF-FF-FF-FF-FF available for 581 assignment 583 02-00-5E-F0-00-00-00-00 to 02-00-5E-FD-FF-FF-FF-FF reserved 585 02-00-5E-FE-00-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF assigned to 586 IPv4 address holders as described above 588 02-00-5E-FF-00-00-00-00 to 02-00-5E-FF-FD-FF-FF-FF reserved 590 02-00-5E-FF-FE-00-00-00 to 02-00-5E-FF-FE-FF-FF-FF assigned for 591 holders of EUI-48 identifiers under the IANA OUI as described 592 above 594 02-00-5E-FF-FF-00-00-00 to 02-00-5E-FF-FF-FF-FF-FF reserved 596 The reserved identifiers above require IESG Ratification (see Section 597 5.1) for assignment. IANA EUI-64 identifier assignments under the 598 IANA OUI must meet the following requirements: 600 o must be for standards purposes (either for an IETF Standard or 601 other standard related to IETF work), 603 o must be for a power-of-two size block of identifiers starting 604 at a boundary that is an equal or greater power of two, 605 including the assignment of one (2**0) identifier, 607 o must not be used to evade the requirement for vendors to obtain 608 their own block of identifiers from the IEEE, and 610 o must be documented in an Internet-Draft or RFC. 612 In addition, approval must be obtained as follows (see the procedure 613 in Section 5.1): 615 Small to medium assignments of a block of 1, 2, 4, ..., 134217728, 616 268435456 (2**0, 2**1, 2**2, ..., 2**27, 2**28) EUI-64 617 identifiers require Expert Review (see Section 5.1). 619 Assignments of any size, including 536870912 (2**29) or more 620 EUI-64 identifiers, may be made with IESG Ratification (see 621 Section 5.1). 623 2.2.3 EUI-64 Documentation Values 625 The following blocks of unmodified 64-bit MAC addresses are for 626 documentation use. The IPv4-derived addresses are based on the IPv4 627 documentation addresses [RFC5737], and the MAC-derived addresses are 628 based on the EUI-48 documentation addresses above. 630 Unicast Values for Documentation Use: 632 00-00-5E-EF-10-00-00-00 to 00-00-5E-EF-10-00-00-FF general 634 00-00-5E-FE-C0-00-02-00 to 00-00-5E-FE-C0-00-02-FF and 635 00-00-5E-FE-C6-33-64-00 to 00-00-5E-FE-C6-33-64-FF and 636 00-00-5E-FE-CB-00-71-00 to 00-00-5E-FE-CB-00-71-FF IPv4 derived 638 00-00-5E-FF-FE-00-53-00 to 00-00-5E-FF-FE-00-53-FF EUI-48 derived 640 00-00-5E-FE-EA-C0-00-02 and 641 00-00-5E-FE-EA-C6-33-64 and 642 00-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 643 [RFC6034] 645 Multicast Values for Documentation Use: 647 01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general 649 01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and 650 01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and 651 01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived 653 01-00-5E-FE-EA-C0-00-02 and 654 01-00-5E-FE-EA-C6-33-64 and 655 01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 656 [RFC6034] 658 01-00-5E-FF-FE-90-10-00 to 01-00-5E-FF-FE-90-10-FF EUI-48 derived 660 2.3 Other 48-bit MAC Identifiers Used by the IETF 662 There are two other blocks of 48-bit MAC identifiers that are used by 663 the IETF as described below. 665 2.3.1 Identifiers Prefixed '33-33' 667 All 48-bit multicast MAC identifiers prefixed "33-33" (that is, the 668 2**32 multicast MAC identifiers in the range from 33-33-00-00-00-00 669 to 33-33-FF-FF-FF-FF) are used as specified in [RFC2464] for IPv6 670 multicast. In all of these identifiers, the Group bit (the bottom 671 bit of the first octet) is on, as is required to work properly with 672 existing hardware as a multicast identifier. They also have the 673 Local bit on but any ethernet using standard IPv6 multicast should 674 note that these addresses will be used for that purpose. These 675 multicast MAC addresses fall into the administratively assigned SLAP 676 quadrant (see Section 2.1.1). 678 (Historical note: It was the custom during IPv6 design to use "3" 679 for unknown or example values and 3333 Coyote Hill Road, Palo 680 Alto, California, is the address of PARC (Palo Alto Research 681 Center, formerly "Xerox PARC"). Ethernet was originally specified 682 by the Digital Equipment Corporation, Intel Corporation, and Xerox 683 Corporation. The pre-IEEE [802.3] Ethernet protocol has sometimes 684 been known as "DIX" Ethernet from the first letters of the names 685 of these companies.) 687 2.3.2 The 'CF Series' 689 The Informational [RFC2153] declared the 3-octet values from CF-00-00 690 through CF-FF-FF to be OUIs available for assignment by IANA to 691 software vendors for use in PPP [RFC1661] or for other uses where 692 vendors do not otherwise need an IEEE-assigned OUI. It should be 693 noted that, when used as 48-bit MAC prefixes, these values have all 694 of the Z, Y, X (Local), and M (Group) special bits at the bottom of 695 the first byte equal to one, while all IEEE-assigned OUIs thus far 696 have the X and M bits zero. Multicast MAC addresses constructed with 697 a "CF" series OUI would fall into the standard assigned SLAP quadrant 698 (see Section 2.1.1). The Group bit is meaningless in PPP. To quote 699 [RFC2153]: "The 'CF0000' series was arbitrarily chosen to match the 700 PPP NLPID 'CF', as a matter of mnemonic convenience." (For further 701 information on NLPIDs, see [RFC6328].) 703 CF-00-00 is reserved, and IANA lists multicast identifier 704 CF-00-00-00-00-00 as used for Ethernet loopback tests. 706 In over a decade of availability, only a handful of values in the CF 707 Series have been assigned. (See "Ethernet Numbers" 708 and "PPP Numbers" 709 ). 711 2.3.2.1 Changes to RFC 2153 713 The IANA Considerations in [RFC2153] were updated as follows by the 714 approval of RFC 5342 (no technical changes have been made): 716 o Use of these identifiers based on IANA assignment was 717 deprecated. 719 o IANA was instructed not to assign any further values in the 'CF 720 Series'. 722 3. Ethernet Protocol Parameters 724 Ethernet protocol parameters provide a means of indicating the 725 contents of a frame -- for example, that its contents are IPv4 or 726 IPv6. 728 The concept has been extended to labeling by "tags". A tag in this 729 sense is a prefix whose type is identified by an Ethertype that is 730 then followed by either another tag, an Ethertype, or an LSAP (Link- 731 Layer Service Access Point) protocol indicator for the "main" body of 732 the frame, as described below. Traditionally, in the [802_O&A] 733 world, tags are a fixed length and do not include any encoding of 734 their own length. Any device that is processing a frame cannot, in 735 general, safely process anything in the frame past an Ethertype it 736 does not understand. An example is the C-Tag (formerly the Q-Tag) 737 [802.1Q]. It provides customer VLAN and priority information for a 738 frame. 740 There are two types of protocol identifier parameters that can occur 741 in Ethernet frames after the initial MAC-48 destination and source 742 identifiers: 744 Ethertypes: These are 16-bit identifiers appearing as the initial 745 two octets after the MAC destination and source (or after a 746 tag), which, when considered as an unsigned integer, are equal 747 to or larger than 0x0600. 749 LSAPs: These are 8-bit protocol identifiers that occur in pairs 750 immediately after an initial 16-bit (two-octet) remaining frame 751 length, which is in turn after the MAC destination and source 752 (or after a tag). Such a length must, when considered as an 753 unsigned integer, be less than 0x5DC, or it could be mistaken 754 as an Ethertype. LSAPs occur in pairs where one is intended to 755 indicate the source protocol handler and one the destination 756 protocol handler; however, use cases where the two are 757 different have been relatively rare. 759 Neither Ethertypes nor LSAPs are assigned by IANA; they are assigned 760 by the IEEE Registration Authority (see Section 1.3 above and 761 Appendix B). However, both LSAPs and Ethertypes have extension 762 mechanisms so that they can be used with five-octet Ethernet protocol 763 identifiers under an OUI, including those assigned by IANA under the 764 IANA OUI. 766 When using the IEEE 802 Logical Link Control (LLC) format (Subnetwork 767 Access Protocol (SNAP)) [802_O&A] for a frame, an OUI-based protocol 768 identifier can be expressed as follows: 770 xx-xx-AA-AA-03-yy-yy-yy-zz-zz 772 where xx-xx is the frame length and, as above, must be small enough 773 not to be confused with an Ethertype; "AA" is the LSAP that indicates 774 this use and is sometimes referred to as the SNAP Service Access 775 Point (SAP); "03" is the LLC control octet indicating datagram 776 service; yy-yy-yy is an OUI; and zz-zz is a protocol number, under 777 that OUI, assigned by the OUI owner. The five-octet length for such 778 OUI-based protocol identifiers was chosen so that, with the LLC 779 control octet ("03"), the result is 16-bit aligned. 781 When using an Ethertype to indicate the main type for a frame body, 782 the special "OUI Extended Ethertype" 88-B7 is available. Using this 783 Ethertype, a frame body can begin with 785 88-B7-yy-yy-yy-zz-zz 787 where yy-yy-yy and zz-zz have the same meaning as in the SNAP format 788 described above. 790 It is also possible, within the SNAP format, to use an arbitrary 791 Ethertype. Putting the Ethertype as the zz-zz field after an all- 792 zeros OUI (00-00-00) does this. It looks like 794 xx-xx-AA-AA-03-00-00-00-zz-zz 796 where zz-zz is the Ethertype. 798 (Note that, at this point, the 802 protocol syntax facilities are 799 sufficiently powerful that they could be chained indefinitely. 800 Whether support for such chaining is generally required is not 801 clear, but [802_O&A] requires support for 803 xx-xx-AA-AA-03-00-00-00-88-B7-yy-yy-yy-zz-zz 805 although this could be more efficiently expressed by simply 806 pinching out the "00-00-00-88-B7" in the middle.) 808 As well as labeling frame contents, 802 protocol types appear within 809 NBMA (Non-Broadcast Multi-Access) Next Hop Resolution Protocol 810 [RFC2332] messages. Such messages have provisions for both two-octet 811 Ethertypes and OUI-based protocol types. 16-bit Ethertypes also occur 812 in the Generic Router Encapsulation (GRE [RFC2784]) header. 814 3.1 Ethernet Protocol Assignment under the IANA OUI 816 Two-octet protocol numbers under the IANA OUI are available, as in 818 xx-xx-AA-AA-03-00-00-5E-qq-qq 820 where qq-qq is the protocol number. 822 A number of such assignments have been made out of the 2**16 protocol 823 numbers available from 00-00-5E-00-00 to 00-00-5E-FF-FF (see [IANA]). 824 The extreme values of this range, 00-00-5E-00-00 and 00-00-5E-FF-FF, 825 are reserved and require IESG Ratification for assignment (see 826 Section 5.1). New assignments of SNAP SAP protocol (qq-qq) numbers 827 under the IANA OUI must meet the following requirements: 829 o the assignment must be for standards use (either for an IETF 830 Standard or other standard related to IETF work), 832 o it must be documented in an Internet-Draft or RFC, and 834 o such protocol numbers are not to be assigned for any protocol 835 that has an Ethertype (because that can be expressed by putting 836 an all-zeros "OUI" before the Ethertype as described above). 838 In addition, the Expert Review (or IESG Ratification for the two 839 reserved values) must be obtained using the procedure specified in 840 Section 5.1. 842 3.2 Documentation Protocol Number 844 0x0042 is a protocol number under the IANA OUI (that is, 845 00-00-5E-00-42) to be used as an example for documentation purposes. 847 4. Other OUI-Based Parameters 849 Some IEEE 802 and other protocols provide for parameters based on an 850 OUI beyond those discussed above. Such parameters most commonly 851 consist of an OUI plus one octet of additional value. They are 852 usually called "vendor specific" parameters, although "organization 853 specific" might be more accurate. They would look like 855 yy-yy-yy-zz 857 where yy-yy-yy is the OUI and zz is the additional specifier. An 858 example is the Cipher Suite Selector in IEEE [802.11]. 860 Values may be assigned under the IANA OUI for such other OUI-based 861 parameter usage by Expert Review except that, for each use, the 862 additional specifier values consisting of all zero bits and all one 863 bits (0x00 (00-00-5E-00) and 0xFF (00-00-5E-FF) for a one-octet 864 specifier) are reserved and require IESG Ratification (see Section 865 5.1) for assignment; also, the additional specifier value 0x42 866 (00-00-5E-42) is assigned for use as an example in documentation. 868 Assignments of such other IANA OUI-based parameters must be for 869 standards use (either for an IETF Standard or other standard related 870 to IETF work) and be documented in an Internet-Draft or RFC. The 871 first time a value is assigned for a particular parameter of this 872 type, an IANA registry will be created to contain that assignment and 873 any subsequent assignments of values for that parameter under the 874 IANA OUI. The Expert will specify the name of the registry. 876 If different policies from those above are required for such a 877 parameter, a BCP or Standards Track RFC must be adopted to update 878 this BCP and specify the new policy and parameter. 880 4.1 LLDP IETF Vendor-Specific TLV Type 882 An example of such an "other IANA OUI based parameter" is specified 883 in [RFC8520]. This provides for a "vendor based" TLV type for 884 announcing a Manufacturer Usage Description (MUD) Uniform Resource 885 Locator (URL) in the IEEE Link Local Discover Protocol (LLDP 886 [802.1AB]). (See also Section 5.7.) 888 5. IANA Considerations 890 This document concerns IANA considerations for the assignment of 891 Ethernet parameters in connection with the IANA OUI and related 892 matters. 894 NOTE: The "IETF OUI Ethernet Numbers" IANA web page is for 895 registries of numbers assigned under the IETF OUI while the "IEEE 896 802 Numbers" IANA web page has Informational lists of numbers 897 assigned by the IEEE Registration Authority. 899 This document does not create any new IANA registries. 901 The MAC address values assigned for documentation and the protocol 902 number for documentation were both assigned by [RFC7042]. 904 No existing assignment is changed by this document. 906 5.1 Expert Review and IESG Ratification 908 This section specifies the procedure for Expert Review and IESG 909 Ratification of MAC, protocol, and other IANA OUI-based identifiers. 910 The Expert(s) referred to in this document shall consist of one or 911 more persons appointed by and serving at the pleasure of the IESG. 913 The procedure described for Expert Review assignments in this 914 document is fully consistent with the IANA Expert Review policy 915 described in [RFC8126]. 917 While finite, the universe of code points from which Expert-judged 918 assignments will be made is felt to be large enough that the 919 requirements given in this document and the Experts' good judgment 920 are sufficient guidance. The idea is for the Expert to provide a 921 light sanity check for small assignments of EUI identifiers, with 922 increased scrutiny by the Expert for medium-sized assignments of EUI 923 identifiers and assignments of protocol identifiers and other IANA 924 OUI-based parameters. However, it can make sense to assign very 925 large portions of the MAC identifier code point space. (Note that 926 existing assignments include one for 1/2 of the entire multicast IANA 927 EUI-48 code point space and one for 1/16 of that multicast code point 928 space.) In those cases, and in cases of the assignment of "reserved" 929 values, IESG Ratification of an Expert Review approval recommendation 930 is required as described below. The procedure is as follows: 932 The applicant always completes the appropriate template from 933 Appendix A below and sends it to IANA . 935 IANA always sends the template to an appointed Expert. If the 936 Expert recuses themselves or is non-responsive, IANA may choose 937 an alternative appointed Expert or, if none is available, will 938 contact the IESG. 940 In all cases, if IANA receives a disapproval from an Expert 941 selected to review an application template, the application 942 will be denied. The Expert should provide a reason for refusal 943 which IANA will communicate back to the applicant. 945 If the assignment is based on Expert Review: 947 If IANA receives approval and code points are available, 948 IANA will make the requested assignment. 950 If the assignment is based on IESG Ratification: 952 The procedure starts with the first steps above for Expert 953 Review. If the Expert disapproves the application, they 954 simply inform IANA; however, if the Expert believes the 955 application should be approved, or is uncertain and believes 956 that the circumstances warrant the attention of the IESG, 957 the Expert will inform IANA about their advice, and IANA 958 will forward the application, together with the reasons 959 provided by the Expert for approval or uncertainty, to the 960 IESG. The IESG must decide whether the assignment will be 961 granted. This can be accomplished by a management item in 962 an IESG telechat as is done for other types of requests. If 963 the IESG decides not to ratify a favorable opinion by the 964 Expert or decides against an application where the Expert is 965 uncertain, the application is denied; otherwise, it is 966 granted. The IESG will communicate its decision to the 967 Expert and to IANA. In case of refusal, the IESG should 968 provide a reason which IANA will communicate to the 969 applicant. 971 5.2 IANA Web Page Changes 973 As this document replaces [RFC7042], references to [RFC7042] in IANA 974 registries on both the IANA IEEE 802 Numbers web page and the IANA 975 IETF OUI Ethernet Number web page will be replaced by references to 976 [this document]. Other IANA web page references to [RFC7042] are not 977 changed. 979 For clarity and parallelism with the IANA "IEEE 802 Numbers" web 980 page, the IANA "Ethernet Numbers" web page is re-named the "IETF OUI 981 Ethernet Numbers" web page. 983 5.3 MAC Address AFNs and RRTYPEs 985 IANA has assigned Address Family Numbers (AFNs) for MAC addresses as 986 follows: 988 AFN Decimal Hex Reference 989 ---------- ------- ------ --------- 990 48-bit MAC 16389 0x4005 [RFC7042] 991 64-bit MAC 16390 0x4006 [RFC7042] 992 24-bit OUI 16391 0x4007 [RFC7961] 994 MAC/24 16392 0x4008 [RFC7961] 995 Lower 24 bits of a 48-bit MAC address 997 MAC/40 16393 0x4009 [RFC7961] 998 Lower 40 bits of a 64-bit MAC address 1000 IANA has assigned DNS RRTYPEs [RFC6895] for MAC addresses as follows: 1002 RRTYPE Code 1003 Data Mnemonic Decimal Hex Reference 1004 ---------- -------- ------- ------ ----------- 1005 48-bit MAC EUI48 108 0x006C [RFC7043] 1006 64-bit MAC EUI64 109 0x006D [RFC7043] 1008 5.4 Informational IANA Web Page Material 1010 IANA maintains an informational listing on its web site concerning 1011 Ethertypes, OUIs, and multicast addresses assigned under OUIs other 1012 than the IANA OUI. The title of this informational registry is "IEEE 1013 802 Numbers". IANA will update that informational registry when 1014 changes are provided or approved by the Expert(s). 1016 5.5 OUI Exhaustion 1018 When the available space for either multicast or unicast EUI-48 1019 identifiers under OUI 00-00-5E has been 90% or more exhausted, IANA 1020 should request an additional OUI from the IEEE Registration Authority 1021 for further IANA assignment. The appointed Expert(s) should monitor 1022 for this condition and notify IANA. 1024 5.6 IANA OUI MAC Address Table 1026 No changes have been made in the "IANA Unicast 48-bit MAC Addresses" 1027 and "IANA Multicast 48-bit MAC Addresses" tables except for the 1028 updates to references as specified in Section 5.2. 1030 5.7 IANA LLDP TLV Subtypes 1032 The IANA Link Layer Discovery Protpcol (LLDP) TLV Subtypes" Registry 1033 is moved from the IANA 802 Numbers web page to the IANA Ethernet 1034 Numbers web page. Three entries in the Registry are updated as 1035 follows: 1037 Value Description Reference 1038 ----- --------------------------------- --------------- 1039 0 Reserved [this document] 1040 42 Example for use in documentation [this document] 1041 255 Reserved [this document] 1043 The entries for 1 (MUD), 2-41 (unassigned), and 43-254 (unassigned) 1044 are unchanged. 1046 6. Security Considerations 1048 This document is concerned with assignment of parameters under the 1049 IANA OUI and closely related matters. It is not directly concerned 1050 with security except as follows: 1052 Confusion and conflict can be caused by the use of MAC addresses 1053 or other OUI-derived protocol parameters as examples in 1054 documentation. Examples that are "only" to be used in 1055 documentation can end up being coded and released or cause 1056 conflicts due to later real use and the possible acquisition of 1057 intellectual property rights in such addresses or parameters. The 1058 reservation herein of MAC addresses and parameters for 1059 documentation purposes will minimize such confusion and conflict. 1061 See [RFC7043] for security considerations in storing MAC addresses in 1062 the DNS. 1064 7. Acknowledgements 1066 The comments and suggestions of the following people, listed in 1067 alphabetic order, are gratefully acknowledged: 1069 This Document: 1070 TBD 1072 RFC 7042 (which was obsoleted by this document): 1073 David Black, Adrian Farrel, Bob Grow, Joel Jaeggli, Pearl 1074 Liang, Glenn Parsons, Pete Resnick, and Dan Romascanu. 1076 Normative References 1078 [802_O&A] - "IEEE Standard for Local and Metropolitan Area Networks: 1079 Overview and Architecture", IEEE Std 802-2014, 12 June 2014. 1081 "Standard for Local and Metropolitan Area Networks: Overview 1082 and Architecture - Draft Amendment: Local Medium Access Control 1083 (MAC) Address Usage", IEEE 802c, Draft 2.2, April 2017. 1085 [RFC8126] - Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1086 Writing an IANA Considerations Section in RFCs", BCP 26, RFC 1087 8126, DOI 10.17487/RFC8126, June 2017, . 1090 Informative References 1092 [802.1CQ] - IEEE 802, "Standard for Local and Metropolitan Area 1093 Networks: Multicast and Local Address Assignment", work in 1094 progress. 1096 [802.1Q] - "IEEE Standard for Local and metropolitan area networks / 1097 Media Access Control (MAC) Bridges and Virtual Bridge Local 1098 Area Networks", IEEE Std 802.1Q-2011, 31 August 2011. 1100 [802.3] - "IEEE Standard for Ethernet", IEEE Std 802.3-2012, 28 1101 December 2012. 1103 [802.11] - "IEEE Standard for Information technology / 1104 Telecommunications and information exchange between systems / 1105 Local and metropolitan area networks / Specific requirements / 1106 Part 11: Wireless LAN Medium Access Control (MAC) and Physical 1107 Layer (PHY) Specifications", IEEE Std 802.11-2012, 29 March 1108 2012. 1110 [EUI-64] - IEEE Registration Authority, "Guidelines for 64-bit Global 1111 Identifier (EUI-64(TM))", , November 2012. 1114 [IANA] - Internet Assigned Numbers Authority, . 1116 [IEEE802] - IEEE 802 LAN/MAN Standards Committee, 1117 . 1119 [IEEEtutorial] - IEEE, "Guidelines for Use of Extended Unique 1120 Identifier (EUI), Organizationally Unique Identifier (OUI), and 1121 Company ID (CID)", 1122 , 3 August 1124 2017. 1126 [InfiniBand] - InfiniBand Trade Association, "InfiniBand Architecture 1127 Specification Volume 1", November 2007. 1129 [RAC_OUI] - Parsons, G., "OUI Registry Restructuring", 1130 draft-ieee-rac-oui-restructuring-01.txt, work in Progress, 1131 September 2013. 1133 [RFC1112] - Deering, S., "Host extensions for IP multicasting", STD 1134 5, RFC 1112, August 1989. 1136 [RFC1661] - Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", 1137 STD 51, RFC 1661, July 1994. 1139 [RFC2153] - Simpson, W., "PPP Vendor Extensions", RFC 2153, May 1997. 1141 [RFC2332] - Luciani, J., Katz, D., Piscitello, D., Cole, B., and N. 1142 Doraswamy, "NBMA Next Hop Resolution Protocol (NHRP)", RFC 1143 2332, April 1998. 1145 [RFC2464] - Crawford, M., "Transmission of IPv6 Packets over Ethernet 1146 Networks", RFC 2464, December 1998. 1148 [RFC2606] - Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS 1149 Names", BCP 32, RFC 2606, June 1999. 1151 [RFC2784] - Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 1152 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, DOI 1153 10.17487/RFC2784, March 2000, . 1156 [RFC3092] - Eastlake 3rd, D., Manros, C., and E. Raymond, "Etymology 1157 of "Foo"", RFC 3092, April 1 2001. 1159 [RFC4291] - Hinden, R. and S. Deering, "IP Version 6 Addressing 1160 Architecture", RFC 4291, February 2006. 1162 [RFC4760] - Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 1163 "Multiprotocol Extensions for BGP-4", RFC 4760, January 2007. 1165 [RFC5214] - Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 1166 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, March 1167 2008. 1169 [RFC5332] - Eckert, T., Rosen, E., Ed., Aggarwal, R., and Y. Rekhter, 1170 "MPLS Multicast Encapsulations", RFC 5332, August 2008. 1172 [RFC5737] - Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address 1173 Blocks Reserved for Documentation", RFC 5737, January 2010. 1175 [RFC5798] - Nadas, S., Ed., "Virtual Router Redundancy Protocol 1176 (VRRP) Version 3 for IPv4 and IPv6", RFC 5798, March 2010. 1178 [RFC6034] - Thaler, D., "Unicast-Prefix-Based IPv4 Multicast 1179 Addresses", RFC 6034, October 2010. 1181 [RFC6328] - Eastlake 3rd, D., "IANA Considerations for Network Layer 1182 Protocol Identifiers", BCP 164, RFC 6328, DOI 10.17487/RFC6328, 1183 July 2011, 1185 [RFC6895] - Eastlake 3rd, D., "Domain Name System (DNS) IANA 1186 Considerations", BCP 42, RFC 6895, April 2013. 1188 [RFC7042] - Eastlake 3rd, D. and J. Abley, "IANA Considerations and 1189 IETF Protocol and Documentation Usage for IEEE 802 Parameters", 1190 BCP 141, RFC 7042, DOI 10.17487/RFC7042, October 2013, 1191 . 1193 [RFC7043] - Abley, J., "Resource Records for EUI-48 and EUI-64 1194 Addresses in the DNS", RFC 7043, October 2013. 1196 [RFC7319] - Eastlake 3rd, D., "IANA Considerations for Connectivity 1197 Fault Management (CFM) Code Points", BCP 191, RFC 7319, DOI 1198 10.17487/RFC7319, July 2014, . 1201 [RFC7961] - Eastlake 3rd, D. and L. Yizhou, "Transparent 1202 Interconnection of Lots of Links (TRILL): Interface Addresses 1203 APPsub-TLV", RFC 7961, DOI 10.17487/RFC7961, August 2016, 1204 . 1206 [RFC8520] - Lear, E., Droms, R., and D. Romascanu, "Manufacturer 1207 Usage Description Specification", RFC 8520, DOI 1208 10.17487/RFC8520, March 2019, . 1211 [RFC8947] - Volz, B., Mrugalski, T., and C. Bernardos, "Link-Layer 1212 Address Assignment Mechanism for DHCPv6", RFC 8947, DOI 1213 10.17487/RFC8947, December 2020, . 1216 [RFC8948] - Bernardos, CJ. and A. Mourad, "Structured Local Address 1217 Plan (SLAP) Quadrant Selection Option for DHCPv6", RFC 8948, 1218 DOI 10.17487/RFC8948, December 2020, . 1221 Appendix A. Templates 1223 This appendix provides the specific templates for IANA assignments of 1224 parameters. Explanatory words in parentheses in the templates below 1225 may be deleted in a completed template as submitted to IANA. 1227 A.1 EUI-48/EUI-64 Identifier or Identifier Block Template 1229 Applicant Name: 1231 Applicant Email: 1233 Applicant Telephone: (starting with country code) 1235 Use Name: (brief name of Parameter use such as "Foo Protocol" 1236 [RFC3092]) 1238 Document: (ID or RFC specifying use to which the identifier or block 1239 of identifiers will be put.) 1241 Specify whether this is an application for EUI-48 or EUI-64 1242 identifiers: 1244 Size of Block requested: (must be a power-of-two-sized block, can be 1245 a block of size one (2**0)) 1247 Specify multicast, unicast, or both: 1249 A.2 IANA OUI-Based Protocol Number Template 1251 Applicant Name: 1253 Applicant Email: 1255 Applicant Telephone: (starting with country code) 1257 Use Name: (brief name of use of code point such as "Foo Protocol") 1259 Document: (ID or RFC specifying use to which the protocol identifier 1260 will be put.) 1262 Note: (any additional note) 1264 A.3 Other IANA OUI-Based Parameter Template 1266 Applicant Name: 1268 Applicant Email: 1270 Applicant Telephone: (starting with country code) 1272 Protocol where the OUI-Based Parameter for which a value is being 1273 requested appears: (such as: Cipher Suite selection in IEEE 802.11) 1275 Use Name: (brief name of use of code point to be assigned, such as 1276 "Foo Cipher Suite" [RFC3092]) 1278 Document: (ID or RFC specifying use to which the other IANA OUI-based 1279 parameter value will be put.) 1281 Note: (any additional note) 1283 Appendix B. Ethertypes 1285 This appendix provides a copy of the IESG Statement issued in October 1286 2012 on obtaining new IETF Ethertypes in Section B.1. Note that there 1287 is an informational list of some important Ethertypes specified for 1288 IETF protocols or by IEEE 802 available on the IANA web site, 1289 currently at [IANA]. The IEEE Registration Authority page of 1290 Ethertypes, http://standards.ieee.org/regauth/ethertype/eth.txt, may 1291 also be useful. See Section 3 above. 1293 B.1 IESG Statement on Ethertypes 1295 From: IESG Date: 25 October 2012 1297 The IEEE Registration Authority (IEEE RA) assigns Ethertypes with 1298 oversight from the IEEE Registration Authority Committee (IEEE RAC). 1300 (See http://standards.ieee.org/develop/regauth/ethertype/.) Some IETF 1301 protocol specifications make use of Ethertypes. All Ethertype 1302 requests are subject to review by a consultant to the IEEE RA 1303 followed by IEEE RAC confirmation. 1305 Since Ethertypes are a fairly scarce resource, the IEEE RAC has let 1306 us know that they will not assign a new Ethertype to a new IETF 1307 protocol specification until the IESG has approved the protocol 1308 specification for publication as an RFC. In exceptional cases, the 1309 IEEE RA is willing to consider "early allocation" of an Ethertype for 1310 an IETF protocol that is still under development as long as the 1311 request comes from and has been vetted by the IESG. 1313 To let the IEEE RAC know that the IESG has approved the request for 1314 an Ethernet assignment for an IETF protocol, all future requests for 1315 assignment of Ethertypes for IETF protocols will be made by the IESG. 1317 Note that playpen Ethertypes have been assigned in IEEE 802 [1] for 1318 use during protocol development and experimentation. 1320 [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001). IEEE 1321 standard for Local and Metropolitan Area Networks: Overview and 1322 Architecture -- Amendment 1: Ethertypes for Prototype and Vendor- 1323 Specific Protocol Development. 1325 Authors' Addresses 1327 Donald E. Eastlake 3rd 1328 Futurewei Technologies 1329 2386 Panoramic Circle 1330 Apopka, FL 32703 1331 USA 1333 Phone: +1-508-634-2066 1334 EMail: d3e3e3@gmail.com 1336 Joe Abley 1337 Hopcount Limited 1338 186 Albert Street, Suite 103 1339 London, ON N6A 1M1 1340 Canada 1342 Phone: +1 519 670 9327 1343 EMail: jabley@hopcount.ca 1345 Copyright, Disclaimer, and Additional IPR Provisions 1347 Copyright (c) 2021 IETF Trust and the persons identified as the 1348 document authors. All rights reserved. 1350 This document is subject to BCP 78 and the IETF Trust's Legal 1351 Provisions Relating to IETF Documents 1352 (http://trustee.ietf.org/license-info) in effect on the date of 1353 publication of this document. Please review these documents 1354 carefully, as they describe your rights and restrictions with respect 1355 to this document. Code Components extracted from this document must 1356 include Simplified BSD License text as described in Section 4.e of 1357 the Trust Legal Provisions and are provided without warranty as 1358 described in the Simplified BSD License. This Internet-Draft is 1359 submitted in full conformance with the provisions of BCP 78 and BCP 1360 79.