idnits 2.17.1 draft-eastlake-rfc7042bis-04.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 (March 16, 2021) is 1130 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) -- Obsolete informational reference (is this intentional?): RFC 7042 (Obsoleted by RFC 9542) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 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: September 15, 2021 March 16, 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 http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft 40 Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 Table of Contents 45 1. Introduction............................................3 46 1.1 Notations Used in This Document........................3 47 1.2 Changes from RFC 7042..................................4 48 1.3 The IEEE Registration Authority........................5 49 1.4 The IANA Organizationally Unique Identifier............5 50 1.5 CFM Code Points........................................5 51 2. Ethernet Identifier Parameters..........................6 52 2.1 48-Bit MAC Identifiers, OUIs, and Other Prefixes.......6 53 2.1.1 Special First Octet Bits.............................7 54 2.1.2 OUIs and CIDs........................................8 55 2.1.3 EUI-48 Assignments under the IANA OUI................9 56 2.1.4 EUI-48 Documentation Values.........................10 57 2.1.5 EUI-48 IANA Assignment Considerations...............10 58 2.2 64-Bit MAC Identifiers................................11 59 2.2.1. IPv6 Use of Modified EUI-64 Identifiers............11 60 2.2.2 EUI-64 IANA Assignment Considerations...............13 61 2.2.3 EUI-64 Documentation Values.........................14 62 2.3 Other 48-bit MAC Identifiers Used by the IETF.........15 63 2.3.1 Identifiers Prefixed '33-33'........................15 64 2.3.2 The 'CF Series'.....................................15 65 2.3.2.1 Changes to RFC 2153...............................16 66 3. Ethernet Protocol Parameters...........................17 67 3.1 Ethernet Protocol Assignment under the IANA OUI.......18 68 3.2 Documentation Protocol Number.........................19 69 4. Other OUI-Based Parameters............................20 70 5. IANA Considerations...................................21 71 5.1 Expert Review and IESG Ratification...................21 72 5.2 MAC Address AFNs and RRTYPEs..........................22 73 5.3 Informational IANA Web Page Material..................23 74 5.4 OUI Exhaustion........................................23 75 5.5 IANA OUI MAC Address Table............................23 76 5.6 SNAP Protocol Number Table and Assignment.............24 78 6. Security Considerations................................25 79 7. Acknowledgements.......................................25 81 Normative References......................................26 82 Informative References....................................26 84 Appendix A. Templates.....................................29 85 A.1 EUI-48/EUI-64 Identifier or Identifier Block Template.29 86 A.2 IANA OUI-Based Protocol Number Template...............29 87 A.3 Other IANA OUI-Based Parameter Template...............30 88 Appendix B. Ethertypes...................................31 89 B.1. Some Ethertypes Specified by the IETF...............31 90 B.2. Some IEEE 802 Ethertypes............................31 92 Authors' Addresses........................................33 94 1. Introduction 96 Some IETF protocols use Ethernet or other IEEE 802-related 97 communication frame formats and parameters [IEEE802]. These include 98 MAC (Media Access Control) addresses and protocol identifiers. 100 This document specifies IANA considerations for the assignment of 101 code points under the IANA OUI including MAC addresses and protocol 102 identifiers. It also discusses several other uses by the IETF of 103 IEEE 802 code points, including IEEE 802 Connectivity Fault 104 Management (CFM) code points [RFC7319], and provides some values for 105 use in documentation. As noted in [RFC2606] and [RFC5737], the use 106 of designated code values reserved for documentation and examples 107 reduces the likelihood of conflicts and confusion arising from their 108 duplication of code points assigned for some deployed use. 110 [RFC8126] is incorporated herein except where there are contrary 111 provisions in this document. In this document, "IESG Ratification" 112 is used in some cases. IESG Ratification is specified in Section 5.1. 113 It is not the same as "IESG Approval" in [RFC8126]. 115 1.1 Notations Used in This Document 117 This document uses hexadecimal notation. Each octet (that is, 8-bit 118 byte) is represented by two hexadecimal digits giving the value of 119 the octet as an unsigned integer. Successive octets are separated by 120 a hyphen. This document consistently uses IETF ("network") bit 121 ordering although the physical order of bit transmission within an 122 octet on an IEEE [802.3] link is from the lowest order bit to the 123 highest order bit (i.e., the reverse of the IETF's ordering). 125 In this document: 127 "AFN" Address Family Number [RFC4760]. 129 "CFM" Connectivity Fault Managment [RFC7319]. 131 "CID" Company Identifier. 133 "EUI" Extended Unique Identifier. 135 "IAB" Individual Address Block, not Internet Architecture Board. 137 "IEEE" Institute for Electrical and Electronics Engineers 138 (www.ieee.org). 140 "IEEE-SA" IEEE Standards Association (standards.ieee.org). 142 "MA-L" MAC Address Block Large, commonly referred to as an OUI. 144 "MA-M" MAC Address Block Medium. 146 "MA-S" MAC Address Block Small. 148 "MAC" Media Access Control, not for Message Authentication Code. 150 "MAC-48" A 48-bit MAC address. This term is obsolete. If globally 151 unique, use EUI-48. 153 "OUI" Organizationally Unique Identifier. An OUI is now officially 154 calle "MA-L" by the IEEE. 156 "RRTYPE" A DNS Resource Record type [RFC6895]. 158 "SLAP" IEEE 802 Structured Local Address Plan [802_O&A]. 160 "TLV" Type, Length, Value. 162 "**" This symbol indicates exponentiation. For example, 2**24 is 163 two to the twenty-fourth power. 165 1.2 Changes from RFC 7042 167 This document obsoletes [RFC7042] and makes the changes listed below. 168 However, the completed application template based upon which an IANA 169 OUI-based protocol number value was assigned for document use remains 170 that in Appendix C of RFC 7042. 172 o Adds information on MA-M (28-bit) and MA-S (36-bit) EUI prefixes 173 that the IEEE Registration Authority assignes. 175 o Adds information on the restructuring of the "local" MAC address 176 space into four quadrants under the Structured Local Address Plan 177 (SLAP [802_O&A]). 179 o Mentions that IEEE 802 CFM Codepoints that have been allocated to 180 the IETF (see Section 1.5). 182 o Clarifies minor details in Section 5.1 on Expert Review and IESG 183 Ratification. 185 1.3 The IEEE Registration Authority 187 Originally the responsibility of Xerox Corporation, the registration 188 authority for Ethernet parameters is now the IEEE Registration 189 Authority, available on the web at: 191 http://standards.ieee.org/regauth/ 193 The IEEE Registration Authority operates under the direction of the 194 IEEE-SA Board of Governors. Anyone may apply to that Authority for 195 parameter assignments. The IEEE Registration Authority may impose 196 fees or other requirements but commonly waives fees for applications 197 from standards development organizations. 199 Lists of some assignments and their holders are downloadable from the 200 IEEE Registration Authority site. 202 1.4 The IANA Organizationally Unique Identifier 204 The Organizationally Unique Identifier (OUI) 00-00-5E has been 205 assigned to IANA by the IEEE Registration Authority. 207 There is no OUI value reserved at this time for documentation, but 208 there are documentation code points under the IANA OUI specified 209 below. 211 1.5 CFM Code Points 213 The IEEE has allocated two blocks of 802 Connectivity Fault 214 Management (CFM) code points to the IETF, one for CFM OpCodes and one 215 for CFM TLV Types. Further information, including IANA 216 considerations for assignment of values from these block for IETF 217 use, are given in [RFC7319]. This document does not further discuss 218 these blocks of codepoints. 220 2. Ethernet Identifier Parameters 222 Section 2.1 discusses 48-bit MAC identifiers, their relationship to 223 OUIs and other prefixes, and assignment under the IANA OUI. Section 224 2.2 extends this to 64-bit identifiers. Section 2.3 discusses other 225 IETF MAC identifier use not under the IANA OUI. ([RAC_OUI] indicates 226 that the IEEE Registration Authority Committee was at one time 227 exploring the feasibility of defining 128-bit identifiers. [RAC_OUI] 228 is an expired draft that also provides additional historic 229 information on [IEEE802] registries.) 231 2.1 48-Bit MAC Identifiers, OUIs, and Other Prefixes 233 48-bit MAC "addresses" are the most commonly used Ethernet interface 234 identifiers. Those that are globally unique are also called EUI-48 235 identifiers (Extended Unique Identifier 48). An EUI-48 is structured 236 into an initial prefix assigned by the IEEE Registration Authority 237 and additional bits assigned by the prefix owner. Currently there 238 are three lengths of prefixes assigned as shown in the table below; 239 however, some prefix bits have special meaning as shown in Figure 1. 241 Prefix Length Owner Supplied Bits 242 in bits Name for EUI-48 243 ------------- ------ -------------------- 244 24 MAC-L (OUI) 24 245 28 MAC-M 20 246 36 MAC-S 12 248 Actually, the bottom four bits, as shown below, of the first octet of 249 the 3-octet 48-bit MAC have speical meaning and are referred to below 250 as the M, X, Y, and Z bits. 252 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 253 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 254 | . . . . Z Y X M| . . . . . . . .| octets 0&1 255 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 256 | . . . . . . . .| . . . . . . . .| octets 2&3 257 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 258 | . . . . . . . .| . . . . . . . .| octets 4&5 259 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 261 Figure 1. 48-bit MAC Address Structure 263 A 3-octet OUI (Organizationally Unique Identifier) is followed by an 264 additional 3 octets assigned by the OUI holder or there may be a 265 larger initial prefix assigned to an organization and a shorter 266 sequence of additional bits so as to add up to 48 bits in total. For 267 example, the IEEE has assigned IABs (Individual Address Blocks), 268 where the first 4 1/2 octets (36 bits) are assigned, giving the 269 holder of the IAB 1 1/2 octets (12 bits) they can control; however, 270 IABs have become historic, and a wider range of prefix lengths are 271 available [RAC_OUI]. 273 The IEEE describes its assignment procedures and policies for IEEE 274 802-related identifiers in [802_O&A]. An IEEE tutorial on EUIs, OUIs, 275 and CIDs is available at [IEEEtutorial]. 277 2.1.1 Special First Octet Bits 279 Four bits within the initial octet of an IEEE MAC interface 280 identifier, such as an EUI-48, have special significance [802_O&A] as 281 follows: 283 M bit --- This bit always indicates a group address and is 284 frequently referred to as the group bit. If it is zero, 285 the MAC address is unicast. If it is a one, the address is 286 multicast or broadcast. This meaning is independent of the 287 values of the X, Y, and Z bits. 289 X bit --- This bit was previously called the "local" bit. If it is 290 zero, the MAC address is a global address under the 291 control of the owner of the IEEE assigned prefix. 292 Previously, if it was a one, the MAC address was 293 considered "local" and under the assignment and control of 294 the local network operator (but see Section 2.3). Now, if 295 it is a one, the nature of the MAC address is optionally 296 determined by the Y and Z bits under the IEEE 802 297 Structured Local Address Plan (SLAP) as described below. 299 Y&Z bits - These two bits have no special meaning if the X bit is 300 zero. If the X bit is one, these two bits divide the 301 formerly uniform "local" MAC address space into four 302 quadrants, as follows. These quadrants are further 303 described below. 305 Y bit Z bit Quadrant 306 ----- ----- ----------- 307 0 0 Administratively Assigned 308 0 1 Extended Local 309 1 0 Reserved 310 1 1 Standard Assigned 312 While a local network administrator can assign any addresses with the 313 X bit a one, the optional SLAP characterizes the four quadrants of 314 the "local" address space using the Y and Z bits as follows: 316 Administratively Assigned - MAC addresses in this quadrant are 317 called Administratively Assigned Identifiers. This is 318 intended for arbitrary local assignment such as random 319 assignment; however, see Section 2.3.1. 321 Extended Local - MAC addresses in this quadrant are called 322 Extended Local Identifiers. These addresses are not 323 actually "local" under SLAP. They are available to the 324 organization that has been assigned the CID (see Section 325 xxx) specifying the other 20 bits of the 24 bit prefix 326 with X, Y, Z bits 1, 0, 1 respectively. 328 Reserved - MAC addresses in this quadrant are reserved for future 329 use under the SLAP. Until such future use, they could be 330 locally assigned as Administratively Assigned Identifiers 331 are assigned but there is a danger that future SLAP use 332 would conflict with such local assignments. 334 Standard Assigned - MAC addresses in this quadrant are known as 335 Standard Assigned Identifiers. It is intended that such 336 addresses be assigned and possibly revoked through a 337 local protocol. There is work in the IEEE [802.1CQ] and 338 the IETF [RFC8947] [RFC8948] related to such protocols. 340 2.1.2 OUIs and CIDs 342 OUI, MAC-M, and MAC-S MAC prefixes are assigned with the Local bit 343 zero and the Group bit unspecified. Multicast identifiers may be 344 constructed by turning on the Group bit, and unicast identifiers may 345 be constructed by leaving the Group bit zero. 347 The Local bit is zero for globally unique EUI-48 identifiers assigned 348 by the owner of an OUI or owner of a longer prefix. If the Local bit 349 is a one, the identifier has been considered by IEEE 802 to be a 350 local identifier under the control of the local network 351 administrator; however, there are now recommendations on 352 optionalmanagement of the local address space as discussed in Section 353 2.1.1. If the Local bit is on, the holder of an OUI has no special 354 authority over MAC identifiers whose first 3 octets correspond to 355 their OUI or the beginning of their longer prefix. 357 An AFN and a DNS RRTYPE have been assigned for 48-bit MAC addresses 358 (see Section 5.2). 360 2.1.3 EUI-48 Assignments under the IANA OUI 362 The OUI 00-00-5E has been assigned to IANA as stated in Section 1.4 363 above. This includes 2**24 EUI-48 multicast identifiers from 364 01-00-5E-00-00-00 to 01-00-5E-FF-FF-FF and 2**24 EUI-48 unicast 365 identifiers from 00-00-5E-00-00-00 to 00-00-5E-FF-FF-FF. 367 Of these EUI-48 identifiers, the sub-blocks reserved or thus far 368 assigned by IANA for purposes of documentation are as follows: 370 Unicast, all blocks of 2**8 addresses thus far: 372 00-00-5E-00-00-00 through 00-00-5E-00-00-FF: reserved and require 373 IESG Ratification for assignment (see Section 5.1). 375 00-00-5E-00-01-00 through 00-00-5E-00-01-FF: assigned for the 376 Virtual Router Redundancy Protocol (VRRP) [RFC5798]. 378 00-00-5E-00-02-00 through 00-00-5E-00-02-FF: assigned for the IPv6 379 Virtual Router Redundancy Protocol (IPv6 VRRP) [RFC5798]. 381 00-00-5E-00-52-00 through 00-00-5E-00-52-FF: used for very small 382 assignments. Currently, 4 out of these 256 values have been 383 assigned. 385 00-00-5E-00-53-00 through 00-00-5E-00-53-FF: assigned for use in 386 documentation. 388 00-00-5E-90-01-00 through 00-00-5E-90-01-FF: used for very small 389 assignments that need paralesl unicast and multicast MAC 390 addresses. Currently 1 out of these 256 values has been 391 assigned. 393 Multicast: 395 01-00-5E-00-00-00 through 01-00-5E-7F-FF-FF: 2**23 addresses 396 assigned for IPv4 multicast [RFC1112]. 398 01-00-5E-80-00-00 through 01-00-5E-8F-FF-FF: 2**20 addresses 399 assigned for MPLS multicast [RFC5332]. 401 01-00-5E-90-00-00 through 01-00-5E-90-00-FF: 2**8 addresses being 402 used for very small assignments. Currently, 4 out of these 256 403 values have been assigned. 405 01-00-5E-90-10-00 through 01-00-5E-90-10-FF: 2**8 addresses for 406 use in documentation. 408 01-00-5E-90-01-00 through 01-00-5E-90-01-FF: used for very small 409 assignments that need paralesl unicast and multicast MAC 410 addresses. Currently 1 out of these 256 values has been 411 assigned. 413 For more detailed and up-to-date information, see the "Ethernet 414 Numbers" registry at http://www.iana.org. 416 2.1.4 EUI-48 Documentation Values 418 The following values have been assigned for use in documentation: 420 00-00-5E-00-53-00 through 00-00-5E-00-53-FF for unicast and 422 01-00-5E-90-10-00 through 01-00-5E-90-10-FF for multicast. 424 2.1.5 EUI-48 IANA Assignment Considerations 426 EUI-48 assignments under the current or a future IANA OUI (see 427 Section 5.4) must meet the following requirements: 429 o must be for standards purposes (either for an IETF Standard or 430 other standard related to IETF work), 432 o must be for a power-of-two size block of identifiers starting 433 at a boundary that is an equal or greater power of two, 434 including the assignment of one (2**0) identifier, 436 o must not be used to evade the requirement for vendors to obtain 437 their own block of identifiers from the IEEE, and 439 o must be documented in an Internet-Draft or RFC. 441 In addition, approval must be obtained as follows (see the procedure 442 in Section 5.1): 444 Small to medium assignments of a block of 1, 2, 4, ..., 32768, 445 65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI-48 identifiers 446 require Expert Review (see Section 5.1). 448 Large assignments of 131072 (2**17) or more EUI-48 identifiers 449 require IESG Ratification (see Section 5.1). 451 2.2 64-Bit MAC Identifiers 453 IEEE also defines a system of 64-bit MAC identifiers including 454 EUI-64s. EUI-64 identifiers are currently used as follows: 456 o In a modified form to construct some IPv6 interface identifiers 457 as described in Section 2.2.1 459 o In IEEE Std 1394 (also known as FireWire and i.Link) 461 o In IEEE Std 802.15.4 (also known as ZigBee) 463 o In [InfiniBand] 465 Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) OUI, or a 466 shorter extension to longer assigned prefixes [RAC_OUI] so as to 467 total 64 bits, produces an EUI-64 identifier under that OUI or longer 468 prefix. As with EUI-48 identifiers, the first octet has the same 469 Group and Local bits. 471 An AFN and a DNS RRTYPE have been assigned for 64-bit MAC addresses 472 (see Section 5.2). 474 The discussion below is almost entirely in terms of the "Modified" 475 form of EUI-64 identifiers; however, anyone assigned such an 476 identifier can also use the unmodified form as a MAC identifier on 477 any link that uses such 64-bit identifiers for interfaces. 479 2.2.1. IPv6 Use of Modified EUI-64 Identifiers 481 MAC-64 identifiers are used to form the lower 64 bits of some IPv6 482 addresses (Section 2.5.1 and Appendix A of [RFC4291] and Appendix A 483 of [RFC5214]). When so used, the MAC-64 is modified by inverting the 484 Local/Global bit to form an IETF "Modified EUI-64 identifier". Below 485 is an illustration of a Modified EUI-64 unicast identifier under the 486 IANA OUI, where aa-bb-cc-dd-ee is the extension. 488 02-00-5E-aa-bb-cc-dd-ee 490 The first octet is shown as 02 rather than 00 because, in Modified 491 EUI-64 identifiers, the sense of the Local/Global bit is inverted 492 compared with EUI-48 identifiers. It is the globally unique values 493 (universal scope) that have the 02 bit on in the first octet, while 494 those with this bit off are locally assigned and out of scope for 495 global assignment. 497 The Local/Global bit was inverted to make it easier for network 498 operators to type in local-scope identifiers. Thus, such Modified 499 EUI-64 identifiers as 1, 2, etc. (ignoring leading zeros) are local. 500 Without the modification, they would have to be 501 02-00-00-00-00-00-00-01, 02-00-00-00-00-00-00-02, etc. to be local. 503 As with 48-bit MAC identifiers, the 01 bit on in the first octet 504 indicates a group identifier. 506 When the first two octets of the extension of a Modified EUI-64 507 identifier are FF-FE, the remainder of the extension is a 24-bit 508 value as assigned by the OUI owner for an EUI-48. For example: 510 02-00-5E-FF-FE-yy-yy-yy 511 or 512 03-00-5E-FF-FE-yy-yy-yy 514 where yy-yy-yy is the portion (of an EUI-48 global unicast or 515 multicast identifier) that is assigned by the OUI owner (IANA in this 516 case). Thus, any holder of one or more EUI-48 identifiers under the 517 IANA OUI also has an equal number of Modified EUI-64 identifiers that 518 can be formed by inserting FF-FE in the middle of their EUI-48 519 identifiers and inverting the Local/Global bit. 521 (Note: [EUI-64] defines FF-FF as the bits to be inserted to create 522 an IEEE EUI-64 identifier from a EUI-48 identifier. That document 523 says the FF-FE value is used when starting with an EUI-48 524 identifier. The IETF uses only FF-FE to create Modified EUI-64 525 identifiers from 48-bit Ethernet station identifiers regardless of 526 whether they are EUI-48 or 48-bit local MAC identifiers. EUI-48 527 and local 48-bit MAC identifiers are syntactically equivalent, and 528 this doesn't cause any problems in practice.) 530 In addition, certain Modified EUI-64 identifiers under the IANA OUI 531 are reserved for holders of IPv4 addresses as follows: 533 02-00-5E-FE-xx-xx-xx-xx 535 where xx-xx-xx-xx is a 32-bit IPv4 address. The owner of an IPv4 536 address has both the unicast- and multicast-derived EUI-64 address. 537 Modified EUI-64 identifiers from 539 02-00-5E-FE-F0-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF 541 are effectively reserved pending the specification of IPv4 Class E 542 addresses. However, for Modified EUI-64 identifiers based on an IPv4 543 address, the Local/Global bit should be set to correspond to whether 544 the IPv4 address is local or global. (Keep in mind that the sense of 545 the Modified EUI-64 identifier Local/Global bit is reversed from that 546 in (unmodified) MAC-64 identifiers.) 548 2.2.2 EUI-64 IANA Assignment Considerations 550 The following table shows which Modified EUI-64 identifiers under the 551 IANA OUI are reserved, assigned, or available as indicated. As noted 552 above, the corresponding MAC addresses can be determined by 553 complementing the 02 bit in the first octet. In all cases, the 554 corresponding multicast 64-bit MAC addresses formed by complementing 555 the 01 bit in the first octet have the same status as the modified 556 64-bit unicast address blocks listed below. 558 02-00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF reserved 560 02-00-5E-10-00-00-00-00 to 02-00-5E-10-00-00-00-FF assigned for 561 documentation use 563 02-00-5E-10-00-00-01-00 to 02-00-5E-EF-FF-FF-FF-FF available for 564 assignment 566 02-00-5E-F0-00-00-00-00 to 02-00-5E-FD-FF-FF-FF-FF reserved 568 02-00-5E-FE-00-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF assigned to 569 IPv4 address holders as described above 571 02-00-5E-FF-00-00-00-00 to 02-00-5E-FF-FD-FF-FF-FF reserved 573 02-00-5E-FF-FE-00-00-00 to 02-00-5E-FF-FE-FF-FF-FF assigned for 574 holders of EUI-48 identifiers under the IANA OUI as described 575 above 577 02-00-5E-FF-FF-00-00-00 to 02-00-5E-FF-FF-FF-FF-FF reserved 579 The reserved identifiers above require IESG Ratification (see Section 580 5.1) for assignment. IANA EUI-64 identifier assignments under the 581 IANA OUI must meet the following requirements: 583 o must be for standards purposes (either for an IETF Standard or 584 other standard related to IETF work), 586 o must be for a power-of-two size block of identifiers starting 587 at a boundary that is an equal or greater power of two, 588 including the assignment of one (2**0) identifier, 590 o must not be used to evade the requirement for vendors to obtain 591 their own block of identifiers from the IEEE, and 593 o must be documented in an Internet-Draft or RFC. 595 In addition, approval must be obtained as follows (see the procedure 596 in Section 5.1): 598 Small to medium assignments of a block of 1, 2, 4, ..., 134217728, 599 268435456 (2**0, 2**1, 2**2, ..., 2**27, 2**28) EUI-64 600 identifiers require Expert Review (see Section 5.1). 602 Assignments of any size, including 536870912 (2**29) or more 603 EUI-64 identifiers, may be made with IESG Ratification (see 604 Section 5.1). 606 2.2.3 EUI-64 Documentation Values 608 The following blocks of unmodified 64-bit MAC addresses are for 609 documentation use. The IPv4-derived addresses are based on the IPv4 610 documentation addresses [RFC5737], and the MAC-derived addresses are 611 based on the EUI-48 documentation addresses above. 613 Unicast Values for Documentation Use: 615 00-00-5E-EF-10-00-00-00 to 00-00-5E-EF-10-00-00-FF general 617 00-00-5E-FE-C0-00-02-00 to 00-00-5E-FE-C0-00-02-FF and 618 00-00-5E-FE-C6-33-64-00 to 00-00-5E-FE-C6-33-64-FF and 619 00-00-5E-FE-CB-00-71-00 to 00-00-5E-FE-CB-00-71-FF IPv4 derived 621 00-00-5E-FF-FE-00-53-00 to 00-00-5E-FF-FE-00-53-FF EUI-48 derived 623 00-00-5E-FE-EA-C0-00-02 and 624 00-00-5E-FE-EA-C6-33-64 and 625 00-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 626 [RFC6034] 628 Multicast Values for Documentation Use: 630 01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general 632 01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and 633 01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and 634 01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived 636 01-00-5E-FE-EA-C0-00-02 and 637 01-00-5E-FE-EA-C6-33-64 and 638 01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 639 [RFC6034] 641 01-00-5E-FF-FE-90-10-00 to 01-00-5E-FF-FE-90-10-FF EUI-48 derived 643 2.3 Other 48-bit MAC Identifiers Used by the IETF 645 There are two other blocks of 48-bit MAC identifiers that are used by 646 the IETF as described below. 648 2.3.1 Identifiers Prefixed '33-33' 650 All 48-bit multicast MAC identifiers prefixed "33-33" (that is, the 651 2**32 multicast MAC identifiers in the range from 33-33-00-00-00-00 652 to 33-33-FF-FF-FF-FF) are used as specified in [RFC2464] for IPv6 653 multicast. In all of these identifiers, the Group bit (the bottom 654 bit of the first octet) is on, as is required to work properly with 655 existing hardware as a multicast identifier. They also have the 656 Local bit on but any ethernet using standard IPv6 multicast should 657 note that these addresses will be used for that purpose. These 658 multicast MAC addresses fall into the administratively assigned SLAP 659 quadrant (see Section 2.1.1). 661 (Historical note: It was the custom during IPv6 design to use "3" 662 for unknown or example values and 3333 Coyote Hill Road, Palo 663 Alto, California, is the address of PARC (Palo Alto Research 664 Center, formerly "Xerox PARC"). Ethernet was originally specified 665 by the Digital Equipment Corporation, Intel Corporation, and Xerox 666 Corporation. The pre-IEEE [802.3] Ethernet protocol has sometimes 667 been known as "DIX" Ethernet from the first letters of the names 668 of these companies.) 670 2.3.2 The 'CF Series' 672 The Informational [RFC2153] declared the 3-octet values from CF-00-00 673 through CF-FF-FF to be OUIs available for assignment by IANA to 674 software vendors for use in PPP [RFC1661] or for other uses where 675 vendors do not otherwise need an IEEE-assigned OUI. It should be 676 noted that, when used as 48-bit MAC prefixes, these values have all 677 of the Z, Y, X (Local), and M (Group) special bits at the bottom of 678 the first byte equal to one, while all IEEE-assigned OUIs thus far 679 have the X and M bits zero. Multicast MAC addresses constructed with 680 a "CF" series OUI would fall into the standard assigned SLAP quadrant 681 (see Section 2.1.1). The Group bit is meaningless in PPP. To quote 682 [RFC2153]: "The 'CF0000' series was arbitrarily chosen to match the 683 PPP NLPID 'CF', as a matter of mnemonic convenience." (For further 684 information on NLPIDs, see [RFC6328].) 686 CF-00-00 is reserved, and IANA lists multicast identifier 687 CF-00-00-00-00-00 as used for Ethernet loopback tests. 689 In over a decade of availability, only a handful of values in the CF 690 Series have been assigned. (See "Ethernet Numbers" 691 and "PPP Numbers" 692 ). 694 2.3.2.1 Changes to RFC 2153 696 The IANA Considerations in [RFC2153] were updated as follows by the 697 approval of RFC 5342 (no technical changes have been made): 699 o Use of these identifiers based on IANA assignment was 700 deprecated. 702 o IANA was instructed not to assign any further values in the 'CF 703 Series'. 705 3. Ethernet Protocol Parameters 707 Ethernet protocol parameters provide a means of indicating the 708 contents of a frame -- for example, that its contents are IPv4 or 709 IPv6. 711 The concept has been extended to labeling by "tags". A tag in this 712 sense is a prefix whose type is identified by an Ethertype that is 713 then followed by either another tag, an Ethertype, or an LSAP (Link- 714 Layer Service Access Point) protocol indicator for the "main" body of 715 the frame, as described below. Traditionally, in the [802_O&A] 716 world, tags are a fixed length and do not include any encoding of 717 their own length. Any device that is processing a frame cannot, in 718 general, safely process anything in the frame past an Ethertype it 719 does not understand. An example is the C-Tag (formerly the Q-Tag) 720 [802.1Q]. It provides customer VLAN and priority information for a 721 frame. 723 There are two types of protocol identifier parameters that can occur 724 in Ethernet frames after the initial MAC-48 destination and source 725 identifiers: 727 Ethertypes: These are 16-bit identifiers appearing as the initial 728 two octets after the MAC destination and source (or after a 729 tag), which, when considered as an unsigned integer, are equal 730 to or larger than 0x0600. 732 LSAPs: These are 8-bit protocol identifiers that occur in pairs 733 immediately after an initial 16-bit (two-octet) remaining frame 734 length, which is in turn after the MAC destination and source 735 (or after a tag). Such a length must, when considered as an 736 unsigned integer, be less than 0x5DC, or it could be mistaken 737 as an Ethertype. LSAPs occur in pairs where one is intended to 738 indicate the source protocol handler and one the destination 739 protocol handler; however, use cases where the two are 740 different have been relatively rare. 742 Neither Ethertypes nor LSAPs are assigned by IANA; they are assigned 743 by the IEEE Registration Authority (see Section 1.3 above and 744 Appendix B). However, both LSAPs and Ethertypes have extension 745 mechanisms so that they can be used with five-octet Ethernet protocol 746 identifiers under an OUI, including those assigned by IANA under the 747 IANA OUI. 749 When using the IEEE 802 Logical Link Control (LLC) format (Subnetwork 750 Access Protocol (SNAP)) [802_O&A] for a frame, an OUI-based protocol 751 identifier can be expressed as follows: 753 xx-xx-AA-AA-03-yy-yy-yy-zz-zz 755 where xx-xx is the frame length and, as above, must be small enough 756 not to be confused with an Ethertype; "AA" is the LSAP that indicates 757 this use and is sometimes referred to as the SNAP Service Access 758 Point (SAP); "03" is the LLC control octet indicating datagram 759 service; yy-yy-yy is an OUI; and zz-zz is a protocol number, under 760 that OUI, assigned by the OUI owner. The five-octet length for such 761 OUI-based protocol identifiers was chosen so that, with the LLC 762 control octet ("03"), the result is 16-bit aligned. 764 When using an Ethertype to indicate the main type for a frame body, 765 the special "OUI Extended Ethertype" 88-B7 is available. Using this 766 Ethertype, a frame body can begin with 768 88-B7-yy-yy-yy-zz-zz 770 where yy-yy-yy and zz-zz have the same meaning as in the SNAP format 771 described above. 773 It is also possible, within the SNAP format, to use an arbitrary 774 Ethertype. Putting the Ethertype as the zz-zz field after an all- 775 zeros OUI (00-00-00) does this. It looks like 777 xx-xx-AA-AA-03-00-00-00-zz-zz 779 where zz-zz is the Ethertype. 781 (Note that, at this point, the 802 protocol syntax facilities are 782 sufficiently powerful that they could be chained indefinitely. 783 Whether support for such chaining is generally required is not 784 clear, but [802_O&A] requires support for 786 xx-xx-AA-AA-03-00-00-00-88-B7-yy-yy-yy-zz-zz 788 although this could be more efficiently expressed by simply 789 pinching out the "00-00-00-88-B7" in the middle.) 791 As well as labeling frame contents, 802 protocol types appear within 792 NBMA (Non-Broadcast Multi-Access) Next Hop Resolution Protocol 793 [RFC2332] messages. Such messages have provisions for both two-octet 794 Ethertypes and OUI-based protocol types. 16-bit Ethertypes also occur 795 in the Generic Router Encapsulation (GRE [RFC2784]) header. 797 3.1 Ethernet Protocol Assignment under the IANA OUI 799 Two-octet protocol numbers under the IANA OUI are available, as in 801 xx-xx-AA-AA-03-00-00-5E-qq-qq 803 where qq-qq is the protocol number. 805 A number of such assignments have been made out of the 2**16 protocol 806 numbers available from 00-00-5E-00-00 to 00-00-5E-FF-FF (see [IANA]). 807 The extreme values of this range, 00-00-5E-00-00 and 00-00-5E-FF-FF, 808 are reserved and require IESG Ratification for assignment (see 809 Section 5.1). New assignments of SNAP SAP protocol (qq-qq) numbers 810 under the IANA OUI must meet the following requirements: 812 o the assignment must be for standards use (either for an IETF 813 Standard or other standard related to IETF work), 815 o it must be documented in an Internet-Draft or RFC, and 817 o such protocol numbers are not to be assigned for any protocol 818 that has an Ethertype (because that can be expressed by putting 819 an all-zeros "OUI" before the Ethertype as described above). 821 In addition, the Expert Review (or IESG Ratification for the two 822 reserved values) must be obtained using the procedure specified in 823 Section 5.1. 825 3.2 Documentation Protocol Number 827 0x0042 is a protocol number under the IANA OUI (that is, 828 00-00-5E-00-42) to be used as an example for documentation purposes. 830 4. Other OUI-Based Parameters 832 Some IEEE 802 and other protocols provide for parameters based on an 833 OUI beyond those discussed above. Such parameters most commonly 834 consist of an OUI plus one octet of additional value. They are 835 usually called "vendor specific" parameters, although "organization 836 specific" might be more accurate. They would look like 838 yy-yy-yy-zz 840 where yy-yy-yy is the OUI and zz is the additional specifier. An 841 example is the Cipher Suite Selector in IEEE [802.11]. 843 Values may be assigned under the IANA OUI for such other OUI-based 844 parameter usage by Expert Review except that, for each use, the 845 additional specifier values consisting of all zero bits and all one 846 bits (0x00 (00-00-5E-00) and 0xFF (00-00-5E-FF) for a one-octet 847 specifier) are reserved and require IESG Ratification (see Section 848 5.1) for assignment; also, the additional specifier value 0x42 849 (00-00-5E-42) is assigned for use as an example in documentation. 851 Assignments of such other IANA OUI-based parameters must be for 852 standards use (either for an IETF Standard or other standard related 853 to IETF work) and be documented in an Internet-Draft or RFC. The 854 first time a value is assigned for a particular parameter of this 855 type, an IANA registry will be created to contain that assignment and 856 any subsequent assignments of values for that parameter under the 857 IANA OUI. The Expert will specify the name of the registry. 859 If different policies from those above are required for such a 860 parameter, a BCP or Standards Track RFC must be adopted to update 861 this BCP and specify the new policy and parameter. 863 5. IANA Considerations 865 This document concerns IANA considerations for the assignment of 866 Ethernet parameters in connection with the IANA OUI and related 867 matters. 869 As this document replaces [RFC7042], references to [RFC7042] in IANA 870 registries will be replaced by references to this document. 872 This document does not create any new IANA registries. 874 The MAC address values assigned for documentation and the protocol 875 number for documentation were both assigned by [RFC7042]. 877 No existing assignment is changed by this document. 879 5.1 Expert Review and IESG Ratification 881 This section specifies the procedure for Expert Review and IESG 882 Ratification of MAC, protocol, and other IANA OUI-based identifiers. 883 The Expert(s) referred to in this document shall consist of one or 884 more persons appointed by and serving at the pleasure of the IESG. 886 The procedure described for Expert Review assignments in this 887 document is fully consistent with the IANA Expert Review policy 888 described in [RFC8126]. 890 While finite, the universe of code points from which Expert-judged 891 assignments will be made is felt to be large enough that the 892 requirements given in this document and the Experts' good judgment 893 are sufficient guidance. The idea is for the Expert to provide a 894 light sanity check for small assignments of EUI identifiers, with 895 increased scrutiny by the Expert for medium-sized assignments of EUI 896 identifiers and assignments of protocol identifiers and other IANA 897 OUI-based parameters. However, it can make sense to assign very 898 large portions of the MAC identifier code point space. (Note that 899 existing assignments include one for 1/2 of the entire multicast IANA 900 EUI-48 code point space and one for 1/16 of that multicast code point 901 space.) In those cases, and in cases of the assignment of "reserved" 902 values, IESG Ratification of an Expert Review approval recommendation 903 is required as described below. The procedure is as follows: 905 The applicant always completes the appropriate template from 906 Appendix A below and sends it to IANA . 908 IANA always sends the template to an appointed Expert. If the 909 Expert recuses themselves or is non-responsive, IANA may choose 910 an alternative appointed Expert or, if none is available, will 911 contact the IESG. 913 In all cases, if IANA receives a disapproval from an Expert 914 selected to review an application template, the application 915 will be denied. The Expert should provide a reason for refusal 916 which IANA will communicate back to the applicant. 918 If the assignment is based on Expert Review: 920 If IANA receives approval and code points are available, 921 IANA will make the requested assignment. 923 If the assignment is based on IESG Ratification: 925 The procedure starts with the first steps above for Expert 926 Review. If the Expert disapproves the application, they 927 simply inform IANA; however, if the Expert believes the 928 application should be approved, or is uncertain and believes 929 that the circumstances warrant the attention of the IESG, 930 the Expert will inform IANA about their advice, and IANA 931 will forward the application, together with the reasons 932 provided by the Expert for approval or uncertainty, to the 933 IESG. The IESG must decide whether the assignment will be 934 granted. This can be accomplished by a management item in 935 an IESG telechat as is done for other types of requests. If 936 the IESG decides not to ratify a favorable opinion by the 937 Expert or decides against an application where the Expert is 938 uncertain, the application is denied; otherwise, it is 939 granted. The IESG will communicate its decision to the 940 Expert and to IANA. In case of refusal, the IESG should 941 provide a reason which IANA will communicate to the 942 applicant. 944 5.2 MAC Address AFNs and RRTYPEs 946 IANA has assigned Address Family Numbers (AFNs) for MAC addresses as 947 follows: 949 AFN Decimal Hex Reference 950 ---------- ------- ------ --------- 951 48-bit MAC 16389 0x4005 [RFC7042] 952 64-bit MAC 16390 0x4006 [RFC7042] 953 24-bit OUI 16391 0x4007 [RFC7961] 955 MAC/24 16392 0x4008 [RFC7961] 956 Lower 24 bits of a 48-bit MAC address 958 MAC/40 16393 0x4009 [RFC7961] 959 Lower 40 bits of a 64-bit MAC address 961 IANA has assigned DNS RRTYPEs [RFC6895] for MAC addresses as follows: 963 RRTYPE Code 964 Data Mnemonic Decimal Hex Reference 965 ---------- -------- ------- ------ ----------- 966 48-bit MAC EUI48 108 0x006C [RFC7043] 967 64-bit MAC EUI64 109 0x006D [RFC7043] 969 5.3 Informational IANA Web Page Material 971 IANA maintains an informational listing on its web site concerning 972 Ethertypes, OUIs, and multicast addresses assigned under OUIs other 973 than the IANA OUI. The title of this informational registry is "IEEE 974 802 Numbers". IANA has merged in those Ethertypes listed in Appendix 975 B that were not already included. IANA will update that 976 informational registry when changes are provided or approved by the 977 Expert(s). 979 5.4 OUI Exhaustion 981 When the available space for either multicast or unicast EUI-48 982 identifiers under OUI 00-00-5E has been 90% or more exhausted, IANA 983 should request an additional OUI from the IEEE Registration Authority 984 for further IANA assignment. The appointed Expert(s) should monitor 985 for this condition and notify IANA. 987 5.5 IANA OUI MAC Address Table 989 No changes have been made in the "IANA Unicast 48-bit MAC Addresses" 990 and "IANA Multicast 48-bit MAC Addresses" tables except for the 991 updates to references as specified in the first part of Section 5. 993 5.6 SNAP Protocol Number Table and Assignment 995 The IANA table formerly called the "SNAP PROTOCOL IDs" table has been 996 renamed "SNAP Protocol Numbers". "PID" has been replaced by 997 "Protocol Number". 999 IANA has assigned 0x0042 as the SNAP protocol number under the IANA 1000 OUI to be used for documentation purposes. 1002 6. Security Considerations 1004 This document is concerned with assignment of parameters under the 1005 IANA OUI and closely related matters. It is not directly concerned 1006 with security except as follows: 1008 Confusion and conflict can be caused by the use of MAC addresses 1009 or other OUI-derived protocol parameters as examples in 1010 documentation. Examples that are "only" to be used in 1011 documentation can end up being coded and released or cause 1012 conflicts due to later real use and the possible acquisition of 1013 intellectual property rights in such addresses or parameters. The 1014 reservation herein of MAC addresses and parameters for 1015 documentation purposes will minimize such confusion and conflict. 1017 See [RFC7043] for security considerations in storing MAC addresses in 1018 the DNS. 1020 7. Acknowledgements 1022 The comments and suggestions of the following people, listed in 1023 alphabetic order, are gratefully acknowledged: 1025 This Document: 1026 TBD 1028 RFC 7042 (which was obsoleted by this document): 1029 David Black, Adrian Farrel, Bob Grow, Joel Jaeggli, Pearl 1030 Liang, Glenn Parsons, Pete Resnick, and Dan Romascanu. 1032 Normative References 1034 [802_O&A] - "IEEE Standard for Local and Metropolitan Area Networks: 1035 Overview and Architecture", IEEE Std 802-2014, 12 June 2014. 1037 "Standard for Local and Metropolitan Area Networks: Overview 1038 and Architecture - Draft Amendment: Local Medium Access Control 1039 (MAC) Address Usage", IEEE 802c, Draft 2.2, April 2017. 1041 [RFC8126] - Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1042 Writing an IANA Considerations Section in RFCs", BCP 26, RFC 1043 8126, DOI 10.17487/RFC8126, June 2017, . 1046 Informative References 1048 [802.1CQ] - IEEE 802, "Standard for Local and Metropolitan Area 1049 Networks: Multicast and Local Address Assignment", work in 1050 progress. 1052 [802.1Q] - "IEEE Standard for Local and metropolitan area networks / 1053 Media Access Control (MAC) Bridges and Virtual Bridge Local 1054 Area Networks", IEEE Std 802.1Q-2011, 31 August 2011. 1056 [802.3] - "IEEE Standard for Ethernet", IEEE Std 802.3-2012, 28 1057 December 2012. 1059 [802.11] - "IEEE Standard for Information technology / 1060 Telecommunications and information exchange between systems / 1061 Local and metropolitan area networks / Specific requirements / 1062 Part 11: Wireless LAN Medium Access Control (MAC) and Physical 1063 Layer (PHY) Specifications", IEEE Std 802.11-2012, 29 March 1064 2012. 1066 [EUI-64] - IEEE Registration Authority, "Guidelines for 64-bit Global 1067 Identifier (EUI-64(TM))", , November 2012. 1070 [IANA] - Internet Assigned Numbers Authority, . 1072 [IEEE802] - IEEE 802 LAN/MAN Standards Committee, 1073 . 1075 [IEEEtutorial] - IEEE, "Guidelines for Use of Extended Unique 1076 Identifier (EUI), Organizationally Unique Identifier (OUI), and 1077 Company ID (CID)", 1078 , 3 August 1080 2017. 1082 [InfiniBand] - InfiniBand Trade Association, "InfiniBand Architecture 1083 Specification Volume 1", November 2007. 1085 [RAC_OUI] - Parsons, G., "OUI Registry Restructuring", 1086 draft-ieee-rac-oui-restructuring-01.txt, work in Progress, 1087 September 2013. 1089 [RFC1112] - Deering, S., "Host extensions for IP multicasting", STD 1090 5, RFC 1112, August 1989. 1092 [RFC1661] - Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", 1093 STD 51, RFC 1661, July 1994. 1095 [RFC2153] - Simpson, W., "PPP Vendor Extensions", RFC 2153, May 1997. 1097 [RFC2332] - Luciani, J., Katz, D., Piscitello, D., Cole, B., and N. 1098 Doraswamy, "NBMA Next Hop Resolution Protocol (NHRP)", RFC 1099 2332, April 1998. 1101 [RFC2464] - Crawford, M., "Transmission of IPv6 Packets over Ethernet 1102 Networks", RFC 2464, December 1998. 1104 [RFC2606] - Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS 1105 Names", BCP 32, RFC 2606, June 1999. 1107 [RFC2784] - Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 1108 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, DOI 1109 10.17487/RFC2784, March 2000, . 1112 [RFC3092] - Eastlake 3rd, D., Manros, C., and E. Raymond, "Etymology 1113 of "Foo"", RFC 3092, April 1 2001. 1115 [RFC4291] - Hinden, R. and S. Deering, "IP Version 6 Addressing 1116 Architecture", RFC 4291, February 2006. 1118 [RFC4760] - Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 1119 "Multiprotocol Extensions for BGP-4", RFC 4760, January 2007. 1121 [RFC5214] - Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 1122 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, March 1123 2008. 1125 [RFC5332] - Eckert, T., Rosen, E., Ed., Aggarwal, R., and Y. Rekhter, 1126 "MPLS Multicast Encapsulations", RFC 5332, August 2008. 1128 [RFC5737] - Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address 1129 Blocks Reserved for Documentation", RFC 5737, January 2010. 1131 [RFC5798] - Nadas, S., Ed., "Virtual Router Redundancy Protocol 1132 (VRRP) Version 3 for IPv4 and IPv6", RFC 5798, March 2010. 1134 [RFC6034] - Thaler, D., "Unicast-Prefix-Based IPv4 Multicast 1135 Addresses", RFC 6034, October 2010. 1137 [RFC6328] - Eastlake 3rd, D., "IANA Considerations for Network Layer 1138 Protocol Identifiers", BCP 164, RFC 6328, DOI 10.17487/RFC6328, 1139 July 2011, 1141 [RFC6895] - Eastlake 3rd, D., "Domain Name System (DNS) IANA 1142 Considerations", BCP 42, RFC 6895, April 2013. 1144 [RFC7042] - Eastlake 3rd, D. and J. Abley, "IANA Considerations and 1145 IETF Protocol and Documentation Usage for IEEE 802 Parameters", 1146 BCP 141, RFC 7042, DOI 10.17487/RFC7042, October 2013, 1147 . 1149 [RFC7043] - Abley, J., "Resource Records for EUI-48 and EUI-64 1150 Addresses in the DNS", RFC 7043, October 2013. 1152 [RFC7319] - Eastlake 3rd, D., "IANA Considerations for Connectivity 1153 Fault Management (CFM) Code Points", BCP 191, RFC 7319, DOI 1154 10.17487/RFC7319, July 2014, . 1157 [RFC7961] - Eastlake 3rd, D. and L. Yizhou, "Transparent 1158 Interconnection of Lots of Links (TRILL): Interface Addresses 1159 APPsub-TLV", RFC 7961, DOI 10.17487/RFC7961, August 2016, 1160 . 1162 [RFC8947] - Volz, B., Mrugalski, T., and C. Bernardos, "Link-Layer 1163 Address Assignment Mechanism for DHCPv6", RFC 8947, DOI 1164 10.17487/RFC8947, December 2020, . 1167 [RFC8948] - Bernardos, CJ. and A. Mourad, "Structured Local Address 1168 Plan (SLAP) Quadrant Selection Option for DHCPv6", RFC 8948, 1169 DOI 10.17487/RFC8948, December 2020, . 1172 Appendix A. Templates 1174 This appendix provides the specific templates for IANA assignments of 1175 parameters. Explanatory words in parentheses in the templates below 1176 may be deleted in a completed template as submitted to IANA. 1178 A.1 EUI-48/EUI-64 Identifier or Identifier Block Template 1180 Applicant Name: 1182 Applicant Email: 1184 Applicant Telephone: (starting with country code) 1186 Use Name: (brief name of Parameter use such as "Foo Protocol" 1187 [RFC3092]) 1189 Document: (ID or RFC specifying use to which the identifier or block 1190 of identifiers will be put.) 1192 Specify whether this is an application for EUI-48 or EUI-64 1193 identifiers: 1195 Size of Block requested: (must be a power-of-two-sized block, can be 1196 a block of size one (2**0)) 1198 Specify multicast, unicast, or both: 1200 A.2 IANA OUI-Based Protocol Number Template 1202 Applicant Name: 1204 Applicant Email: 1206 Applicant Telephone: (starting with country code) 1208 Use Name: (brief name of use of code point such as "Foo Protocol") 1210 Document: (ID or RFC specifying use to which the protocol identifier 1211 will be put.) 1213 Note: (any additional note) 1215 A.3 Other IANA OUI-Based Parameter Template 1217 Applicant Name: 1219 Applicant Email: 1221 Applicant Telephone: (starting with country code) 1223 Protocol where the OUI-Based Parameter for which a value is being 1224 requested appears: (such as: Cipher Suite selection in IEEE 802.11) 1226 Use Name: (brief name of use of code point to be assigned, such as 1227 "Foo Cipher Suite" [RFC3092]) 1229 Document: (ID or RFC specifying use to which the other IANA OUI-based 1230 parameter value will be put.) 1232 Note: (any additional note) 1234 Appendix B. Ethertypes 1236 This appendix lists some Ethertypes specified for IETF protocols or 1237 by IEEE 802 as known at the time of publication. A more up-to-date 1238 list may be available on the IANA web site, currently at [IANA]. The 1239 IEEE Registration Authority page of Ethertypes, 1240 http://standards.ieee.org/regauth/ethertype/eth.txt, may also be 1241 useful. See Section 3 above. 1243 B.1. Some Ethertypes Specified by the IETF 1245 0x0800 Internet Protocol Version 4 (IPv4) 1246 0x0806 Address Resolution Protocol (ARP) 1247 0x0808 Frame Relay ARP 1248 0x22F3 TRILL 1249 0x22F4 L2-IS-IS 1250 0x8035 Reverse Address Resolution Protocol (RARP) 1251 0x86DD Internet Protocol Version 6 (IPv6) 1252 0x876B TCP/IP Compression 1253 0x876C IP Autonomous System 1254 0x880B Point-to-Point Protocol (PPP) 1255 0x880C General Switch Management Protocol (GSMP) 1256 0x8847 MPLS 1257 0x8848 MPLS with upstream-assigned label 1258 0x8861 Multicast Channel Allocation Protocol (MCAP) 1259 0x8863 PPP over Ethernet (PPPoE) Discovery Stage 1260 0x8864 PPP over Ethernet (PPPoE) Session Stage 1261 0x893B TRILL Fine Grained Labeling (FGL) 1262 0x8946 TRILL RBridge Channel 1263 0x894F NSH (Network Service Header) 1264 0x9A22 TRILL Multi Topology 1265 0xA0ED LoWPAN Encapsulation 1266 0xB7EA Control message channel inside GRE 1268 B.2. Some IEEE 802 Ethertypes 1270 0x8100 IEEE Std 802.1Q - Customer VLAN Tag Type (C-Tag, formerly 1271 called the Q-Tag) (initially Wellfleet) 1272 0x8808 IEEE Std 802.3 - Ethernet Passive Optical Network (EPON) 1273 0x888E IEEE Std 802.1X - 802.1X Port-based network access control 1274 0x88A8 IEEE Std 802.1Q - Service VLAN tag identifier (S-Tag) 1275 0x88B5 IEEE Std 802 - Local Experimental Ethertype 1276 0x88B6 IEEE Std 802 - Local Experimental Ethertype 1277 0x88B7 IEEE Std 802 - OUI Extended Ethertype 1278 0x88C7 IEEE Std 802.11 - Pre-Authentication (802.11i) 1279 0x88CC IEEE Std 802.1AB - Link Layer Discovery Protocol (LLDP) 1280 0x88E5 IEEE Std 802.1AE - Media Access Control Security 1281 0x88F5 IEEE Std 802.1Q - Multiple VLAN Registration Protocol 1282 (MVRP) 1283 0x88F6 IEEE Std 802.1Q - Multiple Multicast Registration 1284 Protocol (MMRP) 1285 0x890D IEEE Std 802.11 - Used for a variety of 802.11 Protocols: 1286 Fast Roaming Remote Request/Response 1287 Tunnelled Direct Link Setup 1288 Registered Location Query 1289 Fast Session Transfer 1290 0x8917 IEEE Std 802.21 - Media Independent Handover Protocol 1291 0x8929 IEEE Std 802.1Qbe - Multiple I-SID Registration Protocol 1292 0x8940 IEEE Std 802.1Qbg - ECP Protocol (also used in 802.1BR) 1294 Authors' Addresses 1296 Donald E. Eastlake 3rd 1297 Futurewei Technologies 1298 2386 Panoramic Circle 1299 Apopka, FL 32703 1300 USA 1302 Phone: +1-508-634-2066 1303 EMail: d3e3e3@gmail.com 1305 Joe Abley 1306 Hopcount Limited 1307 186 Albert Stree, Suite 103 1308 London, ON N6A 1M1 1309 Canada 1311 Phone: +1 519 670 9327 1312 EMail: jabley@hopcount.ca 1314 Copyright, Disclaimer, and Additional IPR Provisions 1316 Copyright (c) 2021 IETF Trust and the persons identified as the 1317 document authors. All rights reserved. 1319 This document is subject to BCP 78 and the IETF Trust's Legal 1320 Provisions Relating to IETF Documents 1321 (http://trustee.ietf.org/license-info) in effect on the date of 1322 publication of this document. Please review these documents 1323 carefully, as they describe your rights and restrictions with respect 1324 to this document. Code Components extracted from this document must 1325 include Simplified BSD License text as described in Section 4.e of 1326 the Trust Legal Provisions and are provided without warranty as 1327 described in the Simplified BSD License. This Internet-Draft is 1328 submitted in full conformance with the provisions of BCP 78 and BCP 1329 79.