< draft-bonica-special-purpose-02.txt		draft-bonica-special-purpose-03.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: April 1, 2013 B. Haberman		Expires: April 18, 2013 B. Haberman
	Johns Hopkins University Applied		Johns Hopkins University Applied
	Physics Lab		Physics Lab
	September 28, 2012		October 15, 2012
	Special-Purpose Address Registries		Special-Purpose Address Registries
	draft-bonica-special-purpose-02		draft-bonica-special-purpose-03
	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 April 1, 2013.		This Internet-Draft will expire on April 18, 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 25 ¶		skipping to change at page 2, line 25 ¶
	described in the Simplified BSD License.		described in the Simplified BSD License.
	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 . . . . . . . . . . . . . . . . . . . . . . . 16
	5. Informative References . . . . . . . . . . . . . . . . . . . . 17		5. Informative References . . . . . . . . . . . . . . . . . . . . 16
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
	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 5, line 33 ¶		skipping to change at page 5, line 33 ¶
	o Global - A boolean value indicating whether a IP datagram whose		o Global - A boolean value indicating whether a IP datagram whose
	destination address is drawn from the allocated special-purpose		destination address is drawn from the allocated special-purpose
	address block is routable beyond a specified administrative		address block is routable beyond a specified administrative
	domain.		domain.
	If the value of "Destination" is FALSE, the values of "Routable" and		If the value of "Destination" is FALSE, the values of "Routable" and
	"Global" must also be false.		"Global" must also be false.
	2.2. IPv4 Special-Purpose Address Registry Entries		2.2. IPv4 Special-Purpose Address Registry Entries
	Table 1 though Table 17, below, represent entries with which the IANA		Table 1 though Table 16, below, represent entries with which the IANA
	will initially populate the IPv4 Special-Purpose Address Registry.		will initially populate the IPv4 Special-Purpose Address Registry.
	+------------------+---------------------------+		+------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------------+		+------------------+---------------------------+
	| Prefix | 0.0.0.0/8 |		| Prefix | 0.0.0.0/8 |
	| Name | "This" Network |		| Name | "This" Network |
	| RFC | [RFC1122] Section 3.2.1.3 |		| RFC | [RFC1122] Section 3.2.1.3 |
	| Allocation Date | September, 1981 |		| Allocation Date | September, 1981 |
	| Termination Date | N/A |		| Termination Date | N/A |
	skipping to change at page 10, line 36 ¶		skipping to change at page 10, line 36 ¶
	| Allocation Date | January 2010 |		| Allocation Date | January 2010 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+----------------------------+		+------------------+----------------------------+
	Table 14: TEST-NET-3		Table 14: TEST-NET-3
	+------------------+-------------+
	| Attribute | Value |
	+------------------+-------------+
	| Prefix | 224.0.0.0/4 |
	| Name | Multicast |
	| RFC | [RFC5771] |
	| Allocation Date | March 2010 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | True |
	| Routable | True |
	| Global | N/A [2] |
	+------------------+-------------+
	Table 15: Multicast
	[2] See [RFC5771] for details.
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | 240.0.0.0/4 |		| Prefix | 240.0.0.0/4 |
	| Name | Reserved |		| Name | Reserved |
	| RFC | [RFC1112] Section 4 |		| RFC | [RFC1112] Section 4 |
	| Allocation Date | August 1989 |		| Allocation Date | August 1989 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+---------------------+		+------------------+---------------------+
	Table 16: Reserved for Future Use		Table 15: Reserved for Future Use
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | 255.255.255.255/32 |		| Prefix | 255.255.255.255/32 |
	| Name | Limited Broadcast |		| Name | Limited Broadcast |
	| RFC | [RFC0919] Section 7 |		| RFC | [RFC0919] Section 7 |
	| Allocation Date | October 1984 |		| Allocation Date | October 1984 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | True |		| Destination | True |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+---------------------+		+------------------+---------------------+
	Table 17: Limited Broadcast		Table 16: Limited Broadcast
	2.3. IPv6 Special-Purpose Address Registry Entries		2.3. IPv6 Special-Purpose Address Registry Entries
	Table 18 through Table 30, below, represent entries with which the		Table 17 through Table 28, below, represent entries with which the
	IANA will initially populate the IPv6 Special-Purpose Address		IANA will initially populate the IPv6 Special-Purpose Address
	Registry.		Registry.
	+------------------+------------------+		+------------------+------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+------------------+		+------------------+------------------+
	| Prefix | ::1/128 |		| Prefix | ::1/128 |
	| Name | Loopback Address |		| Name | Loopback Address |
	| RFC | [RFC4291] |		| RFC | [RFC4291] |
	| Allocation Date | February 2006 |		| Allocation Date | February 2006 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+------------------+		+------------------+------------------+
	Table 18: Loopback Address		Table 17: Loopback Address
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | ::/128 |		| Prefix | ::/128 |
	| Name | Unspecified Address |		| Name | Unspecified Address |
	| RFC | [RFC4291] |		| RFC | [RFC4291] |
	| Allocation Date | February 2006 |		| Allocation Date | February 2006 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | False |		| Destination | False |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+---------------------+		+------------------+---------------------+
	Table 19: Unspecified Address		Table 18: Unspecified Address
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | ::FFFF:0:0/96 |		| Prefix | ::FFFF:0:0/96 |
	| Name | IPv4-mapped Address |		| Name | IPv4-mapped Address |
	| RFC | [RFC4291] |		| RFC | [RFC4291] |
	| Allocation Date | February 2006 |		| Allocation Date | February 2006 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+---------------------+		+------------------+---------------------+
	Table 20: IPv4-mapped Address		Table 19: IPv4-mapped Address
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | 0100::/64 |		| Prefix | 0100::/64 |
	| Name | Discard-Only Prefix |		| Name | Discard-Only Prefix |
	| RFC | [RFC6666] |		| RFC | [RFC6666] |
	| Allocation Date | June 2012 |		| Allocation Date | June 2012 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Routable | True |		| Routable | True |
	| Global | False |		| Global | False |
	+------------------+---------------------+		+------------------+---------------------+
	Table 21: Discard-Only Prefix		Table 20: Discard-Only Prefix
	+------------------+---------------------------+		+------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------------+		+------------------+---------------------------+
	| Prefix | 2001:0000::/23 |		| Prefix | 2001:0000::/23 |
	| Name | IETF Protocol Assignments |		| Name | IETF Protocol Assignments |
	| RFC | [RFC2928] |		| RFC | [RFC2928] |
	| Allocation Date | September 2000 |		| Allocation Date | September 2000 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False[3] |		| Source | False[2] |
	| Destination | False[3] |		| Destination | False[2] |
	| Routable | False[3] |		| Routable | False[2] |
	| Global | False[3] |		| Global | False[2] |
	+------------------+---------------------------+		+------------------+---------------------------+
	Table 22: IETF Protocol Assignments		Table 21: IETF Protocol Assignments
	[3] Unless allowed by a more specific allocation		[2] Unless allowed by a more specific allocation
	+------------------+----------------+		+------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+------------------+----------------+
	| Prefix | 2001:0000::/32 |		| Prefix | 2001:0000::/32 |
	| Name | TEREDO |		| Name | TEREDO |
	| RFC | [RFC4380] |		| RFC | [RFC4380] |
	| Allocation Date | January 2006 |		| Allocation Date | January 2006 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Routable | True |		| Routable | True |
	| Global | False |		| Global | False |
	+------------------+----------------+		+------------------+----------------+
	Table 23: TEREDO
			Table 22: TEREDO
	+------------------+----------------+		+------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+------------------+----------------+
	| Prefix | 2001:0002::/48 |		| Prefix | 2001:0002::/48 |
	| Name | Benchmarking |		| Name | Benchmarking |
	| RFC | [RFC5180] |		| RFC | [RFC5180] |
	| Allocation Date | April 2008 |		| Allocation Date | April 2008 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Routable | True |		| Routable | True |
	| Global | False |		| Global | False |
	+------------------+----------------+		+------------------+----------------+
	Table 24: Benchmarking		Table 23: Benchmarking
	+------------------+---------------+		+------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+------------------+---------------+
	| Prefix | 2001:db8::/32 |		| Prefix | 2001:db8::/32 |
	| Name | Documentation |		| Name | Documentation |
	| RFC | [RFC3849] |		| RFC | [RFC3849] |
	| Allocation Date | July 2004 |		| Allocation Date | July 2004 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+---------------+		+------------------+---------------+
	Table 25: Documentation		Table 24: Documentation
	+------------------+--------------+		+------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------+		+------------------+--------------+
	| Prefix | 2001:10::/28 |		| Prefix | 2001:10::/28 |
	| Name | ORCHID |		| Name | ORCHID |
	| RFC | [RFC4843] |		| RFC | [RFC4843] |
	| Allocation Date | March 2007 |		| Allocation Date | March 2007 |
	| Termination Date | March 2014 |		| Termination Date | March 2014 |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+--------------+		+------------------+--------------+
	Table 26: ORCHID		Table 25: ORCHID
	+------------------+---------------+		+------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+------------------+---------------+
	| Prefix | 2002::/16 [4] |		| Prefix | 2002::/16 [3] |
	| Name | 6to4 |		| Name | 6to4 |
	| RFC | [RFC3056] |		| RFC | [RFC3056] |
	| Allocation Date | February 2001 |		| Allocation Date | February 2001 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Routable | True |		| Routable | True |
	| Global | N/A[4] |		| Global | N/A[4] |
	+------------------+---------------+		+------------------+---------------+
	Table 27: 6to4		Table 26: 6to4
	[4] See [RFC3056] for details.		[3] See [RFC3056] for details.
	+------------------+--------------+		+------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------+		+------------------+--------------+
	| Prefix | FC00::/7 |		| Prefix | FC00::/7 |
	| Name | Unique-Local |		| Name | Unique-Local |
	| RFC | [RFC4193] |		| RFC | [RFC4193] |
	| Allocation Date | October 2005 |		| Allocation Date | October 2005 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Routable | True |		| Routable | True |
	| Global | False |		| Global | False |
	+------------------+--------------+		+------------------+--------------+
	Table 28: Unique-Local
			Table 27: Unique-Local
	+------------------+-----------------------+		+------------------+-----------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+-----------------------+		+------------------+-----------------------+
	| Prefix | FE80::/10 |		| Prefix | FE80::/10 |
	| Name | Linked-Scoped Unicast |		| Name | Linked-Scoped Unicast |
	| RFC | [RFC4291] |		| RFC | [RFC4291] |
	| Allocation Date | February 2006 |		| Allocation Date | February 2006 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Routable | False |		| Routable | False |
	| Global | False |		| Global | False |
	+------------------+-----------------------+		+------------------+-----------------------+
	Table 29: Linked-Scoped Unicast		Table 28: Linked-Scoped Unicast
	+------------------+---------------+
	| Attribute | Value |
	+------------------+---------------+
	| Prefix | FF00::/8 [5] |
	| Name | Multicast |
	| RFC | [RFC4291] |
	| Allocation Date | February 2006 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | True |
	| Routable | True |
	| Global | N/A |
	+------------------+---------------+
	Table 30: Multicast
	[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 18, line 44 ¶		skipping to change at page 18, line 25 ¶
	[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",		[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
	BCP 153, RFC 5735, January 2010.		BCP 153, RFC 5735, January 2010.
	[RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special		[RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special
	Purpose Address Registry", RFC 5736, January 2010.		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
	IPv4 Multicast Address Assignments", BCP 51, RFC 5771,
	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.
	[RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and		[RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and
	M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address		M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address
	Space", BCP 153, RFC 6598, April 2012.		Space", BCP 153, RFC 6598, April 2012.
	[RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6",		[RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6",
	RFC 6666, August 2012.		RFC 6666, August 2012.
End of changes. 27 change blocks.
	70 lines changed or deleted		32 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/