IANA IPv6 Special-Purpose Address Registry

Created
2006-01-10
Last Updated
2017-02-23
Available Formats

XML
HTML
Plain text

Registry included below

IANA IPv6 Special-Purpose Address Registry

Registration Procedure(s)
IETF Review
Reference
[RFC4773][RFC6890]
Note
Address prefixes listed in the Special-Purpose Address Registry are
not guaranteed routability in any particular local or global context.

The IPv4 and IPv6 Special-Purpose Address Registries maintain the following 
information regarding each entry:

   o  Address Block - A block of IPv4 or IPv6 addresses that has been
      registered for a special purpose.

   o  Name - A descriptive name for the special-purpose address block.

   o  RFC - The RFC through which the special-purpose address block was
      requested.

   o  Allocation Date - The date upon which the special-purpose address
      block was allocated.

   o  Termination Date - The date upon which the allocation is to be
      terminated.  This field is applicable for limited-use allocations
      only.

   o  Source - A boolean value indicating whether an address from the
      allocated special-purpose address block is valid when used as the
      source address of an IP datagram that transits two devices.

   o  Destination - A boolean value indicating whether an address from
      the allocated special-purpose address block is valid when used as
      the destination address of an IP datagram that transits two
      devices.

   o  Forwardable - A boolean value indicating whether a router may
      forward an IP datagram whose destination address is drawn from the
      allocated special-purpose address block between external
      interfaces.

   o  Global - A boolean value indicating whether an IP datagram whose
      destination address is drawn from the allocated special-purpose
      address block is forwardable beyond a specified administrative
      domain.

   o  Reserved-by-Protocol - A boolean value indicating whether the
      special-purpose address block is reserved by IP, itself.  This
      value is "TRUE" if the RFC that created the special-purpose
      address block requires all compliant IP implementations to behave
      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 
"Global" must also be false.
Available Formats

CSV
Address Block Name RFC Allocation Date Termination Date Source Destination Forwardable Global Reserved-by-Protocol
::1/128 Loopback Address [RFC4291] 2006-02 N/A False False False False True
::/128 Unspecified Address [RFC4291] 2006-02 N/A True False False False True
::ffff:0:0/96 IPv4-mapped Address [RFC4291] 2006-02 N/A False False False False True
64:ff9b::/96 IPv4-IPv6 Translat. [RFC6052] 2010-10 N/A True True True True False
100::/64 Discard-Only Address Block [RFC6666] 2012-06 N/A True True True False False
2001::/23 IETF Protocol Assignments [RFC2928] 2000-09 N/A False[1] False[1] False[1] False[1] False
2001::/32 TEREDO [RFC4380] 2006-01 N/A True True True False False
2001:1::1/128 Port Control Protocol Anycast [RFC7723] 2015-10 N/A True True True True False
2001:1::2/128 Traversal Using Relays around NAT Anycast [RFC-ietf-tram-turn-server-discovery-12] 2017-02 N/A True True True True False
2001:2::/48 Benchmarking [RFC5180] 2008-04 N/A True True True False False
2001:3::/32 AMT [RFC7450] 2014-12 N/A True True True True False
2001:4:112::/48 AS112-v6 [RFC7535] 2014-12 N/A True True True True False
2001:5::/32 EID Space for LISP (Managed by RIPE NCC) [RFC7954] 2016-09 2019-09[2] True[3] True True True True[4]
2001:10::/28 Deprecated (previously ORCHID) [RFC4843] 2007-03 2014-03
2001:20::/28 ORCHIDv2 [RFC7343] 2014-07 N/A True True True True False
2001:db8::/32 Documentation [RFC3849] 2004-07 N/A False False False False False
2002::/16[2] 6to4 [RFC3056] 2001-02 N/A True True True N/A[5] False
2620:4f:8000::/48 Direct Delegation AS112 Service [RFC7534] 2011-05 N/A True True True True False
fc00::/7 Unique-Local [RFC4193] 2005-10 N/A True True True False False
fe80::/10 Linked-Scoped Unicast [RFC4291] 2006-02 N/A True True False False True

Footnotes

[1] 
Unless allowed by a more specific allocation.
[2] 
According to the 3+3 Plan outlined in [RFC7954], the termination date can be postponed to September 2022.
[3] 
Can be used as a multicast source as well.
[4] 
To be used as EID space by routers enabled by LISP [RFC6830].
[5] 
See [RFC3056] for details.