Network Working Group M. Blanchet
Request for Comments: 5156 Viagenie
Category: Informational April 2008
Network Working Group M. Blanchet
Request for Comments: 5156 Viagenie
Category: Informational April 2008
Special-Use IPv6 Addresses
特殊用途IPv6地址
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.
本文档是其他RFC中定义的特殊IPv6地址的汇编。它可以用作无效路由前缀的检查表，用于制定路由和IP数据包的过滤策略。它不讨论通过区域互联网登记处分配给运营商和用户的地址。
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
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
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.
本文档是其他RFC中定义的特殊IPv6地址的汇编。它可以用作无效路由前缀的检查表，用于制定路由和IP数据包的过滤策略。它不讨论通过区域互联网登记处分配给运营商和用户的地址。
The document is structured by address types. The document format is similar to [RFC3330].
文档按地址类型进行结构化。文档格式类似于[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.
本文档中列出的地址不得硬编码到实现中。
::1/128 is the loopback address [RFC4291].
：：1/128是环回地址[RFC4291]。
::/128 is the unspecified address [RFC4291].
：：/128是未指定的地址[RFC4291]。
These two addresses should not appear on the public Internet.
这两个地址不应出现在公共互联网上。
::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses within this block should not appear on the public Internet.
：：FFFF:0:0/96是IPv4映射地址[RFC4291]。此块中的地址不应出现在公共Internet上。
::<ipv4-address>/96 are the IPv4-compatible addresses [RFC4291]. These addresses are deprecated and should not appear on the public Internet.
：<ipv4地址>/96是ipv4兼容的地址[RFC4291]。这些地址已弃用，不应出现在公共Internet上。
fe80::/10 are the link-local unicast [RFC4291] addresses. Addresses within this block should not appear on the public Internet.
fe80:：/10是链路本地单播[RFC4291]地址。此块中的地址不应出现在公共Internet上。
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].
fc00:：/7是唯一的本地地址[RFC4193]。默认情况下，此块中的地址不应出现在公共Internet上。[RFC4193]中进一步描述了公布这些地址的程序。
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.
2001:db8:：/32是文档地址[RFC3849]。它们用于文档目的，如用户手册、RFC等。此区块内的地址不应出现在公共互联网上。
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].
2002:：/16是6to4地址[RFC3056]。当站点运行6to4中继或提供6to4传输服务时，可能会公布6to4地址。运行这样的服务[RFC3964]需要特定于6to4[RFC3964]的过滤规则。[RFC3964]第5.3.1节列出了6to4前缀中不允许的IPv4地址。
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.
2001:：/32是Teredo地址[RFC4380]。当站点运行Teredo中继或提供Teredo传输服务时，可能会公布Teredo地址。
5f00::/8 were the addresses of the first instance of the 6bone experimental network [RFC1897].
5f00:：/8是6bone实验网络[RFC1897]的第一个实例的地址。
3ffe::/16 were the addresses of the second instance of the 6bone experimental network [RFC2471].
3ffe:：/16是6bone实验网络[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 these blocks should not appear on the public Internet until they are reallocated.
5f00:：/8和3ffe:：/16均已返回IANA[RFC3701]。与当前未分配的地址空间类似，这些地址将在将来进行分配。这些区块内的地址在重新分配之前不应出现在公共互联网上。
2001:10::/28 are Overlay Routable Cryptographic Hash IDentifiers (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.
2001:10:：/28是覆盖可路由加密哈希标识符（RAYD）地址[RFC4843]。这些地址用作标识符，不可在IP层路由。此块中的地址不应出现在公共Internet上。
::/0 is the default unicast route address.
：：/0是默认的单播路由地址。
An IANA registry (iana-ipv6-special-registry) exists [RFC4773] for Special-Purpose IPv6 address block assignments for experiments and other purposes. Addresses within this registry should be reviewed for Internet routing considerations.
IANA注册表（IANA-ipv6-special-registry）存在[RFC4773]，用于实验和其他用途的专用ipv6地址块分配。应检查此注册表中的地址以了解Internet路由问题。
ff00::/8 are multicast addresses [RFC4291]. They contain a 4-bit scope in the address field where only some values are of global scope [RFC4291]. Only addresses with global scope in this block may appear on the public Internet.
ff00:：/8是多播地址[RFC4291]。它们在地址字段中包含一个4位作用域，其中只有一些值是全局作用域[RFC4291]。公共Internet上只能显示此块中具有全局作用域的地址。
Multicast routes must not appear in unicast routing tables.
多播路由不能出现在单播路由表中。
Filtering the invalid routing prefixes listed in this document should improve the security of networks.
筛选本文档中列出的无效路由前缀可以提高网络的安全性。
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.
为了确保一致性并为社区利益提供交叉参考，IANA在IANA-ipv6-special-registry的标题中插入了以下段落。
"Other special IPv6 addresses requiring specific considerations for global routing are listed in RFC 5156."
“RFC 5156中列出了需要全局路由特定注意事项的其他特殊IPv6地址。”
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.
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 Bond、Peter Sherbin、Bob Hinden、Gert Doering、Niall O'Reilly、Mark Townsley、Jari Arkko、，Iain Calder为本文件提供了意见和建议。
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006.
[RFC4291]Hinden，R.和S.Deering，“IP版本6寻址体系结构”，RFC 42912006年2月。
[RFC1897] Hinden, R. and J. Postel, "IPv6 Testing Address Allocation", RFC 1897, January 1996.
[RFC1897]Hinden，R.和J.Postel，“IPv6测试地址分配”，RFC18971996年1月。
[RFC2471] Hinden, R., Fink, R., and J. Postel, "IPv6 Testing Address Allocation", RFC 2471, December 1998.
[RFC2471]Hinden，R.，Fink，R.，和J.Postel，“IPv6测试地址分配”，RFC 24711998年12月。
[RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains via IPv4 Clouds", RFC 3056, February 2001.
[RFC3056]Carpenter，B.和K.Moore，“通过IPv4云连接IPv6域”，RFC 3056，2001年2月。
[RFC3330] IANA, "Special-Use IPv4 Addresses", RFC 3330, September 2002.
[RFC3330]IANA，“特殊用途IPv4地址”，RFC33302002年9月。
[RFC3701] Fink, R. and R. Hinden, "6bone (IPv6 Testing Address Allocation) Phaseout", RFC 3701, March 2004.
[RFC3701]Fink，R.和R.Hinden，“6bone（IPv6测试地址分配）逐步淘汰”，RFC 37012004年3月。
[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849, July 2004.
[RFC3849]Huston，G.，Lord，A.，和P.Smith，“为文档保留IPv6地址前缀”，RFC 3849，2004年7月。
[RFC3964] Savola, P. and C. Patel, "Security Considerations for 6to4", RFC 3964, December 2004.
[RFC3964]Savola，P.和C.Patel，“6to4的安全考虑”，RFC 3964，2004年12月。
[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast Addresses", RFC 4193, October 2005.
[RFC4193]Hinden，R.和B.Haberman，“唯一本地IPv6单播地址”，RFC 41932005年10月。
[RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380, February 2006.
[RFC4380]Huitema，C.，“Teredo：通过网络地址转换（NAT）通过UDP传输IPv6”，RFC 43802006年2月。
[RFC4773] Huston, G., "Administration of the IANA Special Purpose IPv6 Address Block", RFC 4773, December 2006.
[RFC4773]Huston，G.“IANA专用IPv6地址块的管理”，RFC 4773，2006年12月。
[RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)", RFC 4843, April 2007.
[RFC4843]Nikander，P.，Laganier，J.，和F.Dupont，“覆盖可路由加密哈希标识符（RAYD）的IPv6前缀”，RFC 4843，2007年4月。
Author's Address
作者地址
Marc Blanchet Viagenie 2600 boul. Laurier, suite 625 Quebec, QC G1V 4W1 Canada
Marc Blanchet Viagenie 2600 boul。加拿大魁北克QC G1V 4W1魁北克625室Laurier
EMail: Marc.Blanchet@viagenie.ca
URI: http://www.viagenie.ca
EMail: Marc.Blanchet@viagenie.ca
URI: http://www.viagenie.ca
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（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.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和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.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为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.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.