Special-Use IPv6 Addresses
RFC 5156
| Document | Type |
RFC - Informational
(April 2008; No errata)
Obsoleted by RFC 6890
|
|
|---|---|---|---|
| Author | Marc Blanchet | ||
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5156 (Informational) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ron Bonica | ||
| Send notices to | (None) | ||
Network Working Group M. Blanchet
Request for Comments: 5156 Viagenie
Category: Informational April 2008
Special-Use IPv6 Addresses
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
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Address Blocks . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Node-Scoped Unicast . . . . . . . . . . . . . . . . . . . . 2
2.2. IPv4-Mapped Addresses . . . . . . . . . . . . . . . . . . . 2
2.3. IPv4-Compatible Addresses . . . . . . . . . . . . . . . . . 2
2.4. Link-Scoped Unicast . . . . . . . . . . . . . . . . . . . . 2
2.5. Unique-Local . . . . . . . . . . . . . . . . . . . . . . . 3
2.6. Documentation Prefix . . . . . . . . . . . . . . . . . . . 3
2.7. 6to4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.8. Teredo . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.9. 6bone . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.10. ORCHID . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.11. Default Route . . . . . . . . . . . . . . . . . . . . . . . 4
2.12. IANA Special-Purpose IPv6 Address Registry . . . . . . . . 4
2.13. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 5
Blanchet Informational [Page 1]
RFC 5156 Special-Use IPv6 Addresses April 2008
1. Introduction
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 [RFC3330].
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.
2. Address Blocks
2.1. Node-Scoped Unicast
::1/128 is the loopback address [RFC4291].
::/128 is the unspecified address [RFC4291].
These two addresses should not appear on the public Internet.
2.2. IPv4-Mapped Addresses
::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses
within this block should not appear on the public Internet.
2.3. IPv4-Compatible Addresses
::<ipv4-address>/96 are the IPv4-compatible addresses [RFC4291].
These addresses are deprecated and should not appear on the public
Internet.
2.4. Link-Scoped Unicast
fe80::/10 are the link-local unicast [RFC4291] addresses. Addresses
within this block should not appear on the public Internet.
Blanchet Informational [Page 2]
RFC 5156 Special-Use IPv6 Addresses April 2008
2.5. Unique-Local
fc00::/7 are the unique-local addresses [RFC4193]. Addresses within
this block should not appear by default on the public Internet.
Procedures for advertising these addresses are further described in
[RFC4193].
2.6. Documentation Prefix
The 2001:db8::/32 are the documentation addresses [RFC3849]. They
are used for documentation purposes such as user manuals, RFCs, etc.
Addresses within this block should not appear on the public Internet.
2.7. 6to4
2002::/16 are the 6to4 addresses [RFC3056]. The 6to4 addresses may
be advertised when the site is running a 6to4 relay or offering a
6to4 transit service. Running such a service [RFC3964] entails
filtering rules specific to 6to4 [RFC3964]. IPv4 addresses
disallowed in 6to4 prefixes are listed in section 5.3.1 of [RFC3964].
2.8. Teredo
2001::/32 are the Teredo addresses [RFC4380]. The Teredo addresses
may be advertised when the site is running a Teredo relay or offering
Show full document text