IANA IPv4 Special-Purpose Address Registry

Created
2009-08-19
Last Updated
2017-07-03
Available Formats

XML HTML Plain text

Registry included below

IANA IPv4 Special-Purpose Address Registry

IANA IPv4 Special-Purpose Address Registry

Registration Procedure(s)
IETF Review
Reference
[RFC5736][RFC6890][RFC8190]
Note
The IETF has reserved the address block of 192.0.0.0/24 for use for
special purposes relating to protocol assignments. This registry
contains the current assignments made by the IETF from this address
block.

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 Globally Reachable - 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 "Globally Reachable" must also be false.

Available Formats
 CSV

Reserved-
Globally
Allocation Termination Source Destination Forwardable by-
Address Block Name RFC Reachable
Date Date Protocol

0.0.0.0/8 "This host on [RFC1122], 1981-09 N/A True False False False True
this network" Section
3.2.1.3
10.0.0.0/8 Private-Use [RFC1918] 1996-02 N/A True True True False False
100.64.0.0/10 Shared [RFC6598] 2012-04 N/A True True True False False
Address Space
127.0.0.0/8 Loopback [RFC1122], 1981-09 N/A False False [1] False [1] False [1] True
Section [1]
3.2.1.3
169.254.0.0/16 Link Local [RFC3927] 2005-05 N/A True True False False True
172.16.0.0/12 Private-Use [RFC1918] 1996-02 N/A True True True False False
192.0.0.0/24 [2] IETF Protocol [RFC6890], 2010-01 N/A False False False False False
Assignments Section
2.1
192.0.0.0/29 IPv4 Service [RFC7335] 2011-06 N/A True True True False False
Continuity
Prefix
192.0.0.8/32 IPv4 dummy [RFC7600] 2015-03 N/A True False False False False
address
192.0.0.9/32 Port Control [RFC7723] 2015-10 N/A True True True True False
Protocol
Anycast
192.0.0.10/32 Traversal Using [RFC8155] 2017-02 N/A True True True True False
Relays around
NAT Anycast
192.0.0.170/32, NAT64/DNS64 [RFC7050], 2013-02 N/A False False False False True
192.0.0.171/32 Discovery Section
2.2
192.0.2.0/24 Documentation [RFC5737] 2010-01 N/A False False False False False
(TEST-NET-1)
192.31.196.0/24 AS112-v4 [RFC7535] 2014-12 N/A True True True True False
192.52.193.0/24 AMT [RFC7450] 2014-12 N/A True True True True False
192.88.99.0/24 Deprecated [RFC7526] 2001-06 2015-03
(6to4 Relay
Anycast)
192.168.0.0/16 Private-Use [RFC1918] 1996-02 N/A True True True False False
192.175.48.0/24 Direct [RFC7534] 1996-01 N/A True True True True False
Delegation
AS112 Service
198.18.0.0/15 Benchmarking [RFC2544] 1999-03 N/A True True True False False
198.51.100.0/24 Documentation [RFC5737] 2010-01 N/A False False False False False
(TEST-NET-2)
203.0.113.0/24 Documentation [RFC5737] 2010-01 N/A False False False False False
(TEST-NET-3)
240.0.0.0/4 Reserved [RFC1112], 1989-08 N/A False False False False True
Section 4
255.255.255.255/32 Limited [RFC8190] 1984-10 N/A False True False False True
Broadcast [RFC919],
Section 7

Footnotes
[1] Several protocols have been granted exceptions to this rule.
For examples, see [RFC8029] and [RFC5884].

[2] Not useable unless by virtue of a more specific reservation.