--- 1/draft-ietf-v6ops-rfc3330-for-ipv6-03.txt 2008-01-15 19:12:13.000000000 +0100 +++ 2/draft-ietf-v6ops-rfc3330-for-ipv6-04.txt 2008-01-15 19:12:13.000000000 +0100 @@ -1,18 +1,18 @@ Network Working Group M. Blanchet Internet-Draft Viagenie -Intended status: Informational October 5, 2007 -Expires: April 7, 2008 +Intended status: Informational January 15, 2008 +Expires: July 18, 2008 Special-Use IPv6 Addresses - draft-ietf-v6ops-rfc3330-for-ipv6-03.txt + 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 Task Force (IETF), its areas, and its working groups. Note that @@ -23,25 +23,25 @@ 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 April 7, 2008. + This Internet-Draft will expire on July 18, 2008. Copyright Notice - Copyright (C) The IETF Trust (2007). + Copyright (C) The IETF Trust (2008). Abstract This document describes the global and other specialized IPv6 address blocks.It does not address IPv6 address space assigned to operators and users through the Regional Internet Registries. These descriptions are useful for route and IP filtering, for documentation and other purposes. Table of Contents @@ -50,152 +50,170 @@ 2. Address Blocks . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Node-scoped Unicast . . . . . . . . . . . . . . . . . . . . 3 2.2. IPv4-Mapped Addresses . . . . . . . . . . . . . . . . . . . 3 2.3. IPv4-compatible Addresses . . . . . . . . . . . . . . . . . 3 2.4. Link-scoped Unicast . . . . . . . . . . . . . . . . . . . . 3 2.5. Unique-Local . . . . . . . . . . . . . . . . . . . . . . . 3 2.6. Documentation Prefix . . . . . . . . . . . . . . . . . . . 4 2.7. 6to4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.8. Teredo . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.9. 6bone . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 2.10. Default Route . . . . . . . . . . . . . . . . . . . . . . . 4 - 2.11. IANA Special Purpose IPv6 Address Block . . . . . . . . . . 4 - 2.12. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . 5 + 2.10. ORCHID . . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 2.11. Default Route . . . . . . . . . . . . . . . . . . . . . . . 4 + 2.12. IANA Special Purpose IPv6 Address Block . . . . . . . . . . 5 + 2.13. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 - 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 - 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 + 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 + 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 + 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 - Intellectual Property and Copyright Statements . . . . . . . . . . 7 + Intellectual Property and Copyright Statements . . . . . . . . . . 8 1. Introduction This document describes the global and other specialized IPv6 address blocks.It does not address IPv6 address space assigned to operators and users through the Regional Internet Registries. These descriptions are useful for route and IP filtering, for documentation and other purposes. 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]. Addresses within this block should not appear on the public Internet. 2.2. IPv4-Mapped Addresses - ::FFFF:0:0/96 is 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. 2.3. IPv4-compatible Addresses - ::ipv4-address/96 is the IPv4-compatible addresses [RFC4291]. These + ::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. 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. - Procedure of advertising these addresses are further described in + + Procedure 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 [RFC4291][RFC3056]. The 6to4 - addresses may be advertised when the site is running a 6to4 relay or - offering a 6to4 transit service. However, the provider of this - service should be aware of the implications of running such - service[RFC3964], which includes some specific filtering rules for - 6to4. IPv4 addresses disallowed in 6to4 prefixes are listed in - section 5.3.1 of [RFC3964]. + 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. However, the provider of this service should + be aware of the implications of running such service[RFC3964], which + include some specific filtering rules for 6to4. 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 a Teredo transit service. 2.9. 6bone 5f00::/8 were the addresses of the first instance of the 6bone experimental network [RFC1897]. 3ffe::/16 were the addresses of the second instance of the 6bone experimental network [RFC2471]. Both 5f00::/8 and 3ffe::/16 were returned to IANA [RFC3701]. These addresses are subject to future allocation, similar to current unallocated address space. Addresses within this block should not appear on the public Internet until they are reallocated. -2.10. Default Route +2.10. ORCHID + + 2001:10::/28 are ORCHID addresses [RFC4843]. 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. + +2.11. Default Route ::/0 is the default unicast route address. -2.11. IANA Special Purpose IPv6 Address Block +2.12. IANA Special Purpose IPv6 Address Block An IANA registry (iana-ipv6-special-registry) is set[RFC4773] for Special Purpose IPv6 address blocks assignments used for experiments and other purposes. Addresses within this registry should be reviewed for Internet routing considerations. -2.12. Multicast +2.13. Multicast ff00::/8 are multicast addresses [RFC4291]. They have a 4 bits scope in the address field where only some value are of global scope [RFC4291]. Only addresses with global scope in this block may appear on the public Internet. Multicast routes must not appear in unicast routing tables. 3. Security Considerations - This document list addresses and guidelines associated with them. + This document lists addresses and guidelines associated with them. The guidelines should improve the security of networks by the filtering of invalid routing prefixes. 4. IANA Considerations - This document has no actions for IANA. + To ensure consistency and to provide cross-referencing for the + benefit of the community, IANA is requested to insert 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 RFCXXXX." + + NOTE TO RFC EDITOR and IANA: replace RFCXXXX by the assigned RFC + number of this document. 5. Acknowledgements 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 and Niall O'Reilly have provided - input and suggestions to this document. + Sherbin, Bob Hinden, Gert Doering, Niall O'Reilly, Mark Townsley and + Jari Arkko have provided input and suggestions to this document. 6. References 6.1. Normative References [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. 6.2. Informative References @@ -223,34 +241,38 @@ [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast Addresses", RFC 4193, October 2005. [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380, February 2006. [RFC4773] Huston, G., "Administration of the IANA Special Purpose IPv6 Address Block", RFC 4773, December 2006. + [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix + for Overlay Routable Cryptographic Hash Identifiers + (ORCHID)", RFC 4843, April 2007. + Author's Address Marc Blanchet Viagenie - 2875 boul. Laurier, suite 1150 - Quebec, QC G1V 2M2 + 2600 boul. Laurier, suite 625 + Quebec, QC G1V 4W5 Canada Email: Marc.Blanchet@viagenie.ca URI: http://www.viagenie.ca Full Copyright Statement - Copyright (C) The IETF Trust (2007). + Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, 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