idnits 2.17.1 draft-eastlake-rfc5342bis-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 15, 2013) is 3878 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 normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 5342 (Obsoleted by RFC 7042) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Donald Eastlake 2 INTERNET-DRAFT Huawei 3 Intended status: Best Current Practice Joe Abley 4 Obsoletes: 5342 ICANN 5 Updates: 2153 6 Expires: February 14, 2013 August 15, 2013 8 IANA Considerations and IETF Protocol and Documentation Usage 9 for IEEE 802 Parameters 10 12 Abstract 14 Some IETF protocols make use of Ethernet frame formats and IEEE 802 15 parameters. This document discusses some use of such parameters in 16 IETF protocols, specifies IANA considerations for assignment of 17 points under the IANA OUI (Organizationally Unique Identifier), and 18 provides some values for use in documentation. This document 19 obsoletes RFC 5342. 21 Status of This Memo 23 This Internet-Draft is submitted to IETF in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Distribution of this document is unlimited. Comments should be sent 27 to the authors. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF), its areas, and its working groups. Note that 31 other groups may also distribute working documents as Internet- 32 Drafts. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft 41 Shadow Directories can be accessed at 42 http://www.ietf.org/shadow.html. 44 Table of Contents 46 1. Introduction............................................3 47 1.1 Notations Used in This Document........................3 48 1.2 Changes from RFC 5342..................................4 49 1.3 The IEEE Registration Authority........................4 50 1.4 The IANA OUI...........................................4 52 2. Ethernet Identifier Parameters..........................5 53 2.1 48-Bit MAC Identifiers, OUIs, and Other Prefixes.......5 54 2.1.1 EUI-48 Assignments under the IANA OUI................6 55 2.1.2 EUI-48 Documentation Values..........................7 56 2.1.3 EUI-48 IANA Assignment Considerations................7 57 2.2 64-Bit MAC Identifiers.................................7 58 2.2.1 IPv6 Use of Modified EUI-64 Identifiers..............8 59 2.2.2 EUI-64 IANA Assignment Considerations................9 60 2.2.3 EUI-64 Documentation Values.........................11 61 2.3 Other MAC-48 Identifiers Used by IETF.................11 62 2.3.1 Identifiers Prefixed 33-33..........................12 63 2.3.2 The 'CF Series'.....................................12 64 2.3.2.1 Changes to RFC 2153...............................12 66 3. Ethernet Protocol Parameters...........................13 67 3.1 Ethernet Protocol Assignment under the IANA OUI.......14 68 3.2 Documentation Protocol Number.........................15 70 4. Other OUI-Based Parameters.............................16 72 5. IANA Considerations....................................17 73 5.1 Expert Review and IESG Ratification...................17 74 5.2 MAC Address AFNs and RRTYPEs..........................18 75 5.3 Informational IANA Web Page Material..................19 76 5.4 OUI Exhaustion........................................19 77 5.5 IANA OUI MAC Address Table............................19 78 5.6 SNAP Protocol Number Table and Assignment.............20 80 6. Security Considerations................................21 81 Acknowledgements..........................................21 82 Normative References......................................22 83 Informative References....................................22 85 Appendix A. Templates.....................................25 86 A.1 EUI-48/EUI-64 Identifier or Identifier Block Template.25 87 A.2 IANA OUI Based Protocol Number Template...............25 88 A.3 Other IANA OUI-Based Parameter Template...............26 89 Appendix B. Ethertypes....................................27 90 B.1 Some Ethertypes Specified by the IETF.................27 91 B.2 Some IEEE 802 Ethertypes..............................27 92 Appendix C: Documentation Protocol Number.................29 93 Appendix Z: Change History................................30 94 Authors' Addresses........................................32 96 1. Introduction 98 Some IETF protocols use Ethernet or other [IEEE] 802 related 99 communication frame formats and parameters [IEEE802]. These include 100 MAC (Media Access Control) identifiers and protocol identifiers. 102 This document specifies IANA considerations for the assignment of 103 code points under the IANA OUI. It also discusses some other IETF 104 use of IEEE 802 code points and provides some values for use in 105 documentation. As noted in [RFC2606] and [RFC5737], the use of 106 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 [RFC5226] is incorporated herein except where there are contrary 111 provisions in this document. In this document "IESG Ratification" is 112 used, in some cases and it is specified in Section 5.1. This is not 113 the same as "IESG Approval" in [RFC5226]. 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 bit ordering although 121 the physical order of bit transmission within an octet on an IEEE 122 [802.3] link is from the lowest order bit to the highest order bit 123 (i.e., the reverse of the IETF's ordering). 125 In this document: 127 "AFN" stands for Address Family Number [RFC4760]. 129 "EUI" stands for Extended Unique Identifier. 131 "IAB" stands for Individual Address Block, not for Internet 132 Architecture Board. 134 "MAC" stands for Media Access Control, not for Message Authentication 135 Code. 137 "OUI" stands for Organizationally Unique Identifier. 139 "RRTYPE" stands for a DNS Resource Record type [RFC6895]. 141 "**" indicates exponentiation. For example, 2**24 is two to the 142 twenty-fourth power. 144 1.2 Changes from RFC 5342 146 Add MAC addresses and IANA OUI-based protocol and other values for 147 use in documentation and add relevant Security Considerations 148 language. 150 Eliminate any requirements for parallel unicast and multicast 151 assignment unless requested. Such requirements had been included in 152 [RFC5342] on the theory they would make bookkeeping easier for IANA 153 but have proved to be problematic in practice. 155 Re-cast informational material about relevant IEEE assignment 156 policies to take into account [RAC-OUIdraft]. 158 Add AFNs and RRTYPEs for 48-bit and 64-bit MACs. 160 1.3 The IEEE Registration Authority 162 Originally the responsibility of Xerox Corporation, the registration 163 authority for Ethernet parameters is now the IEEE Registration 164 Authority, available on the web at: 166 http://standards.ieee.org/regauth/ 168 Anyone may apply to that Authority for parameters. They may impose 169 fees or other requirements but commonly waive fees for applications 170 from standards development organizations. 172 A list of some assignments and their holders is downloadable from the 173 IEEE Registration Authority site. 175 1.4 The IANA OUI 177 The OUI 00-00-5E has been assigned to IANA. 179 There is no OUI value reserved at this time for documentation but 180 there are documentation code points under the IANA OUI specified 181 below. 183 2. Ethernet Identifier Parameters 185 Section 2.1 discusses EUI-48 (Extended Unique Identifier 48) MAC 186 identifiers, their relationship to OUIs and other prefixes, and 187 assignments under the IANA OUI. Section 2.2 extends this to EUI-64 188 identifiers. Section 2.3 discusses other IETF MAC identifier use not 189 under the IANA OUI. 191 [RAC-OUIdraft] indicates that the IEEE Registration Authority 192 Committee is exploring the feasibility of defining a new "EUI-128" 193 identifier. 195 2.1 48-Bit MAC Identifiers, OUIs, and Other Prefixes 197 48-bit MAC "addresses" are the most commonly used Ethernet interface 198 identifiers. Those that are globally unique are also called EUI-48 199 identifiers. An EUI-48 is structured into an initial 3-octet OUI 200 (Organizationally Unique Identifier) and an additional 3 octets 201 assigned by the OUI holder or into a larger initial prefix assigned 202 to an organization and a shorter sequence of additional bits so as to 203 add up to 48 bits in total. For example, the IEEE has assigned IABs 204 (Individual Address Blocks), where the first 4 1/2 octets (36 bits) 205 are assigned, giving the holder of the IAB 1 1/2 octets (12 bits) 206 they can control; however, IABs will become historic and a wider 207 range of prefix lengths will be made available [RAC-OUIdraft]. 209 The IEEE describes its assignment procedures and policies for IEEE 210 802 related identifiers in [802_O&A] which is being revised. 212 Two bits within the initial octet of an EUI-48 have special 213 significance in MAC addresses: the Group bit (01) and the Local bit 214 (02). OUIs and longer MAC prefixes are assigned with the Local bit 215 zero and the Group bit unspecified. Multicast identifiers may be 216 constructed by turning on the Group bit, and unicast identifiers 217 constructed by leaving the Group bit zero. 219 For globally unique EUI-48 identifiers assigned by an OUI or longer 220 prefix owner, the Local bit is zero. If the Local bit is a one, the 221 identifier has been considered by IEEE 802 to be a local identifier 222 under the control of the local network administrator; however, there 223 may be emerging recommendations from the IEEE Registration Authority 224 on management of the local address space. If the Local bit is on, 225 the holder of an OUI has no special authority over MAC identifiers 226 whose first 3 octets correspond to their OUI. 228 An AFN and a DNS RRTYPE have been assigned for 48-bit MAC addresses 229 (see Section 5.2). 231 2.1.1 EUI-48 Assignments under the IANA OUI 233 The OUI 00-00-5E has been assigned to IANA as stated in Section 1.4 234 above. This includes 2**24 EUI-48 multicast identifiers from 235 01-00-5E-00-00-00 to 01-00-5E-FF-FF-FF and 2**24 EUI-48 unicast 236 identifiers from 00-00-5E-00-00-00 to 00-00-5E-FF-FF-FF. 238 Of these EUI-48 identifiers, the sub-blocks reserved or thus far 239 assigned by IANA those for purposes of documentation, are as follows: 241 Unicast, all blocks of 2**8 addresses thus far: 243 00-00-5E-00-00-00 through 00-00-5E-00-00-FF: reserved and require 244 IESG Ratification for assignment (see Section 5.1). 246 00-00-5E-00-01-00 through 00-00-5E-00-01-FF: assigned for the 247 Virtual Router Redundancy Protocol (VRRP) [RFC5798]. 249 00-00-5E-00-02-00 through 00-00-5E-00-02-FF: assigned for the IPv6 250 Virtual Router Redundancy Protocol (VRRP IPv6) [RFC5798]. 252 00-00-5E-00-52-00 through 00-00-5E-00-52-FF: being used for very 253 small assignments. Currently 3 out of these 256 values have 254 been assigned. 256 00-00-5E-00-53-00 through 00-00-5E-00-53-FF: assigned for use in 257 documentation. 259 Multicast: 261 01-00-5E-00-00-00 through 01-00-5E-7F-FF-FF: 2**23 addresses 262 assigned for IPv4 multicast [RFC1112]. 264 01-00-5E-80-00-00 through 01-00-5E-8F-FF-FF: 2**20 addresses 265 assigned for MPLS multicast [RFC5332]. 267 01-00-5E-90-00-00 through 01-00-5E-90-00-FF: 2**8 addresses being 268 used for very small assignments. Currently 4 out of these 269 256 values have been assigned. 271 01-00-5E-90-10-00 through 01-00-5E-90-10-FF: 2**8 addresses for 272 use in documentation. 274 For more detailed and up-to-date information, see the Ethernet Number 275 registry at http://www.iana.org. 277 2.1.2 EUI-48 Documentation Values 279 The following values have been assigned for use in documentation: 281 00-00-5E-00-53-00 through 00-00-5E-00-53-FF for unicast and 283 01-00-5E-90-10-00 through 01-00-5E-90-10-FF for multicast. 285 2.1.3 EUI-48 IANA Assignment Considerations 287 EUI-48 assignments under the current or a future IANA OUI (see 288 Section 5.4) must meet the following requirements: 290 o must be for standards purposes (either for an IETF Standard or 291 other standard related to IETF work), 293 o must be for a block of a power-of-two identifiers starting at a 294 boundary that is an equal or greater power of two, including 295 the assignment of one (2**0) identifier, 297 o must not be used to evade the requirement for vendors to obtain 298 their own block of identifiers from the IEEE, and 300 o must be documented in an Internet-Draft or RFC. 302 In addition, approval must be obtained as follows (see the procedure 303 in Section 5.1): 305 Small to medium assignments of a block of 1, 2, 4, ..., 32768, 306 65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI-48 identifiers 307 require Expert Review. 309 Large assignments of 131072 (2**17) or more EUI-48 identifiers 310 require IESG Ratification (see Section 5.1). 312 ([RFC5342] had a requirement for parallel unicast and multicast 313 assignments under some circumstances even when one of the types was 314 not included in the application. That requirement has proven 315 impractical and is eliminated in this document.) 317 2.2 64-Bit MAC Identifiers 319 IEEE also defines a system of 64-bit MAC identifiers including 320 EUI-64s. EUI-64 identifiers are currently used as follows: 322 o In a modified form to construct some IPv6 Interface Identifiers 323 as described in Section 2.2.1 325 o In IEEE Std 1394 (also known as FireWire and i.Link) 327 o In IEEE Std 802.15.4 (also known as ZigBee) 329 o In [InfiniBand] 331 Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) OUI, or a 332 shorter extension to longer assigned prefixes [RAC-OUIdraft] so as to 333 total 64 bits, produces an EUI-64 identifier under that OUI or longer 334 prefix. As with EUI-48 identifiers, the first octet has the same 335 Group and Local bits. 337 An AFN and a DNS RRTYPE have been assigned for 64-bit MAC addresses 338 (see Section 5.2). 340 The discussion below is almost entirely in terms of the "Modified" 341 form of EUI-64 identifiers; however, anyone assigned such an 342 identifier can also use the unmodified form as a MAC identifier on 343 any link that uses such 64-bit identifiers for interfaces. 345 2.2.1 IPv6 Use of Modified EUI-64 Identifiers 347 MAC-64 identifiers are used to form the lower 64 bits of some IPv6 348 addresses (Section 2.5.1 and Appendix A of [RFC4291] and Appendix A 349 of [RFC5214]). When so used, the MAC-64 is modified by inverting the 350 Local/Global bit to form an IETF "Modified EUI-64 identifier". Below 351 is an illustration of a Modified EUI-64 unicast identifier under the 352 IANA OUI, where aa-bb-cc-dd-ee is the extension. 354 02-00-5E-aa-bb-cc-dd-ee 356 The first octet is shown as 02 rather than 00 because, in Modified 357 EUI-64 identifiers, the sense of the Local/Global bit is inverted 358 compared with EUI-48 identifiers. It is the globally unique values 359 (universal scope) that have the 02 bit on in the first octet, while 360 those with this bit off are locally assigned and out of scope for 361 global assignment. 363 The Local/Global bit was inverted to make it easier for network 364 operators to type in local-scope identifiers. Thus, such Modified 365 EUI-64 identifiers as 1, 2, etc. (ignoring leading zeros), are 366 local. Without the modification, they would have to be 367 02-00-00-00-00-00-00-01, 02-00-00-00-00-00-00-02, etc., to be local. 369 As with MAC-48 identifiers, the 01 bit on in the first octet 370 indicates a group identifier. 372 When the first two octets of the extension of a Modified EUI-64 373 identifier are FF-FE, the remainder of the extension is a 24-bit 374 value as assigned by the OUI owner for an EUI-48. For example: 376 02-00-5E-FF-FE-yy-yy-yy 377 or 378 03-00-5E-FF-FE-yy-yy-yy 380 where yy-yy-yy is the portion (of an EUI-48 global unicast or 381 multicast identifier) that is assigned by the OUI owner (IANA in this 382 case). Thus, any holder of one or more EUI-48 identifiers under the 383 IANA OUI also has an equal number of Modified EUI-64 identifiers that 384 can be formed by inserting FF-FE in the middle of their EUI-48 385 identifiers and inverting the Local/Global bit. 387 (Note: [EUI-64] defines FF-FF as the bits to be inserted to create 388 an IEEE EUI-64 identifier from a MAC-48 identifier. That document 389 says the FF-FE value is used when starting with an EUI-48 390 identifier. The IETF uses only FF-FE to create Modified EUI-64 391 identifiers from 48-bit Ethernet station identifiers regardless of 392 whether they are EUI-48 or MAC-48 local identifiers. EUI-48 and 393 local MAC-48 identifiers are syntactically equivalent, and this 394 doesn't cause any problems in practice.) 396 In addition, certain Modified EUI-64 identifiers under the IANA OUI 397 are reserved for holders of IPv4 addresses as follows: 399 02-00-5E-FE-xx-xx-xx-xx 401 where xx-xx-xx-xx is a 32-bit IPv4 address. The owner of an IPv4 402 address has both the unicast and multicast derived EUI-64 bit 403 address. Modified EUI-64 identifiers from 405 02-00-5E-FE-F0-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF 407 are effectively reserved pending the specification of IPv4 Class E 408 addresses. However, for Modified EUI-64 identifiers based on an IPv4 409 address, the Local/Global bit should be set to correspond to whether 410 the IPv4 address is local or global. (Keep in mind that the sense of 411 the Modified EUI-64 identifier Local/Global bit is reversed from that 412 in (unmodified) MAC-64 identifiers.) 414 2.2.2 EUI-64 IANA Assignment Considerations 416 The following table shows which Modified EUI-64 identifiers under the 417 IANA OUI are reserved, assigned, or available as indicated. As noted 418 above, the corresponding MAC addresses can be determined by 419 complementing the 02 bit in the first octet. In all cases, the 420 corresponding multicast 64-bit MAC addresses formed by complementing 421 the 01 bit in the first octet have the same status as the modified 422 64-bit unicast address blocks listed below. 424 02-00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF reserved 426 02-00-5E-10-00-00-00-00 to 02-00-5E-10-00-00-00-FF assigned for 427 documentation use 429 02-00-5E-EF-10-00-00-00 to 02-00-5E-EF-FF-FF-FF-FF, which is 430 available for assignment 432 02-00-5E-F0-00-00-00-00 to 02-00-5E-FD-FF-FF-FF-FF reserved 434 02-00-5E-FE-00-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF assigned to 435 IPv4 address holders as described above 437 02-00-5E-FF-00-00-00-00 to 02-00-5E-FF-FD-FF-FF-FF reserved 439 02-00-5E-FF-FE-00-00-00 to 02-00-5E-FF-FE-FF-FF-FF assigned for 440 holders of EUI-48 identifiers under the IANA OUI as 441 described above 443 02-00-5E-FF-FF-00-00-00 to 02-00-5E-FF-FF-FF-FF-FF reserved 445 The reserved identifiers above require IESG Ratification (see Section 446 5.1) for assignment. IANA EUI-64 identifier assignments under the 447 IANA OUI must meet the following requirements: 449 o must be for standards purposes (either for an IETF Standard or 450 other standard related to IETF work), 452 o must be for a block of a power-of-two identifiers starting at a 453 boundary that is an equal or greater power of two, including 454 the assignment of one (2**0) identifier, 456 o must not be used to evade the requirement for vendors to obtain 457 their own block of identifiers from the IEEE, and 459 o must be documented in an Internet Draft or RFC. 461 In addition, approval must be obtained as follows (see the procedure 462 in Section 5.1): 464 Small to medium assignments of a block of 1, 2, 4, ..., 134217728, 465 268435456 (2**0, 2**1, 2**2, ..., 2**27, 2**28) EUI-64 466 identifiers require Expert Review. 468 Assignments of any size, including 536870912 (2**29) or more 469 EUI-64 identifiers, may be made with IESG Ratification (see 470 Section 5.1). 472 2.2.3 EUI-64 Documentation Values 474 The following blocks of unmodified 64-bit MAC addresses are for 475 documentation use. The IPv4 derived addresses are based on the IPv4 476 documentation addresses [RFC5737] and the MAC derived addresses are 477 based on the EUI-48 documentation addresses above. 479 Unicast: 481 00-00-5E-EF-10-00-00-00 to 00-00-5E-EF-10-00-00-FF general 483 00-00-5E-FE-C0-00-02-00 to 00-00-5E-FE-C0-00-02-FF and 484 00-00-5E-FE-C6-33-64-00 to 00-00-5E-FE-C6-33-64-FF and 485 00-00-5E-FE-CB-00-71-00 to 00-00-5E-FE-CB-00-71-FF IPv4 derived 487 00-00-5E-FF-FE-00-53-00 to 00-00-5E-FF-FE-00-53-FF EUI-48 derived 489 00-00-5E-FE-EA-C0-00-02 and 490 00-00-5E-FE-EA-C6-33-64 and 491 00-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 492 [RFC6034] 494 Multicast: 496 01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general 498 01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and 499 01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and 500 01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived 502 01-00-5E-FE-EA-C0-00-02 and 503 01-00-5E-FE-EA-C6-33-64 and 504 01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast 505 [RFC6034] 507 01-00-5E-FF-FE-90-10-00 to 01-00-5E-FF-FE-90-10-FF EUI-48 derived 509 2.3 Other MAC-48 Identifiers Used by IETF 511 There are two other blocks of MAC-48 identifiers that are used by the 512 IETF as described below. 514 2.3.1 Identifiers Prefixed 33-33 516 All MAC-48 multicast identifiers prefixed "33-33" (that is, the 2**32 517 multicast MAC identifiers in the range from 33-33-00-00-00-00 to 518 33-33-FF-FF-FF-FF) are used as specified in [RFC2464] for IPv6 519 multicast. In all these identifiers, the Group bit (the bottom bit 520 of the first octet) is on, as is required to work properly with 521 existing hardware as a multicast identifier. They also have the 522 Local bit on and are used for this purpose in IPv6 networks. 524 (Historical note: It was the custom during IPv6 design to use "3" 525 for unknown or example values, and 3333 Coyote Hill Road, Palo 526 Alto, California, is the address of PARC (Palo Alto Research 527 Center, formerly "Xerox PARC"). Ethernet was originally specified 528 by Digital Equipment Corporation, Intel Corporation, and Xerox 529 Corporation. The pre IEEE [802.3] Ethernet protocol has sometimes 530 been known as "DIX" Ethernet from the first letters of the names 531 of these companies.) 533 2.3.2 The 'CF Series' 535 The Informational [RFC2153] declared the 3-octet values from CF-00-00 536 through CF-FF-FF to be OUIs available for assignment by IANA to 537 software vendors for use in PPP [RFC1661] or for other uses where 538 vendors do not otherwise need an IEEE-assigned OUI. It should be 539 noted that, when used as MAC-48 prefixes, these values have the Local 540 and Group bits on, while all IEEE-assigned OUIs thus far have those 541 bits off. The Group bit is meaningless in PPP. To quote [RFC2153]: 542 "The 'CF0000' series was arbitrarily chosen to match the PPP NLPID 543 'CF', as a matter of mnemonic convenience." 545 CF-00-00 is reserved, and IANA lists multicast identifier 546 CF-00-00-00-00-00 as used for Ethernet loopback tests. 548 In over a decade of availability, only a handful of values in the 'CF 549 Series' have been assigned. (See http://www.iana.org under both 550 Ethernet Parameters and PPP Parameters.) 552 2.3.2.1 Changes to RFC 2153 554 The IANA Considerations in [RFC2153] are updated as follows (no 555 technical changes are made): Use of these identifiers based on IANA 556 assignment is deprecated. IANA is directed not to assign any further 557 values in the 'CF Series'. 559 3. Ethernet Protocol Parameters 561 Ethernet protocol parameters provide a means of indicating the 562 contents of a frame -- for example, that its contents are IPv4 or 563 IPv6. 565 The concept has been extended to labeling by "tags". A tag in this 566 sense is a prefix whose type is identified by an Ethertype that is 567 then followed by either another tag, an Ethertype, or an LSAP 568 protocol indicator for the "main" body of the frame, as described 569 below. Traditionally in the [802_O&A] world, tags are fixed length 570 and do not include any encoding of their own length. Any device that 571 is processing a frame cannot, in general, safely process anything in 572 the frame past an Ethertype it does not understand. An example is 573 the C-tag (formerly the Q-tag) [802.1Q]. It provides customer VLAN 574 and priority information for a frame. 576 There are two types of protocol identifier parameters that can occur 577 in Ethernet frames after the initial MAC-48 destination and source 578 identifiers: 580 Ethertypes: These are 16-bit identifiers appearing as the initial 581 two octets after the MAC destination and source (or after a 582 tag) which, when considered as an unsigned integer, are equal 583 to or larger than 0x0600. 585 LSAPs: These are 8-bit protocol identifiers that occur in pairs 586 immediately after an initial 16-bit (two octet) remaining frame 587 length, which is in turn after the MAC destination and source 588 (or after a tag). Such a length must, when considered as an 589 unsigned integer, be less than 0x5DC or it could be mistaken as 590 an Ethertype. LSAPs (Link-Layer Subnet Access Points) occur in 591 pairs where one is intended to indicate the source protocol 592 handler and one the destination protocol handler; however, use 593 cases where the two are different have been relatively rare. 595 Neither Ethertypes nor LSAPs are assigned by IANA; they are assigned 596 by the IEEE Registration Authority (see Section 1.3 above and the 597 Ethertype Annex below). However, both LSAPs and Ethertypes have 598 extension mechanisms so that they can be used with five-octet 599 Ethernet protocol identifiers under an OUI, including those assigned 600 by IANA under the IANA OUI. 602 When using the IEEE 802 LLC format (SNAP) [802_O&A] for a frame, an 603 OUI-based protocol identifier can be expressed as follows: 605 xx-xx-AA-AA-03-yy-yy-yy-zz-zz 607 where xx-xx is the frame length and, as above, must be small enough 608 not to be confused with an Ethertype; "AA" is the LSAP that indicates 609 this use and is sometimes referred to as the SNAP SAP; "03" is the 610 LLC control octet indicating datagram service; yy-yy-yy is an OUI; 611 and zz-zz is a protocol number, under that OUI, assigned by the OUI 612 owner. The odd five-octet length for such OUI-based protocol 613 identifiers was chosen so that, with the LLC control octet ("03"), 614 the result is 16-bit aligned. 616 When using an Ethertype to indicate the main type for a frame body, 617 the special "OUI Extended Ethertype" 88-B7 is available. Using this 618 Ethertype, a frame body can begin with 620 88-B7-yy-yy-yy-zz-zz 622 where yy-yy-yy and zz-zz have the same meaning as in the SNAP format 623 described above. 625 It is also possible, within the SNAP format, to use an arbitrary 626 Ethertype. Putting the Ethertype as the zz-zz field after an all 627 zeros OUI (00-00-00) does this. It looks like 629 xx-xx-AA-AA-03-00-00-00-zz-zz 631 where zz-zz is the Ethertype. 633 (Note that, at this point, the 802 protocol syntax facilities are 634 sufficiently powerful that they could be chained indefinitely. 635 Whether support for such chaining is generally required is not clear, 636 but [802_O&A] requires support for 638 xx-xx-AA-AA-03-00-00-00-88-B7-yy-yy-yy-zz-zz 640 although this could be more efficiently expressed by simply pinching 641 out the "00-00-00-88-B7" in the middle.) 643 As well as labeling frame contents, 802 Protocol types appear within 644 NBMA (Non-Broadcast Multi-Access) Next Hop Resolution Protocol 645 [RFC2332] messages. Such messages have provisions for both two octet 646 Ethertypes and OUI based protocol types. 648 3.1 Ethernet Protocol Assignment under the IANA OUI 650 Two-octet protocol numbers under the IANA OUI are available, as in 652 xx-xx-AA-AA-03-00-00-5E-qq-qq 654 where qq-qq is the protocol number. 656 A number of such assignments have been made out of the 2**16 protocol 657 numbers available from 00-00-5E-00-00 to 00-00-5E-FF-FF (see [IANA]). 658 The extreme values of this range, 00-00-5E-00-00 and 00-00-5E-FF-FF, 659 are reserved and require IESG Ratification for assignment (see 660 Section 5.1). New assignments of SNAP SAP protocol (qq-qq) numbers 661 under the IANA OUI must meet the following requirements: 663 o the assignment must be for standards use (either for an IETF 664 Standard or other standard related to IETF work), 666 o it must be documented in an Internet-Draft or RFC, and 668 o such protocol numbers are not to be assigned for any protocol 669 that has an Ethertype (because that can be expressed by putting 670 an all zeros "OUI" before the Ethertype as described above). 672 In addition, the Expert Review (or IESG Ratification for the two 673 reserved values) must be obtained using the procedure specified in 674 Section 5.1. 676 3.2 Documentation Protocol Number 678 0x0042 is a protocol number under the IANA OUI (that is, 679 00-00-5E-00-42) to be used for documentation purposes. 681 4. Other OUI-Based Parameters 683 Some IEEE 802 and other protocols provide for parameters based on an 684 OUI beyond those discussed above. Such parameters most commonly 685 consist of an OUI plus one octet of additional value. They are 686 usually called "vendor specific" parameters, although "organization 687 specific" might be more accurate. They would look like 689 yy-yy-yy-zz 691 where yy-yy-yy is the OUI and zz is the additional specifier. An 692 example is the Cipher Suite Selector in IEEE [802.11]. 694 Values may be assigned under the IANA OUI for such other OUI-based 695 parameter usage by Expert Review except that, for each use, the 696 additional specifier values consisting of all zero bits and all one 697 bits (0x00 (00-00-5E-00) and 0xFF (00-00-5E-FF) for a one-octet 698 specifier) are reserved and require IESG Ratification (see Section 699 5.1) for assignment; also, the additional specifier value 0x42 700 (00-00-5E-42) is assigned for use in documentation. 702 Assignments of such other IANA OUI-based parameters must be for 703 standards use (either for an IETF Standard or other standard related 704 to IETF work) and be documented in an Internet-Draft or RFC. The 705 first time a value is assigned for a particular parameter of this 706 type, an IANA registry will be created to contain that assignment and 707 any subsequent assignments of values for that parameter under the 708 IANA OUI. The Expert will specify the name of the registry. 710 If different policies from those above are required for such a 711 parameter, a BCP or Standards Track RFC must be adopted updating this 712 BCP and specifying the new policy and parameter. 714 5. IANA Considerations 716 The entirety of this document concerns IANA Considerations for the 717 assignment of Ethernet parameters in connection with the IANA OUI and 718 related matters. 720 As this document replaces [RFC5342], references to [RFC5342] in IANA 721 registries should be replaced by references to this document. In 722 addition, any references in the registries to draft-jabley- 723 eui48-eui64-doc-addr, which has been combined into this document, 724 should be replaced with references to this document. 726 This document does not create any new IANA registries. 728 This document assigns MAC address values for documentation but those 729 values are already in the appropriate IANA tables due to draft- 730 jabley-eui48-eui64-doc-addr. The only other assignment made by this 731 document is a protocol number for documentation in Section 5.6. 733 No existing assignment is changed by this document. 735 5.1 Expert Review and IESG Ratification 737 This section specifies the procedure for Expert Review and IESG 738 Ratification of MAC, protocol, and other IANA OUI-based identifiers. 739 The Expert(s) referred to in this document shall consist of one or 740 more persons appointed by and serving at the pleasure of the IESG. 741 The procedure described for Expert Review assignments in this 742 document is fully consistent with the IANA Expert Review policy 743 described in Section 4.1 of [RFC5226]. 745 While finite, the universe of code points from which Expert judged 746 assignments will be made is felt to be large enough that the 747 requirements given in this document and the Experts' good judgment 748 are sufficient guidance. The idea is for the Expert to provide a 749 light sanity check for small assignments of EUI identifiers with 750 increased scrutiny by the Expert for medium-sized assignments of EUI 751 identifiers, and assignments of protocol identifiers and other IANA 752 OUI based parameters. However, it can make sense to assign very 753 large portions of the MAC identifier code point space. (Note that 754 existing assignments include one for 1/2 of the entire multicast IANA 755 EUI-48 code point space and one for 1/16 of that multicast code point 756 space.) In those cases, and in cases of the assignment of "reserved" 757 values, IESG Ratification of an Expert Review approval recommendation 758 is required as described below. The procedure is as follows: 760 The applicant always completes the appropriate Template from the 761 Template Annex below and sends it to IANA . 763 IANA always sends the Template to an appointed Expert. If the 764 Expert recuses themselves or is non-responsive, IANA may choose 765 an alternative appointed Expert or, if none is available, will 766 contact the IESG. 768 In all case, if IANA receives a disapproval from an Expert 769 selected to review an application Template, the application 770 will be denied. 772 If the assignment is based on Expert Review: 774 If IANA receives approval and code points are available, 775 IANA will make the requested assignment. 777 If the assignment is based on IESG Ratification: 779 The procedure starts with the first steps above for Expert 780 Review. If the Expert disapproves the application, they 781 simply inform IANA; however, if the Expert believes the 782 application should be approved, or is uncertain and believes 783 that the circumstances warrant the attention of the IESG, 784 the Expert will inform IANA about their advice and IANA will 785 forward the application, together with the reasons for 786 approval or uncertainty, to the IESG. The IESG must decide 787 whether the assignment will be granted. This can be 788 accomplished by a management item in an IESG telechat as 789 done for other types of requests. If the IESG decides not 790 to ratify a favorable opinion by the Expert or decides 791 against an application where the Expert is uncertain, the 792 application is denied, otherwise it is granted. The IESG 793 will communicate its decision to the Expert and to IANA. 795 5.2 MAC Address AFNs and RRTYPEs 797 IANA has assigned Address Family Numbers (AFNs) for MAC addresses as 798 follows: 800 AFN Decimal Hex Reference 801 ---------- ------- ------ --------------- 802 48-bit MAC 16389 0x4005 [This document] 803 64-bit MAC 16390 0x4006 [This documnet] 805 IANA has assigned DNS RRTYPEs [RFC6895] for MAC addresses as follows: 807 RRTYPE Code 808 Data Mnemonic Decimal Hex Reference 809 ---------- -------- ------- ------ ----------- 810 48-bit MAC EUI48 108 0x006C [EUIRRTYPE] 811 64-bit MAC EUI64 109 0x006D [EUIRRTYPE] 813 5.3 Informational IANA Web Page Material 815 IANA also maintains an informational listing on its web site 816 concerning Ethertypes, OUIs, and multicast addresses assigned under 817 OUIs other than the IANA OUI. The title of this information registry 818 is "IEEE 802 Numbers". IANA will merge in the Ethertypes listed in 819 Appendix B that are not already included and will update that 820 informational registry when changes are provided by the Expert. 822 5.4 OUI Exhaustion 824 When the available space for either multicast or unicast EUI-48 825 identifiers under OUI 00-00-5E have been 90% or more exhausted, IANA 826 should request an additional OUI from the IEEE Registration Authority 827 for further IANA assignment use. The appointed Expert(s) should 828 monitor for this condition and notify IANA. 830 The preceding paragraph should be included in the IANA Registry as a 831 Note. 833 5.5 IANA OUI MAC Address Table 835 No changes are required in the "IANA Unicast 48-bit MAC Addresses" 836 and "IANA Multicast 48-bit MAC Addresses" tables except for the 837 updates to references specified in the first part of Section 5. 839 The Note preceeding the "IANA 64-bit MAC Addresses" table should be 840 as follows: 842 "These values are prefixed with 00-00-5E to form unicast MAC 843 addresses, with 01-00-5E to form multicast MAC addresses, with 844 02-00-5E to form unicast modified EUI-64 addresses, and with 845 03-00-5E to form multicast modified EUI-64 addresses. See [this 846 document] for more details." 848 5.6 SNAP Protocol Number Table and Assignment 850 The "SNAP PROTOCOL IDs" table is renamed the "SNAP Protocol Numbers" 851 table. The Note for that table and column headers are changed by 852 replacing "PID" with "protocol number". 854 IANA will assign 0x0042 as the SNAP protocol number under the IANA 855 OUI to be used for documentation purposes. 857 6. Security Considerations 859 This document is concerned with assignment of parameters under the 860 IANA OUI and closely related matters. It is not directly concerned 861 with security except as follows: 863 Confusion and conflict can be caused by the use of MAC addresses or 864 other OUI derived protocol parameters as examples in documentation. 865 Examples used "only" in documentation can end up being coded and 866 released or cause conflicts due to later real use and the possible 867 acquisition of intellectual property rights in such addresses or 868 parameters. The reservation herein of MAC addresses and parameters 869 for documentation purposes will minimize such confusion and conflict. 871 See [EUIRRTYPE] for security considerations in storing MAC addresses 872 in the DNS. 874 Acknowledgements 876 The comments and suggestions of the following people, listed in 877 alphabetic order, is gratefully acknowledged: 879 This document: 880 David Black, Adrian Farrel, Bob Grow, Joel Jaeggli, Pearl Liang, 881 Glenn Parsons, Pete Resnick, and Dan Romascanu 883 RFC 5342: 884 Bernard Aboba, Scott O. Bradner, Ian Calder, Michelle Cotton, Lars 885 Eggert, Eric Gray, Alfred Hoenes, Russ Housley, Charlie Kaufman, 886 Erik Nordmark, Dan Romascanu, Mark Townsley, and Geoff Thompson. 888 The document was prepared in raw nroff. All macros used were defined 889 within the source file. 891 Normative References 893 [802_O&A] 895 - "IEEE Standard for Local and Metropolitan Area Networks: 896 Overview and Architecture", IEEE Std 802-2001, 8 March 2002. 898 - "IEEE Standard for Local and Metropolitan Area Networks: 899 Overview and Architecture / Amendment 1: Ethertypes for 900 Prototype and Vendor-Specific Protocol Development", IEEE Std 901 802a-2003, 18 September 2003. 903 [RFC5226] - Narten, T. and H. Alvestrand, "Guidelines for Writing an 904 IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 905 2008. 907 Informative References 909 [802.1Q] - "IEEE Standard for Local and metropolitan area networks / 910 Media Access Control (MAC) Bridges and Virtual Bridge Local 911 Area Networks", IEEE Std 802.1Q-2011, 31 August 2011. 913 [802.3] - "IEEE Standard for Information technology / 914 Telecommunications and information exchange between systems / 915 Local and metropolitan area networks / Specific requirements / 916 Part 3: Carrier sense multiple access with Collision Detection 917 (CSMA/CD) Access Method and Physical Layer Specifications", 918 IEEE Std 802.3-2008, 26 December 2008. 920 [802.11] - "IEEE Standard for Information technology / 921 Telecommunications and information exchange between systems / 922 Local and metropolitan area networks / Specific requirements / 923 Part 11: Wireless LAN Medium Access Control (MAC) and Physical 924 Layer (PHY) Specifications", IEEE Std 802.11-2012, 29 March 925 2012. 927 [EUI-64] - IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) 928 Registration Authority", , March 1997. 931 [EUIRRTYPE] - J. Abley, "Resource Records for EUI-48 and EUI-64 932 Addresses in the DNS", draft-jabley-dnsext-eui48-eui64-rrtypes, 933 work in progress. 935 [IANA] - Internet Assigned Numbers Authority, . 937 [IEEE] - Institute of Electrical and Electronics Engineers, 938 . 940 [IEEE802] - IEEE 802 LAN/MAN (Local Area Network / Metropolitan Area 941 Network) Standards Committee, . 943 [InfiniBand] - InfiniBand Trade Associaiton, "InfiniBand Architecture 944 Specification Volume 1", November 2007. 946 [RAC-OUIdraft] - G. Parsons, "OUI Registry Restructing", draft-ieee- 947 rac-oui-restructuring, work in progress. 949 [RFC1112] - Deering, S., "Host Extensions for IP Multicasting", STD 950 5, RFC 1112, Stanford University, August 1989. 952 [RFC1661] - Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, 953 RFC 1661, July 1994. 955 [RFC2153] - Simpson, W., "PPP Vendor Extensions", RFC 2153, May 1997. 957 [RFC2332] - Luciani, J., Katz, D., Piscitello, D., Cole, B., and N. 958 Doraswamy, "NBMA Next Hop Resolution Protocol (NHRP)", RFC 959 2332, April 1998. 961 [RFC2464] - Crawford, M., "Transmission of IPv6 Packets over Ethernet 962 Networks", RFC 2464, December 1998. 964 [RFC2606] - Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS 965 Names", BCP 32, RFC 2606, June 1999. 967 [RFC3092] - Eastlake 3rd, D., Manros, C., and E. Raymond, "Etymology 968 of "Foo"", RFC 3092, April 1 2001. 970 [RFC4291] - Hinden, R. and S. Deering, "IP Version 6 Addressing 971 Architecture", RFC 4291, February 2006. 973 [RFC4760] - Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 974 "Multiprotocol Extensions for BGP-4", RFC 4760, January 2007. 976 [RFC5214] - Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 977 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, March 978 2008. 980 [RFC5332] - Eckert, T., Rosen, E., Ed., Aggarwal, R., and Y. Rekhter, 981 "MPLS Multicast Encapsulations", RFC 5332, August 2008. 983 [RFC5342] - Eastlake 3rd, D., "IANA Considerations and IETF Protocol 984 Usage for IEEE 802 Parameters", BCP 141, RFC 5342, September 985 2008. 987 [RFC5737] - Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address 988 Blocks Reserved for Documentation", RFC 5737, January 2010. 990 [RFC5798] - Nadas, S., Ed., "Virtual Router Redundancy Protocol 991 (VRRP) Version 3 for IPv4 and IPv6", RFC 5798, March 2010. 993 [RFC6034] - Thaler, D., "Unicast-Prefix-Based IPv4 Multicast 994 Addresses", RFC 6034, October 2010. 996 [RFC6895] - Eastlake 3rd, D., "Domain Name System (DNS) IANA 997 Considerations", BCP 42, RFC 6895, April 2013. 999 Appendix A. Templates 1001 This annex provides the specific templates for IANA assignments of 1002 parameters. Explanatory words in parenthesis in the templates below 1003 may be deleted in a completed template as submitted to IANA. 1005 A.1 EUI-48/EUI-64 Identifier or Identifier Block Template 1007 Applicant Name: 1009 Applicant Email: 1011 Applicant Telephone: (starting with country code) 1013 Use Name: (brief name of Parameter use such as "Foo Protocol" 1014 [RFC3092]) 1016 Document: (ID or RFC specifying use to which the identifier or block 1017 of identifiers will be put.) 1019 Specify whether this is an application for EUI-48 or EUI-64 1020 identifiers: 1022 Size of Block requested: (must be a power-of-two-sized block, can be 1023 a block of size one (2**0)) 1025 Specify multicast, unicast, or both: 1027 A.2 IANA OUI Based Protocol Number Template 1029 Applicant Name: 1031 Applicant Email: 1033 Applicant Telephone: (starting with country code) 1035 Use Name: (brief name of use of code point such as "Foo Protocol") 1037 Document: (ID or RFC specifying use to which the protocol identifier 1038 will be put.) 1040 Note: (any additional note) 1042 A.3 Other IANA OUI-Based Parameter Template 1044 Applicant Name: 1046 Applicant Email: 1048 Applicant Telephone: (starting with country code) 1050 Protocol where the OUI Based Parameter for which a value is being 1051 requested appears: (such as: Cipher Suite selection in IEEE 802.11) 1053 Use Name: (brief name of use of code point to be assigned, such as 1054 "Foo Cipher Suite" [RFC3092]) 1056 Document: (ID or RFC specifying use to which the other IANA OUI based 1057 parameter value will be put.) 1059 Note: (any additional note) 1061 Appendix B. Ethertypes 1063 This annex lists some Ethertypes specified for IETF Protocols or by 1064 IEEE 802 as known at the time of publication. A more up-to-date list 1065 may be available on the IANA web site, currently at [IANA]. The IEEE 1066 Registration Authority page of Ethertypes, 1067 http://standards.ieee.org/regauth/ethertype/eth.txt, may also be 1068 useful. See Section 3 above. 1070 B.1 Some Ethertypes Specified by the IETF 1072 0x0800 Internet Protocol Version 4 (IPv4) 1073 0x0806 Address Resolution Protocol (ARP) 1074 0x0808 Frame Relay ARP 1075 0x22F3 TRILL 1076 0x22F4 L2-IS-IS 1077 0x880B Point-to-Point Tunneling Protocol (PPTP) 1078 0x880C General Switch Management Protocol (GSMP) 1079 0x8035 Reverse Address Resolution Protocol (RARP) 1080 0x86DD Internet Protocol Version 6 (IPv6) 1081 0x8847 MPLS 1082 0x8848 MPLS with upstream-assigned label 1083 0x8861 Multicast Channel Allocation Protocol (MCAP) 1084 0x8863 PPP over Ethernet (PPPoE) Discovery Stage 1085 0x8864 PPP over Ethernet (PPPoE) Session Stage 1086 0x893B TRILL Fine Grained Labeling (FGL) 1087 0x8946 TRILL RBridge Channel 1089 B.2 Some IEEE 802 Ethertypes 1091 0x8100 IEEE Std 802.1Q - Customer VLAN Tag Type (C-Tag, formerly 1092 called the Q-Tag) 1093 0x8808 IEEE Std 802.3 - Ethernet Passive Optical Network (EPON) 1094 0x888E IEEE Std 802.1X - Port-based network access control 1095 0x88A8 IEEE Std 802.1Q - Service VLAN tag identifier (S-Tag) 1096 0x88B5 IEEE Std 802 - Local Experimental Ethertype 1097 0x88B6 IEEE Std 802 - Local Experimental Ethertype 1098 0x88B7 IEEE Std 802 - OUI Extended Ethertype 1099 0x88C7 IEEE Std 802.11 - Pre-Authentication (802.11i) 1100 0x88CC IEEE Std 802.1AB - Link Layer Discovery Protocol (LLDP) 1101 0x88E5 IEEE Std 802.1AE - Media Access Control Security 1102 0x88F5 IEEE Std 802.1Q - Multiple VLAN Registration Protocol 1103 (MVRP) 1104 0x88F6 IEEE Std 802.1Q - Multiple Multicast Registration 1105 Protocol (MMRP) 1106 0x890D IEEE Std 802.11 - Fast Roaming Remote Request (802.11r) 1107 0x8917 IEEE Std 802.21 - Media Independent Handover Protocol 1108 0x8929 IEEE Std 802.1Qbe - Multiple I-SID Registration Protocol 1109 0x8940 IEEE Std 802.1Qbg - ECP Protocol (also used in 802.1BR) 1111 Appendix C: Documentation Protocol Number 1113 Below is the template for assignment of a IANA OUI based protocol 1114 number value for document use. (See Section 3 and Appendix A.2.) 1116 Applicant Name: Donald E. Eastlake, 3rd 1118 Applicant Email: d3e3e3@gmail.com 1120 Applicant Telephone: 1-508-333-2270 1122 Use Name: Documentation 1124 Document: This document. 1126 Note: Request value 0x0042 1128 Appendix Z: Change History 1130 RFC Editor Note: Please delete this section before publication. 1132 From -00 to -01 1134 The -00 version was accidentally labeled with intended status 1135 "Proposed Standard". This has been corrected to "Best Current 1136 Practice". 1138 Update author information. 1140 Add acknowledgement. 1142 Add Change History Appendix. 1144 Fix various typos. 1146 From -01 to -02 1148 Move "Changes from RFC 5342" up from former Section 7 to be a part of 1149 Section 1. 1151 Add AFN numbers for 48-bit and 64-bit MAC addresses. 1153 Add Security Considerations language for documentation purpose MAC 1154 addresses. 1156 Fix various typos. 1158 From -02 to -03 1160 Add assignment of 00-42 as the protocol number for documentation use 1161 to new subsection 5.6 and make editorial changes to the protocol 1162 number subregistry. 1164 Add assigned AFN and RRTYPE values for 48 and 64 bit MAC addresses in 1165 decimal and hex. 1167 Add note to Section 1 that "IESG Ratification" as specified in 1168 Section 5.1 is not the same as "IESG Approval" as specified in RFC 1169 5226. 1171 Add note to 1.4 that there is no documentation OUI but that 1172 documentation code points under the IANA OUI are specified herein. 1174 Replace references to [RFC5342] and draft-jabley-eui48-eui64-doc-addr 1175 in IANA registries with references to this document. 1177 Update note for "IANA 64-bit MAC Addresses" table. 1179 Update "PID" (Protocol ID) in connection with SNAP protocols IANA 1180 table to "protocol number" for consistency. 1182 Update Appendix B. 1184 Minor editorial fixes. 1186 From -03 to -04 1188 Fix typos in IANA OUI in Section 3.2 and 5.5. 1190 Expand "AFN" on first use in Section 5.2. 1192 Direct IANA to merge in any values in Appendix B that are not yet in 1193 the IANA "IEEE 802 Numbers" informational web page. 1195 Minor editorial changes. 1197 From -04 to -05 1199 Re-cast informational material about relevant IEEE assignment 1200 policies to take into account the planned changes by the IEEE 1201 Registraion Authority as per [RAC-OUIdraft]. 1203 Add a sentence forshadowing the future possibility of EUI-128 MAC 1204 addresses. 1206 Add InfiniBand as example of EUI-64 use. 1208 Minor editorial changes. 1210 Authors' Addresses 1212 Donald E. Eastlake 3rd 1213 Huawei Technologies 1214 155 Beaver Street 1215 Milford, MA 01757 USA 1217 Phone: +1-508-634-2066 1218 EMail: d3e3e3@gmail.com 1220 Joe Abley 1221 ICANN 1222 12025 Waterfront Drive, Suite 300 1223 Los Angeles, CA 90094 USA 1225 Phone: +1 519 670 9327 1226 Email: joe.abley@icann.org 1228 Copyright, Disclaimer, and Additional IPR Provisions 1230 Copyright (c) 2013 IETF Trust and the persons identified as the 1231 document authors. All rights reserved. 1233 This document is subject to BCP 78 and the IETF Trust's Legal 1234 Provisions Relating to IETF Documents 1235 (http://trustee.ietf.org/license-info) in effect on the date of 1236 publication of this document. Please review these documents 1237 carefully, as they describe your rights and restrictions with respect 1238 to this document. Code Components extracted from this document must 1239 include Simplified BSD License text as described in Section 4.e of 1240 the Trust Legal Provisions and are provided without warranty as 1241 described in the Simplified BSD License. The definitive version of 1242 an IETF Document is that published by, or under the auspices of, the 1243 IETF. Versions of IETF Documents that are published by third parties, 1244 including those that are translated into other languages, should not 1245 be considered to be definitive versions of IETF Documents. The 1246 definitive version of these Legal Provisions is that published by, or 1247 under the auspices of, the IETF. Versions of these Legal Provisions 1248 that are published by third parties, including those that are 1249 translated into other languages, should not be considered to be 1250 definitive versions of these Legal Provisions. For the avoidance of 1251 doubt, each Contributor to the IETF Standards Process licenses each 1252 Contribution that he or she makes as part of the IETF Standards 1253 Process to the IETF Trust pursuant to the provisions of RFC 5378. No 1254 language to the contrary, or terms, conditions or rights that differ 1255 from or are inconsistent with the rights and licenses granted under 1256 RFC 5378, shall have any effect and shall be null and void, whether 1257 published or posted by such Contributor, or included with or in such 1258 Contribution.