Internet Engineering Task Force (IETF) J. Arkko
Request for Comments: 5737 Ericsson
Updates: 1166 M. Cotton
Category: Informational L. Vegoda
ISSN: 2070-1721 ICANN
January 2010
Internet Engineering Task Force (IETF) J. Arkko
Request for Comments: 5737 Ericsson
Updates: 1166 M. Cotton
Category: Informational L. Vegoda
ISSN: 2070-1721 ICANN
January 2010
IPv4 Address Blocks Reserved for Documentation
为文档保留的IPv4地址块
Abstract
摘要
Three IPv4 unicast address blocks are reserved for use in examples in specifications and other documents. This document describes the use of these blocks.
保留三个IPv4单播地址块，以便在规范和其他文档的示例中使用。本文档描述了这些块的使用。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5737.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc5737.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
This document describes three IPv4 address blocks that are provided for use in documentation. The use of designated address ranges for documentation and examples reduces the likelihood of conflicts and confusion arising from the use of addresses assigned for some other purpose.
本文档描述了为在文档中使用而提供的三个IPv4地址块。在文档和示例中使用指定的地址范围可以减少因使用为其他目的指定的地址而产生冲突和混淆的可能性。
[RFC1166] reserves the first of the three address blocks, 192.0.2.0/24. The other two address blocks have recently been allocated for this purpose, primarily to ease the writing of examples involving addresses from multiple networks.
[RFC1166]保留三个地址块中的第一个，即192.0.2.0/24。另外两个地址块最近已分配用于此目的，主要是为了便于编写涉及多个网络地址的示例。
Other documentation ranges have been defined in the IETF, including the IPv6 documentation prefix [RFC3849] and example domain names [RFC2606]. Documentation also makes use of the ranges reserved in [RFC1918].
IETF中定义了其他文档范围，包括IPv6文档前缀[RFC3849]和示例域名[RFC2606]。文档还利用了[RFC1918]中保留的范围。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、[RFC2119]中所述进行解释。
The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2), and 203.0.113.0/24 (TEST-NET-3) are provided for use in documentation.
模块192.0.2.0/24（TEST-NET-1）、198.51.100.0/24（TEST-NET-2）和203.0.113.0/24（TEST-NET-3）用于文档中。
Addresses within the TEST-NET-1, TEST-NET-2, and TEST-NET-3 blocks SHOULD NOT appear on the public Internet and are used without any coordination with IANA or an Internet registry [RFC2050]. Network operators SHOULD add these address blocks to the list of non-routeable address spaces, and if packet filters are deployed, then this address block SHOULD be added to packet filters.
TEST-NET-1、TEST-NET-2和TEST-NET-3块中的地址不应出现在公共互联网上，并且在未与IANA或互联网注册中心进行任何协调的情况下使用[RFC2050]。网络运营商应将这些地址块添加到不可路由的地址空间列表中，如果部署了包过滤器，则应将该地址块添加到包过滤器中。
These blocks are not for local use, and the filters may be used in both local and public contexts.
这些块不是本地使用的，并且过滤器可以在本地和公共上下文中使用。
Note that 128.66.0.0/16 has been used for some examples in the past. However, this block did not appear in the list of special prefixes in [RFC3330] or its successors, and the block is therefore not reserved for any special purpose. The block can be used for regular address assignments with caution.
请注意，在过去的一些示例中使用了128.66.0.0/16。但是，该块未出现在[RFC3330]或其后续文件中的特殊前缀列表中，因此该块未保留用于任何特殊目的。该块可用于常规地址分配，但需谨慎。
This document has no security implications.
本文件不涉及安全问题。
IANA has recorded the allocation of the three address blocks in the IPv4 address registry. No end party is to be assigned these addresses.
IANA已在IPv4地址注册表中记录了三个地址块的分配情况。不得向任何终端方分配这些地址。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC1166] Kirkpatrick, S., Stahl, M., and M. Recker, "Internet numbers", RFC 1166, July 1990.
[RFC1166]Kirkpatrick，S.，Stahl，M.和M.Recker，“互联网号码”，RFC1166，1990年7月。
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, February 1996.
[RFC1918]Rekhter，Y.，Moskowitz，R.，Karrenberg，D.，Groot，G.，和E.Lear，“私人互联网地址分配”，BCP 5，RFC 1918，1996年2月。
[RFC2050] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and J. Postel, "INTERNET REGISTRY IP ALLOCATION GUIDELINES", BCP 12, RFC 2050, November 1996.
[RFC2050]哈伯德，K.，科斯特斯，M.，康拉德，D.，卡伦伯格，D.，和J.波斯特尔，“互联网注册IP分配指南”，BCP 12，RFC 2050，1996年11月。
[RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names", BCP 32, RFC 2606, June 1999.
[RFC2606]Eastlake，D.和A.Panitz，“保留顶级DNS名称”，BCP 32，RFC 26061999年6月。
[RFC3330] IANA, "Special-Use IPv4 Addresses", RFC 3330, September 2002.
[RFC3330]IANA，“特殊用途IPv4地址”，RFC33302002年9月。
[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月。
The authors would like to offer a special note of thanks to APNIC, which nominated 198.51.100.0/24 and 203.0.113.0/24 for this purpose. The authors would also like to acknowledge that this document inherits material from [RFC3849].
作者想特别感谢APNIC，它为此提名了198.51.100.0/24和203.0.113.0/24。作者还希望确认，本文件继承了[RFC3849]的材料。
The authors would also like to thank Geoff Huston, Peter Koch, Ulf Olsson, John Klensin, and others for interesting discussions of this topic.
作者还想感谢杰夫·休斯顿、彼得·科赫、乌尔夫·奥尔森、约翰·克莱辛和其他人对此话题进行了有趣的讨论。
Authors' Addresses
作者地址
Jari Arkko Ericsson Jorvas 02420 Finland
雅丽爱立信芬兰公司02420
EMail: jari.arkko@piuha.net
EMail: jari.arkko@piuha.net
Michelle Cotton Internet Corporation for Assigned Names and Numbers 4676 Admiralty Way, Suite 330 Marina del Rey 90292 United States of America
Michelle Cotton互联网公司，美国海军部路4676号，330室，Marina del Rey 90292
Phone: +1-310-823-9358
EMail: michelle.cotton@icann.org
URI: http://www.iana.org/
Phone: +1-310-823-9358
EMail: michelle.cotton@icann.org
URI: http://www.iana.org/
Leo Vegoda Internet Corporation for Assigned Names and Numbers 4676 Admiralty Way, Suite 330 Marina del Rey 90292 United States of America
利奥·维戈达互联网名称和编号分配公司，美国海军部路4676号，330室，马里纳·德雷90292
Phone: +1-310-823-9358
EMail: leo.vegoda@icann.org
URI: http://www.iana.org/
Phone: +1-310-823-9358
EMail: leo.vegoda@icann.org
URI: http://www.iana.org/