< draft-bonica-special-purpose-05.txt		draft-bonica-special-purpose-06.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: 4773, 5156, 5735, 5736 Internet Corporation for
	(if approved) Assigned Names and Numbers		(if approved) Assigned Names and Numbers
	Updates: 4773,5736 (if approved) R. Bonica, Ed.		Intended status: BCP R. Bonica, Ed.
	Intended status: BCP Juniper Networks		Expires: July 19, 2013 Juniper Networks
	Expires: July 7, 2013 B. Haberman		B. Haberman
	Johns Hopkins University Applied		Johns Hopkins University Applied
	Physics Lab		Physics Lab
	January 03, 2013		January 15, 2013
	Special-Purpose IP Address Registries		Special-Purpose IP Address Registries
	draft-bonica-special-purpose-05		draft-bonica-special-purpose-06
	Abstract		Abstract
	This memo instructs IANA to restructure its IPv4 and IPv6 Special-		This memo reiterates the assignment of an IPv4 address block
	Purpose Address Registries. Upon restructuring, the aforementioned		(192.0.0.0/24) to IANA. It also instructs IANA to restructure its
	registries will record all special-purpose address blocks,		IPv4 and IPv6 Special-Purpose Address Registries. Upon
	maintaining a common set of information regarding each address block.		restructuring, the aforementioned registries will record all special-
			purpose address blocks, maintaining a common set of information
			regarding each address block.
	This memo updates RFC 5736 and RFC 4773, which define the current		This memo obsoletes RFC 4773, RFC 5156, RFC 5735 and RFC 5736.
	structure of the IPv4 and IPv6 Special-Purpose Address Registries.
	It also obsoletes RFC 5735 and RFC 5156 which document special-
	purpose address blocks that are not currently, but will in the
	future, be recorded in the IPv4 and IPv6 Special-Purpose Address
	Registries.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 July 7, 2013.		This Internet-Draft will expire on July 19, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 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
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	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. Assignment of an IPv4 Address Block to IANA . . . . . . . 4
	2.2. IPv4 Special-Purpose Address Registry Entries . . . . . . 5		2.2. Restructuring of the IPv4 and IPv6 Special-Purpose
	2.3. IPv6 Special-Purpose Address Registry Entries . . . . . . 13		Address Registries . . . . . . . . . . . . . . . . . . . . 4
			2.2.1. Information Requirements . . . . . . . . . . . . . . . 5
			2.2.2. IPv4 Special-Purpose Address Registry Entries . . . . 6
			2.2.3. IPv6 Special-Purpose Address Registry Entries . . . . 13
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 19		3. Security Considerations . . . . . . . . . . . . . . . . . . . 19
	4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20		4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
	5. Informative References . . . . . . . . . . . . . . . . . . . . 20		5. Informative References . . . . . . . . . . . . . . . . . . . . 20
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
	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
	skipping to change at page 3, line 35 ¶		skipping to change at page 3, line 35 ¶
	space in the IPv4 Special-Purpose Address Registry.		space in the IPv4 Special-Purpose Address Registry.
	Likewise, [RFC2928] assigns an IPv6 address block (2001:0000::/23) to		Likewise, [RFC2928] assigns an IPv6 address block (2001:0000::/23) to
	IANA and instructs IANA to allocate special-purpose address blocks		IANA and instructs IANA to allocate special-purpose address blocks
	from this space. [RFC4773] instructs IANA to create an IPv6 Special-		from this space. [RFC4773] instructs IANA to create an IPv6 Special-
	Purpose Address Registry that records allocations from this address		Purpose Address Registry that records allocations from this address
	space. However, [RFC4773] does not instruct IANA to record special-		space. However, [RFC4773] does not instruct IANA to record special-
	purpose address block reservations from outside of the aforementioned		purpose address block reservations from outside of the aforementioned
	space in the IPv6 Special-Purpose Address Registry.		space in the IPv6 Special-Purpose Address Registry.
	This memo instructs IANA to restructure its IPv4 and IPv6 Special-		This memo reiterates the assignment of an IPv4 address block
	Purpose Address Registries. Therefore, this document updates		(192.0.0.0/24) to IANA. It also instructs IANA to restructure its
	[RFC5736] and [RFC4773] which define the current structure of the		IPv4 and IPv6 Special-Purpose Address Registries. Specifically, this
	aforementioned registries.		memo instructs IANA to record all special-purpose address blocks in
			the aforementioned registries. These include, but are not limited
	Specifically, this memo instructs IANA to record all special-purpose		to, IPv4 allocations from 192.0.0.0/24 and IPv6 allocations from
	address blocks in the aforementioned registries. These include, but		2001:0000::/23. Furthermore, this memo defines:
	are not limited to, IPv4 allocations from 192.0.0.0/24 and IPv6
	allocations from 2001:0000::/23. When the aforementioned registries
	include all special-purpose address blocks, [RFC5735] and [RFC5156]
	will become redundant with the registries. Therefore, this memo
	obsoletes [RFC5735] and [RFC5156].
	Furthermore, this memo defines:
	o a common set of information that the registries will maintain		o a common set of information that the registries will maintain
	regarding each special-purpose address block		regarding each special-purpose address block
	o a common set of requirements for future entries		o a common set of requirements for future entries
			When the aforementioned registries include all special-purpose
			address blocks, [RFC5735] and [RFC5156] will become redundant with
			the registries. Therefore, this memo obsoletes [RFC5735] and
			[RFC5156]. Because this memo reiterates the assignment of
			192.0.0.0/24 to IANA, and because it restructures the IPv4 Special-
			Purpose Address Registry, it obsoletes [RFC5736]. Finally, becaue
			this memo restructures the IPv6 Special-Purpose Address Registry, it
			obsoletes [RFC4773].
	2. IANA Considerations		2. IANA Considerations
			2.1. Assignment of an IPv4 Address Block to IANA
			Table 7 of this document records the assignment of an IPv4 address
			block (192.0.0.0/24) to IANA for IETF protocol assignments. This
			address allocation to IANA is intended to support IETF protocol
			assignments. A more general view of the roles of IANA with respect
			to address allocation functions is documented in Sections 4.1 and 4.3
			[RFC2860].
			This document directs IANA to designate special purpose address
			blocks in compliance with [RFC2860].
			2.2. Restructuring of the IPv4 and IPv6 Special-Purpose Address
			Registries
	IANA will restructure the following registries:		IANA will restructure the following registries:
	o IPv4 Special-Purpose Address Registry		o IPv4 Special-Purpose Address Registry
	o IPv6 Special-Purpose Address Registry		o IPv6 Special-Purpose Address Registry
	The IPv4 Special-Purpose Address Registry will record all IPv4		The IPv4 Special-Purpose Address Registry will record all IPv4
	special-purpose address blocks. These reservations will include, but		special-purpose address blocks. These reservations will include, but
	not be limited to, allocations from the 192.0.0.0/24 address block.		not be limited to, allocations from the 192.0.0.0/24 address block.
	Likewise, the IPv6 Special-Purpose Address Registry will record all		Likewise, the IPv6 Special-Purpose Address Registry will record all
	IPv6 special-purpose address blocks. These reservations will		IPv6 special-purpose address blocks. These reservations will
	include, but not be limited to, allocations from the 2001:0000::/23		include, but not be limited to, allocations from the 2001:0000::/23
	address block.		address block.
	Section 2.1 of this document describes information that both		Section 2.2.1 of this document describes information that both
	registries will maintain for each entry. Initially, IANA will		registries will maintain for each entry. Initially, IANA will
	populate the IPv4 Special-Purpose Address Registry with information		populate the IPv4 Special-Purpose Address Registry with information
	taken from Section 2.2 of this document. Likewise, IANA will		taken from Section 2.2.2 of this document. Likewise, IANA will
	populate the IPv6 Special-Purpose Address Registry with information		populate the IPv6 Special-Purpose Address Registry with information
	taken from Section 2.3 of this document.		taken from Section 2.2.3 of this document.
	IANA will update the aforementioned registries as requested in the		IANA will update the aforementioned registries as requested in the
	"IANA Considerations" section of an IETF reviewed document. The		"IANA Considerations" section of a document that has passed IETF
	"IANA Considerations" section must include all of the information		Review [RFC5226]. The "IANA Considerations" section must include all
	specified in Section 2.1 of this document.		of the information specified in Section 2.2.1 of this document.
	2.1. Information Requirements		2.2.1. Information Requirements
	The IPv4 and IPv6 Special-Purpose Address Registries will maintain		The IPv4 and IPv6 Special-Purpose Address Registries will maintain
	the following information regarding each entry:		the following information regarding each entry:
	o Address Block - A block of IPv4 or IPv6 addresses that has been		o Address Block - A block of IPv4 or IPv6 addresses that has been
	registered for a special-purpose		registered for a special-purpose
	o Name - A descriptive name for the special-purpose address block		o Name - A descriptive name for the special-purpose address block
	o RFC - The RFC though which the special-purpose address block was		o RFC - The RFC through which the special-purpose address block was
	requested		requested
	o Allocation Date - The date upon which the special purpose address		o Allocation Date - The date upon which the special purpose address
	block was allocated		block was allocated
	o Termination Date - The date upon which the allocation is to be		o Termination Date - The date upon which the allocation is to be
	terminated. This field is applicable for limited-use allocations		terminated. This field is applicable for limited-use allocations
	only.		only.
	o Source - A boolean value indicated whether an address from the		o Source - A boolean value indicating whether an address from the
	allocated special-purpose address block is valid when used as the		allocated special-purpose address block is valid when used as the
	source address of an IP datagram that transits two devices		source address of an IP datagram that transits two devices
	o Destination - A boolean value indicated whether an address from		o Destination - A boolean value indicating whether an address from
	the allocated special-purpose address block is valid when used as		the allocated special-purpose address block is valid when used as
	the destination address of an IP datagram that transits two		the destination address of an IP datagram that transits two
	devices		devices
	o Forwardable - A boolean value indicating whether a router may		o Forwardable - A boolean value indicating whether a router may
	forward an IP datagram whose destination address is drawn from the		forward an IP datagram whose destination address is drawn from the
	allocated special-purpose address block between external		allocated special-purpose address block between external
	interfaces.		interfaces.
	o Global - A boolean value indicating whether an IP datagram whose		o Global - A boolean value indicating whether an IP datagram whose
	destination address is drawn from the allocated special-purpose		destination address is drawn from the allocated special-purpose
	address block is forwardable beyond a specified administrative		address block is forwardable beyond a specified administrative
	domain.		domain.
	o Reserved - A boolean value indicating whether the special-purpose		o Reserved-by-protocol - A boolean value indicating whether the
	address block is reserved by IP, itself. This value is "TRUE" if		special-purpose address block is reserved by IP, itself. This
	the RFC that created the special-purpose address block requires		value is "TRUE" if the RFC that created the special-purpose
	all compliant IP implementations to behave in a special way when		address block requires all compliant IP implementations to behave
	forwarding packets either to or from addresses contained by the		in a special way when processing packets either to or from
	address block.		addresses contained by the address block.
	If the value of "Destination" is FALSE, the values of "Forwardable"		If the value of "Destination" is FALSE, the values of "Forwardable"
	and "Global" must also be false.		and "Global" must also be false.
	2.2. IPv4 Special-Purpose Address Registry Entries		2.2.2. IPv4 Special-Purpose Address Registry Entries
	Table 1 though Table 16, 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 |
	+------------------+---------------------------+		+----------------------+---------------------------+
	| Address Block | 0.0.0.0/8 |		| Address Block | 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 |
	| Source | True |		| Source | True |
	| Destination | False |		| Destination | False |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved-by-protocol | True |
	+------------------+---------------------------+		+----------------------+---------------------------+
	Table 1: "This" Network		Table 1: "This" Network
	+------------------+---------------+		+----------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+----------------------+---------------+
	| Address Block | 10.0.0.0/8 |		| Address Block | 10.0.0.0/8 |
	| Name | Private-Use |		| Name | Private-Use |
	| RFC | [RFC1918] |		| RFC | [RFC1918] |
	| Allocation Date | February 1996 |		| Allocation Date | February 1996 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+---------------+		+----------------------+---------------+
	Table 2: Private-Use Networks		Table 2: Private-Use Networks
	+------------------+----------------------+		+----------------------+----------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------+		+----------------------+----------------------+
	| Address Block | 100.64.0.0/10 |		| Address Block | 100.64.0.0/10 |
	| Name | Shared Address Space |		| Name | Shared Address Space |
	| RFC | [RFC6598] |		| RFC | [RFC6598] |
	| Allocation Date | April 2012 |		| Allocation Date | April 2012 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+----------------------+		+----------------------+----------------------+
	Table 3: Shared Address Space		Table 3: Shared Address Space
	+------------------+---------------------------+		+----------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------------+		+----------------------+---------------------------+
	| Address Block | 127.0.0.0/8 |		| Address Block | 127.0.0.0/8 |
	| Name | Loopback |		| Name | Loopback |
	| 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 |
	| Source | False |		| Source | False [1] |
	| Destination | False |		| Destination | False [1] |
	| Forwardable | False |		| Forwardable | False [1] |
	| Global | False |		| Global | False [1] |
	| Reserved | True |		| Reserved-by-protocol | True |
	+------------------+---------------------------+		+----------------------+---------------------------+
	Table 4: Loopback		Table 4: Loopback
	+------------------+----------------+		[1] Several protocols have been granted exceptions to this rule. For
	| Attribute | Value |		examples, see [RFC4379] and [RFC5884]
	+------------------+----------------+		+----------------------+----------------+
	| Address Block | 169.254.0.0/16 |		| Attribute | Value |
	| Name | Link Local |		+----------------------+----------------+
	| RFC | [RFC3927] |		| Address Block | 169.254.0.0/16 |
	| Allocation Date | May 2005 |		| Name | Link Local |
	| Termination Date | N/A |		| RFC | [RFC3927] |
	| Source | True |		| Allocation Date | May 2005 |
	| Destination | True |		| Termination Date | N/A |
	| Forwardable | False |		| Source | True |
	| Global | False |		| Destination | True |
	| Reserved | True |		| Forwardable | False |
	+------------------+----------------+		| Global | False |
			| Reserved-by-protocol | True |
			+----------------------+----------------+
	Table 5: Link Local		Table 5: Link Local
	+------------------+---------------+		+----------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+----------------------+---------------+
	| Address Block | 172.16.0.0/12 |		| Address Block | 172.16.0.0/12 |
	| Name | Private-Use |		| Name | Private-Use |
	| RFC | [RFC1122] |		| RFC | [RFC1122] |
	| Allocation Date | February 1996 |		| Allocation Date | February 1996 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+---------------+		+----------------------+---------------+
	Table 6: Private-Use Networks		Table 6: Private-Use Networks
	+------------------+---------------------------+		+----------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------------+		+----------------------+---------------------------+
	| Address Block | 192.0.0.0/24 [1] |		| Address Block | 192.0.0.0/24 [2] |
	| Name | IETF Protocol Assignments |		| Name | IETF Protocol Assignments |
	| RFC | [RFC5736] |		| RFC | [RFC5736] |
	| Allocation Date | January 2010 |		| Allocation Date | January 2010 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+---------------------------+		+----------------------+---------------------------+
	Table 7: IETF Protocol Assignments		Table 7: IETF Protocol Assignments
	[1] Not useable unless by virtue of a more specific reservation.		[2] Not useable unless by virtue of a more specific reservation.
	+------------------+--------------+		+----------------------+------------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------+		+----------------------+------------------------------+
	| Address Block | 192.0.0.0/29 |		| Address Block | 192.0.0.0/29 |
	| Name | DS-Lite |		| Name | DS-Lite |
	| RFC | [RFC6333] |		| RFC | Section 2.1 of this document |
	| Allocation Date | June 2011 |		| Allocation Date | June 2011 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+--------------+		+----------------------+------------------------------+
	Table 8: DS-Lite		Table 8: DS-Lite
	+------------------+----------------------------+		+----------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------------+		+----------------------+----------------------------+
	| Address Block | 192.0.2.0/24 |		| Address Block | 192.0.2.0/24 |
	| Name | Documentation (TEST-NET-1) |		| Name | Documentation (TEST-NET-1) |
	| RFC | [RFC5737] |		| RFC | [RFC5737] |
	| Allocation Date | January 2010 |		| Allocation Date | January 2010 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+----------------------------+		+----------------------+----------------------------+
	Table 9: TEST-NET-1		Table 9: TEST-NET-1
	+------------------+--------------------+		+----------------------+--------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------------+		+----------------------+--------------------+
	| Address Block | 192.88.99.0/24 |		| Address Block | 192.88.99.0/24 |
	| Name | 6to4 Relay Anycast |		| Name | 6to4 Relay Anycast |
	| RFC | [RFC3068] |		| RFC | [RFC3068] |
	| Allocation Date | June 2001 |		| Allocation Date | June 2001 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Forwardable | True |		| Forwardable | True |
	| Global | True |		| Global | True |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+--------------------+		+----------------------+--------------------+
	Table 10: 6to4 Relay Anycast		Table 10: 6to4 Relay Anycast
	+------------------+----------------+		+----------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+----------------------+----------------+
	| Address Block | 192.168.0.0/16 |		| Address Block | 192.168.0.0/16 |
	| Name | Private-Use |		| Name | Private-Use |
	| RFC | [RFC1918] |		| RFC | [RFC1918] |
	| Allocation Date | February 1996 |		| Allocation Date | February 1996 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+----------------+		+----------------------+----------------+
	Table 11: Private-Use Networks		Table 11: Private-Use Networks
	+------------------+---------------+		+----------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+----------------------+---------------+
	| Address Block | 198.18.0.0/15 |		| Address Block | 198.18.0.0/15 |
	| Name | Benchmarking |		| Name | Benchmarking |
	| RFC | [RFC2544] |		| RFC | [RFC2544] |
	| Allocation Date | March 1999 |		| Allocation Date | March 1999 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+---------------+		+----------------------+---------------+
	Table 12: Network Interconnect Device Benchmark Testing		Table 12: Network Interconnect Device Benchmark Testing
	+------------------+----------------------------+		+----------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------------+		+----------------------+----------------------------+
	| Address Block | 198.51.100.0/24 |		| Address Block | 198.51.100.0/24 |
	| Name | Documentation (TEST-NET-2) |		| Name | Documentation (TEST-NET-2) |
	| RFC | [RFC5737] |		| RFC | [RFC5737] |
	| Allocation Date | January 2010 |		| Allocation Date | January 2010 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+----------------------------+		+----------------------+----------------------------+
	Table 13: TEST-NET-2		Table 13: TEST-NET-2
	+------------------+----------------------------+		+----------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------------+		+----------------------+----------------------------+
	| Address Block | 203.0.113.0/24 |		| Address Block | 203.0.113.0/24 |
	| Name | Documentation (TEST-NET-3) |		| Name | Documentation (TEST-NET-3) |
	| RFC | [RFC5737] |		| RFC | [RFC5737] |
	| Allocation Date | January 2010 |		| Allocation Date | January 2010 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | False |		| Source | False |
	| Destination | False |		| Destination | False |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+----------------------------+		+----------------------+----------------------------+
	Table 14: TEST-NET-3		Table 14: TEST-NET-3
	+------------------+---------------------+		+----------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+----------------------+---------------------+
	| Address Block | 240.0.0.0/4 |		| Address Block | 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 |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved-by-protocol | True |
	+------------------+---------------------+		+----------------------+---------------------+
	Table 15: Reserved for Future Use		Table 15: Reserved for Future Use
	+------------------+---------------------+		+----------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+----------------------+---------------------+
	| Address Block | 255.255.255.255/32 |		| Address Block | 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 |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+---------------------+		+----------------------+---------------------+
	Table 16: Limited Broadcast		Table 16: Limited Broadcast
	2.3. IPv6 Special-Purpose Address Registry Entries		2.2.3. IPv6 Special-Purpose Address Registry Entries
	Table 17 through Table 28, 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 |
	+------------------+------------------+		+----------------------+------------------+
	| Address Block | ::1/128 |		| Address Block | ::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 |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved-by-protocol | True |
	+------------------+------------------+		+----------------------+------------------+
	Table 17: Loopback Address		Table 17: Loopback Address
	+------------------+---------------------+		+----------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+----------------------+---------------------+
	| Address Block | ::/128 |		| Address Block | ::/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 |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved-by-protocol | True |
	+------------------+---------------------+		+----------------------+---------------------+
	Table 18: Unspecified Address		Table 18: Unspecified Address
	+------------------+---------------------+		+----------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+----------------------+---------------------+
	| Address Block | ::FFFF:0:0/96 |		| Address Block | ::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 |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved-by-protocol | True |
	+------------------+---------------------+		+----------------------+---------------------+
	Table 19: IPv4-mapped Address		Table 19: IPv4-mapped Address
	+------------------+----------------------------+		+----------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------------+		+----------------------+----------------------------+
	| Address Block | 0100::/64 |		| Address Block | 0100::/64 |
	| Name | Discard-Only Address Block |		| Name | Discard-Only Address Block |
	| 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 |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+----------------------------+		+----------------------+----------------------------+
	Table 20: Discard-Only Prefix		Table 20: Discard-Only Prefix
	+------------------+---------------------------+		+----------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------------+		+----------------------+---------------------------+
	| Address Block | 2001:0000::/23 |		| Address Block | 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[2] |		| Source | False[3] |
	| Destination | False[2] |		| Destination | False[3] |
	| Forwardable | False[2] |		| Forwardable | False[3] |
	| Global | False[2] |		| Global | False[3] |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+---------------------------+		+----------------------+---------------------------+
	Table 21: IETF Protocol Assignments		Table 21: IETF Protocol Assignments
	[2] Unless allowed by a more specific allocation		[3] Unless allowed by a more specific allocation
	+------------------+----------------+		+----------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+----------------------+----------------+
	| Address Block | 2001:0000::/32 |		| Address Block | 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 |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+----------------+		+----------------------+----------------+
	Table 22: TEREDO		Table 22: TEREDO
	+------------------+----------------+		+----------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+----------------------+----------------+
	| Address Block | 2001:0002::/48 |		| Address Block | 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 |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+----------------+		+----------------------+----------------+
	Table 23: Benchmarking		Table 23: Benchmarking
	+------------------+---------------+		+----------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+----------------------+---------------+
	| Address Block | 2001:db8::/32 |		| Address Block | 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 |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+---------------+		+----------------------+---------------+
	Table 24: Documentation		Table 24: Documentation
	+------------------+--------------+		+----------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------+		+----------------------+--------------+
	| Address Block | 2001:10::/28 |		| Address Block | 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 |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+--------------+		+----------------------+--------------+
	Table 25: ORCHID		Table 25: ORCHID
	+------------------+---------------+		+----------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+----------------------+---------------+
	| Address Block | 2002::/16 [3] |		| Address Block | 2002::/16 [4] |
	| 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 |
	| Forwardable | True |		| Forwardable | True |
	| Global | N/A[4] |		| Global | N/A[4] |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+---------------+		+----------------------+---------------+
	Table 26: 6to4		Table 26: 6to4
	[3] See [RFC3056] for details.		[4] See [RFC3056] for details.
	+------------------+--------------+		+----------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------+		+----------------------+--------------+
	| Address Block | FC00::/7 |		| Address Block | 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 |
	| Forwardable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved-by-protocol | False |
	+------------------+--------------+		+----------------------+--------------+
	Table 27: Unique-Local		Table 27: Unique-Local
	+------------------+-----------------------+		+----------------------+-----------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+-----------------------+		+----------------------+-----------------------+
	| Address Block | FE80::/10 |		| Address Block | 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 |
	| Forwardable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved-by-protocol | True |
	+------------------+-----------------------+		+----------------------+-----------------------+
	Table 28: Linked-Scoped Unicast		Table 28: Linked-Scoped Unicast
	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
	skipping to change at page 20, line 36 ¶		skipping to change at page 20, line 36 ¶
	[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.
	[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and		[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
	E. Lear, "Address Allocation for Private Internets",		E. Lear, "Address Allocation for Private Internets",
	BCP 5, RFC 1918, February 1996.		BCP 5, RFC 1918, February 1996.
	[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for		[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for
	Network Interconnect Devices", RFC 2544, March 1999.		Network Interconnect Devices", RFC 2544, March 1999.
			[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
			Understanding Concerning the Technical Work of the
			Internet Assigned Numbers Authority", RFC 2860, June 2000.
	[RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial		[RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial
	IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000.		IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000.
	[RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains		[RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains
	via IPv4 Clouds", RFC 3056, February 2001.		via IPv4 Clouds", RFC 3056, February 2001.
	[RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",		[RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
	RFC 3068, June 2001.		RFC 3068, June 2001.
	[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix		[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
	skipping to change at page 21, line 16 ¶		skipping to change at page 21, line 20 ¶
	[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and		[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
	B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,		B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
	March 2005.		March 2005.
	[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.
			[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
			Label Switched (MPLS) Data Plane Failures", RFC 4379,
			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		[RFC4773] Huston, G., "Administration of the IANA Special Purpose
	IPv6 Address Block", RFC 4773, December 2006.		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,		[RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156,
	April 2008.		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.
			[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
			IANA Considerations Section in RFCs", BCP 26, RFC 5226,
			May 2008.
	[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.
			[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
			"Bidirectional Forwarding Detection (BFD) for MPLS Label
			Switched Paths (LSPs)", RFC 5884, June 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. 58 change blocks.
	447 lines changed or deleted		483 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/