Network Working Group M. Blanchet Internet-Draft Viagenie Intended status: Informational March 20, 2007 Expires: September 21, 2007 Special-Use IPv6 Addresses draft-ietf-v6ops-rfc3330-for-ipv6-00.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 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 September 21, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). 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. Blanchet Expires September 21, 2007 [Page 1] Internet-Draft Special-Use IPv6 Addresses March 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Address Types . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Node-scoped Unicast . . . . . . . . . . . . . . . . . . . . 3 2.2. IPv4-Mapped Addresses . . . . . . . . . . . . . . . . . . . 3 2.3. Link-scoped Unicast . . . . . . . . . . . . . . . . . . . . 3 2.4. Site-scoped Unicast . . . . . . . . . . . . . . . . . . . . 3 2.5. Documentation Prefix . . . . . . . . . . . . . . . . . . . 3 2.6. 6to4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.7. Teredo . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.8. 6bone . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.9. Default Route . . . . . . . . . . . . . . . . . . . . . . . 4 2.10. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 6. Informative References . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 7 Blanchet Expires September 21, 2007 [Page 2] Internet-Draft Special-Use IPv6 Addresses March 2007 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. Some tips about filtering are given, but are not mandatory to implement. 2. Address Types 2.1. Node-scoped Unicast ::1/128 is the loopback address [RFC4291]. ::/128 is the unspecified address [RFC4291]. The node-scoped unicast addresses should not be advertised and should be filtered out when received. 2.2. IPv4-Mapped Addresses ::FFFF:0:0/96 is the IPv4-mapped addresses [RFC4291]. IPv4-mapped addresses should not be advertised and should be filtered out when received. 2.3. Link-scoped Unicast fe80::/10 are the link-local unicast[RFC4291] addresses.Link-local addresses should not be advertised and should be filtered out when received. 2.4. Site-scoped Unicast fc00::/7 are the unique-local addresses [RFC4193]. Unique-local addresses should not be adverstied on the public Internet. 2.5. Documentation Prefix The 2001:0db8::/32 are the documentation addresses [RFC3849]. They are used for documentation purposes such as user manuals, RFCs, etc. Documentation addresses should not be advertised and should be filtered out when received. Blanchet Expires September 21, 2007 [Page 3] Internet-Draft Special-Use IPv6 Addresses March 2007 2.6. 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. 2.7. 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.8. 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. These addresses should not be advertised and should be filtered out when received until they are reallocated. 2.9. Default Route ::/0 is the default unicast route address. 2.10. Multicast ff00::/8 are multicast addresses [RFC4291]. They have a 4 bits scope in the address field. Only addresses having the 'E' value in the scope field are of global scope, all other values are local or reserved. Therefore, only ffXe:: routes may be advertised outside a site, where X may be any value. Multicast routes must not appear in unicast routing tables. 3. Security Considerations This document list addresses and guidelines associated with them. The guidelines should improve the security of networks by the filtering of invalid routing prefixes. Blanchet Expires September 21, 2007 [Page 4] Internet-Draft Special-Use IPv6 Addresses March 2007 4. IANA Considerations This document has no actions for IANA. 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 and Alain Durand have provided input and suggestions to this document. 6. Informative References [RFC1897] Hinden, R. and J. Postel, "IPv6 Testing Address Allocation", RFC 1897, January 1996. [RFC2471] Hinden, R., Fink, R., and J. Postel, "IPv6 Testing Address Allocation", RFC 2471, December 1998. [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains via IPv4 Clouds", RFC 3056, February 2001. [RFC3701] Fink, R. and R. Hinden, "6bone (IPv6 Testing Address Allocation) Phaseout", RFC 3701, March 2004. [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849, July 2004. [RFC3964] Savola, P. and C. Patel, "Security Considerations for 6to4", RFC 3964, December 2004. [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast Addresses", RFC 4193, October 2005. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380, February 2006. Blanchet Expires September 21, 2007 [Page 5] Internet-Draft Special-Use IPv6 Addresses March 2007 Author's Address Marc Blanchet Viagenie Email: Marc.Blanchet@viagenie.ca Blanchet Expires September 21, 2007 [Page 6] Internet-Draft Special-Use IPv6 Addresses March 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). 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 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 BCP 78 and BCP 79. 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 http://www.ietf.org/ipr. 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 ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Blanchet Expires September 21, 2007 [Page 7]