draft-ietf-v6ops-rfc3330-for-ipv6-04.txt   rfc5156.txt 
Network Working Group M. Blanchet Network Working Group M. Blanchet
Internet-Draft Viagenie Request for Comments: 5156 Viagenie
Intended status: Informational January 15, 2008
Expires: July 18, 2008
Special-Use IPv6 Addresses Special-Use IPv6 Addresses
draft-ietf-v6ops-rfc3330-for-ipv6-04.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Status of This Memo
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 18, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2008). 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 Abstract
This document describes the global and other specialized IPv6 address This document is a compilation of special IPv6 addresses defined in
blocks. It does not address IPv6 address space assigned to operators other RFCs. It can be used as a checklist of invalid routing
and users through the Regional Internet Registries. These prefixes for developing filtering policies for routes and IP packets.
descriptions are useful for route and IP filtering, for documentation It does not discuss addresses that are assigned to operators and
and other purposes. users through the Regional Internet Registries.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Address Blocks . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Address Blocks . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Node-scoped Unicast . . . . . . . . . . . . . . . . . . . . 3 2.1. Node-Scoped Unicast . . . . . . . . . . . . . . . . . . . . 2
2.2. IPv4-Mapped Addresses . . . . . . . . . . . . . . . . . . . 3 2.2. IPv4-Mapped Addresses . . . . . . . . . . . . . . . . . . . 2
2.3. IPv4-compatible Addresses . . . . . . . . . . . . . . . . . 3 2.3. IPv4-Compatible Addresses . . . . . . . . . . . . . . . . . 2
2.4. Link-scoped Unicast . . . . . . . . . . . . . . . . . . . . 3 2.4. Link-Scoped Unicast . . . . . . . . . . . . . . . . . . . . 2
2.5. Unique-Local . . . . . . . . . . . . . . . . . . . . . . . 3 2.5. Unique-Local . . . . . . . . . . . . . . . . . . . . . . . 3
2.6. Documentation Prefix . . . . . . . . . . . . . . . . . . . 4 2.6. Documentation Prefix . . . . . . . . . . . . . . . . . . . 3
2.7. 6to4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.7. 6to4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.8. Teredo . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.8. Teredo . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.9. 6bone . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.9. 6bone . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.10. ORCHID . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.10. ORCHID . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.11. Default Route . . . . . . . . . . . . . . . . . . . . . . . 4 2.11. Default Route . . . . . . . . . . . . . . . . . . . . . . . 4
2.12. IANA Special Purpose IPv6 Address Block . . . . . . . . . . 5 2.12. IANA Special-Purpose IPv6 Address Registry . . . . . . . . 4
2.13. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.13. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 6 6.2. Informative References . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 8
1. Introduction 1. Introduction
This document describes the global and other specialized IPv6 address This document is a compilation of special IPv6 addresses defined in
blocks.It does not address IPv6 address space assigned to operators other RFCs. It can be used as a checklist of invalid routing
and users through the Regional Internet Registries. These prefixes for developing filtering policies for routes and IP packets.
descriptions are useful for route and IP filtering, for documentation It does not discuss addresses that are assigned to operators and
and other purposes. users through the Regional Internet Registries.
The document is structured by address types. The document format is The document is structured by address types. The document format is
similar to [RFC3330]. similar to [RFC3330].
Some tips about filtering are given, but are not mandatory to Some tips about filtering are given, but are not mandatory to
implement. implement.
The addresses listed in this document must not be hard coded into The addresses listed in this document must not be hard-coded into
implementations. implementations.
2. Address Blocks 2. Address Blocks
2.1. Node-scoped Unicast 2.1. Node-Scoped Unicast
::1/128 is the loopback address [RFC4291]. ::1/128 is the loopback address [RFC4291].
::/128 is the unspecified address [RFC4291]. ::/128 is the unspecified address [RFC4291].
Addresses within this block should not appear on the public Internet. These two addresses should not appear on the public Internet.
2.2. IPv4-Mapped Addresses 2.2. IPv4-Mapped Addresses
::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses ::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses
within this block should not appear on the public Internet. within this block should not appear on the public Internet.
2.3. IPv4-compatible Addresses 2.3. IPv4-Compatible Addresses
::ipv4-address/96 are the IPv4-compatible addresses [RFC4291]. These ::<ipv4-address>/96 are the IPv4-compatible addresses [RFC4291].
addresses are deprecated and should not appear on the public These addresses are deprecated and should not appear on the public
Internet. Internet.
2.4. Link-scoped Unicast 2.4. Link-Scoped Unicast
fe80::/10 are the link-local unicast [RFC4291] addresses. Addresses fe80::/10 are the link-local unicast [RFC4291] addresses. Addresses
within this block should not appear on the public Internet. within this block should not appear on the public Internet.
2.5. Unique-Local 2.5. Unique-Local
fc00::/7 are the unique-local addresses [RFC4193]. Addresses within fc00::/7 are the unique-local addresses [RFC4193]. Addresses within
this block should not appear by default on the public Internet. this block should not appear by default on the public Internet.
Procedures for advertising these addresses are further described in
Procedure for advertising these addresses are further described in
[RFC4193]. [RFC4193].
2.6. Documentation Prefix 2.6. Documentation Prefix
The 2001:db8::/32 are the documentation addresses [RFC3849]. They The 2001:db8::/32 are the documentation addresses [RFC3849]. They
are used for documentation purposes such as user manuals, RFCs, etc. are used for documentation purposes such as user manuals, RFCs, etc.
Addresses within this block should not appear on the public Internet. Addresses within this block should not appear on the public Internet.
2.7. 6to4 2.7. 6to4
2002::/16 are the 6to4 addresses [RFC3056]. The 6to4 addresses may 2002::/16 are the 6to4 addresses [RFC3056]. The 6to4 addresses may
be advertised when the site is running a 6to4 relay or offering a be advertised when the site is running a 6to4 relay or offering a
6to4 transit service. However, the provider of this service should 6to4 transit service. Running such a service [RFC3964] entails
be aware of the implications of running such service[RFC3964], which filtering rules specific to 6to4 [RFC3964]. IPv4 addresses
include some specific filtering rules for 6to4. IPv4 addresses
disallowed in 6to4 prefixes are listed in section 5.3.1 of [RFC3964]. disallowed in 6to4 prefixes are listed in section 5.3.1 of [RFC3964].
2.8. Teredo 2.8. Teredo
2001::/32 are the Teredo addresses [RFC4380]. The Teredo addresses 2001::/32 are the Teredo addresses [RFC4380]. The Teredo addresses
may be advertised when the site is running a Teredo relay or offering may be advertised when the site is running a Teredo relay or offering
a Teredo transit service. a Teredo transit service.
2.9. 6bone 2.9. 6bone
5f00::/8 were the addresses of the first instance of the 6bone 5f00::/8 were the addresses of the first instance of the 6bone
experimental network [RFC1897]. experimental network [RFC1897].
3ffe::/16 were the addresses of the second instance of the 6bone 3ffe::/16 were the addresses of the second instance of the 6bone
experimental network [RFC2471]. experimental network [RFC2471].
Both 5f00::/8 and 3ffe::/16 were returned to IANA [RFC3701]. These Both 5f00::/8 and 3ffe::/16 were returned to IANA [RFC3701]. These
addresses are subject to future allocation, similar to current addresses are subject to future allocation, similar to current
unallocated address space. Addresses within this block should not unallocated address space. Addresses within these blocks should not
appear on the public Internet until they are reallocated. appear on the public Internet until they are reallocated.
2.10. ORCHID 2.10. ORCHID
2001:10::/28 are ORCHID addresses [RFC4843]. These addresses are 2001:10::/28 are Overlay Routable Cryptographic Hash IDentifiers
used as identifiers and are not routable at the IP layer. Addresses (ORCHID) addresses [RFC4843]. These addresses are used as
within this block should not appear on the public Internet. identifiers and are not routable at the IP layer. Addresses within
this block should not appear on the public Internet.
2.11. Default Route 2.11. Default Route
::/0 is the default unicast route address. ::/0 is the default unicast route address.
2.12. IANA Special Purpose IPv6 Address Block 2.12. IANA Special-Purpose IPv6 Address Registry
An IANA registry (iana-ipv6-special-registry) is set [RFC4773] for An IANA registry (iana-ipv6-special-registry) exists [RFC4773] for
Special Purpose IPv6 address blocks assignments used for experiments Special-Purpose IPv6 address block assignments for experiments and
and other purposes. Addresses within this registry should be other purposes. Addresses within this registry should be reviewed
reviewed for Internet routing considerations. for Internet routing considerations.
2.13. Multicast 2.13. Multicast
ff00::/8 are multicast addresses [RFC4291]. They have a 4 bits scope ff00::/8 are multicast addresses [RFC4291]. They contain a 4-bit
in the address field where only some value are of global scope scope in the address field where only some values are of global scope
[RFC4291]. Only addresses with global scope in this block may appear [RFC4291]. Only addresses with global scope in this block may appear
on the public Internet. on the public Internet.
Multicast routes must not appear in unicast routing tables. Multicast routes must not appear in unicast routing tables.
3. Security Considerations 3. Security Considerations
This document lists addresses and guidelines associated with them. Filtering the invalid routing prefixes listed in this document should
The guidelines should improve the security of networks by the improve the security of networks.
filtering of invalid routing prefixes.
4. IANA Considerations 4. IANA Considerations
To ensure consistency and to provide cross-referencing for the To ensure consistency and to provide cross-referencing for the
benefit of the community, IANA is requested to insert the following benefit of the community, IANA has inserted the following paragraph
paragraph in the header of the iana-ipv6-special registry. in the header of the iana-ipv6-special-registry.
"Other special IPv6 addresses requiring specific considerations for "Other special IPv6 addresses requiring specific considerations for
global routing are listed in RFCXXXX." global routing are listed in RFC 5156."
NOTE TO RFC EDITOR and IANA: replace RFCXXXX by the assigned RFC
number of this document.
5. Acknowledgements 5. Acknowledgements
Florent Parent, Pekka Savola, Tim Chown, Alain Baudot, Stig Venaas, Florent Parent, Pekka Savola, Tim Chown, Alain Baudot, Stig Venaas,
Vincent Jardin, Olaf Bonness, David Green, Gunter Van de Velde, Vincent Jardin, Olaf Bonness, David Green, Gunter Van de Velde,
Michael Barnes, Fred Baker, Edward Lewis, Marla Azinger, Brian Michael Barnes, Fred Baker, Edward Lewis, Marla Azinger, Brian
Carpenter, Mark Smith, Kevin Loch, Alain Durand, Jim Bound, Peter Carpenter, Mark Smith, Kevin Loch, Alain Durand, Jim Bound, Peter
Sherbin, Bob Hinden, Gert Doering, Niall O'Reilly, Mark Townsley and Sherbin, Bob Hinden, Gert Doering, Niall O'Reilly, Mark Townsley,
Jari Arkko have provided input and suggestions to this document. Jari Arkko, and Iain Calder have provided input and suggestions to
this document.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
6.2. Informative References 6.2. Informative References
skipping to change at page 7, line 10 skipping to change at page 6, line 10
[RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix
for Overlay Routable Cryptographic Hash Identifiers for Overlay Routable Cryptographic Hash Identifiers
(ORCHID)", RFC 4843, April 2007. (ORCHID)", RFC 4843, April 2007.
Author's Address Author's Address
Marc Blanchet Marc Blanchet
Viagenie Viagenie
2600 boul. Laurier, suite 625 2600 boul. Laurier, suite 625
Quebec, QC G1V 4W5 Quebec, QC G1V 4W1
Canada Canada
Email: Marc.Blanchet@viagenie.ca EMail: Marc.Blanchet@viagenie.ca
URI: http://www.viagenie.ca URI: http://www.viagenie.ca
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
skipping to change at page 8, line 44 skipping to change at line 272
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 29 change blocks. 
99 lines changed or deleted 66 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/