Registry included below
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.
|Address Block||Name||RFC||Allocation Date||Termination Date||Source||Destination||Forwardable||Global||Reserved-by-Protocol|
|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||False||False||False||False|
|2001:1::1/128||Port Control Protocol Anycast||[RFC7723]||2015-10||N/A||True||True||True||True||False|
|2001:5::/32||EID Space for LISP (Managed by RIPE NCC)||[RFC-ietf-lisp-eid-block-13]||2015-10||2018-12||True||True||True||True||True|
|2001:10::/28||Deprecated (previously ORCHID)||[RFC4843]||2007-03||2014-03|
|2620:4f:8000::/48||Direct Delegation AS112 Service||[RFC7534]||2011-05||N/A||True||True||True||True||False|
Unless allowed by a more specific allocation.
According to the 3+3 Plan outlined in [RFC-ietf-lisp-eid-block-13], termination date can be postponed to December 2021.
Can be used as a multicast source as well.
To be used as EID space by LISP [RFC6830] enabled routers.
See [RFC3056] for details.