< draft-bonica-special-purpose-01.txt		draft-bonica-special-purpose-02.txt >
	Network Working Group M. Cotton		Network Working Group M. Cotton
	Internet-Draft L. Vegoda		Internet-Draft L. Vegoda
	Obsoletes: 5156, 5735 Internet Corporation for		Obsoletes: 5156, 5735 Internet Corporation for
	(if approved) Assigned Names and Numbers		(if approved) Assigned Names and Numbers
	Updates: 4773,5736 (if approved) R. Bonica, Ed.		Updates: 4773,5736 (if approved) R. Bonica, Ed.
	Intended status: BCP Juniper Networks		Intended status: BCP Juniper Networks
	Expires: March 31, 2013 B. Haberman		Expires: April 1, 2013 B. Haberman
	Johns Hopkins University Applied		Johns Hopkins University Applied
	Physics Lab		Physics Lab
	September 27, 2012		September 28, 2012
	Special-Purpose Address Registries		Special-Purpose Address Registries
	draft-bonica-special-purpose-01		draft-bonica-special-purpose-02
	Abstract		Abstract
	This memo instructs IANA to restructure its IPv4 and IPv6 Special-		This memo instructs IANA to restructure its IPv4 and IPv6 Special-
	Purpose Address Registries. Upon restructuring, the aforementioned		Purpose Address Registries. Upon restructuring, the aforementioned
	registries will record all special-purpose address blocks,		registries will record all special-purpose address blocks,
	maintaining a common set of information regarding each address block.		maintaining a common set of information regarding each address block.
	This memo updates RFC 5736 and RFC 4773, which define the current		This memo updates RFC 5736 and RFC 4773, which define the current
	structure of the IPv4 and IPv6 Special-Purpose Address Registries.		structure of the IPv4 and IPv6 Special-Purpose Address Registries.
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	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."
	This Internet-Draft will expire on March 31, 2013.		This Internet-Draft will expire on April 1, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	skipping to change at page 2, line 26 ¶		skipping to change at page 2, line 26 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4		2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
	2.1. Information Requirements . . . . . . . . . . . . . . . . . 4		2.1. Information Requirements . . . . . . . . . . . . . . . . . 4
	2.2. IPv4 Special-Purpose Address Registry Entries . . . . . . 5		2.2. IPv4 Special-Purpose Address Registry Entries . . . . . . 5
	2.3. IPv6 Special-Purpose Address Registry Entries . . . . . . 11		2.3. IPv6 Special-Purpose Address Registry Entries . . . . . . 11
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 16		3. Security Considerations . . . . . . . . . . . . . . . . . . . 16
	4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17		4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
	5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17		5. Informative References . . . . . . . . . . . . . . . . . . . . 17
	5.1. Normative References . . . . . . . . . . . . . . . . . . . 17
	5.2. Informative References . . . . . . . . . . . . . . . . . . 17
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
	1. Introduction		1. Introduction
	In order to support new protocols and practices, the IETF		In order to support new protocols and practices, the IETF
	occasionally reserves an address block a for special purpose. For		occasionally reserves an address block a for special purpose. For
	example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to		example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to
	represent the local (i.e., "this") network. Likewise, [RFC4291]		represent the local (i.e., "this") network. Likewise, [RFC4291]
	reserves an IPv6 address block (fe80::/10) to represent link-scoped		reserves an IPv6 address block (fe80::/10) to represent link-scoped
	unicast addresses.		unicast addresses.
	skipping to change at page 16, line 38 ¶		skipping to change at page 16, line 38 ¶
	| Allocation Date | February 2006 |		| Allocation Date | February 2006 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | True |		| Destination | True |
	| Routable | True |		| Routable | True |
	| Global | N/A |		| Global | N/A |
	+------------------+---------------+		+------------------+---------------+
	Table 30: Multicast		Table 30: Multicast
	[5] See [RFC4007] for global scoping for details		[5] See [RFC4007] for global scoping details
	3. Security Considerations		3. Security Considerations
	Security of the Internet's routing system relies on the ability to		Security of the Internet's routing system relies on the ability to
	authenticate an assertion of unique control of an address block.		authenticate an assertion of unique control of an address block.
	Measures to authenticate such assertions rely on validation that the		Measures to authenticate such assertions rely on validation that the
	address block forms part of an existing allocated address block, and		address block forms part of an existing allocated address block, and
	that there is a trustable and unique reference in the IANA address		that there is a trustable and unique reference in the IANA address
	registries.		registries.
	skipping to change at page 17, line 19 ¶		skipping to change at page 17, line 19 ¶
	parseable, and also the use of file signatures and associated		parseable, and also the use of file signatures and associated
	certificate mechanisms to allow applications to confirm that the		certificate mechanisms to allow applications to confirm that the
	registry contents are current, and that they have been published by		registry contents are current, and that they have been published by
	the IANA.		the IANA.
	4. Acknowledgements		4. Acknowledgements
	The authors would like to acknowledge an anonymous donor, without		The authors would like to acknowledge an anonymous donor, without
	whom this document would not have been written.		whom this document would not have been written.
	5. References		5. Informative References
	5.1. Normative References
	[RFC4773] Huston, G., "Administration of the IANA Special Purpose
	IPv6 Address Block", RFC 4773, December 2006.
	[RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156,
	April 2008.
	[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
	BCP 153, RFC 5735, January 2010.
	[RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special
	Purpose Address Registry", RFC 5736, January 2010.
	5.2. Informative References
	[RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5,		[RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5,
	RFC 919, October 1984.		RFC 919, October 1984.
	[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,		[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
	RFC 1112, August 1989.		RFC 1112, August 1989.
	[RFC1122] Braden, R., "Requirements for Internet Hosts -		[RFC1122] Braden, R., "Requirements for Internet Hosts -
	Communication Layers", STD 3, RFC 1122, October 1989.		Communication Layers", STD 3, RFC 1122, October 1989.
	skipping to change at page 18, line 38 ¶		skipping to change at page 18, line 21 ¶
	[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast		[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
	Addresses", RFC 4193, October 2005.		Addresses", RFC 4193, October 2005.
	[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing		[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
	Architecture", RFC 4291, February 2006.		Architecture", RFC 4291, February 2006.
	[RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through		[RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through
	Network Address Translations (NATs)", RFC 4380,		Network Address Translations (NATs)", RFC 4380,
	February 2006.		February 2006.
			[RFC4773] Huston, G., "Administration of the IANA Special Purpose
			IPv6 Address Block", RFC 4773, December 2006.
	[RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix		[RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix
	for Overlay Routable Cryptographic Hash Identifiers		for Overlay Routable Cryptographic Hash Identifiers
	(ORCHID)", RFC 4843, April 2007.		(ORCHID)", RFC 4843, April 2007.
			[RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156,
			April 2008.
	[RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D.		[RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D.
	Dugatkin, "IPv6 Benchmarking Methodology for Network		Dugatkin, "IPv6 Benchmarking Methodology for Network
	Interconnect Devices", RFC 5180, May 2008.		Interconnect Devices", RFC 5180, May 2008.
			[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
			BCP 153, RFC 5735, January 2010.
			[RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special
			Purpose Address Registry", RFC 5736, January 2010.
	[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks		[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
	Reserved for Documentation", RFC 5737, January 2010.		Reserved for Documentation", RFC 5737, January 2010.
	[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for		[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for
	IPv4 Multicast Address Assignments", BCP 51, RFC 5771,		IPv4 Multicast Address Assignments", BCP 51, RFC 5771,
	March 2010.		March 2010.
	[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-		[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
	Stack Lite Broadband Deployments Following IPv4		Stack Lite Broadband Deployments Following IPv4
	Exhaustion", RFC 6333, August 2011.		Exhaustion", RFC 6333, August 2011.
End of changes. 10 change blocks.
	25 lines changed or deleted		19 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/