Debian Codegraph @

rfc7042.html

raw
1 <pre>Internet Engineering Task Force (IETF) D. Eastlake 3rd
2 Request for Comments: 7042 Huawei
3 BCP: 141 J. Abley
4 Obsoletes: <a href="./rfc5342">5342</a> Dyn, Inc.
5 Updates: <a href="./rfc2153">2153</a> October 2013
6 Category: Best Current Practice
7 ISSN: 2070-1721
8
9
10 <span class="h1">IANA Considerations and IETF Protocol and Documentation Usage</span>
11 <span class="h1">for IEEE 802 Parameters</span>
12
13 Abstract
14
15 Some IETF protocols make use of Ethernet frame formats and IEEE 802
16 parameters. This document discusses several uses of such parameters
17 in IETF protocols, specifies IANA considerations for assignment of
18 points under the IANA OUI (Organizationally Unique Identifier), and
19 provides some values for use in documentation. This document
20 obsoletes <a href="./rfc5342">RFC 5342</a>.
21
22 Status of This Memo
23
24 This memo documents an Internet Best Current Practice.
25
26 This document is a product of the Internet Engineering Task Force
27 (IETF). It represents the consensus of the IETF community. It has
28 received public review and has been approved for publication by the
29 Internet Engineering Steering Group (IESG). Further information on
30 BCPs is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
31
32 Information about the current status of this document, any errata,
33 and how to provide feedback on it may be obtained at
34 <a href="http://www.rfc-editor.org/info/rfc7042">http://www.rfc-editor.org/info/rfc7042</a>.
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Eastlake &amp; Abley BCP [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2013 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Eastlake &amp; Abley BCP [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
111
112
113 Table of Contents
114
115 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
116 <a href="#section-1.1">1.1</a>. Notations Used in This Document ............................<a href="#page-4">4</a>
117 <a href="#section-1.2">1.2</a>. Changes from <a href="./rfc5342">RFC 5342</a> ......................................<a href="#page-5">5</a>
118 <a href="#section-1.3">1.3</a>. The IEEE Registration Authority ............................<a href="#page-5">5</a>
119 <a href="#section-1.4">1.4</a>. The IANA OUI ...............................................<a href="#page-5">5</a>
120 <a href="#section-2">2</a>. Ethernet Identifier Parameters ..................................<a href="#page-5">5</a>
121 <a href="#section-2.1">2.1</a>. 48-Bit MAC Identifiers, OUIs, and Other Prefixes ...........<a href="#page-6">6</a>
122 <a href="#section-2.1.1">2.1.1</a>. EUI-48 Assignments under the IANA OUI ...............<a href="#page-6">6</a>
123 <a href="#section-2.1.2">2.1.2</a>. EUI-48 Documentation Values .........................<a href="#page-7">7</a>
124 <a href="#section-2.1.3">2.1.3</a>. EUI-48 IANA Assignment Considerations ...............<a href="#page-8">8</a>
125 <a href="#section-2.2">2.2</a>. 64-Bit MAC Identifiers .....................................<a href="#page-8">8</a>
126 <a href="#section-2.2.1">2.2.1</a>. IPv6 Use of Modified EUI-64 Identifiers .............<a href="#page-9">9</a>
127 <a href="#section-2.2.2">2.2.2</a>. EUI-64 IANA Assignment Considerations ..............<a href="#page-10">10</a>
128 <a href="#section-2.2.3">2.2.3</a>. EUI-64 Documentation Values ........................<a href="#page-12">12</a>
129 <a href="#section-2.3">2.3</a>. Other MAC-48 Identifiers Used by the IETF .................<a href="#page-12">12</a>
130 <a href="#section-2.3.1">2.3.1</a>. Identifiers Prefixed "33-33" .......................<a href="#page-12">12</a>
131 <a href="#section-2.3.2">2.3.2</a>. The 'CF Series' ....................................<a href="#page-13">13</a>
132 <a href="#section-2.3.2.1">2.3.2.1</a>. Changes to <a href="./rfc2153">RFC 2153</a> .......................<a href="#page-13">13</a>
133 <a href="#section-3">3</a>. Ethernet Protocol Parameters ...................................<a href="#page-14">14</a>
134 <a href="#section-3.1">3.1</a>. Ethernet Protocol Assignment under the IANA OUI ...........<a href="#page-16">16</a>
135 <a href="#section-3.2">3.2</a>. Documentation Protocol Number .............................<a href="#page-16">16</a>
136 <a href="#section-4">4</a>. Other OUI-Based Parameters .....................................<a href="#page-16">16</a>
137 <a href="#section-5">5</a>. IANA Considerations ............................................<a href="#page-17">17</a>
138 <a href="#section-5.1">5.1</a>. Expert Review and IESG Ratification .......................<a href="#page-17">17</a>
139 <a href="#section-5.2">5.2</a>. MAC Address AFNs and RRTYPEs ..............................<a href="#page-19">19</a>
140 <a href="#section-5.3">5.3</a>. Informational IANA Web Page Material ......................<a href="#page-19">19</a>
141 <a href="#section-5.4">5.4</a>. OUI Exhaustion ............................................<a href="#page-19">19</a>
142 <a href="#section-5.5">5.5</a>. IANA OUI MAC Address Table ................................<a href="#page-19">19</a>
143 <a href="#section-5.6">5.6</a>. SNAP Protocol Number Table and Assignment .................<a href="#page-20">20</a>
144 <a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-20">20</a>
145 <a href="#section-7">7</a>. Acknowledgements ...............................................<a href="#page-20">20</a>
146 <a href="#section-8">8</a>. References .....................................................<a href="#page-21">21</a>
147 <a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-21">21</a>
148 <a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-21">21</a>
149 <a href="#appendix-A">Appendix A</a>. Templates .............................................<a href="#page-24">24</a>
150 <a href="#appendix-A.1">A.1</a>. EUI-48/EUI-64 Identifier or Identifier Block Template .....<a href="#page-24">24</a>
151 <a href="#appendix-A.2">A.2</a>. IANA OUI-Based Protocol Number Template ...................<a href="#page-24">24</a>
152 <a href="#appendix-A.3">A.3</a>. Other IANA OUI-Based Parameter Template ...................<a href="#page-25">25</a>
153 <a href="#appendix-B">Appendix B</a>. Ethertypes ............................................<a href="#page-25">25</a>
154 <a href="#appendix-B.1">B.1</a>. Some Ethertypes Specified by the IETF .....................<a href="#page-25">25</a>
155 <a href="#appendix-B.2">B.2</a>. Some IEEE 802 Ethertypes ..................................<a href="#page-26">26</a>
156 <a href="#appendix-C">Appendix C</a>. Documentation Protocol Number .........................<a href="#page-26">26</a>
157
158
159
160
161
162
163
164 <span class="grey">Eastlake &amp; Abley BCP [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
170
171 Some IETF protocols use Ethernet or other IEEE 802-related
172 communication frame formats and parameters [<a href="#ref-IEEE802">IEEE802</a>]. These include
173 MAC (Media Access Control) identifiers and protocol identifiers.
174
175 This document specifies IANA considerations for the assignment of
176 code points under the IANA OUI. It also discusses several other uses
177 by the IETF of IEEE 802 code points and provides some values for use
178 in documentation. As noted in [<a href="./rfc2606" title="&quot;Reserved Top Level DNS Names&quot;">RFC2606</a>] and [<a href="./rfc5737" title="&quot;IPv4 Address Blocks Reserved for Documentation&quot;">RFC5737</a>], the use of
179 designated code values reserved for documentation and examples
180 reduces the likelihood of conflicts and confusion arising from their
181 duplication of code points assigned for some deployed use.
182
183 [<a id="ref-RFC5226">RFC5226</a>] is incorporated herein except where there are contrary
184 provisions in this document. In this document, "IESG Ratification"
185 is used in some cases, and it is specified in <a href="#section-5.1">Section 5.1</a>. This is
186 not the same as "IESG Approval" in [<a href="./rfc5226" title="">RFC5226</a>].
187
188 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Notations Used in This Document</span>
189
190 This document uses hexadecimal notation. Each octet (that is, 8-bit
191 byte) is represented by two hexadecimal digits giving the value of
192 the octet as an unsigned integer. Successive octets are separated by
193 a hyphen. This document consistently uses IETF bit ordering although
194 the physical order of bit transmission within an octet on an IEEE
195 [<a href="#ref-802.3" title="&quot;IEEE Standard for Ethernet&quot;">802.3</a>] link is from the lowest order bit to the highest order bit
196 (i.e., the reverse of the IETF's ordering).
197
198 In this document:
199
200 "AFN" stands for Address Family Number [<a href="./rfc4760" title="&quot;Multiprotocol Extensions for BGP-4&quot;">RFC4760</a>].
201
202 "EUI" stands for Extended Unique Identifier.
203
204 "IAB" stands for Individual Address Block, not for Internet
205 Architecture Board.
206
207 "MAC" stands for Media Access Control, not for Message
208 Authentication Code.
209
210 "OUI" stands for Organizationally Unique Identifier.
211
212 "RRTYPE" stands for a DNS Resource Record type [<a href="./rfc6895" title="&quot;Domain Name System (DNS) IANA Considerations&quot;">RFC6895</a>].
213
214 "**" indicates exponentiation. For example, 2**24 is two to the
215 twenty-fourth power.
216
217
218
219
220 <span class="grey">Eastlake &amp; Abley BCP [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
223
224
225 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Changes from <a href="./rfc5342">RFC 5342</a></span>
226
227 o Added MAC addresses and IANA OUI-based protocol and other values
228 for use in documentation, and added relevant Security
229 Considerations language.
230
231 o Eliminated any requirements for parallel unicast and multicast
232 assignment unless requested. Such requirements had been included
233 in [<a href="./rfc5342" title="&quot;IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters&quot;">RFC5342</a>] on the theory they would make bookkeeping easier for
234 IANA but they have proved to be problematic in practice.
235
236 o Re-casted informational material about relevant IEEE assignment
237 policies to take into account [<a href="#ref-RAC-OUI" title="&quot;OUI Registry Restructuring&quot;">RAC-OUI</a>].
238
239 o Added AFNs and RRTYPEs for 48-bit and 64-bit MACs.
240
241 <span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. The IEEE Registration Authority</span>
242
243 Originally the responsibility of Xerox Corporation, the registration
244 authority for Ethernet parameters is now the IEEE Registration
245 Authority, available on the web at:
246
247 <a href="http://standards.ieee.org/regauth/">http://standards.ieee.org/regauth/</a>
248
249 Anyone may apply to that Authority for parameters. They may impose
250 fees or other requirements but commonly waive fees for applications
251 from standards development organizations.
252
253 A list of some assignments and their holders is downloadable from the
254 IEEE Registration Authority site.
255
256 <span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a>. The IANA OUI</span>
257
258 The OUI 00-00-5E has been assigned to IANA.
259
260 There is no OUI value reserved at this time for documentation, but
261 there are documentation code points under the IANA OUI specified
262 below.
263
264 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Ethernet Identifier Parameters</span>
265
266 <a href="#section-2.1">Section 2.1</a> discusses EUI-48 (Extended Unique Identifier 48) MAC
267 identifiers, their relationship to OUIs and other prefixes, and
268 assignments under the IANA OUI. <a href="#section-2.2">Section 2.2</a> extends this to EUI-64
269 identifiers. <a href="#section-2.3">Section 2.3</a> discusses other IETF MAC identifier use not
270 under the IANA OUI.
271
272
273
274
275
276 <span class="grey">Eastlake &amp; Abley BCP [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
279
280
281 [<a id="ref-RAC-OUI">RAC-OUI</a>] indicates that the IEEE Registration Authority Committee is
282 exploring the feasibility of defining a new "EUI-128" identifier.
283
284 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. 48-Bit MAC Identifiers, OUIs, and Other Prefixes</span>
285
286 48-bit MAC "addresses" are the most commonly used Ethernet interface
287 identifiers. Those that are globally unique are also called EUI-48
288 identifiers. An EUI-48 is structured into an initial 3-octet OUI
289 (Organizationally Unique Identifier) and an additional 3 octets
290 assigned by the OUI holder or into a larger initial prefix assigned
291 to an organization and a shorter sequence of additional bits so as to
292 add up to 48 bits in total. For example, the IEEE has assigned IABs
293 (Individual Address Blocks), where the first 4 1/2 octets (36 bits)
294 are assigned, giving the holder of the IAB 1 1/2 octets (12 bits)
295 they can control; however, IABs will become historic, and a wider
296 range of prefix lengths will be made available [<a href="#ref-RAC-OUI" title="&quot;OUI Registry Restructuring&quot;">RAC-OUI</a>].
297
298 The IEEE describes its assignment procedures and policies for IEEE
299 802-related identifiers in [802_O&amp;A], which is being revised.
300
301 Two bits within the initial octet of an EUI-48 have special
302 significance in MAC addresses: the Group bit (01) and the Local bit
303 (02). OUIs and longer MAC prefixes are assigned with the Local bit
304 zero and the Group bit unspecified. Multicast identifiers may be
305 constructed by turning on the Group bit, and unicast identifiers may
306 be constructed by leaving the Group bit zero.
307
308 The Local bit is zero for globally unique EUI-48 identifiers assigned
309 by the owner of an OUI or owner of a longer prefix. If the Local bit
310 is a one, the identifier has been considered by IEEE 802 to be a
311 local identifier under the control of the local network
312 administrator; however, there may be emerging recommendations from
313 the IEEE Registration Authority on management of the local address
314 space. If the Local bit is on, the holder of an OUI has no special
315 authority over MAC identifiers whose first 3 octets correspond to
316 their OUI.
317
318 An AFN and a DNS RRTYPE have been assigned for 48-bit MAC addresses
319 (see <a href="#section-5.2">Section 5.2</a>).
320
321 <span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. EUI-48 Assignments under the IANA OUI</span>
322
323 The OUI 00-00-5E has been assigned to IANA as stated in <a href="#section-1.4">Section 1.4</a>
324 above. This includes 2**24 EUI-48 multicast identifiers from
325 01-00-5E-00-00-00 to 01-00-5E-FF-FF-FF and 2**24 EUI-48 unicast
326 identifiers from 00-00-5E-00-00-00 to 00-00-5E-FF-FF-FF.
327
328
329
330
331
332 <span class="grey">Eastlake &amp; Abley BCP [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
335
336
337 Of these EUI-48 identifiers, the sub-blocks reserved or thus far
338 assigned by IANA for purposes of documentation are as follows:
339
340 Unicast, all blocks of 2**8 addresses thus far:
341
342 00-00-5E-00-00-00 through 00-00-5E-00-00-FF: reserved and require
343 IESG Ratification for assignment (see <a href="#section-5.1">Section 5.1</a>).
344
345 00-00-5E-00-01-00 through 00-00-5E-00-01-FF: assigned for the
346 Virtual Router Redundancy Protocol (VRRP) [<a href="./rfc5798" title="&quot;Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6&quot;">RFC5798</a>].
347
348 00-00-5E-00-02-00 through 00-00-5E-00-02-FF: assigned for the IPv6
349 Virtual Router Redundancy Protocol (IPv6 VRRP) [<a href="./rfc5798" title="&quot;Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6&quot;">RFC5798</a>].
350
351 00-00-5E-00-52-00 through 00-00-5E-00-52-FF: used for very small
352 assignments. Currently, 3 out of these 256 values have been
353 assigned.
354
355 00-00-5E-00-53-00 through 00-00-5E-00-53-FF: assigned for use in
356 documentation.
357
358 Multicast:
359
360 01-00-5E-00-00-00 through 01-00-5E-7F-FF-FF: 2**23 addresses
361 assigned for IPv4 multicast [<a href="./rfc1112" title="&quot;Host extensions for IP multicasting&quot;">RFC1112</a>].
362
363 01-00-5E-80-00-00 through 01-00-5E-8F-FF-FF: 2**20 addresses
364 assigned for MPLS multicast [<a href="./rfc5332" title="&quot;MPLS Multicast Encapsulations&quot;">RFC5332</a>].
365
366 01-00-5E-90-00-00 through 01-00-5E-90-00-FF: 2**8 addresses being
367 used for very small assignments. Currently, 4 out of these 256
368 values have been assigned.
369
370 01-00-5E-90-10-00 through 01-00-5E-90-10-FF: 2**8 addresses for
371 use in documentation.
372
373 For more detailed and up-to-date information, see the "Ethernet
374 Numbers" registry at <a href="http://www.iana.org">http://www.iana.org</a>.
375
376 <span class="h4"><a class="selflink" id="section-2.1.2" href="#section-2.1.2">2.1.2</a>. EUI-48 Documentation Values</span>
377
378 The following values have been assigned for use in documentation:
379
380 00-00-5E-00-53-00 through 00-00-5E-00-53-FF for unicast and
381
382 01-00-5E-90-10-00 through 01-00-5E-90-10-FF for multicast.
383
384
385
386
387
388 <span class="grey">Eastlake &amp; Abley BCP [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
391
392
393 <span class="h4"><a class="selflink" id="section-2.1.3" href="#section-2.1.3">2.1.3</a>. EUI-48 IANA Assignment Considerations</span>
394
395 EUI-48 assignments under the current or a future IANA OUI (see
396 <a href="#section-5.4">Section 5.4</a>) must meet the following requirements:
397
398 o must be for standards purposes (either for an IETF Standard or
399 other standard related to IETF work),
400
401 o must be for a power-of-two size block of identifiers starting
402 at a boundary that is an equal or greater power of two,
403 including the assignment of one (2**0) identifier,
404
405 o must not be used to evade the requirement for vendors to obtain
406 their own block of identifiers from the IEEE, and
407
408 o must be documented in an Internet-Draft or RFC.
409
410 In addition, approval must be obtained as follows (see the procedure
411 in <a href="#section-5.1">Section 5.1</a>):
412
413 Small to medium assignments of a block of 1, 2, 4, ..., 32768,
414 65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI-48 identifiers
415 require Expert Review (see <a href="#section-5.1">Section 5.1</a>).
416
417 Large assignments of 131072 (2**17) or more EUI-48 identifiers
418 require IESG Ratification (see <a href="#section-5.1">Section 5.1</a>).
419
420 ([<a href="./rfc5342" title="&quot;IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters&quot;">RFC5342</a>] had a requirement for parallel unicast and multicast
421 assignments under some circumstances even when one of the types was
422 not included in the application. That requirement has proved
423 impractical and is eliminated in this document.)
424
425 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. 64-Bit MAC Identifiers</span>
426
427 IEEE also defines a system of 64-bit MAC identifiers including
428 EUI-64s. EUI-64 identifiers are currently used as follows:
429
430 o In a modified form to construct some IPv6 interface identifiers
431 as described in <a href="#section-2.2.1">Section 2.2.1</a>
432
433 o In IEEE Std 1394 (also known as FireWire and i.Link)
434
435 o In IEEE Std 802.15.4 (also known as ZigBee)
436
437 o In [<a href="#ref-InfiniBand">InfiniBand</a>]
438
439
440
441
442
443
444 <span class="grey">Eastlake &amp; Abley BCP [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
447
448
449 Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) OUI, or a
450 shorter extension to longer assigned prefixes [<a href="#ref-RAC-OUI" title="&quot;OUI Registry Restructuring&quot;">RAC-OUI</a>] so as to
451 total 64 bits, produces an EUI-64 identifier under that OUI or longer
452 prefix. As with EUI-48 identifiers, the first octet has the same
453 Group and Local bits.
454
455 An AFN and a DNS RRTYPE have been assigned for 64-bit MAC addresses
456 (see <a href="#section-5.2">Section 5.2</a>).
457
458 The discussion below is almost entirely in terms of the "Modified"
459 form of EUI-64 identifiers; however, anyone assigned such an
460 identifier can also use the unmodified form as a MAC identifier on
461 any link that uses such 64-bit identifiers for interfaces.
462
463 <span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. IPv6 Use of Modified EUI-64 Identifiers</span>
464
465 MAC-64 identifiers are used to form the lower 64 bits of some IPv6
466 addresses (<a href="#section-2.5.1">Section 2.5.1</a> and <a href="./rfc4291#appendix-A">Appendix&nbsp;A of [RFC4291]</a> and <a href="./rfc5214#appendix-A">Appendix&nbsp;A
467 of [RFC5214]</a>). When so used, the MAC-64 is modified by inverting the
468 Local/Global bit to form an IETF "Modified EUI-64 identifier". Below
469 is an illustration of a Modified EUI-64 unicast identifier under the
470 IANA OUI, where aa-bb-cc-dd-ee is the extension.
471
472 02-00-5E-aa-bb-cc-dd-ee
473
474 The first octet is shown as 02 rather than 00 because, in Modified
475 EUI-64 identifiers, the sense of the Local/Global bit is inverted
476 compared with EUI-48 identifiers. It is the globally unique values
477 (universal scope) that have the 02 bit on in the first octet, while
478 those with this bit off are locally assigned and out of scope for
479 global assignment.
480
481 The Local/Global bit was inverted to make it easier for network
482 operators to type in local-scope identifiers. Thus, such Modified
483 EUI-64 identifiers as 1, 2, etc. (ignoring leading zeros) are local.
484 Without the modification, they would have to be
485 02-00-00-00-00-00-00-01, 02-00-00-00-00-00-00-02, etc. to be local.
486
487 As with MAC-48 identifiers, the 01 bit on in the first octet
488 indicates a group identifier.
489
490 When the first two octets of the extension of a Modified EUI-64
491 identifier are FF-FE, the remainder of the extension is a 24-bit
492 value as assigned by the OUI owner for an EUI-48. For example:
493
494 02-00-5E-FF-FE-yy-yy-yy
495 or
496 03-00-5E-FF-FE-yy-yy-yy
497
498
499
500 <span class="grey">Eastlake &amp; Abley BCP [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
503
504
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.
511
512 (Note: [<a href="#ref-EUI-64" title="&quot;Guidelines for 64-bit Global Identifier (EUI-64(TM))&quot;">EUI-64</a>] defines FF-FF as the bits to be inserted to create
513 an IEEE EUI-64 identifier from a MAC-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 MAC-48 local identifiers. EUI-48 and
518 local MAC-48 identifiers are syntactically equivalent, and this
519 doesn't cause any problems in practice.)
520
521 In addition, certain Modified EUI-64 identifiers under the IANA OUI
522 are reserved for holders of IPv4 addresses as follows:
523
524 02-00-5E-FE-xx-xx-xx-xx
525
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
529
530 02-00-5E-FE-F0-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF
531
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.)
538
539 <span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>. EUI-64 IANA Assignment Considerations</span>
540
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.
548
549 02-00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF reserved
550
551 02-00-5E-10-00-00-00-00 to 02-00-5E-10-00-00-00-FF assigned for
552 documentation use
553
554
555
556 <span class="grey">Eastlake &amp; Abley BCP [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
559
560
561 02-00-5E-10-00-00-01-00 to 02-00-5E-EF-FF-FF-FF-FF, which is
562 available for assignment
563
564 02-00-5E-F0-00-00-00-00 to 02-00-5E-FD-FF-FF-FF-FF reserved
565
566 02-00-5E-FE-00-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF assigned to
567 IPv4 address holders as described above
568
569 02-00-5E-FF-00-00-00-00 to 02-00-5E-FF-FD-FF-FF-FF reserved
570
571 02-00-5E-FF-FE-00-00-00 to 02-00-5E-FF-FE-FF-FF-FF assigned for
572 holders of EUI-48 identifiers under the IANA OUI as described
573 above
574
575 02-00-5E-FF-FF-00-00-00 to 02-00-5E-FF-FF-FF-FF-FF reserved
576
577 The reserved identifiers above require IESG Ratification (see
578 <a href="#section-5.1">Section 5.1</a>) for assignment. IANA EUI-64 identifier assignments
579 under the IANA OUI must meet the following requirements:
580
581 o must be for standards purposes (either for an IETF Standard or
582 other standard related to IETF work),
583
584 o must be for a power-of-two size block of identifiers starting
585 at a boundary that is an equal or greater power of two,
586 including the assignment of one (2**0) identifier,
587
588 o must not be used to evade the requirement for vendors to obtain
589 their own block of identifiers from the IEEE, and
590
591 o must be documented in an Internet-Draft or RFC.
592
593 In addition, approval must be obtained as follows (see the procedure
594 in <a href="#section-5.1">Section 5.1</a>):
595
596 Small to medium assignments of a block of 1, 2, 4, ..., 134217728,
597 <a href="#section-268435456">268435456</a> (2**0, 2**1, 2**2, ..., 2**27, 2**28) EUI-64
598 identifiers require Expert Review (see <a href="#section-5.1">Section 5.1</a>).
599
600 Assignments of any size, including 536870912 (2**29) or more
601 EUI-64 identifiers, may be made with IESG Ratification (see
602 <a href="#section-5.1">Section 5.1</a>).
603
604
605
606
607
608
609
610
611
612 <span class="grey">Eastlake &amp; Abley BCP [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
615
616
617 <span class="h4"><a class="selflink" id="section-2.2.3" href="#section-2.2.3">2.2.3</a>. EUI-64 Documentation Values</span>
618
619 The following blocks of unmodified 64-bit MAC addresses are for
620 documentation use. The IPv4-derived addresses are based on the IPv4
621 documentation addresses [<a href="./rfc5737" title="&quot;IPv4 Address Blocks Reserved for Documentation&quot;">RFC5737</a>], and the MAC-derived addresses are
622 based on the EUI-48 documentation addresses above.
623
624 Unicast:
625
626 00-00-5E-EF-10-00-00-00 to 00-00-5E-EF-10-00-00-FF general
627
628 00-00-5E-FE-C0-00-02-00 to 00-00-5E-FE-C0-00-02-FF and
629 00-00-5E-FE-C6-33-64-00 to 00-00-5E-FE-C6-33-64-FF and
630 00-00-5E-FE-CB-00-71-00 to 00-00-5E-FE-CB-00-71-FF IPv4 derived
631
632 00-00-5E-FF-FE-00-53-00 to 00-00-5E-FF-FE-00-53-FF EUI-48 derived
633
634 00-00-5E-FE-EA-C0-00-02 and
635 00-00-5E-FE-EA-C6-33-64 and
636 00-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast
637 [<a href="./rfc6034" title="&quot;Unicast-Prefix-Based IPv4 Multicast Addresses&quot;">RFC6034</a>]
638
639 Multicast:
640
641 01-00-5E-EF-10-00-00-00 to 01-00-5E-EF-10-00-00-FF general
642
643 01-00-5E-FE-C0-00-02-00 to 01-00-5E-FE-C0-00-02-FF and
644 01-00-5E-FE-C6-33-64-00 to 01-00-5E-FE-C6-33-64-FF and
645 01-00-5E-FE-CB-00-71-00 to 01-00-5E-FE-CB-00-71-FF IPv4 derived
646
647 01-00-5E-FE-EA-C0-00-02 and
648 01-00-5E-FE-EA-C6-33-64 and
649 01-00-5E-FE-EA-CB-00-71 IPv4 multicast derived from IPv4 unicast
650 [<a href="./rfc6034" title="&quot;Unicast-Prefix-Based IPv4 Multicast Addresses&quot;">RFC6034</a>]
651
652 01-00-5E-FF-FE-90-10-00 to 01-00-5E-FF-FE-90-10-FF EUI-48 derived
653
654 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Other MAC-48 Identifiers Used by the IETF</span>
655
656 There are two other blocks of MAC-48 identifiers that are used by the
657 IETF as described below.
658
659 <span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>. Identifiers Prefixed "33-33"</span>
660
661 All MAC-48 multicast identifiers prefixed "33-33" (that is, the 2**32
662 multicast MAC identifiers in the range from 33-33-00-00-00-00 to
663 33-33-FF-FF-FF-FF) are used as specified in [<a href="./rfc2464" title="&quot;Transmission of IPv6 Packets over Ethernet Networks&quot;">RFC2464</a>] for IPv6
664 multicast. In all of these identifiers, the Group bit (the bottom
665
666
667
668 <span class="grey">Eastlake &amp; Abley BCP [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
671
672
673 bit of the first octet) is on, as is required to work properly with
674 existing hardware as a multicast identifier. They also have the
675 Local bit on and are used for this purpose in IPv6 networks.
676
677 (Historical note: It was the custom during IPv6 design to use "3"
678 for unknown or example values, and 3333 Coyote Hill Road, Palo
679 Alto, California, is the address of PARC (Palo Alto Research
680 Center, formerly "Xerox PARC"). Ethernet was originally specified
681 by the Digital Equipment Corporation, Intel Corporation, and Xerox
682 Corporation. The pre-IEEE [<a href="#ref-802.3" title="&quot;IEEE Standard for Ethernet&quot;">802.3</a>] Ethernet protocol has sometimes
683 been known as "DIX" Ethernet from the first letters of the names
684 of these companies.)
685
686 <span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a>. The 'CF Series'</span>
687
688 The Informational [<a href="./rfc2153" title="&quot;PPP Vendor Extensions&quot;">RFC2153</a>] declared the 3-octet values from CF-00-00
689 through CF-FF-FF to be OUIs available for assignment by IANA to
690 software vendors for use in PPP [<a href="./rfc1661" title="&quot;The Point-to-Point Protocol (PPP)&quot;">RFC1661</a>] or for other uses where
691 vendors do not otherwise need an IEEE-assigned OUI. It should be
692 noted that, when used as MAC-48 prefixes, these values have the Local
693 and Group bits on, while all IEEE-assigned OUIs thus far have those
694 bits off. The Group bit is meaningless in PPP. To quote [<a href="./rfc2153" title="&quot;PPP Vendor Extensions&quot;">RFC2153</a>]:
695 "The 'CF0000' series was arbitrarily chosen to match the PPP NLPID
696 'CF', as a matter of mnemonic convenience."
697
698 CF-00-00 is reserved, and IANA lists multicast identifier
699 CF-00-00-00-00-00 as used for Ethernet loopback tests.
700
701 In over a decade of availability, only a handful of values in the
702 'CF Series' have been assigned. (See "Ethernet Numbers"
703 &lt;<a href="http://www.iana.org/assignments/ethernet-numbers">http://www.iana.org/assignments/ethernet-numbers</a>&gt; and "PPP Numbers"
704 &lt;<a href="http://www.iana.org/assignments/ppp-numbers">http://www.iana.org/assignments/ppp-numbers</a>&gt;).
705
706 <span class="h5"><a class="selflink" id="section-2.3.2.1" href="#section-2.3.2.1">2.3.2.1</a>. Changes to <a href="./rfc2153">RFC 2153</a></span>
707
708 The IANA Considerations in [<a href="./rfc2153" title="&quot;PPP Vendor Extensions&quot;">RFC2153</a>] were updated as follows by the
709 approval of [<a href="./rfc5342" title="&quot;IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters&quot;">RFC5342</a>] (no technical changes were made at that time):
710
711 o Use of these identifiers based on IANA assignment was
712 deprecated.
713
714 o IANA was instructed not to assign any further values in the
715 'CF Series'.
716
717
718
719
720
721
722
723
724 <span class="grey">Eastlake &amp; Abley BCP [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
727
728
729 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Ethernet Protocol Parameters</span>
730
731 Ethernet protocol parameters provide a means of indicating the
732 contents of a frame -- for example, that its contents are IPv4 or
733 IPv6.
734
735 The concept has been extended to labeling by "tags". A tag in this
736 sense is a prefix whose type is identified by an Ethertype that is
737 then followed by either another tag, an Ethertype, or an LSAP (Link-
738 Layer Service Access Point) protocol indicator for the "main" body of
739 the frame, as described below. Traditionally, in the [802_O&amp;A]
740 world, tags are a fixed length and do not include any encoding of
741 their own length. Any device that is processing a frame cannot, in
742 general, safely process anything in the frame past an Ethertype it
743 does not understand. An example is the C-Tag (formerly the Q-Tag)
744 [<a href="#ref-802.1Q" title="&quot;IEEE Standard for Local and metropolitan area networks / Media Access Control (MAC) Bridges and Virtual Bridge Local Area Networks&quot;">802.1Q</a>]. It provides customer VLAN and priority information for a
745 frame.
746
747 There are two types of protocol identifier parameters that can occur
748 in Ethernet frames after the initial MAC-48 destination and source
749 identifiers:
750
751 Ethertypes: These are 16-bit identifiers appearing as the initial
752 two octets after the MAC destination and source (or after a
753 tag), which, when considered as an unsigned integer, are equal
754 to or larger than 0x0600.
755
756 LSAPs: These are 8-bit protocol identifiers that occur in pairs
757 immediately after an initial 16-bit (two-octet) remaining frame
758 length, which is in turn after the MAC destination and source
759 (or after a tag). Such a length must, when considered as an
760 unsigned integer, be less than 0x5DC, or it could be mistaken
761 as an Ethertype. LSAPs occur in pairs where one is intended to
762 indicate the source protocol handler and one the destination
763 protocol handler; however, use cases where the two are
764 different have been relatively rare.
765
766 Neither Ethertypes nor LSAPs are assigned by IANA; they are assigned
767 by the IEEE Registration Authority (see <a href="#section-1.3">Section 1.3</a> above and
768 <a href="#appendix-B">Appendix B</a>). However, both LSAPs and Ethertypes have extension
769 mechanisms so that they can be used with five-octet Ethernet protocol
770 identifiers under an OUI, including those assigned by IANA under the
771 IANA OUI.
772
773
774
775
776
777
778
779
780 <span class="grey">Eastlake &amp; Abley BCP [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
783
784
785 When using the IEEE 802 Logical Link Control (LLC) format (Subnetwork
786 Access Protocol (SNAP)) [802_O&amp;A] for a frame, an OUI-based protocol
787 identifier can be expressed as follows:
788
789 xx-xx-AA-AA-03-yy-yy-yy-zz-zz
790
791 where xx-xx is the frame length and, as above, must be small enough
792 not to be confused with an Ethertype; "AA" is the LSAP that indicates
793 this use and is sometimes referred to as the SNAP Service Access
794 Point (SAP); "03" is the LLC control octet indicating datagram
795 service; yy-yy-yy is an OUI; and zz-zz is a protocol number, under
796 that OUI, assigned by the OUI owner. The odd five-octet length for
797 such OUI-based protocol identifiers was chosen so that, with the LLC
798 control octet ("03"), the result is 16-bit aligned.
799
800 When using an Ethertype to indicate the main type for a frame body,
801 the special "OUI Extended Ethertype" 88-B7 is available. Using this
802 Ethertype, a frame body can begin with
803
804 88-B7-yy-yy-yy-zz-zz
805
806 where yy-yy-yy and zz-zz have the same meaning as in the SNAP format
807 described above.
808
809 It is also possible, within the SNAP format, to use an arbitrary
810 Ethertype. Putting the Ethertype as the zz-zz field after an all-
811 zeros OUI (00-00-00) does this. It looks like
812
813 xx-xx-AA-AA-03-00-00-00-zz-zz
814
815 where zz-zz is the Ethertype.
816
817 (Note that, at this point, the 802 protocol syntax facilities are
818 sufficiently powerful that they could be chained indefinitely.
819 Whether support for such chaining is generally required is not
820 clear, but [802_O&amp;A] requires support for
821
822 xx-xx-AA-AA-03-00-00-00-88-B7-yy-yy-yy-zz-zz
823
824 although this could be more efficiently expressed by simply
825 pinching out the "00-00-00-88-B7" in the middle.)
826
827 As well as labeling frame contents, 802 protocol types appear within
828 NBMA (Non-Broadcast Multi-Access) Next Hop Resolution Protocol
829 [<a href="./rfc2332" title="&quot;NBMA Next Hop Resolution Protocol (NHRP)&quot;">RFC2332</a>] messages. Such messages have provisions for both two-octet
830 Ethertypes and OUI-based protocol types.
831
832
833
834
835
836 <span class="grey">Eastlake &amp; Abley BCP [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
839
840
841 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Ethernet Protocol Assignment under the IANA OUI</span>
842
843 Two-octet protocol numbers under the IANA OUI are available, as in
844
845 xx-xx-AA-AA-03-00-00-5E-qq-qq
846
847 where qq-qq is the protocol number.
848
849 A number of such assignments have been made out of the 2**16 protocol
850 numbers available from 00-00-5E-00-00 to 00-00-5E-FF-FF (see [<a href="#ref-IANA">IANA</a>]).
851 The extreme values of this range, 00-00-5E-00-00 and 00-00-5E-FF-FF,
852 are reserved and require IESG Ratification for assignment (see
853 <a href="#section-5.1">Section 5.1</a>). New assignments of SNAP SAP protocol (qq-qq) numbers
854 under the IANA OUI must meet the following requirements:
855
856 o the assignment must be for standards use (either for an IETF
857 Standard or other standard related to IETF work),
858
859 o it must be documented in an Internet-Draft or RFC, and
860
861 o such protocol numbers are not to be assigned for any protocol
862 that has an Ethertype (because that can be expressed by putting
863 an all-zeros "OUI" before the Ethertype as described above).
864
865 In addition, the Expert Review (or IESG Ratification for the two
866 reserved values) must be obtained using the procedure specified in
867 <a href="#section-5.1">Section 5.1</a>.
868
869 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Documentation Protocol Number</span>
870
871 0x0042 is a protocol number under the IANA OUI (that is,
872 00-00-5E-00-42) to be used for documentation purposes.
873
874 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Other OUI-Based Parameters</span>
875
876 Some IEEE 802 and other protocols provide for parameters based on an
877 OUI beyond those discussed above. Such parameters most commonly
878 consist of an OUI plus one octet of additional value. They are
879 usually called "vendor specific" parameters, although "organization
880 specific" might be more accurate. They would look like
881
882 yy-yy-yy-zz
883
884 where yy-yy-yy is the OUI and zz is the additional specifier. An
885 example is the Cipher Suite Selector in IEEE [<a href="#ref-802.11" title="&quot;IEEE Standard for Information technology / Telecommunications and information exchange between systems / Local and metropolitan area networks / Specific requirements / Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications&quot;">802.11</a>].
886
887 Values may be assigned under the IANA OUI for such other OUI-based
888 parameter usage by Expert Review except that, for each use, the
889
890
891
892 <span class="grey">Eastlake &amp; Abley BCP [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
895
896
897 additional specifier values consisting of all zero bits and all one
898 bits (0x00 (00-00-5E-00) and 0xFF (00-00-5E-FF) for a one-octet
899 specifier) are reserved and require IESG Ratification (see
900 <a href="#section-5.1">Section 5.1</a>) for assignment; also, the additional specifier value
901 0x42 (00-00-5E-42) is assigned for use in documentation.
902
903 Assignments of such other IANA OUI-based parameters must be for
904 standards use (either for an IETF Standard or other standard related
905 to IETF work) and be documented in an Internet-Draft or RFC. The
906 first time a value is assigned for a particular parameter of this
907 type, an IANA registry will be created to contain that assignment and
908 any subsequent assignments of values for that parameter under the
909 IANA OUI. The Expert will specify the name of the registry.
910
911 If different policies from those above are required for such a
912 parameter, a BCP or Standards Track RFC must be adopted to update
913 this BCP and specify the new policy and parameter.
914
915 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
916
917 The entirety of this document concerns IANA considerations for the
918 assignment of Ethernet parameters in connection with the IANA OUI and
919 related matters.
920
921 As this document replaces [<a href="./rfc5342" title="&quot;IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters&quot;">RFC5342</a>], references to [<a href="./rfc5342" title="&quot;IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters&quot;">RFC5342</a>] in IANA
922 registries have been replaced by references to this document. In
923 addition, any references in the registries to [<a href="#ref-DOC-ADDR" title="&quot;EUI-48 and EUI-64 Address Assignments for use in Documentation&quot;">DOC-ADDR</a>], which has
924 been combined into this document, have been replaced by references to
925 this document.
926
927 This document does not create any new IANA registries.
928
929 This document assigns MAC address values for documentation. These
930 values had been previously assigned by [<a href="#ref-DOC-ADDR" title="&quot;EUI-48 and EUI-64 Address Assignments for use in Documentation&quot;">DOC-ADDR</a>]; as noted above,
931 any references in the registries to [<a href="#ref-DOC-ADDR" title="&quot;EUI-48 and EUI-64 Address Assignments for use in Documentation&quot;">DOC-ADDR</a>] have been replaced by
932 references to this document.
933
934 The only other assignment that has been made by this document is a
935 protocol number for documentation. See <a href="#section-5.6">Section 5.6</a> for details.
936
937 No existing assignment is changed by this document.
938
939 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Expert Review and IESG Ratification</span>
940
941 This section specifies the procedure for Expert Review and IESG
942 Ratification of MAC, protocol, and other IANA OUI-based identifiers.
943 The Expert(s) referred to in this document shall consist of one or
944 more persons appointed by and serving at the pleasure of the IESG.
945
946
947
948 <span class="grey">Eastlake &amp; Abley BCP [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
951
952
953 The procedure described for Expert Review assignments in this
954 document is fully consistent with the IANA Expert Review policy
955 described in [<a href="./rfc5226" title="">RFC5226</a>].
956
957 While finite, the universe of code points from which Expert-judged
958 assignments will be made is felt to be large enough that the
959 requirements given in this document and the Experts' good judgment
960 are sufficient guidance. The idea is for the Expert to provide a
961 light sanity check for small assignments of EUI identifiers, with
962 increased scrutiny by the Expert for medium-sized assignments of EUI
963 identifiers and assignments of protocol identifiers and other IANA
964 OUI-based parameters. However, it can make sense to assign very
965 large portions of the MAC identifier code point space. (Note that
966 existing assignments include one for 1/2 of the entire multicast IANA
967 EUI-48 code point space and one for 1/16 of that multicast code point
968 space.) In those cases, and in cases of the assignment of "reserved"
969 values, IESG Ratification of an Expert Review approval recommendation
970 is required as described below. The procedure is as follows:
971
972 The applicant always completes the appropriate template from
973 <a href="#appendix-A">Appendix A</a> below and sends it to IANA &lt;[email protected]&gt;.
974
975 IANA always sends the template to an appointed Expert. If the
976 Expert recuses themselves or is non-responsive, IANA may choose
977 an alternative appointed Expert or, if none is available, will
978 contact the IESG.
979
980 In all cases, if IANA receives a disapproval from an Expert
981 selected to review an application template, the application
982 will be denied.
983
984 If the assignment is based on Expert Review:
985
986 If IANA receives approval and code points are available,
987 IANA will make the requested assignment.
988
989 If the assignment is based on IESG Ratification:
990
991 The procedure starts with the first steps above for Expert
992 Review. If the Expert disapproves the application, they
993 simply inform IANA; however, if the Expert believes the
994 application should be approved, or is uncertain and believes
995 that the circumstances warrant the attention of the IESG,
996 the Expert will inform IANA about their advice, and IANA
997 will forward the application, together with the reasons for
998 approval or uncertainty, to the IESG. The IESG must decide
999 whether the assignment will be granted. This can be
1000 accomplished by a management item in an IESG telechat as is
1001
1002
1003
1004 <span class="grey">Eastlake &amp; Abley BCP [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1007
1008
1009 done for other types of requests. If the IESG decides not
1010 to ratify a favorable opinion by the Expert or decides
1011 against an application where the Expert is uncertain, the
1012 application is denied; otherwise, it is granted. The IESG
1013 will communicate its decision to the Expert and to IANA.
1014
1015 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. MAC Address AFNs and RRTYPEs</span>
1016
1017 IANA has assigned Address Family Numbers (AFNs) for MAC addresses as
1018 follows:
1019
1020 AFN Decimal Hex Reference
1021 ---------- ------- ------ ---------
1022 48-bit MAC 16389 0x4005 [<a href="./rfc7042">RFC7042</a>]
1023 64-bit MAC 16390 0x4006 [<a href="./rfc7042">RFC7042</a>]
1024
1025 IANA has assigned DNS RRTYPEs [<a href="./rfc6895" title="&quot;Domain Name System (DNS) IANA Considerations&quot;">RFC6895</a>] for MAC addresses as follows:
1026
1027 RRTYPE Code
1028 Data Mnemonic Decimal Hex Reference
1029 ---------- -------- ------- ------ -----------
1030 48-bit MAC EUI48 108 0x006C [<a href="./rfc7043" title="&quot;Resource Records for EUI-48 and EUI-64 Addresses in the DNS&quot;">RFC7043</a>]
1031 64-bit MAC EUI64 109 0x006D [<a href="./rfc7043" title="&quot;Resource Records for EUI-48 and EUI-64 Addresses in the DNS&quot;">RFC7043</a>]
1032
1033 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Informational IANA Web Page Material</span>
1034
1035 IANA maintains an informational listing on its web site concerning
1036 Ethertypes, OUIs, and multicast addresses assigned under OUIs other
1037 than the IANA OUI. The title of this informational registry is "IEEE
1038 802 Numbers". IANA has merged in those Ethertypes listed in <a href="#appendix-B">Appendix</a>
1039 <a href="#appendix-B">B</a> that were not already included. IANA will update that
1040 informational registry when changes are provided by the Expert.
1041
1042 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. OUI Exhaustion</span>
1043
1044 When the available space for either multicast or unicast EUI-48
1045 identifiers under OUI 00-00-5E has been 90% or more exhausted, IANA
1046 should request an additional OUI from the IEEE Registration Authority
1047 for further IANA assignment. The appointed Expert(s) should monitor
1048 for this condition and notify IANA.
1049
1050 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. IANA OUI MAC Address Table</span>
1051
1052 No changes have been made in the "IANA Unicast 48-bit MAC Addresses"
1053 and "IANA Multicast 48-bit MAC Addresses" tables except for the
1054 updates to references as specified in the first part of <a href="#section-5">Section 5</a>.
1055
1056
1057
1058
1059
1060 <span class="grey">Eastlake &amp; Abley BCP [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1063
1064
1065 <span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. SNAP Protocol Number Table and Assignment</span>
1066
1067 The "SNAP PROTOCOL IDs" table has been renamed the "SNAP Protocol
1068 Numbers" table. "PID" has been replaced by "Protocol Number".
1069
1070 IANA has assigned 0x0042 as the SNAP protocol number under the IANA
1071 OUI to be used for documentation purposes.
1072
1073 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
1074
1075 This document is concerned with assignment of parameters under the
1076 IANA OUI and closely related matters. It is not directly concerned
1077 with security except as follows.
1078
1079 Confusion and conflict can be caused by the use of MAC addresses or
1080 other OUI-derived protocol parameters as examples in documentation.
1081 Examples used "only" in documentation can end up being coded and
1082 released or cause conflicts due to later real use and the possible
1083 acquisition of intellectual property rights in such addresses or
1084 parameters. The reservation herein of MAC addresses and parameters
1085 for documentation purposes will minimize such confusion and conflict.
1086
1087 See [<a href="./rfc7043" title="&quot;Resource Records for EUI-48 and EUI-64 Addresses in the DNS&quot;">RFC7043</a>] for security considerations in storing MAC addresses in
1088 the DNS.
1089
1090 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
1091
1092 The comments and suggestions of the following people, listed in
1093 alphabetic order, are gratefully acknowledged:
1094
1095 This document:
1096 David Black, Adrian Farrel, Bob Grow, Joel Jaeggli, Pearl Liang,
1097 Glenn Parsons, Pete Resnick, and Dan Romascanu.
1098
1099 <a href="./rfc5342">RFC 5342</a>:
1100 Bernard Aboba, Scott O. Bradner, Ian Calder, Michelle Cotton, Lars
1101 Eggert, Eric Gray, Alfred Hoenes, Russ Housley, Charlie Kaufman,
1102 Erik Nordmark, Dan Romascanu, Geoff Thompson, and Mark Townsley.
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Eastlake &amp; Abley BCP [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
1122
1123 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
1124
1125 [802_O&amp;A] "IEEE Standard for Local and Metropolitan Area Networks:
1126 Overview and Architecture", IEEE Std 802-2001, 8 March
1127 2002.
1128
1129 "IEEE Standard for Local and Metropolitan Area Networks:
1130 Overview and Architecture / Amendment 1: Ethertypes for
1131 Prototype and Vendor-Specific Protocol Development", IEEE
1132 Std 802a-2003, 18 September 2003.
1133
1134 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
1135 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
1136 May 2008.
1137
1138 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
1139
1140 [<a id="ref-802.1Q">802.1Q</a>] "IEEE Standard for Local and metropolitan area networks /
1141 Media Access Control (MAC) Bridges and Virtual Bridge
1142 Local Area Networks", IEEE Std 802.1Q-2011, 31 August
1143 2011.
1144
1145 [<a id="ref-802.3">802.3</a>] "IEEE Standard for Ethernet", IEEE Std 802.3-2012, 28
1146 December 2012.
1147
1148 [<a id="ref-802.11">802.11</a>] "IEEE Standard for Information technology /
1149 Telecommunications and information exchange between
1150 systems / Local and metropolitan area networks / Specific
1151 requirements / Part 11: Wireless LAN Medium Access Control
1152 (MAC) and Physical Layer (PHY) Specifications", IEEE Std
1153 802.11-2012, 29 March 2012.
1154
1155 [<a id="ref-DOC-ADDR">DOC-ADDR</a>] Abley, J., "EUI-48 and EUI-64 Address Assignments for use
1156 in Documentation", Work in Progress, March 2013.
1157
1158 [<a id="ref-EUI-64">EUI-64</a>] IEEE Registration Authority, "Guidelines for 64-bit Global
1159 Identifier (EUI-64(TM))", &lt;<a href="http://standards.ieee.org/regauth/oui/tutorials/EUI64.html">http://standards.ieee.org/</a>
1160 <a href="http://standards.ieee.org/regauth/oui/tutorials/EUI64.html">regauth/oui/tutorials/EUI64.html</a>&gt;, November 2012.
1161
1162 [<a id="ref-IANA">IANA</a>] Internet Assigned Numbers Authority,
1163 &lt;<a href="http://www.iana.org">http://www.iana.org</a>&gt;.
1164
1165 [<a id="ref-IEEE802">IEEE802</a>] IEEE 802 LAN/MAN Standards Committee,
1166 &lt;<a href="http://www.ieee802.org">http://www.ieee802.org</a>&gt;.
1167
1168
1169
1170
1171
1172 <span class="grey">Eastlake &amp; Abley BCP [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1175
1176
1177 [<a id="ref-InfiniBand">InfiniBand</a>]
1178 InfiniBand Trade Association, "InfiniBand Architecture
1179 Specification Volume 1", November 2007.
1180
1181 [<a id="ref-RAC-OUI">RAC-OUI</a>] Parsons, G., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22OUI+Registry+Restructuring%22'>"OUI Registry Restructuring"</a>, Work in
1182 Progress, September 2013.
1183
1184 [<a id="ref-RFC1112">RFC1112</a>] Deering, S., "Host extensions for IP multicasting", STD 5,
1185 <a href="./rfc1112">RFC 1112</a>, August 1989.
1186
1187 [<a id="ref-RFC1661">RFC1661</a>] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", STD
1188 51, <a href="./rfc1661">RFC 1661</a>, July 1994.
1189
1190 [<a id="ref-RFC2153">RFC2153</a>] Simpson, W., "PPP Vendor Extensions", <a href="./rfc2153">RFC 2153</a>, May 1997.
1191
1192 [<a id="ref-RFC2332">RFC2332</a>] Luciani, J., Katz, D., Piscitello, D., Cole, B., and N.
1193 Doraswamy, "NBMA Next Hop Resolution Protocol (NHRP)", <a href="./rfc2332">RFC</a>
1194 <a href="./rfc2332">2332</a>, April 1998.
1195
1196 [<a id="ref-RFC2464">RFC2464</a>] Crawford, M., "Transmission of IPv6 Packets over Ethernet
1197 Networks", <a href="./rfc2464">RFC 2464</a>, December 1998.
1198
1199 [<a id="ref-RFC2606">RFC2606</a>] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS
1200 Names", <a href="https://www.rfc-editor.org/bcp/bcp32">BCP 32</a>, <a href="./rfc2606">RFC 2606</a>, June 1999.
1201
1202 [<a id="ref-RFC3092">RFC3092</a>] Eastlake 3rd, D., Manros, C., and E. Raymond, "Etymology
1203 of "Foo"", <a href="./rfc3092">RFC 3092</a>, April 1 2001.
1204
1205 [<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
1206 Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006.
1207
1208 [<a id="ref-RFC4760">RFC4760</a>] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
1209 "Multiprotocol Extensions for BGP-4", <a href="./rfc4760">RFC 4760</a>, January
1210 2007.
1211
1212 [<a id="ref-RFC5214">RFC5214</a>] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site
1213 Automatic Tunnel Addressing Protocol (ISATAP)", <a href="./rfc5214">RFC 5214</a>,
1214 March 2008.
1215
1216 [<a id="ref-RFC5332">RFC5332</a>] Eckert, T., Rosen, E., Ed., Aggarwal, R., and Y. Rekhter,
1217 "MPLS Multicast Encapsulations", <a href="./rfc5332">RFC 5332</a>, August 2008.
1218
1219 [<a id="ref-RFC5342">RFC5342</a>] Eastlake 3rd, D., "IANA Considerations and IETF Protocol
1220 Usage for IEEE 802 Parameters", <a href="https://www.rfc-editor.org/bcp/bcp141">BCP 141</a>, <a href="./rfc5342">RFC 5342</a>,
1221 September 2008.
1222
1223 [<a id="ref-RFC5737">RFC5737</a>] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
1224 Reserved for Documentation", <a href="./rfc5737">RFC 5737</a>, January 2010.
1225
1226
1227
1228 <span class="grey">Eastlake &amp; Abley BCP [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1231
1232
1233 [<a id="ref-RFC5798">RFC5798</a>] Nadas, S., Ed., "Virtual Router Redundancy Protocol (VRRP)
1234 Version 3 for IPv4 and IPv6", <a href="./rfc5798">RFC 5798</a>, March 2010.
1235
1236 [<a id="ref-RFC6034">RFC6034</a>] Thaler, D., "Unicast-Prefix-Based IPv4 Multicast
1237 Addresses", <a href="./rfc6034">RFC 6034</a>, October 2010.
1238
1239 [<a id="ref-RFC6895">RFC6895</a>] Eastlake 3rd, D., "Domain Name System (DNS) IANA
1240 Considerations", <a href="https://www.rfc-editor.org/bcp/bcp42">BCP 42</a>, <a href="./rfc6895">RFC 6895</a>, April 2013.
1241
1242 [<a id="ref-RFC7043">RFC7043</a>] Abley, J., "Resource Records for EUI-48 and EUI-64
1243 Addresses in the DNS", <a href="./rfc7043">RFC 7043</a>, October 2013.
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Eastlake &amp; Abley BCP [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1287
1288
1289 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Templates</span>
1290
1291 This appendix provides the specific templates for IANA assignments of
1292 parameters. Explanatory words in parentheses in the templates below
1293 may be deleted in a completed template as submitted to IANA.
1294
1295 <span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. EUI-48/EUI-64 Identifier or Identifier Block Template</span>
1296
1297 Applicant Name:
1298
1299 Applicant Email:
1300
1301 Applicant Telephone: (starting with country code)
1302
1303 Use Name: (brief name of Parameter use such as "Foo Protocol"
1304 [<a href="./rfc3092" title="&quot;Etymology of &quot;">RFC3092</a>])
1305
1306 Document: (ID or RFC specifying use to which the identifier or block
1307 of identifiers will be put.)
1308
1309 Specify whether this is an application for EUI-48 or EUI-64
1310 identifiers:
1311
1312 Size of Block requested: (must be a power-of-two-sized block, can be
1313 a block of size one (2**0))
1314
1315 Specify multicast, unicast, or both:
1316
1317 <span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. IANA OUI-Based Protocol Number Template</span>
1318
1319 Applicant Name:
1320
1321 Applicant Email:
1322
1323 Applicant Telephone: (starting with country code)
1324
1325 Use Name: (brief name of use of code point such as "Foo Protocol")
1326
1327 Document: (ID or RFC specifying use to which the protocol identifier
1328 will be put.)
1329
1330 Note: (any additional note)
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Eastlake &amp; Abley BCP [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1343
1344
1345 <span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>. Other IANA OUI-Based Parameter Template</span>
1346
1347 Applicant Name:
1348
1349 Applicant Email:
1350
1351 Applicant Telephone: (starting with country code)
1352
1353 Protocol where the OUI-Based Parameter for which a value is being
1354 requested appears: (such as: Cipher Suite selection in IEEE 802.11)
1355
1356 Use Name: (brief name of use of code point to be assigned, such as
1357 "Foo Cipher Suite" [<a href="./rfc3092" title="&quot;Etymology of &quot;">RFC3092</a>])
1358
1359 Document: (ID or RFC specifying use to which the other IANA OUI-based
1360 parameter value will be put.)
1361
1362 Note: (any additional note)
1363
1364 <span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Ethertypes</span>
1365
1366 This appendix lists some Ethertypes specified for IETF protocols or
1367 by IEEE 802 as known at the time of publication. A more up-to-date
1368 list may be available on the IANA web site, currently at [<a href="#ref-IANA">IANA</a>]. The
1369 IEEE Registration Authority page of Ethertypes,
1370 <a href="http://standards.ieee.org/regauth/ethertype/eth.txt">http://standards.ieee.org/regauth/ethertype/eth.txt</a>, may also be
1371 useful. See <a href="#section-3">Section 3</a> above.
1372
1373 <span class="h3"><a class="selflink" id="appendix-B.1" href="#appendix-B.1">B.1</a>. Some Ethertypes Specified by the IETF</span>
1374
1375 0x0800 Internet Protocol Version 4 (IPv4)
1376 0x0806 Address Resolution Protocol (ARP)
1377 0x0808 Frame Relay ARP
1378 0x22F3 TRILL
1379 0x22F4 L2-IS-IS
1380 0x8035 Reverse Address Resolution Protocol (RARP)
1381 0x86DD Internet Protocol Version 6 (IPv6)
1382 0x880B Point-to-Point Protocol (PPP)
1383 0x880C General Switch Management Protocol (GSMP)
1384 0x8847 MPLS
1385 0x8848 MPLS with upstream-assigned label
1386 0x8861 Multicast Channel Allocation Protocol (MCAP)
1387 0x8863 PPP over Ethernet (PPPoE) Discovery Stage
1388 0x8864 PPP over Ethernet (PPPoE) Session Stage
1389 0x893B TRILL Fine Grained Labeling (FGL)
1390 0x8946 TRILL RBridge Channel
1391
1392
1393
1394
1395
1396 <span class="grey">Eastlake &amp; Abley BCP [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1399
1400
1401 <span class="h3"><a class="selflink" id="appendix-B.2" href="#appendix-B.2">B.2</a>. Some IEEE 802 Ethertypes</span>
1402
1403 0x8100 IEEE Std 802.1Q - Customer VLAN Tag Type (C-Tag, formerly
1404 called the Q-Tag) (initially Wellfleet)
1405 0x8808 IEEE Std 802.3 - Ethernet Passive Optical Network (EPON)
1406 0x888E IEEE Std 802.1X - Port-based network access control
1407 0x88A8 IEEE Std 802.1Q - Service VLAN tag identifier (S-Tag)
1408 0x88B5 IEEE Std 802 - Local Experimental Ethertype
1409 0x88B6 IEEE Std 802 - Local Experimental Ethertype
1410 0x88B7 IEEE Std 802 - OUI Extended Ethertype
1411 0x88C7 IEEE Std 802.11 - Pre-Authentication (802.11i)
1412 0x88CC IEEE Std 802.1AB - Link Layer Discovery Protocol (LLDP)
1413 0x88E5 IEEE Std 802.1AE - Media Access Control Security
1414 0x88F5 IEEE Std 802.1Q - Multiple VLAN Registration Protocol
1415 (MVRP)
1416 0x88F6 IEEE Std 802.1Q - Multiple Multicast Registration
1417 Protocol (MMRP)
1418 0x890D IEEE Std 802.11 - Fast Roaming Remote Request (802.11r)
1419 0x8917 IEEE Std 802.21 - Media Independent Handover Protocol
1420 0x8929 IEEE Std 802.1Qbe - Multiple I-SID Registration Protocol
1421 0x8940 IEEE Std 802.1Qbg - ECP Protocol (also used in 802.1BR)
1422
1423 <span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">Appendix C</a>. Documentation Protocol Number</span>
1424
1425 Below is the template based on which an IANA OUI-based protocol
1426 number value was assigned for document use. (See <a href="#section-3">Section 3</a> and
1427 <a href="#appendix-A.2">Appendix A.2</a>.)
1428
1429 Applicant Name: Donald E. Eastlake 3rd
1430
1431 Applicant Email: [email protected]
1432
1433 Applicant Telephone: 1-508-333-2270
1434
1435 Use Name: Documentation
1436
1437 Document: This document.
1438
1439 Note: Request value 0x0042
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">Eastlake &amp; Abley BCP [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc7042">RFC 7042</a> IANA/IETF and IEEE 802 Parameters October 2013</span>
1455
1456
1457 Authors' Addresses
1458
1459 Donald E. Eastlake 3rd
1460 Huawei Technologies
1461 155 Beaver Street
1462 Milford, MA 01757
1463 USA
1464
1465 Phone: +1-508-634-2066
1466 EMail: [email protected]
1467
1468
1469 Joe Abley
1470 Dyn, Inc.
1471 470 Moore Street
1472 London, ON N6C 2C2
1473 Canada
1474
1475 Phone: +1 519 670 9327
1476 EMail: [email protected]
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508 Eastlake &amp; Abley BCP [Page 27]
1509 </pre>