draft-arkko-arp-iana-rules-05.txt		draft-arkko-arp-iana-rules.txt
	Network Working Group J. Arkko		Network Working Group J. Arkko
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Updates: C. Pignataro		Updates: C. Pignataro
	826,951,1044,1329,2131,2132,2176,2225,2834,2835,3315,4338,4361,4701Cisco		826,951,1044,1329,2131,2132,2176,2225,2834,2835,3315,4338,4361,4701Cisco
	(if approved) December 2, 2008		(if approved) February 12, 2009
	Intended status: Standards Track		Intended status: Standards Track
	Expires: June 5, 2009		Expires: August 16, 2009
	IANA Allocation Guidelines for the Address Resolution Protocol (ARP)		IANA Allocation Guidelines for the Address Resolution Protocol (ARP)
	draft-arkko-arp-iana-rules-05		draft-arkko-arp-iana-rules-06
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		This Internet-Draft is submitted to IETF in full conformance with the
	applicable patent or other IPR claims of which he or she is aware		provisions of BCP 78 and BCP 79.
	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		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on June 5, 2009.		This Internet-Draft will expire on August 16, 2009.
			Copyright Notice
			Copyright (c) 2009 IETF Trust and the persons identified as the
			document authors. All rights reserved.
			This document is subject to BCP 78 and the IETF Trust's Legal
			Provisions Relating to IETF Documents
			(http://trustee.ietf.org/license-info) in effect on the date of
			publication of this document. Please review these documents
			carefully, as they describe your rights and restrictions with respect
			to this document.
	Abstract		Abstract
	This document specifies the IANA guidelines for allocating new values		This document specifies the IANA guidelines for allocating new values
	in the Address Resolution Protocol (ARP). This document also		in the Address Resolution Protocol (ARP). This document also
	reserves some numbers for experimentation purposes. The changes also		reserves some numbers for experimentation purposes. The changes also
	affect other protocols that employ values from the ARP name spaces.		affect other protocols that employ values from the ARP name spaces.
	1. Introduction		1. Introduction
	skipping to change at page 2, line 23		skipping to change at page 2, line 34
	Configuration Protocol (DHCP) [RFC2131], as well as in the "hardware		Configuration Protocol (DHCP) [RFC2131], as well as in the "hardware
	type" field in the DHCP Unique Identifiers in DHCPv6 [RFC3315].		type" field in the DHCP Unique Identifiers in DHCPv6 [RFC3315].
	These protocols are therefore affected by the update in the IANA		These protocols are therefore affected by the update in the IANA
	rules. Other affected specifications include the specialized address		rules. Other affected specifications include the specialized address
	resolution mechanisms in HYPERchannel [RFC1044], DHCP options		resolution mechanisms in HYPERchannel [RFC1044], DHCP options
	[RFC2132], [RFC4361], ATM (Asynchronous Transfer Mode) ARP [RFC2225],		[RFC2132], [RFC4361], ATM (Asynchronous Transfer Mode) ARP [RFC2225],
	HARP (High-Performance Parallel Interface ARP) [RFC2834], [RFC2835],		HARP (High-Performance Parallel Interface ARP) [RFC2834], [RFC2835],
	Dual MAC FDDI (Fiber Distributed Data Interface) ARP [RFC1329], MAPOS		Dual MAC FDDI (Fiber Distributed Data Interface) ARP [RFC1329], MAPOS
	(Multiple Access Protocol over Synchronous Optical Network/		(Multiple Access Protocol over Synchronous Optical Network/
	Synchronous Digital Hierarchy) ARP [RFC2176], FC (Fibre Channel) ARP		Synchronous Digital Hierarchy) ARP [RFC2176], FC (Fibre Channel) ARP
	[RFC4338], and DNS Resource Records [RFC4701].		[RFC4338], and the DNS DHCID Resource Record [RFC4701].
	The IANA guidelines are given in Section 2. Previously, no IANA		The IANA guidelines are given in Section 2. Previously, no IANA
	guidance existed for such allocations.		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		This document also reserves some numbers for experimentation
	purposes. These numbers are given in Section 3.		purposes. These numbers are given in Section 3.
	2. IANA Considerations		2. IANA Considerations
	The following rules apply to the fields of ARP:		The following rules apply to the fields of ARP:
	ar$hrd (16 bits) Hardware address space		ar$hrd (16 bits) Hardware address space
	skipping to change at page 3, line 20		skipping to change at page 3, line 37
	ar$pro (16 bits) Protocol address space		ar$pro (16 bits) Protocol address space
	These numbers share the Ethertype space. The Ethertype space is		These numbers share the Ethertype space. The Ethertype space is
	administered as described in [RFC5342].		administered as described in [RFC5342].
	ar$op (16 bits) Opcode		ar$op (16 bits) Opcode
	Requests for new ar$op values are made through IETF Review or IESG		Requests for new ar$op values are made through IETF Review or IESG
	Approval [RFC5226].		Approval [RFC5226].
			Upon the approval of this specification, IANA should update all three
			registration policies listed in arp-parameters registry as specified
			in the above list, and add a reference to either this RFC or RFC
			5342, as appropriate. RFC Editor: This paragraph can be removed upon
			publication.
	3. Allocations Defined in This Document		3. Allocations Defined in This Document
	When testing new protocol extension ideas, it is often necessary to		When testing new protocol extension ideas, it is often necessary to
	use an actual constant in order to use the new function, even when		use an actual constant in order to use the new function, even when
	testing in a closed environment. This document reserves the		testing in a closed environment. This document reserves the
	following numbers for experimentation purposes in ARP:		following numbers for experimentation purposes in ARP:
	o Two new ar$hrd values are allocated for experimental purposes,		o Two new ar$hrd values are allocated for experimental purposes,
	HW_EXP1 (TBD-BY-IANA-1, but below 256) and HW_EXP2 (TBD-BY-IANA-2,		HW_EXP1 (TBD-BY-IANA-1, but below 256) and HW_EXP2 (TBD-BY-IANA-2,
	but above 255 and preferably with different values in the least		but above 255 and preferably with different values in the least
	skipping to change at page 3, line 43		skipping to change at page 4, line 18
	purposes, OP_EXP1 (TBD-BY-IANA-3, any value will be sufficient)		purposes, OP_EXP1 (TBD-BY-IANA-3, any value will be sufficient)
	and OP_EXP2 (TBD-BY-IANA-4, any value will be sufficient).		and OP_EXP2 (TBD-BY-IANA-4, any value will be sufficient).
	Note that [RFC5342], Section B.2 lists two Ethertypes that can be		Note that [RFC5342], Section B.2 lists two Ethertypes that can be
	used for experimental purposes.		used for experimental purposes.
	In addition, for both ar$hrd and ar$op the values 0 and 65535 are		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		marked as reserved. This means that they are not available for
	allocation.		allocation.
			Upon the approval of this specification, IANA should add the two new
			allocations and two reserved values for both ar$hrd and ar$op to the
			arp-parameters registry, and reference this RFC. RFC Editor: This
			paragraph can be removed upon publication.
	4. Security Considerations		4. Security Considerations
	This specification does not change the security properties of the		This specification does not change the security properties of the
	affected protocols.		affected protocols.
	However, a few words are necessary about the use of the experimental		However, a few words are necessary about the use of the experimental
	code points defined in Section 3. Potentially harmful side-effects		code points defined in Section 3. Potentially harmful side-effects
	from the use of the experimental values needs to be carefully		from the use of the experimental values needs to be carefully
	evaluated before deploying any experiment across networks that the		evaluated before deploying any experiment across networks that the
	owner of the experiment does not entirely control. Guidance given in		owner of the experiment does not entirely control. Guidance given in
	[RFC3692] about the use of experimental values needs to be followed.		[RFC3692] about the use of experimental values needs to be followed.
	5. Acknowledgments		5. Acknowledgments
	The lack of any current rules has come up as new values were		The lack of any current rules has come up as new values were
	requested from IANA. The author would like to thank Michelle Cotton		requested from IANA and they contacted IESG for advice. The author
	in particular for bringing this issue up. When no rules exist, IANA		would like to thank Michelle Cotton in particular for bringing this
	consults the IESG for approval of the new values. The purpose of		issue up. The author would also like to thank Brian Carpenter,
	this specification is to establish the rules and allow IANA to		Thomas Narten, Scott Bradner, Donald Eastlake, Andrew G. Malis, Brian
	operate based on the rules, without requiring confirmation from the		Haberman, Robert Sparks, Larry Zhu, and Dave Thaler for feedback.
	IESG. The author would also like to thank Brian Carpenter, Thomas
	Narten, Scott Bradner, Donald Eastlake, Andrew G. Malis, Brian
	Haberman, Robert Sparks, and Dave Thaler for feedback.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or		[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or
	converting network protocol addresses to 48.bit Ethernet		converting network protocol addresses to 48.bit Ethernet
	address for transmission on Ethernet hardware", STD 37,		address for transmission on Ethernet hardware", STD 37,
	RFC 826, November 1982.		RFC 826, November 1982.
	skipping to change at page 7, line 4		skipping to change at line 284
	Email: jari.arkko@piuha.net		Email: jari.arkko@piuha.net
	Carlos Pignataro		Carlos Pignataro
	Cisco Systems		Cisco Systems
	7200-12 Kit Creek Road		7200-12 Kit Creek Road
	PO Box 14987		PO Box 14987
	Research Triangle Park, NC 27709		Research Triangle Park, NC 27709
	USA		USA
	Email: cpignata@cisco.com		Email: cpignata@cisco.com
	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.
End of changes. 11 change blocks.
	18 lines changed or deleted		38 lines changed or added
This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/