1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Network Working Group J. Arkko
Request for Comments: 5494 Ericsson
Updates: <a href="./rfc826">826</a>, <a href="./rfc951">951</a>, <a href="./rfc1044">1044</a>, <a href="./rfc1329">1329</a>, <a href="./rfc2131">2131</a>, C. Pignataro
<a href="./rfc2132">2132</a>, <a href="./rfc2176">2176</a>, <a href="./rfc2225">2225</a>, <a href="./rfc2834">2834</a>, <a href="./rfc2835">2835</a>, Cisco Systems
3315, 4338, 4361, 4701 April 2009
Category: Standards Track
<span class="h1">IANA Allocation Guidelines for the Address Resolution Protocol (ARP)</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This document specifies the IANA guidelines for allocating new values
in the Address Resolution Protocol (ARP). This document also
reserves some numbers for experimentation purposes. The changes also
affect other protocols that employ values from the ARP name spaces.
<span class="grey">Arkko & Pignataro Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5494">RFC 5494</a> ARP IANA Rules April 2009</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies the IANA guidelines [<a href="./rfc5226" title="">RFC5226</a>] for allocating
new values for various fields in the Address Resolution Protocol
(ARP) [<a href="./rfc0826" title=""Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48.bit Ethernet address for transmission on Ethernet hardware"">RFC0826</a>]. The change is also applicable to extensions of ARP
that use the same message format, such as [<a href="./rfc0903" title=""Reverse Address Resolution Protocol"">RFC0903</a>], [<a href="./rfc1931" title=""Dynamic RARP Extensions for Automatic Network Address Acquisition"">RFC1931</a>], and
[<a href="./rfc2390" title=""Inverse Address Resolution Protocol"">RFC2390</a>].
The change also affects other protocols that employ values from the
ARP name spaces. For instance, the ARP hardware address type
(ar$hrd) number space is also used in the "htype" (hardware address
type) fields in the Bootstrap Protocol (BOOTP) [<a href="./rfc0951" title=""Bootstrap Protocol"">RFC0951</a>] and Dynamic
Host Configuration Protocol (DHCP) [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>], as well as in the
"hardware type" field in the DHCP Unique Identifiers in DHCPv6
[<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>]. These protocols are therefore affected by the update in
the IANA rules. Other affected specifications include the
specialized address resolution mechanisms in:
o HYPERchannel [<a href="./rfc1044" title=""Internet Protocol on Network System's HYPERchannel: Protocol specification"">RFC1044</a>]
o DHCP options [<a href="./rfc2132" title=""DHCP Options and BOOTP Vendor Extensions"">RFC2132</a>] [<a href="./rfc4361" title=""Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)"">RFC4361</a>]
o ATM (Asynchronous Transfer Mode) ARP [<a href="./rfc2225" title=""Classical IP and ARP over ATM"">RFC2225</a>]
o HARP (High-Performance Parallel Interface ARP) [<a href="./rfc2834" title=""ARP and IP Broadcast over HIPPI-800"">RFC2834</a>] [<a href="./rfc2835" title=""IP and ARP over HIPPI-6400 (GSN)"">RFC2835</a>]
o Dual MAC (Media Access Control) FDDI (Fiber Distributed Data
Interface) ARP [<a href="./rfc1329" title=""Thoughts on Address Resolution for Dual MAC FDDI Networks"">RFC1329</a>]
o MAPOS (Multiple Access Protocol over Synchronous Optical Network/
Synchronous Digital Hierarchy) ARP [<a href="./rfc2176" title=""IPv4 over MAPOS Version 1"">RFC2176</a>]
o FC (Fibre Channel) ARP [<a href="./rfc4338" title=""Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel"">RFC4338</a>]
o DNS DHCID Resource Record [<a href="./rfc4701" title=""A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)"">RFC4701</a>]
The IANA guidelines are given in <a href="#section-2">Section 2</a>. Previously, no IANA
guidance existed for such allocations. The purpose of this document
is to allow IANA to manage number assignments based on these
guidelines in a consistent manner.
This document also reserves some numbers for experimentation
purposes. These numbers are given in <a href="#section-3">Section 3</a>.
<span class="grey">Arkko & Pignataro Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5494">RFC 5494</a> ARP IANA Rules April 2009</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IANA Considerations</span>
The following rules apply to the fields of ARP:
ar$hrd (16 bits) Hardware address space
Requests for ar$hrd values below 256 or for a batch of more than
one new value are made through Expert Review [<a href="./rfc5226" title="">RFC5226</a>].
Note that certain protocols, such as BOOTP and DHCPv4, employ
these values within an 8-bit field. The expert should determine
that a need to allocate the new values exists and that the
existing values are insufficient to represent the new hardware
address types. The expert should also determine the applicability
of the request and assign values higher than 255 for requests that
do not apply to BOOTP/DHCPv4. Similarly, the expert should assign
1-octet values for requests that apply to BOOTP/DHCPv4, as for
example the "IPsec tunnel" with value 31 [<a href="./rfc3456" title=""Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode"">RFC3456</a>]. Conversely,
ARP-only uses, without a foreseeable reason to use the same value
in BOOTP/DHCPv4, should favor 2-octet values.
Requests for individual new ar$hrd values that do not specify a
value, or where the requested value is greater than 255, are made
through First Come First Served [<a href="./rfc5226" title="">RFC5226</a>]. The assignment will
always result in a 2-octet value.
ar$pro (16 bits) Protocol address space
These numbers share the Ethertype space. The Ethertype space is
administered as described in [<a href="./rfc5342" title=""IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters"">RFC5342</a>].
ar$op (16 bits) Opcode
Requests for new ar$op values are made through IETF Review or IESG
Approval [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Allocations Defined in This Document</span>
When testing new protocol extension ideas, it is often necessary to
use an actual constant in order to use the new function, even when
testing in a closed environment. This document reserves the
following numbers for experimentation purposes in ARP:
o Two new ar$hrd values are allocated for experimental purposes:
HW_EXP1 (36) and HW_EXP2 (256). Note that these two new values
were purposely chosen so that one would be below 256 and the other
would be above 255, and so that there would be different values in
the least and most significant octets.
<span class="grey">Arkko & Pignataro Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5494">RFC 5494</a> ARP IANA Rules April 2009</span>
o Two new values for the ar$op are allocated for experimental
purposes: OP_EXP1 (24) and OP_EXP2 (25).
Note that <a href="./rfc5342#appendix-B.2">Appendix B.2 of [RFC5342]</a> lists two Ethertypes that can be
used for experimental purposes.
In addition, for both ar$hrd and ar$op, the values 0 and 65535 are
marked as reserved. This means that they are not available for
allocation.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This specification does not change the security properties of the
affected protocols.
However, a few words are necessary about the use of the experimental
code points defined in <a href="#section-3">Section 3</a>. Potentially harmful side effects
from the use of the experimental values need to be carefully
evaluated before deploying any experiment across networks that the
owner of the experiment does not entirely control. Guidance given in
[<a href="./rfc3692" title=""Assigning Experimental and Testing Numbers Considered Useful"">RFC3692</a>] about the use of experimental values needs to be followed.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
The lack of any current rules has come up as new values were
requested from IANA, who contacted the IESG for advice. The author
would like to thank Michelle Cotton in particular for bringing up
this issue. The author would also like to thank Brian Carpenter,
Thomas Narten, Scott Bradner, Donald Eastlake, Andrew G. Malis, Brian
Haberman, Robert Sparks, Larry Zhu, and Dave Thaler for feedback.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC0826">RFC0826</a>] Plummer, D., "Ethernet Address Resolution Protocol: Or
converting network protocol addresses to 48.bit Ethernet
address for transmission on Ethernet hardware", STD 37,
<a href="./rfc826">RFC 826</a>, November 1982.
[<a id="ref-RFC0951">RFC0951</a>] Croft, B. and J. Gilmore, "Bootstrap Protocol", <a href="./rfc951">RFC 951</a>,
September 1985.
[<a id="ref-RFC1044">RFC1044</a>] Hardwick, K. and J. Lekashman, "Internet Protocol on
Network System's HYPERchannel: Protocol specification",
STD 45, <a href="./rfc1044">RFC 1044</a>, February 1988.
<span class="grey">Arkko & Pignataro Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5494">RFC 5494</a> ARP IANA Rules April 2009</span>
[<a id="ref-RFC1329">RFC1329</a>] Kuehn, P., "Thoughts on Address Resolution for Dual MAC
FDDI Networks", <a href="./rfc1329">RFC 1329</a>, May 1992.
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol",
<a href="./rfc2131">RFC 2131</a>, March 1997.
[<a id="ref-RFC2132">RFC2132</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997.
[<a id="ref-RFC2176">RFC2176</a>] Murakami, K. and M. Maruyama, "IPv4 over MAPOS Version 1",
<a href="./rfc2176">RFC 2176</a>, June 1997.
[<a id="ref-RFC2225">RFC2225</a>] Laubach, M. and J. Halpern, "Classical IP and ARP over
ATM", <a href="./rfc2225">RFC 2225</a>, April 1998.
[<a id="ref-RFC2834">RFC2834</a>] Pittet, J., "ARP and IP Broadcast over HIPPI-800",
<a href="./rfc2834">RFC 2834</a>, May 2000.
[<a id="ref-RFC2835">RFC2835</a>] Pittet, J., "IP and ARP over HIPPI-6400 (GSN)", <a href="./rfc2835">RFC 2835</a>,
May 2000.
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003.
[<a id="ref-RFC3692">RFC3692</a>] Narten, T., "Assigning Experimental and Testing Numbers
Considered Useful", <a href="https://www.rfc-editor.org/bcp/bcp82">BCP 82</a>, <a href="./rfc3692">RFC 3692</a>, January 2004.
[<a id="ref-RFC4338">RFC4338</a>] DeSanti, C., Carlson, C., and R. Nixon, "Transmission of
IPv6, IPv4, and Address Resolution Protocol (ARP) Packets
over Fibre Channel", <a href="./rfc4338">RFC 4338</a>, January 2006.
[<a id="ref-RFC4361">RFC4361</a>] Lemon, T. and B. Sommerfeld, "Node-specific Client
Identifiers for Dynamic Host Configuration Protocol
Version Four (DHCPv4)", <a href="./rfc4361">RFC 4361</a>, February 2006.
[<a id="ref-RFC4701">RFC4701</a>] Stapp, M., Lemon, T., and A. Gustafsson, "A DNS Resource
Record (RR) for Encoding Dynamic Host Configuration
Protocol (DHCP) Information (DHCID RR)", <a href="./rfc4701">RFC 4701</a>,
October 2006.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
[<a id="ref-RFC5342">RFC5342</a>] Eastlake. , D., "IANA Considerations and IETF Protocol
Usage for IEEE 802 Parameters", <a href="https://www.rfc-editor.org/bcp/bcp141">BCP 141</a>, <a href="./rfc5342">RFC 5342</a>,
September 2008.
<span class="grey">Arkko & Pignataro Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5494">RFC 5494</a> ARP IANA Rules April 2009</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC0903">RFC0903</a>] Finlayson, R., Mann, T., Mogul, J., and M. Theimer,
"Reverse Address Resolution Protocol", STD 38, <a href="./rfc903">RFC 903</a>,
June 1984.
[<a id="ref-RFC1931">RFC1931</a>] Brownell, D., "Dynamic RARP Extensions for Automatic
Network Address Acquisition", <a href="./rfc1931">RFC 1931</a>, April 1996.
[<a id="ref-RFC2390">RFC2390</a>] Bradley, T., Brown, C., and A. Malis, "Inverse Address
Resolution Protocol", <a href="./rfc2390">RFC 2390</a>, September 1998.
[<a id="ref-RFC3456">RFC3456</a>] Patel, B., Aboba, B., Kelly, S., and V. Gupta, "Dynamic
Host Configuration Protocol (DHCPv4) Configuration of
IPsec Tunnel Mode", <a href="./rfc3456">RFC 3456</a>, January 2003.
<span class="grey">Arkko & Pignataro Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5494">RFC 5494</a> ARP IANA Rules April 2009</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Changes from the Original RFCs</span>
This document specifies only the IANA rules associated with various
fields in ARP. The specification of these rules also affects the
allocation of corresponding fields in protocols listed in <a href="#section-1">Section 1</a>
that share the registry. This document does not make any changes in
the operation of these protocols themselves.
Authors' Addresses
Jari Arkko
Ericsson
Jorvas 02420
Finland
EMail: jari.arkko@piuha.net
Carlos Pignataro
Cisco Systems
7200-12 Kit Creek Road
Research Triangle Park, NC 27709
USA
EMail: cpignata@cisco.com
Arkko & Pignataro Standards Track [Page 7]
</pre>
|
