< draft-bonica-special-purpose-04.txt		draft-bonica-special-purpose-05.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: June 23, 2013 B. Haberman		Expires: July 7, 2013 B. Haberman
	Johns Hopkins University Applied		Johns Hopkins University Applied
	Physics Lab		Physics Lab
	December 20, 2012		January 03, 2013
	Special-Purpose Address Registries		Special-Purpose IP Address Registries
	draft-bonica-special-purpose-04		draft-bonica-special-purpose-05
	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 June 23, 2013.		This Internet-Draft will expire on July 7, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 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
	skipping to change at page 4, line 40 ¶		skipping to change at page 4, line 40 ¶
	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 an IETF reviewed document. The
	"IANA Considerations" section must include all of the information		"IANA Considerations" section must include all of the information
	specified in Section 2.1 of this document.		specified in Section 2.1 of this document.
	2.1. Information Requirements		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 Prefix - An IPv4 or IPv6 prefix that identifies the special-		o Address Block - A block of IPv4 or IPv6 addresses that has been
	purpose address block		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 though 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
	skipping to change at page 5, line 18 ¶		skipping to change at page 5, line 18 ¶
	o Source - A boolean value indicated whether an address from the		o Source - A boolean value indicated 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 indicated 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 Routable - A boolean value indicating whether a IP datagram whose		o Forwardable - A boolean value indicating whether a router may
	destination address is drawn from the allocated special-purpose		forward an IP datagram whose destination address is drawn from the
	address block is routable (i.e., may traverse more than a single		allocated special-purpose address block between external
	IP interface)		interfaces.
	o Global - A boolean value indicating whether a 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 routable beyond a specified administrative		address block is forwardable beyond a specified administrative
	domain.		domain.
	o Reserved - A boolean value indicatating whether the special-		o Reserved - A boolean value indicating whether the special-purpose
	purpose address block is reserved by IP, itself. This value is		address block is reserved by IP, itself. This value is "TRUE" if
	"TRUE" if the RFC that created the special-purpose address block		the RFC that created the special-purpose address block requires
	requires all compliant IP implementations to behave in a special		all compliant IP implementations to behave in a special way when
	way when forwarding packets either to or from addresses contained		forwarding packets either to or from addresses contained by the
	by the address block.		address block.
	If the value of "Destination" is FALSE, the values of "Routable" and		If the value of "Destination" is FALSE, the values of "Forwardable"
	"Global" must also be false.		and "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 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 |
	+------------------+---------------------------+		+------------------+---------------------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved | True |
	+------------------+---------------------------+		+------------------+---------------------------+
	Table 1: "This" Network		Table 1: "This" Network
	+------------------+---------------+		+------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+------------------+---------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+---------------+		+------------------+---------------+
	Table 2: Private-Use Networks		Table 2: Private-Use Networks
	+------------------+----------------------+		+------------------+----------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------+		+------------------+----------------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+----------------------+		+------------------+----------------------+
	Table 3: Shared Address Space		Table 3: Shared Address Space
	+------------------+---------------------------+		+------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------------+		+------------------+---------------------------+
	| Prefix | 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 |
	| Destination | False |		| Destination | False |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved | True |
	+------------------+---------------------------+		+------------------+---------------------------+
	Table 4: Loopback		Table 4: Loopback
	+------------------+----------------+		+------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+------------------+----------------+
	| Prefix | 169.254.0.0/16 |		| Address Block | 169.254.0.0/16 |
	| Name | Link Local |		| Name | Link Local |
	| RFC | [RFC3927] |		| RFC | [RFC3927] |
	| Allocation Date | May 2005 |		| Allocation Date | May 2005 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved | True |
	+------------------+----------------+		+------------------+----------------+
	Table 5: Link Local		Table 5: Link Local
	+------------------+---------------+		+------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+------------------+---------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+---------------+		+------------------+---------------+
	Table 6: Private-Use Networks		Table 6: Private-Use Networks
	+------------------+---------------------------+		+------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------------+		+------------------+---------------------------+
	| Prefix | 192.0.0.0/24 [1] |		| Address Block | 192.0.0.0/24 [1] |
	| 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+---------------------------+		+------------------+---------------------------+
	Table 7: IETF Protocol Assignments		Table 7: IETF Protocol Assignments
	[1] Not useable unless by virtue of a more specific reservation.		[1] Not useable unless by virtue of a more specific reservation.
	+------------------+--------------+		+------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------+		+------------------+--------------+
	| Prefix | 192.0.0.0/29 |		| Address Block | 192.0.0.0/29 |
	| Name | DS-Lite |		| Name | DS-Lite |
	| RFC | [RFC6333] |		| RFC | [RFC6333] |
	| Allocation Date | June 2011 |		| Allocation Date | June 2011 |
	| Termination Date | N/A |		| Termination Date | N/A |
	| Source | True |		| Source | True |
	| Destination | True |		| Destination | True |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+--------------+		+------------------+--------------+
	Table 8: DS-Lite		Table 8: DS-Lite
	+------------------+----------------------------+		+------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------------+		+------------------+----------------------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+----------------------------+		+------------------+----------------------------+
	Table 9: TEST-NET-1		Table 9: TEST-NET-1
	+------------------+--------------------+		+------------------+--------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------------+		+------------------+--------------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | True |		| Global | True |
	| Reserved | False |		| Reserved | False |
	+------------------+--------------------+		+------------------+--------------------+
	Table 10: 6to4 Relay Anycast		Table 10: 6to4 Relay Anycast
	+------------------+----------------+		+------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+------------------+----------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+----------------+		+------------------+----------------+
	Table 11: Private-Use Networks		Table 11: Private-Use Networks
	+------------------+---------------+		+------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+------------------+---------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+---------------+		+------------------+---------------+
	Table 12: Network Interconnect Device Benchmark Testing		Table 12: Network Interconnect Device Benchmark Testing
	+------------------+----------------------------+		+------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------------+		+------------------+----------------------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+----------------------------+		+------------------+----------------------------+
	Table 13: TEST-NET-2		Table 13: TEST-NET-2
	+------------------+----------------------------+		+------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------------------+		+------------------+----------------------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+----------------------------+		+------------------+----------------------------+
	Table 14: TEST-NET-3		Table 14: TEST-NET-3
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved | True |
	+------------------+---------------------+		+------------------+---------------------+
	Table 15: Reserved for Future Use		Table 15: Reserved for Future Use
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+---------------------+		+------------------+---------------------+
	Table 16: Limited Broadcast		Table 16: Limited Broadcast
	2.3. IPv6 Special-Purpose Address Registry Entries		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 |
	+------------------+------------------+		+------------------+------------------+
	| Prefix | ::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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved | True |
	+------------------+------------------+		+------------------+------------------+
	Table 17: Loopback Address		Table 17: Loopback Address
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | ::/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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved | True |
	+------------------+---------------------+		+------------------+---------------------+
	Table 18: Unspecified Address		Table 18: Unspecified Address
	+------------------+---------------------+		+------------------+---------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+---------------------+
	| Prefix | ::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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved | True |
	+------------------+---------------------+		+------------------+---------------------+
	Table 19: IPv4-mapped Address		Table 19: IPv4-mapped Address
	+------------------+---------------------+		+------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------+		+------------------+----------------------------+
	| Prefix | 0100::/64 |		| Address Block | 0100::/64 |
	| Name | Discard-Only Prefix |		| 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+---------------------+		+------------------+----------------------------+
	Table 20: Discard-Only Prefix		Table 20: Discard-Only Prefix
	+------------------+---------------------------+		+------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------------------+		+------------------+---------------------------+
	| Prefix | 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[2] |
	| Destination | False[2] |		| Destination | False[2] |
	| Routable | False[2] |		| Forwardable | False[2] |
	| Global | False[2] |		| Global | False[2] |
	| Reserved | False |		| Reserved | False |
	+------------------+---------------------------+		+------------------+---------------------------+
	Table 21: IETF Protocol Assignments		Table 21: IETF Protocol Assignments
	[2] Unless allowed by a more specific allocation		[2] Unless allowed by a more specific allocation
	+------------------+----------------+		+------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+------------------+----------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+----------------+		+------------------+----------------+
	Table 22: TEREDO		Table 22: TEREDO
	+------------------+----------------+		+------------------+----------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+----------------+		+------------------+----------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+----------------+		+------------------+----------------+
	Table 23: Benchmarking		Table 23: Benchmarking
	+------------------+---------------+		+------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+------------------+---------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+---------------+		+------------------+---------------+
	Table 24: Documentation		Table 24: Documentation
	+------------------+--------------+		+------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------+		+------------------+--------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+--------------+		+------------------+--------------+
	Table 25: ORCHID		Table 25: ORCHID
	+------------------+---------------+		+------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+---------------+		+------------------+---------------+
	| Prefix | 2002::/16 [3] |		| Address Block | 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 |		| Forwardable | True |
	| Global | N/A[4] |		| Global | N/A[4] |
	| Resereved | False |		| Reserved | False |
	+------------------+---------------+		+------------------+---------------+
	Table 26: 6to4		Table 26: 6to4
	[3] See [RFC3056] for details.		[3] See [RFC3056] for details.
	+------------------+--------------+		+------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+--------------+		+------------------+--------------+
	| Prefix | 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 |
	| Routable | True |		| Forwardable | True |
	| Global | False |		| Global | False |
	| Reserved | False |		| Reserved | False |
	+------------------+--------------+		+------------------+--------------+
	Table 27: Unique-Local		Table 27: Unique-Local
	+------------------+-----------------------+		+------------------+-----------------------+
	| Attribute | Value |		| Attribute | Value |
	+------------------+-----------------------+		+------------------+-----------------------+
	| Prefix | 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 |
	| Routable | False |		| Forwardable | False |
	| Global | False |		| Global | False |
	| Reserved | True |		| Reserved | 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.
	skipping to change at page 20, line 14 ¶		skipping to change at page 20, line 14 ¶
	of a comprehensive registry framework that can be used as a trust		of a comprehensive registry framework that can be used as a trust
	point for commencing a chain of address validation. Consideration		point for commencing a chain of address validation. Consideration
	should be given to IANA registry publication formats that are machine		should be given to IANA registry publication formats that are machine
	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 thank Geoff Huston and Randy Bush for their helpful
	whom this document would not have been written.		comments. The authors also express their gratitude to an anonymous
			donor, without whom this document would not have been written.
	5. Informative References		5. 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 -
	skipping to change at page 22, line 35 ¶		skipping to change at page 22, line 36 ¶
	Fax:		Fax:
	Email: leo.vegoda@icann.org		Email: leo.vegoda@icann.org
	URI: http://www.icann.org/		URI: http://www.icann.org/
	Ronald P Bonica (editor)		Ronald P Bonica (editor)
	Juniper Networks		Juniper Networks
	2251 Corporate Park Drive		2251 Corporate Park Drive
	Herndon, Virginia 20171		Herndon, Virginia 20171
	USA		USA
	Email: internet-drafts@bonica.org		Email: ron.bonica@verizon.net
	Brian Haberman		Brian Haberman
	Johns Hopkins University Applied Physics Lab		Johns Hopkins University Applied Physics Lab
	11100 Johns Hopkins Road		11100 Johns Hopkins Road
	Laurel, Maryland 20723-6099		Laurel, Maryland 20723-6099
	USA		USA
	Email: brian@innovationslab.net		Email: brian@innovationslab.net
End of changes. 69 change blocks.
	94 lines changed or deleted		95 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/