Movatterモバイル変換


[0]ホーム

URL:


Internet Assigned Numbers Authority

IPv4 Special-Purpose Address Space

Created
2009-08-19
Last Updated
2025-10-09
Available Formats

XML

HTML

Plain text

Registry Included Below

IPv4 Special-Purpose Address Space

Registration Procedure(s)
IETF Review
Reference
[RFC5736][RFC6890][RFC Errata 6404][RFC8190]
Note
The IETF has reserved the address block of 192.0.0.0/24 for use forspecial purposes relating to protocol assignments. This registrycontains the current assignments made by the IETF from this addressblock.Address prefixes listed in the Special-Purpose Address Registry arenot guaranteed routability in any particular local or global context.The IPv4 and IPv6 Special-Purpose Address Registries maintain thefollowing 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.
Formerly known as
IANA IPv4 Special-Purpose Address Registry (pursuant to [IESG decision])
Available Formats

CSV
Address BlockNameRFCAllocation DateTermination DateSourceDestinationForwardableGlobally ReachableReserved-by-Protocol
0.0.0.0/8"This network"[RFC791], Section 3.21981-09N/ATrueFalseFalseFalseTrue
0.0.0.0/32"This host on this network"[RFC1122], Section 3.2.1.31981-09N/ATrueFalseFalseFalseTrue
10.0.0.0/8Private-Use[RFC1918]1996-02N/ATrueTrueTrueFalseFalse
100.64.0.0/10Shared Address Space[RFC6598]2012-04N/ATrueTrueTrueFalseFalse
127.0.0.0/8Loopback[RFC1122], Section 3.2.1.31981-09N/AFalse [1]False [1]False [1]False [1]True
169.254.0.0/16Link Local[RFC3927]2005-05N/ATrueTrueFalseFalseTrue
172.16.0.0/12Private-Use[RFC1918]1996-02N/ATrueTrueTrueFalseFalse
192.0.0.0/24 [2]IETF Protocol Assignments[RFC6890], Section 2.12010-01N/AFalseFalseFalseFalseFalse
192.0.0.0/29IPv4 Service Continuity Prefix[RFC7335]2011-06N/ATrueTrueTrueFalseFalse
192.0.0.8/32IPv4 dummy address[RFC7600]2015-03N/ATrueFalseFalseFalseFalse
192.0.0.9/32Port Control Protocol Anycast[RFC7723]2015-10N/ATrueTrueTrueTrueFalse
192.0.0.10/32Traversal Using Relays around NAT Anycast[RFC8155]2017-02N/ATrueTrueTrueTrueFalse
192.0.0.170/32, 192.0.0.171/32NAT64/DNS64 Discovery[RFC8880][RFC7050], Section 2.22013-02N/AFalseFalseFalseFalseTrue
192.0.2.0/24Documentation (TEST-NET-1)[RFC5737]2010-01N/AFalseFalseFalseFalseFalse
192.31.196.0/24AS112-v4[RFC7535]2014-12N/ATrueTrueTrueTrueFalse
192.52.193.0/24AMT[RFC7450]2014-12N/ATrueTrueTrueTrueFalse
192.88.99.0/24Deprecated (6to4 Relay Anycast)[RFC7526]2001-062015-03
192.88.99.2/326a44-relay anycast address[RFC6751]2012-10N/ATrueTrueTrueFalseFalse
192.168.0.0/16Private-Use[RFC1918]1996-02N/ATrueTrueTrueFalseFalse
192.175.48.0/24Direct Delegation AS112 Service[RFC7534]1996-01N/ATrueTrueTrueTrueFalse
198.18.0.0/15Benchmarking[RFC2544]1999-03N/ATrueTrueTrueFalseFalse
198.51.100.0/24Documentation (TEST-NET-2)[RFC5737]2010-01N/AFalseFalseFalseFalseFalse
203.0.113.0/24Documentation (TEST-NET-3)[RFC5737]2010-01N/AFalseFalseFalseFalseFalse
240.0.0.0/4Reserved[RFC1112], Section 41989-08N/AFalseFalseFalseFalseTrue
255.255.255.255/32Limited Broadcast[RFC8190] [RFC919], Section 71984-10N/AFalseTrueFalseFalseTrue

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.

[8]ページ先頭

©2009-2026 Movatter.jp