< draft-bchv-rfc6890bis-05.txt		draft-bchv-rfc6890bis-06.txt >
	Network Working Group R. Bonica		Network Working Group R. Bonica
	Internet-Draft Juniper Networks		Internet-Draft Juniper Networks
	Obsoletes: 6890 (if approved) M. Cotton		Updates: 6890 (if approved) M. Cotton
	Intended status: Best Current Practice ICANN		Intended status: Best Current Practice ICANN
	Expires: September 11, 2017 B. Haberman		Expires: October 9, 2017 B. Haberman
	Johns Hopkins University		Johns Hopkins University
	L. Vegoda		L. Vegoda
	ICANN		ICANN
	March 10, 2017		April 7, 2017
	Special-Purpose IP Address Registries		Updates to Special-Purpose IP Address Registries
	draft-bchv-rfc6890bis-05		draft-bchv-rfc6890bis-06
	Abstract		Abstract
	This memo updates the IANA IPv6 Special-Purpose Address Registries to		This memo updates the IANA IPv4 and IPv6 Special-Purpose Address
	address issues raised by the definition of a global prefix. For		Registries to address issues raised by the definition of a "global"
	completeness, this memo contains all the assignments made to the IANA		prefix. It also corrects several errors in registry entries to
	Special-Purpose Address Registries.		ensure the integrity of the IANA Special-Purpose Address Registries.
	This memo obsoletes RFC 6890.		This memo updates RFC 6890.
	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 September 11, 2017.		This Internet-Draft will expire on October 9, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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. Requirements Language . . . . . . . . . . . . . . . . . . . . 3		2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
	3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3		2.1. Definition of Global . . . . . . . . . . . . . . . . . . 3
	3.1. Assignment of an IPv4 Address Block to IANA . . . . . . . 3		2.2. Updates to the IPv4 Special-Purpose Address Registry . . 3
	3.2. Restructuring of the IPv4 and IPv6 Special-Purpose		2.3. Updates to the IPv6 Special-Purpose Address Registry . . 3
	Address Registries . . . . . . . . . . . . . . . . . . . 3		3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
	3.2.1. Information Requirements . . . . . . . . . . . . . . 4		4. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3.2.2. IPv4 Special-Purpose Address Registry Entries . . . . 5		4.1. Normative References . . . . . . . . . . . . . . . . . . 4
	3.2.3. IPv6 Special-Purpose Address Registry Entries . . . . 15		4.2. Informative References . . . . . . . . . . . . . . . . . 4
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 25		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
	5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
	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.
	Several issues have been raised with the documentation of some of the		Several issues have been raised with the documentation of some of the
	special-purpose address blocks in [RFC6890]. Specifically, the		special-purpose address blocks in [RFC6890]. Specifically, the
	definition of global provided in [RFC6890] was misleading as it		definition of "global" provided in [RFC6890] was misleading as it
	slightly differed from the generally accepted definition of "global		slightly differed from the generally accepted definition of "global
	scope" (i.e., the ability to forward beyond the boundaries of an		scope" (i.e., the ability to forward beyond the boundaries of an
	administrative domain, described as "global unicast" in the IPv6		administrative domain, described as "global unicast" in the IPv6
	addressing architecture [RFC4291]).		addressing architecture [RFC4291]).
	This memo reiterates the assignments made to the IPv4 and IPv6		This memo updates the definition of "global" from [RFC6890] for the
	Special-Purpose Address Registries and augments the fields contained		IPv4 and IPv6 Special-Purpose Address Registries, augments the fields
	within the registries in order to address the confusion raised by the		contained within the registries in order to address the confusion
	definition of "global".		raised by the definition of "global", and corrects some errors in
			some of the entries in the Special-Purpose Address Registries.
	This memo obsoletes [RFC6890].
	2. Requirements Language
	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].
	3. IANA Considerations
	3.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
	in [RFC2860].
	IANA has designated special-purpose address blocks in compliance with
	[RFC2860].
	3.2. Restructuring of the IPv4 and IPv6 Special-Purpose Address
	Registries
	IANA has restructured the following registries:
	IPv4 Special-Purpose Address Registry
	(https://www.iana.org/assignments/iana-ipv4-special-registry/iana-
	ipv4-special-registry.xhtml)
	IPv6 Special-Purpose Address Registry
	(https://www,iana.org/assignments/iana-ipv6-special-registry/iana-
	ipv6-special-registry.xhtml)
	The IPv4 Special-Purpose Address Registry records all IPv4 special-
	purpose address blocks. These reservations include, but are not
	limited to, allocations from the 192.0.0.0/24 address block.
	Likewise, the IPv6 Special-Purpose Address Registry records all IPv6
	special-purpose address blocks. These reservations include, but are
	not limited to, allocations from the 2001:0000::/23 address block,
	which is a globally scoped address block.
	Section 3.2.1 of this document describes information that both
	registries will maintain for each entry. IANA has populated the IPv4
	Special-Purpose Address Registry with information taken from
	Section 3.2.2 of this document. Likewise, IANA has populated the
	IPv6 Special-Purpose Address Registry with information taken from
	Section 3.2.3 of this document.
	IANA will update the aforementioned registries as requested in the
	"IANA Considerations" section of a document that has passed IETF
	Review [RFC5226]. The "IANA Considerations" section MUST include all
	of the information specified in Section 3.2.1 of this document.
	3.2.1. Information Requirements
	The IPv4 and IPv6 Special-Purpose Address Registries maintain the
	following information regarding each entry:
	Address Block - A block of IPv4 or IPv6 addresses that has been
	registered for a special purpose.
	Name - A descriptive name for the special-purpose address block.
	RFC - The RFC through which the special-purpose address block was
	requested.
	Allocation Date - The date upon which the special-purpose address
	block was allocated.
	Termination Date - The date upon which the allocation is to be		This memo updates [RFC6890].
	terminated. This field is applicable for limited-use allocations
	only.
	Source - A boolean value indicating whether an address from the		2. IANA Considerations
	allocated special-purpose address block is valid when used as the
	source address of an IP datagram that transits two devices.
	Destination - A boolean value indicating whether an address from		2.1. Definition of Global
	the allocated special-purpose address block is valid when used as
	the destination address of an IP datagram that transits two
	devices.
	Forwardable - A boolean value indicating whether a router may		[RFC6890] defined the term "global" without taking into consideration
	forward an IP datagram whose destination address is drawn from the		the multiple uses of the term. Specifically, IP addresses can be
	allocated special-purpose address block between external		global in terms of allocation scope as well as global in terms of
	interfaces (i.e., different administrative domains).		routing/reachability. To address this ambiguity, the use of the term
			"global" defined in [RFC6890] is replaced with "globally reachable".
			The following definition replaces the definiton of "global" in the
			IANA Special-Purpose Address Registries:
	Globally Reachable - A boolean value indicating whether an IP		o 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		The same relationship between the value of "Destination" and the
	special-purpose address block is reserved by IP, itself. This		values of "Forwardable" and "Global" described in [RFC6890] holds for
	value is "TRUE" if the RFC that created the special-purpose		"Globally Reachable". If the value of "Destination" is FALSE, the
	address block requires all compliant IP implementations to behave		values of "Forwardable" and "Globally Reachable" must also be FALSE.
	in a special way when processing packets either to or from
	addresses contained by the address block.
	If the value of "Destination" is FALSE, the values of "Forwardable"
	and "Globally Reachable" must also be FALSE.
	3.2.2. IPv4 Special-Purpose Address Registry Entries
	Table 1 through Table 22, below, represent entries with which IANA
	has initially populated the IPv4 Special-Purpose Address Registry.
	+----------------------+-----------------------------+
	| Attribute | Value |
	+----------------------+-----------------------------+
	| Address Block | 0.0.0.0/8 |
	| Name | "This host on this network" |
	| RFC | [RFC1122], Section 3.2.1.3 |
	| Allocation Date | September 1981 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | True |
	+----------------------+-----------------------------+
	Table 1: This host on this network
	+----------------------+---------------+
	| Attribute | Value |
	+----------------------+---------------+
	| Address Block | 10.0.0.0/8 |
	| Name | Private-Use |
	| RFC | [RFC1918] |
	| Allocation Date | February 1996 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+---------------+
	Table 2: Private-Use Networks
	+----------------------+----------------------+
	| Attribute | Value |
	+----------------------+----------------------+
	| Address Block | 100.64.0.0/10 |
	| Name | Shared Address Space |
	| RFC | [RFC6598] |
	| Allocation Date | April 2012 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+----------------------+
	Table 3: Shared Address Space
	+----------------------+----------------------------+
	| Attribute | Value |
	+----------------------+----------------------------+
	| Address Block | 127.0.0.0/8 |
	| Name | Loopback |
	| RFC | [RFC1122], Section 3.2.1.3 |
	| Allocation Date | September 1981 |
	| Termination Date | N/A |
	| Source | False [1] |
	| Destination | False [1] |
	| Forwardable | False [1] |
	| Globally Reachable | False [1] |
	| Reserved-by-Protocol | True |
	+----------------------+----------------------------+
	Table 4: Loopback
	[1] Several protocols have been granted exceptions to this rule. For
	examples, see [RFC4379] and [RFC5884].
	+----------------------+----------------+
	| Attribute | Value |
	+----------------------+----------------+
	| Address Block | 169.254.0.0/16 |
	| Name | Link Local |
	| RFC | [RFC3927] |
	| Allocation Date | May 2005 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | True |
	+----------------------+----------------+
	Table 5: Link Local
	+----------------------+---------------+
	| Attribute | Value |
	+----------------------+---------------+
	| Address Block | 172.16.0.0/12 |
	| Name | Private-Use |
	| RFC | [RFC1918] |
	| Allocation Date | February 1996 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+---------------+
	Table 6: Private-Use Networks
	+----------------------+---------------------------+
	| Attribute | Value |
	+----------------------+---------------------------+
	| Address Block | 192.0.0.0/24 [2] |
	| Name | IETF Protocol Assignments |
	| RFC | Section 2.1 of RFC XXXX |
	| Allocation Date | January 2010 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+---------------------------+
	Table 7: IETF Protocol Assignments
	[2] Not usable unless by virtue of a more specific reservation.
	RFC Editor NOTE : Please update XXXX in the above table with the RFC
	number assigned to this document. This note can be removed prior to
	publication.
	+----------------------+--------------------------------+
	| Attribute | Value |
	+----------------------+--------------------------------+
	| Address Block | 192.0.0.0/29 |
	| Name | IPv4 Service Continuity Prefix |
	| RFC | [RFC7335] |
	| Allocation Date | June 2011 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+--------------------------------+
	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 |
	+----------------------+----------------------------+
	| Address Block | 192.0.2.0/24 |
	| Name | Documentation (TEST-NET-1) |
	| RFC | [RFC5737] |
	| Allocation Date | January 2010 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+----------------------------+
	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 |
	+----------------------+-------------------------------+
	| Address Block | 192.88.99.0/24 |
	| Name | Deprecated 6to4 Relay Anycast |
	| RFC | [RFC7526] |
	| Allocation Date | June 2001 |
	| Termination Date | March 2015 |
	| Source | N/A |
	| Destination | N/A |
	| Forwardable | N/A |
	| Globally Reachable | N/A |
	| Reserved-by-Protocol | N/A |
	+----------------------+-------------------------------+
	Table 15: 6to4 Relay Anycast - Deprecated
	+----------------------+----------------+
	| Attribute | Value |
	+----------------------+----------------+
	| Address Block | 192.168.0.0/16 |
	| Name | Private-Use |
	| RFC | [RFC1918] |
	| Allocation Date | February 1996 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+----------------+
	Table 16: Private-Use Networks
	+----------------------+---------------------------------+
	| Attribute | Value |
	+----------------------+---------------------------------+
	| Address Block | 192.175.48.0/24 |
	| Name | Direct Delegation AS112 Service |
	| 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 |
	+----------------------+---------------+
	| Address Block | 198.18.0.0/15 |
	| Name | Benchmarking |
	| RFC | [RFC2544] |
	| Allocation Date | March 1999 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+---------------+
	Table 18: Network Interconnect Device Benchmark Testing
	+----------------------+----------------------------+
	| Attribute | Value |
	+----------------------+----------------------------+
	| Address Block | 198.51.100.0/24 |
	| Name | Documentation (TEST-NET-2) |
	| RFC | [RFC5737] |
	| Allocation Date | January 2010 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+----------------------------+
	Table 19: TEST-NET-2
	+----------------------+----------------------------+
	| Attribute | Value |
	+----------------------+----------------------------+
	| Address Block | 203.0.113.0/24 |
	| Name | Documentation (TEST-NET-3) |
	| RFC | [RFC5737] |
	| Allocation Date | January 2010 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+----------------------------+
	Table 20: TEST-NET-3
	+----------------------+----------------------+
	| Attribute | Value |
	+----------------------+----------------------+
	| Address Block | 240.0.0.0/4 |
	| Name | Reserved |
	| RFC | [RFC1112], Section 4 |
	| Allocation Date | August 1989 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | True |
	+----------------------+----------------------+
	Table 21: Reserved for Future Use
	+----------------------+----------------------+
	| Attribute | Value |
	+----------------------+----------------------+
	| Address Block | 255.255.255.255/32 |
	| Name | Limited Broadcast |
	| RFC | [RFC0919], Section 7 |
	| Allocation Date | October 1984 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | True |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | True |
	+----------------------+----------------------+
	Table 22: Limited Broadcast
	3.2.3. IPv6 Special-Purpose Address Registry Entries
	Table 23 through Table 41, below, represent entries with which the
	IANA has initially populated the IPv6 Special-Purpose Address
	Registry.
	+----------------------+------------------+
	| Attribute | Value |
	+----------------------+------------------+
	| Address Block | ::1/128 |
	| Name | Loopback Address |
	| RFC | [RFC4291] |
	| Allocation Date | February 2006 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | True |
	+----------------------+------------------+
	Table 23: Loopback Address
	+----------------------+---------------------+
	| Attribute | Value |
	+----------------------+---------------------+
	| Address Block | ::/128 |
	| Name | Unspecified Address |
	| RFC | [RFC4291] |
	| Allocation Date | February 2006 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | True |
	+----------------------+---------------------+
	Table 24: Unspecified Address
	+----------------------+---------------------+
	| Attribute | Value |
	+----------------------+---------------------+
	| Address Block | ::ffff:0:0/96 |
	| Name | IPv4-mapped Address |
	| RFC | [RFC4291] |
	| Allocation Date | February 2006 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | True |
	+----------------------+---------------------+
	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 |
	+----------------------+----------------------------+
	| Address Block | 100::/64 |
	| Name | Discard-Only Address Block |
	| RFC | [RFC6666] |
	| Allocation Date | June 2012 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+----------------------------+
	Table 27: Discard-Only Prefix
	+----------------------+---------------------------+
	| Attribute | Value |
	+----------------------+---------------------------+
	| Address Block | 2001::/23 |
	| Name | IETF Protocol Assignments |
	| RFC | [RFC2928] |
	| Allocation Date | September 2000 |
	| Termination Date | N/A |
	| Source | False[1] |
	| Destination | False[1] |
	| Forwardable | False[1] |
	| Globally Reachable | False[1] |
	| Reserved-by-Protocol | False |
	+----------------------+---------------------------+
	Table 28: IETF Protocol Assignments
	[1] Unless allowed by a more specific allocation.
	+----------------------+--------------+
	| Attribute | Value |
	+----------------------+--------------+
	| Address Block | 2001::/32 |
	| Name | TEREDO |
	| RFC | [RFC4380] |
	| Allocation Date | January 2006 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | N/A [2] |
	| Reserved-by-Protocol | False |
	+----------------------+--------------+
	Table 29: TEREDO
	[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 |
	+----------------------+--------------+
	| Address Block | 2001:2::/48 |
	| Name | Benchmarking |
	| RFC | [RFC5180] |
	| Allocation Date | April 2008 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+--------------+
	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 |
	+----------------------+---------------+
	| Address Block | 2001:db8::/32 |
	| Name | Documentation |
	| RFC | [RFC3849] |
	| Allocation Date | July 2004 |
	| Termination Date | N/A |
	| Source | False |
	| Destination | False |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | False |
	+----------------------+---------------+
	Table 37: Documentation
	+----------------------+---------------+
	| Attribute | Value |
	+----------------------+---------------+
	| Address Block | 2002::/16 [6] |
	| Name | 6to4 |
	| RFC | [RFC3056] |
	| Allocation Date | February 2001 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | N/A [6] |
	| Reserved-by-Protocol | False |
	+----------------------+---------------+
	Table 38: 6to4
	[6] See [RFC3056] for details.
	+----------------------+---------------------------------+		The "Global" column in the IPv4 Special-Purpose Address Registry
	| Attribute | Value |		(https://www.iana.org/assignments/iana-ipv4-special-registry) and the
	+----------------------+---------------------------------+		IPv6 Special-Purpose Address Registry
	| Address Block | 2620:4f:8000::/48 |		(https://www.iana.org/assignments/iana-ipv6-special-registry) is
	| Name | Direct Delegation AS112 Service |		renamed to "Globally Reachable".
	| 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		2.2. Updates to the IPv4 Special-Purpose Address Registry
	+----------------------+--------------+		o Limited Broadcast prefix (255.255.255.255/32) - The Reserved-by-
	| Attribute | Value |		Protocol value is changed from False to True.
	+----------------------+--------------+
	| Address Block | fc00::/7 |
	| Name | Unique-Local |
	| RFC | [RFC4193] |
	| Allocation Date | October 2005 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | True |
	| Globally Reachable | False [7] |
	| Reserved-by-Protocol | False |
	+----------------------+--------------+
	Table 40: Unique-Local (Private)		2.3. Updates to the IPv6 Special-Purpose Address Registry
	[7] See [RFC4193] for more details on the routability of Unique-Local		o TEREDO prefix (2001::/32) - The Globally Reachable value is
	addresses. The Unique-Local prefix is drawn from the IPv6 Global		changed from False to "N/A [2]". The [2] footnote states:
	Unicast Address range, but is specified as not globally routed.
	+----------------------+-----------------------+		* See [RFC4380] for details.
	| Attribute | Value |
	+----------------------+-----------------------+
	| Address Block | fe80::/10 |
	| Name | Linked-Scoped Unicast |
	| RFC | [RFC4291] |
	| Allocation Date | February 2006 |
	| Termination Date | N/A |
	| Source | True |
	| Destination | True |
	| Forwardable | False |
	| Globally Reachable | False |
	| Reserved-by-Protocol | True |
	+----------------------+-----------------------+
	Table 41: Link-Scoped Unicast		o EID Space for LISP (2001:5::/32) - All footnotes are incremented
			by 1.
	4. Security Considerations		o 6to4 (2002::/16) - All footnotes are incremented by 1.
	Security of the Internet's routing system relies on the ability to		o Unique-Local (fc00::/7) - The Globally Reachable value is changed
	authenticate an assertion of unique control of an address block.		from False to "False [7]". The [7] footnote states:
	Measures to authenticate such assertions rely on validation that the
	address block forms part of an existing allocated address block and
	that there is a trustable and unique reference in the IANA address
	registries.
	The proposed registry is intended to provide an authoritative source		* See [RFC4193] for more details on the routability of Unique-
	of information regarding the currency and intended purpose of special		Local addresses. The Unique-Local prefix is drawn from the
	purpose address blocks that are designated from the IANA-administered		IPv6 Global Unicast Address range, but is specified as not
	Special-Purpose registry. This is a small step towards the creation		globally routed.
	of a comprehensive registry framework that can be used as a trust
	point for commencing a chain of address validation. Consideration
	should be given to IANA registry publication formats that are machine
	parsable. Additionally, consideration should be given to the use of
	file signatures and associated certificate mechanisms to allow
	applications to confirm that the registry contents are current and
	that they have been published by the IANA.
	5. Acknowledgements		3. 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. Daniel Migualt provided an in-depth		versions of this document. Daniel Migualt provided an in-depth
	review that helped strengthen the text within the document.		review that helped strengthen the text within the document.
	6. References		4. 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		4.1. Normative References
	[RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5,		[RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,
	RFC 919, DOI 10.17487/RFC0919, October 1984,		"Special-Purpose IP Address Registries", BCP 153,
	<http://www.rfc-editor.org/info/rfc919>.		RFC 6890, DOI 10.17487/RFC6890, April 2013,
			<http://www.rfc-editor.org/info/rfc6890>.
	[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,		4.2. Informative References
	RFC 1112, DOI 10.17487/RFC1112, August 1989,
	<http://www.rfc-editor.org/info/rfc1112>.
	[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -		[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
	Communication Layers", STD 3, RFC 1122,		Communication Layers", STD 3, RFC 1122,
	DOI 10.17487/RFC1122, October 1989,		DOI 10.17487/RFC1122, October 1989,
	<http://www.rfc-editor.org/info/rfc1122>.		<http://www.rfc-editor.org/info/rfc1122>.
	[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
	and E. Lear, "Address Allocation for Private Internets",
	BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996,
	<http://www.rfc-editor.org/info/rfc1918>.
	[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for
	Network Interconnect Devices", RFC 2544,
	DOI 10.17487/RFC2544, March 1999,
	<http://www.rfc-editor.org/info/rfc2544>.
	[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
	Understanding Concerning the Technical Work of the
	Internet Assigned Numbers Authority", RFC 2860,
	DOI 10.17487/RFC2860, June 2000,
	<http://www.rfc-editor.org/info/rfc2860>.
	[RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial
	IPv6 Sub-TLA ID Assignments", RFC 2928,
	DOI 10.17487/RFC2928, September 2000,
	<http://www.rfc-editor.org/info/rfc2928>.
	[RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains
	via IPv4 Clouds", RFC 3056, DOI 10.17487/RFC3056, February
	2001, <http://www.rfc-editor.org/info/rfc3056>.
	[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
	Reserved for Documentation", RFC 3849,
	DOI 10.17487/RFC3849, July 2004,
	<http://www.rfc-editor.org/info/rfc3849>.
	[RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic
	Configuration of IPv4 Link-Local Addresses", RFC 3927,
	DOI 10.17487/RFC3927, May 2005,
	<http://www.rfc-editor.org/info/rfc3927>.
	[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast		[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
	Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005,		Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005,
	<http://www.rfc-editor.org/info/rfc4193>.		<http://www.rfc-editor.org/info/rfc4193>.
	[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing		[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
	Architecture", RFC 4291, DOI 10.17487/RFC4291, February		Architecture", RFC 4291, DOI 10.17487/RFC4291, February
	2006, <http://www.rfc-editor.org/info/rfc4291>.		2006, <http://www.rfc-editor.org/info/rfc4291>.
	[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
	Label Switched (MPLS) Data Plane Failures", RFC 4379,
	DOI 10.17487/RFC4379, February 2006,
	<http://www.rfc-editor.org/info/rfc4379>.
	[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,
	DOI 10.17487/RFC4380, February 2006,		DOI 10.17487/RFC4380, February 2006,
	<http://www.rfc-editor.org/info/rfc4380>.		<http://www.rfc-editor.org/info/rfc4380>.
	[RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix
	for Overlay Routable Cryptographic Hash Identifiers
	(ORCHID)", RFC 4843, DOI 10.17487/RFC4843, April 2007,
	<http://www.rfc-editor.org/info/rfc4843>.
	[RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D.
	Dugatkin, "IPv6 Benchmarking Methodology for Network
	Interconnect Devices", RFC 5180, DOI 10.17487/RFC5180, May
	2008, <http://www.rfc-editor.org/info/rfc5180>.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	DOI 10.17487/RFC5226, May 2008,
	<http://www.rfc-editor.org/info/rfc5226>.
	[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
	Reserved for Documentation", RFC 5737,
	DOI 10.17487/RFC5737, January 2010,
	<http://www.rfc-editor.org/info/rfc5737>.
	[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
	"Bidirectional Forwarding Detection (BFD) for MPLS Label
	Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884,
	June 2010, <http://www.rfc-editor.org/info/rfc5884>.
	[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.
	Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,
	DOI 10.17487/RFC6052, October 2010,
	<http://www.rfc-editor.org/info/rfc6052>.
	[RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and
	M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address
	Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April
	2012, <http://www.rfc-editor.org/info/rfc6598>.
	[RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6",
	RFC 6666, DOI 10.17487/RFC6666, August 2012,
	<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,
	"Special-Purpose IP Address Registries", BCP 153,
	RFC 6890, DOI 10.17487/RFC6890, April 2013,
	<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
	Prefix for 6to4 Relay Routers", BCP 196, RFC 7526,
	DOI 10.17487/RFC7526, May 2015,
	<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
	Email: michelle.cotton@icann.org		Email: michelle.cotton@icann.org
	Brian Haberman		Brian Haberman
	Johns Hopkins University		Johns Hopkins University
	Email: brian@innovationslab.net		Email: brian@innovationslab.net
	Leo Vegoda		Leo Vegoda
	ICANN		ICANN
	Email: leo.vegoda@icann.org		Email: leo.vegoda@icann.org
End of changes. 36 change blocks.
	1020 lines changed or deleted		71 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/