5156
INFORMATIONAL
Special-Use IPv6 Addresses (Obsoleted)
Authors: M. Blanchet
Date: April 2008
Area: ops
Working Group: v6ops
Stream: IETF
Obsoleted by:
RFC 6890
Abstract
This document is a compilation of special IPv6 addresses defined in other RFCs. It can be used as a checklist of invalid routing prefixes for developing filtering policies for routes and IP packets. It does not discuss addresses that are assigned to operators and users through the Regional Internet Registries. This memo provides information for the Internet community.
RFC 5156
Obsoleted by: 6890 INFORMATIONAL
Network Working Group M. Blanchet
Request for Comments: 5156 Viagenie
Category: Informational April 2008
<span class="h1">Special-Use IPv6 Addresses</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Abstract
This document is a compilation of special IPv6 addresses defined in
other RFCs. It can be used as a checklist of invalid routing
prefixes for developing filtering policies for routes and IP packets.
It does not discuss addresses that are assigned to operators and
users through the Regional Internet Registries.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Address Blocks . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2.1">2.1</a>. Node-Scoped Unicast . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2.2">2.2</a>. IPv4-Mapped Addresses . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2.3">2.3</a>. IPv4-Compatible Addresses . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2.4">2.4</a>. Link-Scoped Unicast . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2.5">2.5</a>. Unique-Local . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.6">2.6</a>. Documentation Prefix . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.7">2.7</a>. 6to4 . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.8">2.8</a>. Teredo . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.9">2.9</a>. 6bone . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.10">2.10</a>. ORCHID . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.11">2.11</a>. Default Route . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.12">2.12</a>. IANA Special-Purpose IPv6 Address Registry . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.13">2.13</a>. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<span class="grey">Blanchet Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc5156">RFC 5156</a> Special-Use IPv6 Addresses April 2008</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document is a compilation of special IPv6 addresses defined in
other RFCs. It can be used as a checklist of invalid routing
prefixes for developing filtering policies for routes and IP packets.
It does not discuss addresses that are assigned to operators and
users through the Regional Internet Registries.
The document is structured by address types. The document format is
similar to [<a href="./rfc3330" title=""Special-Use IPv4 Addresses"">RFC3330</a>].
Some tips about filtering are given, but are not mandatory to
implement.
The addresses listed in this document must not be hard-coded into
implementations.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Address Blocks</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Node-Scoped Unicast</span>
::1/128 is the loopback address [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>].
::/128 is the unspecified address [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>].
These two addresses should not appear on the public Internet.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. IPv4-Mapped Addresses</span>
::FFFF:0:0/96 are the IPv4-mapped addresses [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>]. Addresses
within this block should not appear on the public Internet.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. IPv4-Compatible Addresses</span>
::<ipv4-address>/96 are the IPv4-compatible addresses [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>].
These addresses are deprecated and should not appear on the public
Internet.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Link-Scoped Unicast</span>
fe80::/10 are the link-local unicast [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] addresses. Addresses
within this block should not appear on the public Internet.
<span class="grey">Blanchet Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc5156">RFC 5156</a> Special-Use IPv6 Addresses April 2008</span>
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Unique-Local</span>
fc00::/7 are the unique-local addresses [<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>]. Addresses within
this block should not appear by default on the public Internet.
Procedures for advertising these addresses are further described in
[<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>].
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Documentation Prefix</span>
The 2001:db8::/32 are the documentation addresses [<a href="./rfc3849" title=""IPv6 Address Prefix Reserved for Documentation"">RFC3849</a>]. They
are used for documentation purposes such as user manuals, RFCs, etc.
Addresses within this block should not appear on the public Internet.
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. 6to4</span>
2002::/16 are the 6to4 addresses [<a href="./rfc3056" title=""Connection of IPv6 Domains via IPv4 Clouds"">RFC3056</a>]. The 6to4 addresses may
be advertised when the site is running a 6to4 relay or offering a
6to4 transit service. Running such a service [<a href="./rfc3964" title=""Security Considerations for 6to4"">RFC3964</a>] entails
filtering rules specific to 6to4 [<a href="./rfc3964" title=""Security Considerations for 6to4"">RFC3964</a>]. IPv4 addresses
disallowed in 6to4 prefixes are listed in <a href="./rfc3964#section-5.3.1">section 5.3.1 of [RFC3964]</a>.
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Teredo</span>
2001::/32 are the Teredo addresses [<a href="./rfc4380" title=""Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)"">RFC4380</a>]. The Teredo addresses
may be advertised when the site is running a Teredo relay or offering
a Teredo transit service.
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. 6bone</span>
5f00::/8 were the addresses of the first instance of the 6bone
experimental network [<a href="./rfc1897" title=""IPv6 Testing Address Allocation"">RFC1897</a>].
3ffe::/16 were the addresses of the second instance of the 6bone
experimental network [<a href="./rfc2471" title=""IPv6 Testing Address Allocation"">RFC2471</a>].
Both 5f00::/8 and 3ffe::/16 were returned to IANA [<a href="./rfc3701" title=""6bone (IPv6 Testing Address Allocation) Phaseout"">RFC3701</a>]. These
addresses are subject to future allocation, similar to current
unallocated address space. Addresses within these blocks should not
appear on the public Internet until they are reallocated.
<span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. ORCHID</span>
2001:10::/28 are Overlay Routable Cryptographic Hash IDentifiers
(ORCHID) addresses [<a href="./rfc4843" title=""An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)"">RFC4843</a>]. These addresses are used as
identifiers and are not routable at the IP layer. Addresses within
this block should not appear on the public Internet.
<span class="grey">Blanchet Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc5156">RFC 5156</a> Special-Use IPv6 Addresses April 2008</span>
<span class="h3"><a class="selflink" id="section-2.11" href="#section-2.11">2.11</a>. Default Route</span>
::/0 is the default unicast route address.
<span class="h3"><a class="selflink" id="section-2.12" href="#section-2.12">2.12</a>. IANA Special-Purpose IPv6 Address Registry</span>
An IANA registry (iana-ipv6-special-registry) exists [<a href="./rfc4773" title=""Administration of the IANA Special Purpose IPv6 Address Block"">RFC4773</a>] for
Special-Purpose IPv6 address block assignments for experiments and
other purposes. Addresses within this registry should be reviewed
for Internet routing considerations.
<span class="h3"><a class="selflink" id="section-2.13" href="#section-2.13">2.13</a>. Multicast</span>
ff00::/8 are multicast addresses [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>]. They contain a 4-bit
scope in the address field where only some values are of global scope
[<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>]. Only addresses with global scope in this block may appear
on the public Internet.
Multicast routes must not appear in unicast routing tables.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
Filtering the invalid routing prefixes listed in this document should
improve the security of networks.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
To ensure consistency and to provide cross-referencing for the
benefit of the community, IANA has inserted the following paragraph
in the header of the iana-ipv6-special-registry.
"Other special IPv6 addresses requiring specific considerations for
global routing are listed in <a href="./rfc5156">RFC 5156</a>."
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
Florent Parent, Pekka Savola, Tim Chown, Alain Baudot, Stig Venaas,
Vincent Jardin, Olaf Bonness, David Green, Gunter Van de Velde,
Michael Barnes, Fred Baker, Edward Lewis, Marla Azinger, Brian
Carpenter, Mark Smith, Kevin Loch, Alain Durand, Jim Bound, Peter
Sherbin, Bob Hinden, Gert Doering, Niall O'Reilly, Mark Townsley,
Jari Arkko, and Iain Calder have provided input and suggestions to
this document.
<span class="grey">Blanchet Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc5156">RFC 5156</a> Special-Use IPv6 Addresses April 2008</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC1897">RFC1897</a>] Hinden, R. and J. Postel, "IPv6 Testing Address
Allocation", <a href="./rfc1897">RFC 1897</a>, January 1996.
[<a id="ref-RFC2471">RFC2471</a>] Hinden, R., Fink, R., and J. Postel, "IPv6 Testing Address
Allocation", <a href="./rfc2471">RFC 2471</a>, December 1998.
[<a id="ref-RFC3056">RFC3056</a>] Carpenter, B. and K. Moore, "Connection of IPv6 Domains
via IPv4 Clouds", <a href="./rfc3056">RFC 3056</a>, February 2001.
[<a id="ref-RFC3330">RFC3330</a>] IANA, "Special-Use IPv4 Addresses", <a href="./rfc3330">RFC 3330</a>,
September 2002.
[<a id="ref-RFC3701">RFC3701</a>] Fink, R. and R. Hinden, "6bone (IPv6 Testing Address
Allocation) Phaseout", <a href="./rfc3701">RFC 3701</a>, March 2004.
[<a id="ref-RFC3849">RFC3849</a>] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
Reserved for Documentation", <a href="./rfc3849">RFC 3849</a>, July 2004.
[<a id="ref-RFC3964">RFC3964</a>] Savola, P. and C. Patel, "Security Considerations for
6to4", <a href="./rfc3964">RFC 3964</a>, December 2004.
[<a id="ref-RFC4193">RFC4193</a>] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Addresses", <a href="./rfc4193">RFC 4193</a>, October 2005.
[<a id="ref-RFC4380">RFC4380</a>] Huitema, C., "Teredo: Tunneling IPv6 over UDP through
Network Address Translations (NATs)", <a href="./rfc4380">RFC 4380</a>,
February 2006.
[<a id="ref-RFC4773">RFC4773</a>] Huston, G., "Administration of the IANA Special Purpose
IPv6 Address Block", <a href="./rfc4773">RFC 4773</a>, December 2006.
[<a id="ref-RFC4843">RFC4843</a>] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix
for Overlay Routable Cryptographic Hash Identifiers
(ORCHID)", <a href="./rfc4843">RFC 4843</a>, April 2007.
<span class="grey">Blanchet Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc5156">RFC 5156</a> Special-Use IPv6 Addresses April 2008</span>
Author's Address
Marc Blanchet
Viagenie
2600 boul. Laurier, suite 625
Quebec, QC G1V 4W1
Canada
EMail: [email protected]
URI: <a href="http://www.viagenie.ca">http://www.viagenie.ca</a>
<span class="grey">Blanchet Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc5156">RFC 5156</a> Special-Use IPv6 Addresses April 2008</span>
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
[email protected].
Blanchet Informational [Page 7]
Annotations
Select text to annotate