< draft-bchv-rfc6890bis-02.txt		draft-bchv-rfc6890bis-03.txt >
	Network Working Group R. Bonica		Network Working Group R. Bonica
	Internet-Draft Juniper Networks		Internet-Draft Juniper Networks
	Obsoletes: RFC 6890 (if approved) M. Cotton		Obsoletes: 6890 (if approved) M. Cotton
	Intended status: Best Current Practice ICANN		Intended status: Best Current Practice ICANN
	Expires: February 27, 2017 B. Haberman		Expires: August 10, 2017 B. Haberman
	Johns Hopkins University		Johns Hopkins University
	L. Vegoda		L. Vegoda
	ICANN		ICANN
	August 26, 2016		February 6, 2017
	Special-Purpose IP Address Registries		Special-Purpose IP Address Registries
	draft-bchv-rfc6890bis-02		draft-bchv-rfc6890bis-03
	Abstract		Abstract
	This memo updates the IANA IPv6 Special-Purpose Address Registries to		This memo updates the IANA IPv6 Special-Purpose Address Registries to
	address issues raised by the definition of a global prefix. For		address issues raised by the definition of a global prefix. For
	completeness, this memo contains all the assignments made by RFC 6890		completeness, this memo contains all the assignments made by RFC 6890
	to the IANA Special-Purpose Address Registries.		to the IANA Special-Purpose Address Registries.
	This memo obsoletes RFC 6890.		This memo obsoletes RFC 6890.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 February 27, 2017.		This Internet-Draft will expire on August 10, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3		2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
	2.1. Assignment of an IPv4 Address Block to IANA . . . . . . . 3		3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
	2.2. Restructuring of the IPv4 and IPv6 Special-Purpose		3.1. Assignment of an IPv4 Address Block to IANA . . . . . . . 3
			3.2. Restructuring of the IPv4 and IPv6 Special-Purpose
	Address Registries . . . . . . . . . . . . . . . . . . . 3		Address Registries . . . . . . . . . . . . . . . . . . . 3
	2.2.1. Information Requirements . . . . . . . . . . . . . . 4		3.2.1. Information Requirements . . . . . . . . . . . . . . 4
	2.2.2. IPv4 Special-Purpose Address Registry Entries . . . . 5		3.2.2. IPv4 Special-Purpose Address Registry Entries . . . . 5
	2.2.3. IPv6 Special-Purpose Address Registry Entries . . . . 12		3.2.3. IPv6 Special-Purpose Address Registry Entries . . . . 15
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 19		4. Security Considerations . . . . . . . . . . . . . . . . . . . 25
	4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
	5. Informative References . . . . . . . . . . . . . . . . . . . 19		6. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22		6.1. Normative References . . . . . . . . . . . . . . . . . . 26
			6.2. Informative References . . . . . . . . . . . . . . . . . 26
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
	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 for a special purpose. For		occasionally reserves an address block for a 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.
	The current list of all special-purpose address blocks are described		Several issues have been raised with the documentation of some of the
	in [RFC6890]. However, several issues have been raised with how		special-purpose address blocks in [RFC6890]. Specifically, the
	"global" is defined in that document. Specifically, the definition		definition of global provided in [RFC6890] was misleading as it
	of global provided in [RFC6890] focuses on the prefix's ability to be		slightly differed from the generally accepted definition of "global
	routed globally within the Internet and does not indicate if the		scope" (i.e., the ability to forward beyond the boundaries of an
	prefix is globally scoped (i.e., may be routed beyond the local link;		administrative domain, described as "global unicast" in the IPv6
	described as "global unicast" in the IPv6 addressing architecture		addressing architecture [RFC4291]).
	[RFC4291]).
	This memo reiterates the assignments made to the IPv4 and IPv6		This memo reiterates the assignments made to the IPv4 and IPv6
	Special-Purpose Address Registries and augments the fields contained		Special-Purpose Address Registries and augments the fields contained
	within the registires in order to address the confusion raised by the		within the registries in order to address the confusion raised by the
	definition of "global". Furthermore, this memo defines:		definition of "global".
	o a common set of information that the registries will maintain		This memo obsoletes [RFC6890].
	regarding each special-purpose address block
	o a common set of requirements for future entries		2. Requirements Language
	This memo obsoletes [RFC6890].		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
			"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
			document are to be interpreted as described in [RFC2119].
	2. IANA Considerations		3. IANA Considerations
	2.1. Assignment of an IPv4 Address Block to IANA		3.1. Assignment of an IPv4 Address Block to IANA
	Table 7 of this document records the assignment of an IPv4 address		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		block (192.0.0.0/24) to IANA for IETF protocol assignments. This
	address allocation to IANA is intended to support IETF protocol		address allocation to IANA is intended to support IETF protocol
	assignments. A more general view of the roles of IANA with respect		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		to address allocation functions is documented in Sections 4.1 and 4.3
	[RFC2860].		[RFC2860].
	IANA has designated special-purpose address blocks in compliance with		IANA has designated special-purpose address blocks in compliance with
	[RFC2860].		[RFC2860].
	2.2. Restructuring of the IPv4 and IPv6 Special-Purpose Address		3.2. Restructuring of the IPv4 and IPv6 Special-Purpose Address
	Registries		Registries
	IANA has restructured the following registries:		IANA has restructured the following registries:
	IPv4 Special-Purpose Address Registry		IPv4 Special-Purpose Address Registry
	IPv6 Special-Purpose Address Registry		IPv6 Special-Purpose Address Registry
	The IPv4 Special-Purpose Address Registry records all IPv4 special-		The IPv4 Special-Purpose Address Registry records all IPv4 special-
	purpose address blocks. These reservations include, but are not		purpose address blocks. These reservations include, but are not
	limited to, allocations from the 192.0.0.0/24 address block.		limited to, allocations from the 192.0.0.0/24 address block.
	Likewise, the IPv6 Special-Purpose Address Registry records all IPv6		Likewise, the IPv6 Special-Purpose Address Registry records all IPv6
	special-purpose address blocks. These reservations include, but are		special-purpose address blocks. These reservations include, but are
	not limited to, allocations from the 2001:0000::/23 address block,		not limited to, allocations from the 2001:0000::/23 address block,
	which is a globally scoped address block.		which is a globally scoped address block.
	Section 2.2.1 of this document describes information that both		Section 3.2.1 of this document describes information that both
	registries will maintain for each entry. IANA has populated the IPv4		registries will maintain for each entry. IANA has populated the IPv4
	Special-Purpose Address Registry with information taken from		Special-Purpose Address Registry with information taken from
	Section 2.2.2 of this document. Likewise, IANA has populated the		Section 3.2.2 of this document. Likewise, IANA has populated the
	IPv6 Special-Purpose Address Registry with information taken from		IPv6 Special-Purpose Address Registry with information taken from
	Section 2.2.3 of this document.		Section 3.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 a document that has passed IETF		"IANA Considerations" section of a document that has passed IETF
	Review [RFC5226]. The "IANA Considerations" section MUST include all		Review [RFC5226]. The "IANA Considerations" section MUST include all
	of the information specified in Section 2.2.1 of this document.		of the information specified in Section 3.2.1 of this document.
	2.2.1. Information Requirements		3.2.1. Information Requirements
	The IPv4 and IPv6 Special-Purpose Address Registries maintain the		The IPv4 and IPv6 Special-Purpose Address Registries maintain the
	following information regarding each entry:		following information regarding each entry:
	Address Block - A block of IPv4 or IPv6 addresses that has been		Address Block - A block of IPv4 or IPv6 addresses that has been
	registered for a special purpose.		registered for a special purpose.
	Name - A descriptive name for the special-purpose address block.		Name - A descriptive name for the special-purpose address block.
	RFC - The RFC through which the special-purpose address block was		RFC - The RFC through which the special-purpose address block was
	skipping to change at page 4, line 37 ¶		skipping to change at page 4, line 37 ¶
	source address of an IP datagram that transits two devices.		source address of an IP datagram that transits two devices.
	Destination - A boolean value indicating whether an address from		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.
	Forwardable - A boolean value indicating whether a router may		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 (i.e., different administrative domains).
	Globally Reachable - A boolean value indicating whether an IP		Globally Reachable - A boolean value indicating whether an IP
	datagram whose destination address is drawn from the allocated		datagram whose destination address is drawn from the allocated
	special-purpose address block is forwardable beyond a specified		special-purpose address block is forwardable beyond a specified
	administrative domain.		administrative domain.
	Reserved-by-Protocol - A boolean value indicating whether the		Reserved-by-Protocol - A boolean value indicating whether the
	special-purpose address block is reserved by IP, itself. This		special-purpose address block is reserved by IP, itself. This
	value is "TRUE" if the RFC that created the special-purpose		value is "TRUE" if the RFC that created the special-purpose
	address block requires all compliant IP implementations to behave		address block requires all compliant IP implementations to behave
	in a special way when processing packets either to or from		in a special way when processing packets either to or from
	addresses contained by the 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 "Globally Reachable" must also be false.		and "Globally Reachable" must also be FALSE.
	2.2.2. IPv4 Special-Purpose Address Registry Entries		3.2.2. IPv4 Special-Purpose Address Registry Entries
	Table 1 though Table 16, below, represent entries with which IANA has		Table 1 through Table 22, below, represent entries with which IANA
	initially populated the IPv4 Special-Purpose Address Registry.		has initially populated 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 host on this network" |		| Name | "This host on 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 |
	skipping to change at page 8, line 24 ¶		skipping to change at page 8, line 24 ¶
	| Destination | False |		| Destination | False |
	| Forwardable | False |		| Forwardable | False |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+------------------------------+		+----------------------+------------------------------+
	Table 7: IETF Protocol Assignments		Table 7: IETF Protocol Assignments
	[2] Not usable unless by virtue of a more specific reservation.		[2] Not usable 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 | IPv4 Service Continuity Prefix |
	| RFC | [RFC6333] |		| RFC | [RFC7335] |
	| 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+--------------+		+----------------------+--------------------------------+
	Table 8: DS-Lite		Table 8: IPv4 Service Continuity
			+----------------------+--------------------+
			| Attribute | Value |
			+----------------------+--------------------+
			| Address Block | 192.0.0.8/32 |
			| Name | IPv4 dummy address |
			| RFC | [RFC7600] |
			| Allocation Date | March 2015 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | False |
			| Forwardable | False |
			| Globally Reachable | False |
			| Reserved-by-Protocol | False |
			+----------------------+--------------------+
			Table 9: IPv4 Dummy Address
			+----------------------+-------------------------------+
			| Attribute | Value |
			+----------------------+-------------------------------+
			| Address Block | 192.0.0.9/32 |
			| Name | Port Control Protocol Anycast |
			| RFC | [RFC7723] |
			| Allocation Date | October 2015 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+-------------------------------+
			Table 10: PCP Anycast
			+----------------------+--------------------------------+
			| Attribute | Value |
			+----------------------+--------------------------------+
			| Address Block | 192.0.0.170/32, 192.0.0.171/32 |
			| Name | NAT64/DNS64 Discovery |
			| RFC | [RFC7050] |
			| Allocation Date | February 2013 |
			| Termination Date | N/A |
			| Source | False |
			| Destination | False |
			| Forwardable | False |
			| Globally Reachable | False |
			| Reserved-by-Protocol | True |
			+----------------------+--------------------------------+
			Table 11: NAT64/DNS64 Discovery
	+----------------------+----------------------------+		+----------------------+----------------------------+
	| 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+----------------------------+		+----------------------+----------------------------+
	Table 9: TEST-NET-1		Table 12: TEST-NET-1
			+----------------------+-----------------+
			| Attribute | Value |
			+----------------------+-----------------+
			| Address Block | 192.31.196.0/24 |
			| Name | AS112-v4 |
			| RFC | [RFC7535] |
			| Allocation Date | December 2014 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+-----------------+
			Table 13: AS112 - IPv4
			+----------------------+-----------------+
			| Attribute | Value |
			+----------------------+-----------------+
			| Address Block | 192.52.193.0/24 |
			| Name | AMT |
			| RFC | [RFC7450] |
			| Allocation Date | December 2014 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+-----------------+
			Table 14: Automatic Multicast Tunneling
	+----------------------+-------------------------------+		+----------------------+-------------------------------+
	| Attribute | Value |		| Attribute | Value |
	+----------------------+-------------------------------+		+----------------------+-------------------------------+
	| Address Block | 192.88.99.0/24 |		| Address Block | 192.88.99.0/24 |
	| Name | Deprecated 6to4 Relay Anycast |		| Name | Deprecated 6to4 Relay Anycast |
	| RFC | [RFC7526] |		| RFC | [RFC7526] |
	| Allocation Date | June 2001 |		| Allocation Date | June 2001 |
	| Termination Date | March 2015 |		| Termination Date | March 2015 |
	| Source | N/A |		| Source | N/A |
	| Destination | N/A |		| Destination | N/A |
	| Forwardable | N/A |		| Forwardable | N/A |
	| Globally Reachable | N/A |		| Globally Reachable | N/A |
	| Reserved-by-Protocol | N/A |		| Reserved-by-Protocol | N/A |
	+----------------------+-------------------------------+		+----------------------+-------------------------------+
	Table 10: 6to4 Relay Anycast		Table 15: 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+----------------+		+----------------------+----------------+
	Table 11: Private-Use Networks		Table 16: Private-Use Networks
			+----------------------+-----------------+
			| Attribute | Value |
			+----------------------+-----------------+
			| Address Block | 192.175.48.0/24 |
			| Name | Private-Use |
			| RFC | [RFC7534] |
			| Allocation Date | January 1996 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+-----------------+
			Table 17: Direct Delegation AS112 Service
	+----------------------+---------------+		+----------------------+---------------+
	| 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+---------------+		+----------------------+---------------+
	Table 12: Network Interconnect Device Benchmark Testing		Table 18: 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+----------------------------+		+----------------------+----------------------------+
	Table 13: TEST-NET-2		Table 19: 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+----------------------------+		+----------------------+----------------------------+
	Table 14: TEST-NET-3		Table 20: 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | True |		| Reserved-by-Protocol | True |
	+----------------------+----------------------+		+----------------------+----------------------+
	Table 15: Reserved for Future Use		Table 21: 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | True |		| Reserved-by-Protocol | True |
	+----------------------+----------------------+		+----------------------+----------------------+
	Table 16: Limited Broadcast		Table 22: Limited Broadcast
	2.2.3. IPv6 Special-Purpose Address Registry Entries		3.2.3. IPv6 Special-Purpose Address Registry Entries
	Table 17 through Table 29, below, represent entries with which the		Table 23 through Table 41, below, represent entries with which the
	IANA has initially populated the IPv6 Special-Purpose Address		IANA has initially populated 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | True |		| Reserved-by-Protocol | True |
	+----------------------+------------------+		+----------------------+------------------+
	Table 17: Loopback Address		Table 23: 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | True |		| Reserved-by-Protocol | True |
	+----------------------+---------------------+		+----------------------+---------------------+
	Table 18: Unspecified Address		Table 24: Unspecified Address
	+----------------------+---------------------+
	| Attribute | Value |
	+----------------------+---------------------+
	| Address Block | 64:ff9b::/96 |
	| Name | IPv4-IPv6 Translat. |
	| RFC | [RFC6052] |
	| Allocation Date | October 2010 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | True |
	| Reserved-by-Protocol | False |
	+----------------------+---------------------+
	Table 19: IPv4-IPv6 Translation 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | True |		| Reserved-by-Protocol | True |
	+----------------------+---------------------+		+----------------------+---------------------+
	Table 20: IPv4-Mapped Address		Table 25: IPv4-Mapped Address
			+----------------------+---------------------+
			| Attribute | Value |
			+----------------------+---------------------+
			| Address Block | 64:ff9b::/96 |
			| Name | IPv4-IPv6 Translat. |
			| RFC | [RFC6052] |
			| Allocation Date | October 2010 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+---------------------+
			Table 26: IPv4-IPv6 Translation Address
	+----------------------+----------------------------+		+----------------------+----------------------------+
	| Attribute | Value |		| Attribute | Value |
	+----------------------+----------------------------+		+----------------------+----------------------------+
	| Address Block | 100::/64 |		| Address Block | 100::/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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+----------------------------+		+----------------------+----------------------------+
	Table 21: Discard-Only Prefix		Table 27: Discard-Only Prefix
	+----------------------+---------------------------+		+----------------------+---------------------------+
	| Attribute | Value |		| Attribute | Value |
	+----------------------+---------------------------+		+----------------------+---------------------------+
	| Address Block | 2001::/23 |		| Address Block | 2001::/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[1] |		| Source | False[1] |
	| Destination | False[1] |		| Destination | False[1] |
	| Forwardable | False[1] |		| Forwardable | False[1] |
	| Globally Reachable | False[1] |		| Globally Reachable | False[1] |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+---------------------------+		+----------------------+---------------------------+
	Table 22: IETF Protocol Assignments		Table 28: IETF Protocol Assignments
	[1] Unless allowed by a more specific allocation.		[1] Unless allowed by a more specific allocation.
	+----------------------+--------------+		+----------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+----------------------+--------------+		+----------------------+--------------+
	| Address Block | 2001::/32 |		| Address Block | 2001::/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 |
	| Globally Reachable | N/A [2] |		| Globally Reachable | N/A [2] |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+--------------+		+----------------------+--------------+
	Table 23: TEREDO		Table 29: TEREDO
	[2] See [RFC4380] for details.		[2] See [RFC4380] for details.
			+----------------------+-------------------------------+
			| Attribute | Value |
			+----------------------+-------------------------------+
			| Address Block | 2001:1::1/128 |
			| Name | Port Control Protocol Anycast |
			| RFC | [RFC7723] |
			| Allocation Date | November 2015 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+-------------------------------+
			Table 30: Port Control Protocol Anycast
	+----------------------+--------------+		+----------------------+--------------+
	| Attribute | Value |		| Attribute | Value |
	+----------------------+--------------+		+----------------------+--------------+
	| Address Block | 2001:2::/48 |		| Address Block | 2001:2::/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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+--------------+		+----------------------+--------------+
	Table 24: Benchmarking		Table 31: Benchmarking
			+----------------------+---------------+
			| Attribute | Value |
			+----------------------+---------------+
			| Address Block | 2001:3::/32 |
			| Name | AMT |
			| RFC | [RFC7450] |
			| Allocation Date | December 2014 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+---------------+
			Table 32: Automatic Multicast Tunneling
			+----------------------+-----------------+
			| Attribute | Value |
			+----------------------+-----------------+
			| Address Block | 2001:4:112::/48 |
			| Name | AS112-v6 |
			| RFC | [RFC7535] |
			| Allocation Date | December 2014 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+-----------------+
			Table 33: AS112 - IPv6
			+----------------------+------------------------------------------+
			| Attribute | Value |
			+----------------------+------------------------------------------+
			| Address Block | 2001:5::/32 |
			| Name | EID Space for LISP (Managed by RIPE NCC) |
			| RFC | [RFC7954] |
			| Allocation Date | September 2016 |
			| Termination Date | September 2019[3] |
			| Source | True[4] |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | True[5] |
			+----------------------+------------------------------------------+
			Table 34: EID Space - LISP
			[3] According to the 3+3 Plan outlined in [RFC7954], the termination
			date can be postponed to September 2022.
			[4] Can be used as a multicast source as well.
			[5] To be used as EID space by routers enabled by LISP [RFC6830].
			+----------------------+--------------------------------+
			| Attribute | Value |
			+----------------------+--------------------------------+
			| Address Block | 2001:10::/28 |
			| Name | Deprecated (previously ORCHID) |
			| RFC | [RFC4843] |
			| Allocation Date | March 2007 |
			| Termination Date | March 2014 |
			| Source | |
			| Destination | |
			| Forwardable | |
			| Globally Reachable | |
			| Reserved-by-Protocol | |
			+----------------------+--------------------------------+
			Table 35: ORCHIDv1 - Deprecated
			+----------------------+--------------+
			| Attribute | Value |
			+----------------------+--------------+
			| Address Block | 2001:20::/28 |
			| Name | ORCHIDv2 |
			| RFC | [RFC7343] |
			| Allocation Date | July 2014 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+--------------+
			Table 36: ORCHIDv2
	+----------------------+---------------+		+----------------------+---------------+
	| 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+---------------+		+----------------------+---------------+
	Table 25: Documentation		Table 37: Documentation
	+----------------------+--------------+
	| Attribute | Value |
	+----------------------+--------------+
	| Address Block | 2001:10::/28 |
	| Name | ORCHID |
	| RFC | [RFC4843] |
	| Allocation Date | March 2007 |
	| Termination Date | March 2014 |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+--------------+
	Table 26: ORCHID
	+----------------------+---------------+		+----------------------+---------------+
	| Attribute | Value |		| Attribute | Value |
	+----------------------+---------------+		+----------------------+---------------+
	| Address Block | 2002::/16 [2] |		| Address Block | 2002::/16 [2] |
	| 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 |
	| Globally Reachable | N/A [3] |		| Globally Reachable | N/A [6] |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+---------------+		+----------------------+---------------+
	Table 27: 6to4		Table 38: 6to4
	[3] See [RFC3056] for details.		[6] See [RFC3056] for details.
			+----------------------+---------------------------------+
			| Attribute | Value |
			+----------------------+---------------------------------+
			| Address Block | 2620:4f:8000::/48 |
			| Name | Direct Delegation AS112 Service |
			| RFC | [RFC7534] |
			| Allocation Date | May 2011 |
			| Termination Date | N/A |
			| Source | True |
			| Destination | True |
			| Forwardable | True |
			| Globally Reachable | True |
			| Reserved-by-Protocol | False |
			+----------------------+---------------------------------+
			Table 39: Direct Delegation AS112 Service
	+----------------------+--------------+		+----------------------+--------------+
	| 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 |
	| Globally Reachable | False [4] |		| Globally Reachable | False [7] |
	| Reserved-by-Protocol | False |		| Reserved-by-Protocol | False |
	+----------------------+--------------+		+----------------------+--------------+
	Table 28: Unique-Local (Private)		Table 40: Unique-Local (Private)
	[4] See [RFC4193] for more details on the routability of Unique-Local		[7] See [RFC4193] for more details on the routability of Unique-Local
	addresses. The Unique-Local prefix is drawn from the IPv6 Global		addresses. The Unique-Local prefix is drawn from the IPv6 Global
	Unicast Address range, but is specified as not globally routed.		Unicast Address range, but is specified as not globally routed.
	+----------------------+-----------------------+		+----------------------+-----------------------+
	| 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 |
	| Globally Reachable | False |		| Globally Reachable | False |
	| Reserved-by-Protocol | True |		| Reserved-by-Protocol | True |
	+----------------------+-----------------------+		+----------------------+-----------------------+
	Table 29: Link-Scoped Unicast		Table 41: Link-Scoped Unicast
	3. Security Considerations		4. 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.
	The proposed registry is intended to provide an authoritative source		The proposed registry is intended to provide an authoritative source
	of information regarding the currency and intended purpose of special		of information regarding the currency and intended purpose of special
	purpose address blocks that are designated from the IANA-administered		purpose address blocks that are designated from the IANA-administered
	Special-Purpose registry. This is a small step towards the creation		Special-Purpose registry. This is a small step towards the creation
	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
	parsable. Additionally, consideration should be given to the use of		parsable. Additionally, consideration should be given to the use of
	file signatures and associated certificate mechanisms to allow		file signatures and associated certificate mechanisms to allow
	applications to confirm that the registry contents are current and		applications to confirm that the registry contents are current and
	that they have been published by the IANA.		that they have been published by the IANA.
	4. Acknowledgements		5. Acknowledgements
	Brian Carpenter and C.M. Heard provided useful comments on initial		Brian Carpenter and C.M. Heard provided useful comments on initial
	versions of this document.		versions of this document. Daniel Migualt provided an in-depth
			review that helped strengthen the text within the document.
	5. Informative References		6. References
			6.1. Normative References
			[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
			Requirement Levels", BCP 14, RFC 2119,
			DOI 10.17487/RFC2119, March 1997,
			<http://www.rfc-editor.org/info/rfc2119>.
			6.2. Informative References
	[RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5,		[RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5,
	RFC 919, DOI 10.17487/RFC0919, October 1984,		RFC 919, DOI 10.17487/RFC0919, October 1984,
	<http://www.rfc-editor.org/info/rfc919>.		<http://www.rfc-editor.org/info/rfc919>.
	[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,		[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
	RFC 1112, DOI 10.17487/RFC1112, August 1989,		RFC 1112, DOI 10.17487/RFC1112, August 1989,
	<http://www.rfc-editor.org/info/rfc1112>.		<http://www.rfc-editor.org/info/rfc1112>.
	[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -		[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
	skipping to change at page 21, line 49 ¶		skipping to change at page 28, line 15 ¶
	[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,		[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
	"Bidirectional Forwarding Detection (BFD) for MPLS Label		"Bidirectional Forwarding Detection (BFD) for MPLS Label
	Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884,		Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884,
	June 2010, <http://www.rfc-editor.org/info/rfc5884>.		June 2010, <http://www.rfc-editor.org/info/rfc5884>.
	[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.		[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.
	Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,		Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,
	DOI 10.17487/RFC6052, October 2010,		DOI 10.17487/RFC6052, October 2010,
	<http://www.rfc-editor.org/info/rfc6052>.		<http://www.rfc-editor.org/info/rfc6052>.
	[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
	Stack Lite Broadband Deployments Following IPv4
	Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011,
	<http://www.rfc-editor.org/info/rfc6333>.
	[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, DOI 10.17487/RFC6598, April		Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April
	2012, <http://www.rfc-editor.org/info/rfc6598>.		2012, <http://www.rfc-editor.org/info/rfc6598>.
	[RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6",		[RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6",
	RFC 6666, DOI 10.17487/RFC6666, August 2012,		RFC 6666, DOI 10.17487/RFC6666, August 2012,
	<http://www.rfc-editor.org/info/rfc6666>.		<http://www.rfc-editor.org/info/rfc6666>.
			[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
			Locator/ID Separation Protocol (LISP)", RFC 6830,
			DOI 10.17487/RFC6830, January 2013,
			<http://www.rfc-editor.org/info/rfc6830>.
	[RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,		[RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,
	"Special-Purpose IP Address Registries", BCP 153,		"Special-Purpose IP Address Registries", BCP 153,
	RFC 6890, DOI 10.17487/RFC6890, April 2013,		RFC 6890, DOI 10.17487/RFC6890, April 2013,
	<http://www.rfc-editor.org/info/rfc6890>.		<http://www.rfc-editor.org/info/rfc6890>.
			[RFC7050] Savolainen, T., Korhonen, J., and D. Wing, "Discovery of
			the IPv6 Prefix Used for IPv6 Address Synthesis",
			RFC 7050, DOI 10.17487/RFC7050, November 2013,
			<http://www.rfc-editor.org/info/rfc7050>.
			[RFC7335] Byrne, C., "IPv4 Service Continuity Prefix", RFC 7335,
			DOI 10.17487/RFC7335, August 2014,
			<http://www.rfc-editor.org/info/rfc7335>.
			[RFC7343] Laganier, J. and F. Dupont, "An IPv6 Prefix for Overlay
			Routable Cryptographic Hash Identifiers Version 2
			(ORCHIDv2)", RFC 7343, DOI 10.17487/RFC7343, September
			2014, <http://www.rfc-editor.org/info/rfc7343>.
			[RFC7450] Bumgardner, G., "Automatic Multicast Tunneling", RFC 7450,
			DOI 10.17487/RFC7450, February 2015,
			<http://www.rfc-editor.org/info/rfc7450>.
	[RFC7526] Troan, O. and B. Carpenter, Ed., "Deprecating the Anycast		[RFC7526] Troan, O. and B. Carpenter, Ed., "Deprecating the Anycast
	Prefix for 6to4 Relay Routers", BCP 196, RFC 7526,		Prefix for 6to4 Relay Routers", BCP 196, RFC 7526,
	DOI 10.17487/RFC7526, May 2015,		DOI 10.17487/RFC7526, May 2015,
	<http://www.rfc-editor.org/info/rfc7526>.		<http://www.rfc-editor.org/info/rfc7526>.
			[RFC7534] Abley, J. and W. Sotomayor, "AS112 Nameserver Operations",
			RFC 7534, DOI 10.17487/RFC7534, May 2015,
			<http://www.rfc-editor.org/info/rfc7534>.
			[RFC7535] Abley, J., Dickson, B., Kumari, W., and G. Michaelson,
			"AS112 Redirection Using DNAME", RFC 7535,
			DOI 10.17487/RFC7535, May 2015,
			<http://www.rfc-editor.org/info/rfc7535>.
			[RFC7600] Despres, R., Jiang, S., Ed., Penno, R., Lee, Y., Chen, G.,
			and M. Chen, "IPv4 Residual Deployment via IPv6 - A
			Stateless Solution (4rd)", RFC 7600, DOI 10.17487/RFC7600,
			July 2015, <http://www.rfc-editor.org/info/rfc7600>.
			[RFC7723] Kiesel, S. and R. Penno, "Port Control Protocol (PCP)
			Anycast Addresses", RFC 7723, DOI 10.17487/RFC7723,
			January 2016, <http://www.rfc-editor.org/info/rfc7723>.
			[RFC7954] Iannone, L., Lewis, D., Meyer, D., and V. Fuller,
			"Locator/ID Separation Protocol (LISP) Endpoint Identifier
			(EID) Block", RFC 7954, DOI 10.17487/RFC7954, September
			2016, <http://www.rfc-editor.org/info/rfc7954>.
	Authors' Addresses		Authors' Addresses
	Ronald Bonica		Ronald Bonica
	Juniper Networks		Juniper Networks
	Email: rbonica@juniper.net		Email: rbonica@juniper.net
	Michelle Cotton		Michelle Cotton
	ICANN		ICANN
End of changes. 61 change blocks.
	126 lines changed or deleted		390 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/