One document matched: draft-arkko-arp-iana-rules-02.txt
Differences from draft-arkko-arp-iana-rules-01.txt
Network Working Group J. Arkko
Internet-Draft Ericsson
Updates: C. Pignataro
826,1044,951,2131,2132,2225,2834,2835,3315,4338,4361,4701 Cisco Systems
(if approved) November 28, 2008
Intended status: Standards Track
Expires: June 1, 2009
IANA Allocation Guidelines for the Address Resolution Protocol (ARP)
draft-arkko-arp-iana-rules-02
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 1, 2009.
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.
1. Introduction
This document specifies the IANA guidelines [RFC5226] for allocating
Arkko & Pignataro Expires June 1, 2009 [Page 1]
Internet-Draft ARP IANA Rules November 2008
new values for various fields in the Address Resolution Protocol
(ARP) [RFC0826]. The change is also applicable to extensions of ARP
that use the same message format, such as [RFC0903] and [RFC2390].
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 Bootstrap Protocol (BOOTP) [RFC0951] and Dynamic Host
Configuration Protocol (DHCP) [RFC2131], as well as in the "hardware
type" field in the DHCP Unique Identifiers in DHCPv6 [RFC3315].
These protocols are therefore affected by the update in the IANA
rules. Other affected specifications include the specialized address
resolution mechanisms in HYPERchannel [RFC1044], DHCP options
[RFC2132], [RFC4361], ATM (Asynchronous Transfer Mode) ARP [RFC2225],
HARP (High-Performance Parallel Interface ARP) [RFC2834], [RFC2835],
FC (Fibre Channel) ARP [RFC4338], and DNS Resource Records [RFC4701].
The IANA guidelines are given in Section 2. Previously, no IANA
guidance existed for such allocations.
This document also reserves some numbers for experimentation
purposes. These numbers are given in Section 3.
2. IANA Considerations
The following rules apply to the fields of ARP:
ar$hrd (16 bits) Hardware address space
Requests for individual new ar$hrd values are made through First
Come First Served [RFC5226]. Requests for ar$hrd values below 256
or a batch of several new values are made through Expert Review
[RFC5226]. Note that certain protocols, such as BOOTP and DHCPv4
employ these values within a 8 bit field. The expert should
determine that the 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 one-octet values for requests that clearly apply to BOOTP/
DHCPv4 but not ARP, as for example the "IPsec tunnel" with value
31 [RFC3456]. Conversely, ARP-only uses should favor 2-octet
values.
Arkko & Pignataro Expires June 1, 2009 [Page 2]
Internet-Draft ARP IANA Rules November 2008
ar$pro (16 bits) Protocol address space
These numbers share the Ethertype space. The Ethertype space is
administered as described in [RFC5342].
ar$op (16 bits) Opcode
Requests for new ar$op values are made through IETF Review or IESG
Approval [RFC5226].
3. Allocations Defined in This Document
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 One new ar$hrd value is allocated for experimental purposes,
HW_EXP (TBD).
o Two new values for the ar$op are allocated for experimental
purposes, OP_EXP1 (TBD, but below 256) and OP_EXP2 (TBD, but above
255 and preferrably with different values in the least and most
significant octets).
Note that [RFC5342], Section B.2 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.
4. Security Considerations
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 Section 3. Potentially harmful side-effects
from the use of the experimental values needs to be carefully
evaluated before deploying any experiment across networks that the
owner of the experiment does not entirely control. Guidance given in
[RFC3692] about the use of experimental values needs to be followed.
Arkko & Pignataro Expires June 1, 2009 [Page 3]
Internet-Draft ARP IANA Rules November 2008
5. Acknowledgments
The lack of any current rules has come up as new values were
requested from IANA. The author would like to thank Michelle Cotton
in particular for bringing this issue up. When no rules exist, IANA
consults the IESG for approval of the new values. The purpose of
this specification is to establish the rules and allow IANA to
operate based on the rules, without requiring confirmation from the
IESG. The author would also like to thank Brian Carpenter, Thomas
Narten, Scott Bradner, Donald Eastlake, Andrew G. Malis, Brian
Haberman, and Dave Thaler for feedback.
6. References
6.1. Normative References
[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or
converting network protocol addresses to 48.bit Ethernet
address for transmission on Ethernet hardware", STD 37,
RFC 826, November 1982.
[RFC0951] Croft, B. and J. Gilmore, "Bootstrap Protocol", RFC 951,
September 1985.
[RFC1044] Hardwick, K. and J. Lekashman, "Internet Protocol on
Network System's HYPERchannel: Protocol specification",
STD 45, RFC 1044, February 1988.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997.
[RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997.
[RFC2225] Laubach, M. and J. Halpern, "Classical IP and ARP over
ATM", RFC 2225, April 1998.
[RFC2834] Pittet, J., "ARP and IP Broadcast over HIPPI-800",
RFC 2834, May 2000.
[RFC2835] Pittet, J., "IP and ARP over HIPPI-6400 (GSN)", RFC 2835,
May 2000.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003.
Arkko & Pignataro Expires June 1, 2009 [Page 4]
Internet-Draft ARP IANA Rules November 2008
[RFC3692] Narten, T., "Assigning Experimental and Testing Numbers
Considered Useful", BCP 82, RFC 3692, January 2004.
[RFC4338] DeSanti, C., Carlson, C., and R. Nixon, "Transmission of
IPv6, IPv4, and Address Resolution Protocol (ARP) Packets
over Fibre Channel", RFC 4338, January 2006.
[RFC4361] Lemon, T. and B. Sommerfeld, "Node-specific Client
Identifiers for Dynamic Host Configuration Protocol
Version Four (DHCPv4)", RFC 4361, February 2006.
[RFC4701] Stapp, M., Lemon, T., and A. Gustafsson, "A DNS Resource
Record (RR) for Encoding Dynamic Host Configuration
Protocol (DHCP) Information (DHCID RR)", RFC 4701,
October 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5342] Eastlake. , D., "IANA Considerations and IETF Protocol
Usage for IEEE 802 Parameters", BCP 141, RFC 5342,
September 2008.
6.2. Informative References
[RFC0903] Finlayson, R., Mann, T., Mogul, J., and M. Theimer,
"Reverse Address Resolution Protocol", STD 38, RFC 903,
June 1984.
[RFC2390] Bradley, T., Brown, C., and A. Malis, "Inverse Address
Resolution Protocol", RFC 2390, September 1998.
[RFC3456] Patel, B., Aboba, B., Kelly, S., and V. Gupta, "Dynamic
Host Configuration Protocol (DHCPv4) Configuration of
IPsec Tunnel Mode", RFC 3456, January 2003.
Appendix A. Changes from the Original RFCs
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 Section 1
that share the registry. This document does not make any changes in
the operation of these protocols themselves.
Arkko & Pignataro Expires June 1, 2009 [Page 5]
Internet-Draft ARP IANA Rules November 2008
Authors' Addresses
Jari Arkko
Ericsson
Jorvas 02420
Finland
Email: jari.arkko@piuha.net
Carlos Pignataro
Cisco Systems
7200-12 Kit Creek Road
PO Box 14987
Research Triangle Park, NC 27709
USA
Email: cpignata@cisco.com
Arkko & Pignataro Expires June 1, 2009 [Page 6]
Internet-Draft ARP IANA Rules November 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Arkko & Pignataro Expires June 1, 2009 [Page 7]
| PAFTECH AB 2003-2026 | 2026-04-23 09:49:43 |