idnits 2.17.1 draft-eastlake-rfc7042bis-03.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 20, 2020) is 1312 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) == Unused Reference: 'IEEEtutorial' is defined on line 1068, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 7042 (Obsoleted by RFC 9542) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 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: March 19, 2021 September 20, 2020 7 IANA Considerations and IETF Protocol and Documentation Usage 8 for IEEE 802 Parameters 9 draft-eastlake-rfc7042bis-03.txt 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........................4 49 1.4 The IANA Organizationally Unique Identifier............5 50 1.5 CFM Code Points........................................5 52 2. Ethernet Identifier Parameters..........................6 53 2.1 48-Bit MAC Identifiers, OUIs, and Other Prefixes.......6 54 2.1.1 Special First Octet Bits.............................7 55 2.1.2 OUIs and CIDs........................................8 56 2.1.3 EUI-48 Assignments under the IANA OUI................9 57 2.1.4 EUI-48 Documentation Values.........................10 58 2.1.5 EUI-48 IANA Assignment Considerations...............10 59 2.2 64-Bit MAC Identifiers................................10 60 2.2.1. IPv6 Use of Modified EUI-64 Identifiers............11 61 2.2.2 EUI-64 IANA Assignment Considerations...............12 62 2.2.3 EUI-64 Documentation Values.........................14 63 2.3 Other 48-bit MAC Identifiers Used by the IETF.........14 64 2.3.1 Identifiers Prefixed '33-33'........................14 65 2.3.2 The 'CF Series'.....................................15 66 2.3.2.1 Changes to RFC 2153...............................15 68 3. Ethernet Protocol Parameters...........................17 69 3.1 Ethernet Protocol Assignment under the IANA OUI.......18 70 3.2 Documentation Protocol Number.........................19 72 4. Other OUI-Based Parameters............................20 74 5. IANA Considerations...................................21 75 5.1 Expert Review and IESG Ratification...................21 76 5.2 MAC Address AFNs and RRTYPEs..........................22 77 5.3 Informational IANA Web Page Material..................23 78 5.4 OUI Exhaustion........................................23 79 5.5 IANA OUI MAC Address Table............................23 80 5.6 SNAP Protocol Number Table and Assignment.............24 82 6. Security Considerations................................25 83 7. Acknowledgements.......................................25 84 Normative References......................................26 85 Informative References....................................26 87 Appendix A. Templates.....................................29 88 A.1 EUI-48/EUI-64 Identifier or Identifier Block Template.29 89 A.2 IANA OUI-Based Protocol Number Template...............29 90 A.3 Other IANA OUI-Based Parameter Template...............30 91 Appendix B. Ethertypes...................................31 92 B.1. Some Ethertypes Specified by the IETF...............31 93 B.2. Some IEEE 802 Ethertypes............................31 95 1. Introduction 97 Some IETF protocols use Ethernet or other IEEE 802-related 98 communication frame formats and parameters [IEEE802]. These include 99 MAC (Media Access Control) addresses and protocol identifiers. 101 This document specifies IANA considerations for the assignment of 102 code points under the IANA OUI including MAC addresses and protocol 103 identifiers. It also discusses several other uses by the IETF of 104 IEEE 802 code points, including IEEE 802 Connectivity Fault 105 Management (CFM) code points [RFC7319], and provides some values for 106 use in documentation. As noted in [RFC2606] and [RFC5737], the use 107 of designated code values reserved for documentation and examples 108 reduces the likelihood of conflicts and confusion arising from their 109 duplication of code points assigned for some deployed use. 111 [RFC8126] is incorporated herein except where there are contrary 112 provisions in this document. In this document, "IESG Ratification" 113 is used in some cases. IESG Ratification is specified in Section 5.1. 114 It is not the same as "IESG Approval" in [RFC8126]. 116 1.1 Notations Used in This Document 118 This document uses hexadecimal notation. Each octet (that is, 8-bit 119 byte) is represented by two hexadecimal digits giving the value of 120 the octet as an unsigned integer. Successive octets are separated by 121 a hyphen. This document consistently uses IETF bit ordering although 122 the physical order of bit transmission within an octet on an IEEE 123 [802.3] link is from the lowest order bit to the highest order bit 124 (i.e., the reverse of the IETF's ordering). 126 In this document: 128 "AFN" Address Family Number [RFC4760]. 130 "CFM" Connectivity Fault Managment [RFC7319]. 132 "CID" Company Identifier. 134 "EUI" Extended Unique Identifier. 136 "IAB" Individual Address Block, not Internet Architecture Board 137 (iab.org). 139 "IEEE" Institute for Electrical and Electronics Engineers 140 (www.ieee.org). 142 "IEEE-SA" IEEE Standards Association (standards.ieee.org). 144 "MA-L" MAC Address Block Large, commonly referred to as an OUI. 146 "MA-M" MAC Address Block Medium. 148 "MA-S" MAC Address Block Small. 150 "MAC" Media Access Control, not for Message Authentication Code. 152 "MAC-48" A 48-bit MAC address. This term is obsolete. If globally 153 unique, use EUI-48. 155 "OUI" Organizationally Unique Identifier. An OUI is now officially 156 calle "MA-L" by the IEEE. 158 "RRTYPE" A DNS Resource Record type [RFC6895]. 160 "SLAP" IEEE 802 Structured Local Address Plan [802_O&A]. 162 "TLV" Type, Length, Value. 164 "**" This symbol indicates exponentiation. For example, 2**24 is 165 two to the twenty-fourth power. 167 1.2 Changes from RFC 7042 169 This document obsoletes [RFC7042] and makes the changes listed below. 170 However, the completed application template based upon which an IANA 171 OUI-based protocol number value was assigned for document use remains 172 that in Appendix C of RFC 7042. 174 o Information on MA-M (28-bit) and MA-S (36-bit) EUI prefixes that 175 the IEEE Registration Authority assignes. 177 o The restructuring of the "local" MAC address space into four 178 quadrants under the Structured Local Address Plan (SLAP [802_O&A]. 180 o Mention of the IEEE 802 CFM Codepoints that have been allocated to 181 the IETF (see Section 1.5). 183 o Minor details clarified in Section 5.1 on Expert Review and IESG 184 Ratification. 186 1.3 The IEEE Registration Authority 188 Originally the responsibility of Xerox Corporation, the registration 189 authority for Ethernet parameters is now the IEEE Registration 190 Authority, available on the web at: 192 http://standards.ieee.org/regauth/ 194 The IEEE Registration Authority operates under the direction of the 195 IEEE-SA Board of Governors. Anyone may apply to that Authority for 196 parameter assignments. The IEEE Registration Authority may impose 197 fees or other requirements but commonly waives fees for applications 198 from standards development organizations. 200 Lists of some assignments and their holders are downloadable from the 201 IEEE Registration Authority site. 203 1.4 The IANA Organizationally Unique Identifier 205 The Organizationally Unique Identifier (OUI) 00-00-5E has been 206 assigned to IANA. 208 There is no OUI value reserved at this time for documentation, but 209 there are documentation code points under the IANA OUI specified 210 below. 212 1.5 CFM Code Points 214 The IEEE has allocated two blocks of 802 Connectivity Fault 215 Management (CFM) code points to the IETF, one for CFM OpCodes and one 216 for CFM TLV Types. Further information, including IANA 217 considerations for assignment of values from these block for IETF 218 use, are given in [RFC7319]. This document does not further discuss 219 these blocks of codepoints. 221 2. Ethernet Identifier Parameters 223 Section 2.1 discusses 48-bit MAC identifiers, their relationship to 224 OUIs and other prefixes, and assignment under the IANA OUI. Section 225 2.2 extends this to 64-bit identifiers. Section 2.3 discusses other 226 IETF MAC identifier use not under the IANA OUI. ([RAC_OUI] indicates 227 that the IEEE Registration Authority Committee was at one time 228 exploring the feasibility of defining 128-bit identifiers. [RAC_OUI] 229 is an expired draft that also provides additional historic 230 information on [IEEE802] registries.) 232 2.1 48-Bit MAC Identifiers, OUIs, and Other Prefixes 234 48-bit MAC "addresses" are the most commonly used Ethernet interface 235 identifiers. Those that are globally unique are also called EUI-48 236 identifiers (Extended Unique Identifier 48). An EUI-48 is structured 237 into an initial prefix assigned by the IEEE Registration Authority 238 and additional bits assigned by the prefix owner. Currently there 239 are three lengths of prefixes assigned as shown in the table below; 240 however, some prefix bits have special meaning as shown in Figure 1. 242 Prefix Length Owner Supplied Bits 243 in bits Name for EUI-48 244 ------------- ------ -------------------- 245 24 OUI (MAC-L) 24 246 28 MAC-M 20 247 36 MAC-S 12 249 Actually, the bottom four bits, as shown below, of the first octet of 250 the 3-octet 48-bit MAC have speical meaning and are referred to below 251 as the M, X, Y, and Z bits. 253 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 254 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 255 | . . . . Z Y X M| . . . . . . . .| octets 0&1 256 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 257 | . . . . . . . .| . . . . . . . .| octets 2&3 258 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 259 | . . . . . . . .| . . . . . . . .| octets 4&5 260 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 262 Figure 1. 48-bit MAC Address Structure 264 A 3-octet OUI (Organizationally Unique Identifier) is followed by an 265 additional 3 octets assigned by the OUI holder or into a larger 266 initial prefix assigned to an organization and a shorter sequence of 267 additional bits so as to add up to 48 bits in total. For example, 268 the IEEE has assigned IABs (Individual Address Blocks), where the 269 first 4 1/2 octets (36 bits) are assigned, giving the holder of the 270 IAB 1 1/2 octets (12 bits) they can control; however, IABs have 271 become historic, and a wider range of prefix lengths will be made 272 available [RAC_OUI]. 274 The IEEE describes its assignment procedures and policies for IEEE 275 802-related identifiers in [802_O&A]. An IEEE tutorial on EUIs, OUIs, 276 and CIDs is available at [IEEE tutorial]. 278 2.1.1 Special First Octet Bits 280 Four bits within the initial octet of an IEEE MAC interface 281 identifier, such as an EUI-48, have special significance [802_O&A] as 282 follows: 284 M bit --- This bit always indicates a group address and is 285 frequently referred to as the group bit. If it is zero, 286 the MAC address is unicast. If it is a one, the address is 287 multicast or broadcast. This meaning is independent of the 288 values of the X, Y, and Z bits. 290 X bit --- This bit was previously called the "local" bit. If it is 291 zero, the MAC address is a global address under the 292 control of the owner of the IEEE assigned prefix. 293 Previously, if it was a one, the MAC address was 294 considered "local" and under the assignment and control of 295 the local network operator (but see Section 2.3). Now, if 296 it is a one, the nature of the MAC address is optionally 297 determined by the Y and Z bits under the IEEE 802 298 Structured Local Address Plan (SLAP) as described below. 300 Y&Z bits - These two bits have no special meaning if the X bit is 301 zero. If the X bit is one, these tow bits divide the 302 formerly uniform "local" MAC address space into four 303 quadrants, as follows. These quadrants are further 304 described below. 306 Y bit Z bit Quadrant ----- ----- ----------- 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 four quadrants of the 314 "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 such future SLAP 332 use would cause a conflict. 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 on-going work in the IEEE 338 [802.1CQ] and the IETF [DHCPmac] [SLAPquad] to develop 339 such protocols. 341 2.1.2 OUIs and CIDs 343 OUI, MAC-M, and MAC-S MAC prefixes are assigned with the Local bit 344 zero and the Group bit unspecified. Multicast identifiers may be 345 constructed by turning on the Group bit, and unicast identifiers may 346 be constructed by leaving the Group bit zero. 348 The Local bit is zero for globally unique EUI-48 identifiers assigned 349 by the owner of an OUI or owner of a longer prefix. If the Local bit 350 is a one, the identifier has been considered by IEEE 802 to be a 351 local identifier under the control of the local network 352 administrator; however, there may be emerging recommendations from 353 the IEEE Registration Authority on management of the local address 354 space. If the Local bit is on, the holder of an OUI has no special 355 authority over MAC identifiers whose first 3 octets correspond to 356 their OUI. 358 An AFN and a DNS RRTYPE have been assigned for 48-bit MAC addresses 359 (see Section 5.2). 361 2.1.3 EUI-48 Assignments under the IANA OUI 363 The OUI 00-00-5E has been assigned to IANA as stated in Section 1.4 364 above. This includes 2**24 EUI-48 multicast identifiers from 365 01-00-5E-00-00-00 to 01-00-5E-FF-FF-FF and 2**24 EUI-48 unicast 366 identifiers from 00-00-5E-00-00-00 to 00-00-5E-FF-FF-FF. 368 Of these EUI-48 identifiers, the sub-blocks reserved or thus far 369 assigned by IANA for purposes of documentation are as follows: 371 Unicast, all blocks of 2**8 addresses thus far: 373 00-00-5E-00-00-00 through 00-00-5E-00-00-FF: reserved and require 374 IESG Ratification for assignment (see Section 5.1). 376 00-00-5E-00-01-00 through 00-00-5E-00-01-FF: assigned for the 377 Virtual Router Redundancy Protocol (VRRP) [RFC5798]. 379 00-00-5E-00-02-00 through 00-00-5E-00-02-FF: assigned for the IPv6 380 Virtual Router Redundancy Protocol (IPv6 VRRP) [RFC5798]. 382 00-00-5E-00-52-00 through 00-00-5E-00-52-FF: used for very small 383 assignments. Currently, 3 out of these 256 values have been 384 assigned. 386 00-00-5E-00-53-00 through 00-00-5E-00-53-FF: assigned for use in 387 documentation. 389 Multicast: 391 01-00-5E-00-00-00 through 01-00-5E-7F-FF-FF: 2**23 addresses 392 assigned for IPv4 multicast [RFC1112]. 394 01-00-5E-80-00-00 through 01-00-5E-8F-FF-FF: 2**20 addresses 395 assigned for MPLS multicast [RFC5332]. 397 01-00-5E-90-00-00 through 01-00-5E-90-00-FF: 2**8 addresses being 398 used for very small assignments. Currently, 4 out of these 256 399 values have been assigned. 401 01-00-5E-90-10-00 through 01-00-5E-90-10-FF: 2**8 addresses for 402 use in documentation. 404 For more detailed and up-to-date information, see the "Ethernet 405 Numbers" registry at http://www.iana.org. 407 2.1.4 EUI-48 Documentation Values 409 The following values have been assigned for use in documentation: 411 00-00-5E-00-53-00 through 00-00-5E-00-53-FF for unicast and 413 01-00-5E-90-10-00 through 01-00-5E-90-10-FF for multicast. 415 2.1.5 EUI-48 IANA Assignment Considerations 417 EUI-48 assignments under the current or a future IANA OUI (see 418 Section 5.4) must meet the following requirements: 420 o must be for standards purposes (either for an IETF Standard or 421 other standard related to IETF work), 423 o must be for a power-of-two size block of identifiers starting 424 at a boundary that is an equal or greater power of two, 425 including the assignment of one (2**0) identifier, 427 o must not be used to evade the requirement for vendors to obtain 428 their own block of identifiers from the IEEE, and 430 o must be documented in an Internet-Draft or RFC. 432 In addition, approval must be obtained as follows (see the procedure 433 in Section 5.1): 435 Small to medium assignments of a block of 1, 2, 4, ..., 32768, 436 65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI-48 identifiers 437 require Expert Review (see Section 5.1). 439 Large assignments of 131072 (2**17) or more EUI-48 identifiers 440 require IESG Ratification (see Section 5.1). 442 2.2 64-Bit MAC Identifiers 444 IEEE also defines a system of 64-bit MAC identifiers including 445 EUI-64s. EUI-64 identifiers are currently used as follows: 447 o In a modified form to construct some IPv6 interface identifiers 448 as described in Section 2.2.1 450 o In IEEE Std 1394 (also known as FireWire and i.Link) 452 o In IEEE Std 802.15.4 (also known as ZigBee) 453 o In [InfiniBand] 455 Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) OUI, or a 456 shorter extension to longer assigned prefixes [RAC_OUI] so as to 457 total 64 bits, produces an EUI-64 identifier under that OUI or longer 458 prefix. As with EUI-48 identifiers, the first octet has the same 459 Group and Local bits. 461 An AFN and a DNS RRTYPE have been assigned for 64-bit MAC addresses 462 (see Section 5.2). 464 The discussion below is almost entirely in terms of the "Modified" 465 form of EUI-64 identifiers; however, anyone assigned such an 466 identifier can also use the unmodified form as a MAC identifier on 467 any link that uses such 64-bit identifiers for interfaces. 469 2.2.1. IPv6 Use of Modified EUI-64 Identifiers 471 MAC-64 identifiers are used to form the lower 64 bits of some IPv6 472 addresses (Section 2.5.1 and Appendix A of [RFC4291] and Appendix A 473 of [RFC5214]). When so used, the MAC-64 is modified by inverting the 474 Local/Global bit to form an IETF "Modified EUI-64 identifier". Below 475 is an illustration of a Modified EUI-64 unicast identifier under the 476 IANA OUI, where aa-bb-cc-dd-ee is the extension. 478 02-00-5E-aa-bb-cc-dd-ee 480 The first octet is shown as 02 rather than 00 because, in Modified 481 EUI-64 identifiers, the sense of the Local/Global bit is inverted 482 compared with EUI-48 identifiers. It is the globally unique values 483 (universal scope) that have the 02 bit on in the first octet, while 484 those with this bit off are locally assigned and out of scope for 485 global assignment. 487 The Local/Global bit was inverted to make it easier for network 488 operators to type in local-scope identifiers. Thus, such Modified 489 EUI-64 identifiers as 1, 2, etc. (ignoring leading zeros) are local. 490 Without the modification, they would have to be 491 02-00-00-00-00-00-00-01, 02-00-00-00-00-00-00-02, etc. to be local. 493 As with 48-bit MAC identifiers, the 01 bit on in the first octet 494 indicates a group identifier. 496 When the first two octets of the extension of a Modified EUI-64 497 identifier are FF-FE, the remainder of the extension is a 24-bit 498 value as assigned by the OUI owner for an EUI-48. For example: 500 02-00-5E-FF-FE-yy-yy-yy 502 or 503 03-00-5E-FF-FE-yy-yy-yy 505 where yy-yy-yy is the portion (of an EUI-48 global unicast or 506 multicast identifier) that is assigned by the OUI owner (IANA in this 507 case). Thus, any holder of one or more EUI-48 identifiers under the 508 IANA OUI also has an equal number of Modified EUI-64 identifiers that 509 can be formed by inserting FF-FE in the middle of their EUI-48 510 identifiers and inverting the Local/Global bit. 512 (Note: [EUI-64] defines FF-FF as the bits to be inserted to create 513 an IEEE EUI-64 identifier from a EUI-48 identifier. That document 514 says the FF-FE value is used when starting with an EUI-48 515 identifier. The IETF uses only FF-FE to create Modified EUI-64 516 identifiers from 48-bit Ethernet station identifiers regardless of 517 whether they are EUI-48 or 48-bit local MAC identifiers. EUI-48 518 and local 48-bit MAC identifiers are syntactically equivalent, and 519 this doesn't cause any problems in practice.) 521 In addition, certain Modified EUI-64 identifiers under the IANA OUI 522 are reserved for holders of IPv4 addresses as follows: 524 02-00-5E-FE-xx-xx-xx-xx 526 where xx-xx-xx-xx is a 32-bit IPv4 address. The owner of an IPv4 527 address has both the unicast- and multicast-derived EUI-64 address. 528 Modified EUI-64 identifiers from 530 02-00-5E-FE-F0-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF 532 are effectively reserved pending the specification of IPv4 Class E 533 addresses. However, for Modified EUI-64 identifiers based on an IPv4 534 address, the Local/Global bit should be set to correspond to whether 535 the IPv4 address is local or global. (Keep in mind that the sense of 536 the Modified EUI-64 identifier Local/Global bit is reversed from that 537 in (unmodified) MAC-64 identifiers.) 539 2.2.2 EUI-64 IANA Assignment Considerations 541 The following table shows which Modified EUI-64 identifiers under the 542 IANA OUI are reserved, assigned, or available as indicated. As noted 543 above, the corresponding MAC addresses can be determined by 544 complementing the 02 bit in the first octet. In all cases, the 545 corresponding multicast 64-bit MAC addresses formed by complementing 546 the 01 bit in the first octet have the same status as the modified 547 64-bit unicast address blocks listed below. 549 02-00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF reserved 550 02-00-5E-10-00-00-00-00 to 02-00-5E-10-00-00-00-FF assigned for 551 documentation use 553 02-00-5E-10-00-00-01-00 to 02-00-5E-EF-FF-FF-FF-FF available for 554 assignment 556 02-00-5E-F0-00-00-00-00 to 02-00-5E-FD-FF-FF-FF-FF reserved 558 02-00-5E-FE-00-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF assigned to 559 IPv4 address holders as described above 561 02-00-5E-FF-00-00-00-00 to 02-00-5E-FF-FD-FF-FF-FF reserved 563 02-00-5E-FF-FE-00-00-00 to 02-00-5E-FF-FE-FF-FF-FF assigned for 564 holders of EUI-48 identifiers under the IANA OUI as described 565 above 567 02-00-5E-FF-FF-00-00-00 to 02-00-5E-FF-FF-FF-FF-FF reserved 569 The reserved identifiers above require IESG Ratification (see Section 570 5.1) for assignment. IANA EUI-64 identifier assignments under the 571 IANA OUI must meet the following requirements: 573 o must be for standards purposes (either for an IETF Standard or 574 other standard related to IETF work), 576 o must be for a power-of-two size block of identifiers starting 577 at a boundary that is an equal or greater power of two, 578 including the assignment of one (2**0) identifier, 580 o must not be used to evade the requirement for vendors to obtain 581 their own block of identifiers from the IEEE, and 583 o must be documented in an Internet-Draft or RFC. 585 In addition, approval must be obtained as follows (see the procedure 586 in Section 5.1): 588 Small to medium assignments of a block of 1, 2, 4, ..., 134217728, 589 268435456 (2**0, 2**1, 2**2, ..., 2**27, 2**28) EUI-64 590 identifiers require Expert Review (see Section 5.1). 592 Assignments of any size, including 536870912 (2**29) or more 593 EUI-64 identifiers, may be made with IESG Ratification (see 594 Section 5.1). 596 2.2.3 EUI-64 Documentation Values 598 The following blocks of unmodified 64-bit MAC addresses are for 599 documentation use. The IPv4-derived addresses are based on the IPv4 600 documentation addresses [RFC5737], and the MAC-derived addresses are 601 based on the EUI-48 documentation addresses above. 603 Unicast Values for Documentation Use: 605 00-00-5E-EF-10-00-00-00 to 00-00-5E-EF-10-00-00-FF general 607 00-00-5E-FE-C0-00-02-00 to 00-00-5E-FE-C0-00-02-FF and 608 00-00-5E-FE-C6-33-64-00 to 00-00-5E-FE-C6-33-64-FF and 609 00-00-5E-FE-CB-00-71-00 to 00-00-5E-FE-CB-00-71-FF IPv4 derived 611 00-00-5E-FF-FE-00-53-00 to 00-00-5E-FF-FE-00-53-FF EUI-48 derived 613 00-00-5E-FE-EA-C0-00-02 and 614 00-00-5E-FE-EA-C6-33-64 and 615 00-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 616 [RFC6034] 618 Multicast Values for Documentation Use: 620 01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general 622 01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and 623 01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and 624 01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived 626 01-00-5E-FE-EA-C0-00-02 and 627 01-00-5E-FE-EA-C6-33-64 and 628 01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 629 [RFC6034] 631 01-00-5E-FF-FE-90-10-00 to 01-00-5E-FF-FE-90-10-FF EUI-48 derived 633 2.3 Other 48-bit MAC Identifiers Used by the IETF 635 There are two other blocks of 48-bit MAC identifiers that are used by 636 the IETF as described below. 638 2.3.1 Identifiers Prefixed '33-33' 640 All 48-bit multicast MAC identifiers prefixed "33-33" (that is, the 641 2**32 multicast MAC identifiers in the range from 33-33-00-00-00-00 642 to 33-33-FF-FF-FF-FF) are used as specified in [RFC2464] for IPv6 643 multicast. In all of these identifiers, the Group bit (the bottom 644 bit of the first octet) is on, as is required to work properly with 645 existing hardware as a multicast identifier. They also have the 646 Local bit on but any ethernet using standard IPv6 multicast should 647 note that these addresses will be used for that purpose. 649 (Historical note: It was the custom during IPv6 design to use "3" 650 for unknown or example values and 3333 Coyote Hill Road, Palo 651 Alto, California, is the address of PARC (Palo Alto Research 652 Center, formerly "Xerox PARC"). Ethernet was originally specified 653 by the Digital Equipment Corporation, Intel Corporation, and Xerox 654 Corporation. The pre-IEEE [802.3] Ethernet protocol has sometimes 655 been known as "DIX" Ethernet from the first letters of the names 656 of these companies.) 658 2.3.2 The 'CF Series' 660 The Informational [RFC2153] declared the 3-octet values from CF-00-00 661 through CF-FF-FF to be OUIs available for assignment by IANA to 662 software vendors for use in PPP [RFC1661] or for other uses where 663 vendors do not otherwise need an IEEE-assigned OUI. It should be 664 noted that, when used as 48-bit MAC prefixes, these values have all 665 of the Z, Y, X (Local), and M (Group) special bits at the bottom of 666 the first byte equal to one, while all IEEE-assigned OUIs thus far 667 have the X and M bits zero. The Group bit is meaningless in PPP. To 668 quote [RFC2153]: "The 'CF0000' series was arbitrarily chosen to match 669 the PPP NLPID 'CF', as a matter of mnemonic convenience." (For 670 further information on NLPIDs, see [RFC6328].) 672 CF-00-00 is reserved, and IANA lists multicast identifier 673 CF-00-00-00-00-00 as used for Ethernet loopback tests. 675 In over a decade of availability, only a handful of values in the CF 676 Series have been assigned. (See "Ethernet Numbers" 677 and "PPP Numbers" 678 ). 680 2.3.2.1 Changes to RFC 2153 682 The IANA Considerations in [RFC2153] were updated as follows by the 683 approval of RFC 5342 (no technical changes have been made): 685 o Use of these identifiers based on IANA assignment was 686 deprecated. 688 o IANA was instructed not to assign any further values in the 'CF 689 Series'. 691 3. Ethernet Protocol Parameters 693 Ethernet protocol parameters provide a means of indicating the 694 contents of a frame -- for example, that its contents are IPv4 or 695 IPv6. 697 The concept has been extended to labeling by "tags". A tag in this 698 sense is a prefix whose type is identified by an Ethertype that is 699 then followed by either another tag, an Ethertype, or an LSAP (Link- 700 Layer Service Access Point) protocol indicator for the "main" body of 701 the frame, as described below. Traditionally, in the [802_O&A] 702 world, tags are a fixed length and do not include any encoding of 703 their own length. Any device that is processing a frame cannot, in 704 general, safely process anything in the frame past an Ethertype it 705 does not understand. An example is the C-Tag (formerly the Q-Tag) 706 [802.1Q]. It provides customer VLAN and priority information for a 707 frame. 709 There are two types of protocol identifier parameters that can occur 710 in Ethernet frames after the initial MAC-48 destination and source 711 identifiers: 713 Ethertypes: These are 16-bit identifiers appearing as the initial 714 two octets after the MAC destination and source (or after a 715 tag), which, when considered as an unsigned integer, are equal 716 to or larger than 0x0600. 718 LSAPs: These are 8-bit protocol identifiers that occur in pairs 719 immediately after an initial 16-bit (two-octet) remaining frame 720 length, which is in turn after the MAC destination and source 721 (or after a tag). Such a length must, when considered as an 722 unsigned integer, be less than 0x5DC, or it could be mistaken 723 as an Ethertype. LSAPs occur in pairs where one is intended to 724 indicate the source protocol handler and one the destination 725 protocol handler; however, use cases where the two are 726 different have been relatively rare. 728 Neither Ethertypes nor LSAPs are assigned by IANA; they are assigned 729 by the IEEE Registration Authority (see Section 1.3 above and 730 Appendix B). However, both LSAPs and Ethertypes have extension 731 mechanisms so that they can be used with five-octet Ethernet protocol 732 identifiers under an OUI, including those assigned by IANA under the 733 IANA OUI. 735 When using the IEEE 802 Logical Link Control (LLC) format (Subnetwork 736 Access Protocol (SNAP)) [802_O&A] for a frame, an OUI-based protocol 737 identifier can be expressed as follows: 739 xx-xx-AA-AA-03-yy-yy-yy-zz-zz 741 where xx-xx is the frame length and, as above, must be small enough 742 not to be confused with an Ethertype; "AA" is the LSAP that indicates 743 this use and is sometimes referred to as the SNAP Service Access 744 Point (SAP); "03" is the LLC control octet indicating datagram 745 service; yy-yy-yy is an OUI; and zz-zz is a protocol number, under 746 that OUI, assigned by the OUI owner. The five-octet length for such 747 OUI-based protocol identifiers was chosen so that, with the LLC 748 control octet ("03"), the result is 16-bit aligned. 750 When using an Ethertype to indicate the main type for a frame body, 751 the special "OUI Extended Ethertype" 88-B7 is available. Using this 752 Ethertype, a frame body can begin with 754 88-B7-yy-yy-yy-zz-zz 756 where yy-yy-yy and zz-zz have the same meaning as in the SNAP format 757 described above. 759 It is also possible, within the SNAP format, to use an arbitrary 760 Ethertype. Putting the Ethertype as the zz-zz field after an all- 761 zeros OUI (00-00-00) does this. It looks like 763 xx-xx-AA-AA-03-00-00-00-zz-zz 765 where zz-zz is the Ethertype. 767 (Note that, at this point, the 802 protocol syntax facilities are 768 sufficiently powerful that they could be chained indefinitely. 769 Whether support for such chaining is generally required is not 770 clear, but [802_O&A] requires support for 772 xx-xx-AA-AA-03-00-00-00-88-B7-yy-yy-yy-zz-zz 774 although this could be more efficiently expressed by simply 775 pinching out the "00-00-00-88-B7" in the middle.) 777 As well as labeling frame contents, 802 protocol types appear within 778 NBMA (Non-Broadcast Multi-Access) Next Hop Resolution Protocol 779 [RFC2332] messages. Such messages have provisions for both two-octet 780 Ethertypes and OUI-based protocol types. 16-bit Ethertypes also occur 781 in the Generic Router Encapsulation (GRE [RFC2784]) header. 783 3.1 Ethernet Protocol Assignment under the IANA OUI 785 Two-octet protocol numbers under the IANA OUI are available, as in 787 xx-xx-AA-AA-03-00-00-5E-qq-qq 789 where qq-qq is the protocol number. 791 A number of such assignments have been made out of the 2**16 protocol 792 numbers available from 00-00-5E-00-00 to 00-00-5E-FF-FF (see [IANA]). 793 The extreme values of this range, 00-00-5E-00-00 and 00-00-5E-FF-FF, 794 are reserved and require IESG Ratification for assignment (see 795 Section 5.1). New assignments of SNAP SAP protocol (qq-qq) numbers 796 under the IANA OUI must meet the following requirements: 798 o the assignment must be for standards use (either for an IETF 799 Standard or other standard related to IETF work), 801 o it must be documented in an Internet-Draft or RFC, and 803 o such protocol numbers are not to be assigned for any protocol 804 that has an Ethertype (because that can be expressed by putting 805 an all-zeros "OUI" before the Ethertype as described above). 807 In addition, the Expert Review (or IESG Ratification for the two 808 reserved values) must be obtained using the procedure specified in 809 Section 5.1. 811 3.2 Documentation Protocol Number 813 0x0042 is a protocol number under the IANA OUI (that is, 814 00-00-5E-00-42) to be used as an example for documentation purposes. 816 4. Other OUI-Based Parameters 818 Some IEEE 802 and other protocols provide for parameters based on an 819 OUI beyond those discussed above. Such parameters most commonly 820 consist of an OUI plus one octet of additional value. They are 821 usually called "vendor specific" parameters, although "organization 822 specific" might be more accurate. They would look like 824 yy-yy-yy-zz 826 where yy-yy-yy is the OUI and zz is the additional specifier. An 827 example is the Cipher Suite Selector in IEEE [802.11]. 829 Values may be assigned under the IANA OUI for such other OUI-based 830 parameter usage by Expert Review except that, for each use, the 831 additional specifier values consisting of all zero bits and all one 832 bits (0x00 (00-00-5E-00) and 0xFF (00-00-5E-FF) for a one-octet 833 specifier) are reserved and require IESG Ratification (see Section 834 5.1) for assignment; also, the additional specifier value 0x42 835 (00-00-5E-42) is assigned for use as an example in documentation. 837 Assignments of such other IANA OUI-based parameters must be for 838 standards use (either for an IETF Standard or other standard related 839 to IETF work) and be documented in an Internet-Draft or RFC. The 840 first time a value is assigned for a particular parameter of this 841 type, an IANA registry will be created to contain that assignment and 842 any subsequent assignments of values for that parameter under the 843 IANA OUI. The Expert will specify the name of the registry. 845 If different policies from those above are required for such a 846 parameter, a BCP or Standards Track RFC must be adopted to update 847 this BCP and specify the new policy and parameter. 849 5. IANA Considerations 851 This document concerns IANA considerations for the assignment of 852 Ethernet parameters in connection with the IANA OUI and related 853 matters. 855 As this document replaces [RFC7042], references to [RFC7042] in IANA 856 registries will be replaced by references to this document. 858 This document does not create any new IANA registries. 860 The MAC address values assigned for documentation and the protocol 861 number for documentation were both assigned by [RFC7042]. 863 No existing assignment is changed by this document. 865 5.1 Expert Review and IESG Ratification 867 This section specifies the procedure for Expert Review and IESG 868 Ratification of MAC, protocol, and other IANA OUI-based identifiers. 869 The Expert(s) referred to in this document shall consist of one or 870 more persons appointed by and serving at the pleasure of the IESG. 872 The procedure described for Expert Review assignments in this 873 document is fully consistent with the IANA Expert Review policy 874 described in [RFC8126]. 876 While finite, the universe of code points from which Expert-judged 877 assignments will be made is felt to be large enough that the 878 requirements given in this document and the Experts' good judgment 879 are sufficient guidance. The idea is for the Expert to provide a 880 light sanity check for small assignments of EUI identifiers, with 881 increased scrutiny by the Expert for medium-sized assignments of EUI 882 identifiers and assignments of protocol identifiers and other IANA 883 OUI-based parameters. However, it can make sense to assign very 884 large portions of the MAC identifier code point space. (Note that 885 existing assignments include one for 1/2 of the entire multicast IANA 886 EUI-48 code point space and one for 1/16 of that multicast code point 887 space.) In those cases, and in cases of the assignment of "reserved" 888 values, IESG Ratification of an Expert Review approval recommendation 889 is required as described below. The procedure is as follows: 891 The applicant always completes the appropriate template from 892 Appendix A below and sends it to IANA . 894 IANA always sends the template to an appointed Expert. If the 895 Expert recuses themselves or is non-responsive, IANA may choose 896 an alternative appointed Expert or, if none is available, will 897 contact the IESG. 899 In all cases, if IANA receives a disapproval from an Expert 900 selected to review an application template, the application 901 will be denied. The Expert should provide a reason for refusal 902 which IANA will communicate back to the applicant. 904 If the assignment is based on Expert Review: 906 If IANA receives approval and code points are available, 907 IANA will make the requested assignment. 909 If the assignment is based on IESG Ratification: 911 The procedure starts with the first steps above for Expert 912 Review. If the Expert disapproves the application, they 913 simply inform IANA; however, if the Expert believes the 914 application should be approved, or is uncertain and believes 915 that the circumstances warrant the attention of the IESG, 916 the Expert will inform IANA about their advice, and IANA 917 will forward the application, together with the reasons 918 provided by the Expert for approval or uncertainty, to the 919 IESG. The IESG must decide whether the assignment will be 920 granted. This can be accomplished by a management item in 921 an IESG telechat as is done for other types of requests. If 922 the IESG decides not to ratify a favorable opinion by the 923 Expert or decides against an application where the Expert is 924 uncertain, the application is denied; otherwise, it is 925 granted. The IESG will communicate its decision to the 926 Expert and to IANA. In case of refusal, the IESG should 927 provide a reason which IANA will communicate to the 928 applicant. 930 5.2 MAC Address AFNs and RRTYPEs 932 IANA has assigned Address Family Numbers (AFNs) for MAC addresses as 933 follows: 935 AFN Decimal Hex Reference 936 ---------- ------- ------ --------- 937 48-bit MAC 16389 0x4005 [RFC7042] 938 64-bit MAC 16390 0x4006 [RFC7042] 939 24-bit OUI 16391 0x4007 [RFC7961] 941 MAC/24 16392 0x4008 [RFC7961] 942 Lower 24 bits of a 48-bit MAC address 944 MAC/40 16393 0x4009 [RFC7961] 945 Lower 40 bits of a 64-bit MAC address 947 IANA has assigned DNS RRTYPEs [RFC6895] for MAC addresses as follows: 949 RRTYPE Code 950 Data Mnemonic Decimal Hex Reference 951 ---------- -------- ------- ------ ----------- 952 48-bit MAC EUI48 108 0x006C [RFC7043] 953 64-bit MAC EUI64 109 0x006D [RFC7043] 955 5.3 Informational IANA Web Page Material 957 IANA maintains an informational listing on its web site concerning 958 Ethertypes, OUIs, and multicast addresses assigned under OUIs other 959 than the IANA OUI. The title of this informational registry is "IEEE 960 802 Numbers". IANA has merged in those Ethertypes listed in Appendix 961 B that were not already included. IANA will update that 962 informational registry when changes are provided by the Expert(s). 964 5.4 OUI Exhaustion 966 When the available space for either multicast or unicast EUI-48 967 identifiers under OUI 00-00-5E has been 90% or more exhausted, IANA 968 should request an additional OUI from the IEEE Registration Authority 969 for further IANA assignment. The appointed Expert(s) should monitor 970 for this condition and notify IANA. 972 5.5 IANA OUI MAC Address Table 974 No changes have been made in the "IANA Unicast 48-bit MAC Addresses" 975 and "IANA Multicast 48-bit MAC Addresses" tables except for the 976 updates to references as specified in the first part of Section 5. 978 5.6 SNAP Protocol Number Table and Assignment 980 The IANA table formerly called the "SNAP PROTOCOL IDs" table has been 981 renamed "SNAP Protocol Numbers". "PID" has been replaced by 982 "Protocol Number". 984 IANA has assigned 0x0042 as the SNAP protocol number under the IANA 985 OUI to be used for documentation purposes. 987 6. Security Considerations 989 This document is concerned with assignment of parameters under the 990 IANA OUI and closely related matters. It is not directly concerned 991 with security except as follows. 993 Confusion and conflict can be caused by the use of MAC addresses or 994 other OUI-derived protocol parameters as examples in documentation. 995 Examples that are "only" to be used in documentation can end up being 996 coded and released or cause conflicts due to later real use and the 997 possible acquisition of intellectual property rights in such 998 addresses or parameters. The reservation herein of MAC addresses and 999 parameters for documentation purposes will minimize such confusion 1000 and conflict. 1002 See [RFC7043] for security considerations in storing MAC addresses in 1003 the DNS. 1005 7. Acknowledgements 1007 The comments and suggestions of the following people, listed in 1008 alphabetic order, are gratefully acknowledged: 1010 This Document: 1011 TBD 1013 RFC 7042 (which was obsoleted by this document): 1014 David Black, Adrian Farrel, Bob Grow, Joel Jaeggli, Pearl 1015 Liang, Glenn Parsons, Pete Resnick, and Dan Romascanu. 1017 Normative References 1019 [802_O&A] - "IEEE Standard for Local and Metropolitan Area Networks: 1020 Overview and Architecture", IEEE Std 802-2014, 12 June 2014. 1022 "Standard for Local and Metropolitan Area Networks: Overview 1023 and Architecture - Draft Amendment: Local Medium Access Control 1024 (MAC) Address Usage", IEEE 802c, Draft 2.2, April 2017. 1026 [RFC8126] - Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1027 Writing an IANA Considerations Section in RFCs", BCP 26, RFC 1028 8126, DOI 10.17487/RFC8126, June 2017, . 1031 Informative References 1033 [802.1CQ] - IEEE 802, "Standard for Local and Metropolitan Area 1034 Networks: Multicast and Local Address Assignment", work in 1035 progress. 1037 [802.1Q] - "IEEE Standard for Local and metropolitan area networks / 1038 Media Access Control (MAC) Bridges and Virtual Bridge Local 1039 Area Networks", IEEE Std 802.1Q-2011, 31 August 2011. 1041 [802.3] - "IEEE Standard for Ethernet", IEEE Std 802.3-2012, 28 1042 December 2012. 1044 [802.11] - "IEEE Standard for Information technology / 1045 Telecommunications and information exchange between systems / 1046 Local and metropolitan area networks / Specific requirements / 1047 Part 11: Wireless LAN Medium Access Control (MAC) and Physical 1048 Layer (PHY) Specifications", IEEE Std 802.11-2012, 29 March 1049 2012. 1051 [DHCPmac] - B. Volz, T., Mrugalski, CJ. Bernardos, "Link-Layer 1052 Addresses Assignment Mechanism for DHCPv6", draft-ietf-dhc-mac- 1053 assign, work in progress. 1055 [SLAPquad] - CJ. Bernardos, A. Mourad, "SLAP quadrant selection 1056 options for DHCPv6", draft-ietf-dhc-slap-quadrant, work in 1057 progress. 1059 [EUI-64] - IEEE Registration Authority, "Guidelines for 64-bit Global 1060 Identifier (EUI-64(TM))", , November 2012. 1063 [IANA] - Internet Assigned Numbers Authority, . 1065 [IEEE802] - IEEE 802 LAN/MAN Standards Committee, 1066 . 1068 [IEEEtutorial] - IEEE, "Guidelines for Use of Extended Unique 1069 Identifier (EUI), Organizationally Unique Identifier (OUI), and 1070 Company ID (CID)", 1071 , 3 August 1073 2017. 1075 [InfiniBand] - InfiniBand Trade Association, "InfiniBand Architecture 1076 Specification Volume 1", November 2007. 1078 [RAC_OUI] - Parsons, G., "OUI Registry Restructuring", draft-ieee- 1079 rac-oui-restructuring-01.txt, work in Progress, September 2013. 1081 [RFC1112] - Deering, S., "Host extensions for IP multicasting", STD 1082 5, RFC 1112, August 1989. 1084 [RFC1661] - Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", 1085 STD 51, RFC 1661, July 1994. 1087 [RFC2153] - Simpson, W., "PPP Vendor Extensions", RFC 2153, May 1997. 1089 [RFC2332] - Luciani, J., Katz, D., Piscitello, D., Cole, B., and N. 1090 Doraswamy, "NBMA Next Hop Resolution Protocol (NHRP)", RFC 1091 2332, April 1998. 1093 [RFC2464] - Crawford, M., "Transmission of IPv6 Packets over Ethernet 1094 Networks", RFC 2464, December 1998. 1096 [RFC2606] - Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS 1097 Names", BCP 32, RFC 2606, June 1999. 1099 [RFC2784] - Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 1100 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, DOI 1101 10.17487/RFC2784, March 2000, . 1104 [RFC3092] - Eastlake 3rd, D., Manros, C., and E. Raymond, "Etymology 1105 of "Foo"", RFC 3092, April 1 2001. 1107 [RFC4291] - Hinden, R. and S. Deering, "IP Version 6 Addressing 1108 Architecture", RFC 4291, February 2006. 1110 [RFC4760] - Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 1111 "Multiprotocol Extensions for BGP-4", RFC 4760, January 2007. 1113 [RFC5214] - Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 1114 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, March 1115 2008. 1117 [RFC5332] - Eckert, T., Rosen, E., Ed., Aggarwal, R., and Y. Rekhter, 1118 "MPLS Multicast Encapsulations", RFC 5332, August 2008. 1120 [RFC5737] - Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address 1121 Blocks Reserved for Documentation", RFC 5737, January 2010. 1123 [RFC5798] - Nadas, S., Ed., "Virtual Router Redundancy Protocol 1124 (VRRP) Version 3 for IPv4 and IPv6", RFC 5798, March 2010. 1126 [RFC6034] - Thaler, D., "Unicast-Prefix-Based IPv4 Multicast 1127 Addresses", RFC 6034, October 2010. 1129 [RFC6328] - Eastlake 3rd, D., "IANA Considerations for Network Layer 1130 Protocol Identifiers", BCP 164, RFC 6328, DOI 10.17487/RFC6328, 1131 July 2011, 1133 [RFC6895] - Eastlake 3rd, D., "Domain Name System (DNS) IANA 1134 Considerations", BCP 42, RFC 6895, April 2013. 1136 [RFC7042] - Eastlake 3rd, D. and J. Abley, "IANA Considerations and 1137 IETF Protocol and Documentation Usage for IEEE 802 Parameters", 1138 BCP 141, RFC 7042, DOI 10.17487/RFC7042, October 2013, 1139 . 1141 [RFC7043] - Abley, J., "Resource Records for EUI-48 and EUI-64 1142 Addresses in the DNS", RFC 7043, October 2013. 1144 [RFC7319] - Eastlake 3rd, D., "IANA Considerations for Connectivity 1145 Fault Management (CFM) Code Points", BCP 191, RFC 7319, DOI 1146 10.17487/RFC7319, July 2014, . 1149 [RFC7961] - Eastlake 3rd, D. and L. Yizhou, "Transparent 1150 Interconnection of Lots of Links (TRILL): Interface Addresses 1151 APPsub-TLV", RFC 7961, DOI 10.17487/RFC7961, August 2016, 1152 . 1154 Appendix A. Templates 1156 This appendix provides the specific templates for IANA assignments of 1157 parameters. Explanatory words in parentheses in the templates below 1158 may be deleted in a completed template as submitted to IANA. 1160 A.1 EUI-48/EUI-64 Identifier or Identifier Block Template 1162 Applicant Name: 1164 Applicant Email: 1166 Applicant Telephone: (starting with country code) 1168 Use Name: (brief name of Parameter use such as "Foo Protocol" 1169 [RFC3092]) 1171 Document: (ID or RFC specifying use to which the identifier or block 1172 of identifiers will be put.) 1174 Specify whether this is an application for EUI-48 or EUI-64 1175 identifiers: 1177 Size of Block requested: (must be a power-of-two-sized block, can be 1178 a block of size one (2**0)) 1180 Specify multicast, unicast, or both: 1182 A.2 IANA OUI-Based Protocol Number Template 1184 Applicant Name: 1186 Applicant Email: 1188 Applicant Telephone: (starting with country code) 1190 Use Name: (brief name of use of code point such as "Foo Protocol") 1192 Document: (ID or RFC specifying use to which the protocol identifier 1193 will be put.) 1195 Note: (any additional note) 1197 A.3 Other IANA OUI-Based Parameter Template 1199 Applicant Name: 1201 Applicant Email: 1203 Applicant Telephone: (starting with country code) 1205 Protocol where the OUI-Based Parameter for which a value is being 1206 requested appears: (such as: Cipher Suite selection in IEEE 802.11) 1208 Use Name: (brief name of use of code point to be assigned, such as 1209 "Foo Cipher Suite" [RFC3092]) 1211 Document: (ID or RFC specifying use to which the other IANA OUI-based 1212 parameter value will be put.) 1214 Note: (any additional note) 1216 Appendix B. Ethertypes 1218 This appendix lists some Ethertypes specified for IETF protocols or 1219 by IEEE 802 as known at the time of publication. A more up-to-date 1220 list may be available on the IANA web site, currently at [IANA]. The 1221 IEEE Registration Authority page of Ethertypes, 1222 http://standards.ieee.org/regauth/ethertype/eth.txt, may also be 1223 useful. See Section 3 above. 1225 B.1. Some Ethertypes Specified by the IETF 1227 0x0800 Internet Protocol Version 4 (IPv4) 1228 0x0806 Address Resolution Protocol (ARP) 1229 0x0808 Frame Relay ARP 1230 0x22F3 TRILL 1231 0x22F4 L2-IS-IS 1232 0x8035 Reverse Address Resolution Protocol (RARP) 1233 0x86DD Internet Protocol Version 6 (IPv6) 1234 0x876B TCP/IP Compression 1235 0x876C IP Autonomous System 1236 0x880B Point-to-Point Protocol (PPP) 1237 0x880C General Switch Management Protocol (GSMP) 1238 0x8847 MPLS 1239 0x8848 MPLS with upstream-assigned label 1240 0x8861 Multicast Channel Allocation Protocol (MCAP) 1241 0x8863 PPP over Ethernet (PPPoE) Discovery Stage 1242 0x8864 PPP over Ethernet (PPPoE) Session Stage 1243 0x893B TRILL Fine Grained Labeling (FGL) 1244 0x8946 TRILL RBridge Channel 1245 0x894F NSH (Network Service Header) 1246 0x9A22 TRILL Multi Topology 1247 0xA0ED LoWPAN Encapsulation 1248 0xB7EA Control message channel inside GRE 1250 B.2. Some IEEE 802 Ethertypes 1252 0x8100 IEEE Std 802.1Q - Customer VLAN Tag Type (C-Tag, formerly 1253 called the Q-Tag) (initially Wellfleet) 1254 0x8808 IEEE Std 802.3 - Ethernet Passive Optical Network (EPON) 1255 0x888E IEEE Std 802.1X - 802.1X Port-based network access control 1256 0x88A8 IEEE Std 802.1Q - Service VLAN tag identifier (S-Tag) 1257 0x88B5 IEEE Std 802 - Local Experimental Ethertype 1258 0x88B6 IEEE Std 802 - Local Experimental Ethertype 1259 0x88B7 IEEE Std 802 - OUI Extended Ethertype 1260 0x88C7 IEEE Std 802.11 - Pre-Authentication (802.11i) 1261 0x88CC IEEE Std 802.1AB - Link Layer Discovery Protocol (LLDP) 1262 0x88E5 IEEE Std 802.1AE - Media Access Control Security 1263 0x88F5 IEEE Std 802.1Q - Multiple VLAN Registration Protocol 1264 (MVRP) 1265 0x88F6 IEEE Std 802.1Q - Multiple Multicast Registration 1266 Protocol (MMRP) 1267 0x890D IEEE Std 802.11 - Used for a variety of 802.11 Protocols: 1268 Fast Roaming Remote Request/Response 1269 Tunnelled Direct Link Setup 1270 Registered Location Query 1271 Fast Session Transfer 1272 0x8917 IEEE Std 802.21 - Media Independent Handover Protocol 1273 0x8929 IEEE Std 802.1Qbe - Multiple I-SID Registration Protocol 1274 0x8940 IEEE Std 802.1Qbg - ECP Protocol (also used in 802.1BR) 1276 Authors' Addresses 1278 Donald E. Eastlake 3rd 1279 Futurewei Technologies 1280 2386 Panoramic Circle 1281 Apopka, FL 32703 1282 USA 1284 Phone: +1-508-634-2066 1285 EMail: d3e3e3@gmail.com 1287 Joe Abley 1288 Hopcount Limited 1289 186 Albert Stree, Suite 103 1290 London, ON N6A 1M1 1291 Canada 1293 Phone: +1 519 670 9327 1294 EMail: jabley@hopcount.ca 1296 Copyright, Disclaimer, and Additional IPR Provisions 1298 Copyright (c) 2020 IETF Trust and the persons identified as the 1299 document authors. All rights reserved. 1301 This document is subject to BCP 78 and the IETF Trust's Legal 1302 Provisions Relating to IETF Documents 1303 (http://trustee.ietf.org/license-info) in effect on the date of 1304 publication of this document. Please review these documents 1305 carefully, as they describe your rights and restrictions with respect 1306 to this document. Code Components extracted from this document must 1307 include Simplified BSD License text as described in Section 4.e of 1308 the Trust Legal Provisions and are provided without warranty as 1309 described in the Simplified BSD License. This Internet-Draft is 1310 submitted in full conformance with the provisions of BCP 78 and BCP 1311 79.