Internet Engineering Task Force (IETF) J. Mitchell
Request for Comments: 6996 Microsoft Corporation
BCP: 6 July 2013
Updates: 1930
Category: Best Current Practice
ISSN: 2070-1721
Internet Engineering Task Force (IETF) J. Mitchell
Request for Comments: 6996 Microsoft Corporation
BCP: 6 July 2013
Updates: 1930
Category: Best Current Practice
ISSN: 2070-1721
Autonomous System (AS) Reservation for Private Use
自主系统（AS）专用预订
Abstract
摘要
This document describes the reservation of Autonomous System Numbers (ASNs) that are for Private Use only, known as Private Use ASNs, and provides operational guidance on their use. This document enlarges the total space available for Private Use ASNs by documenting the reservation of a second, larger range and updates RFC 1930 by replacing Section 10 of that document.
本文件描述了仅限私人使用的自治系统编号（ASN）的保留，称为私人使用ASN，并提供了有关其使用的操作指南。本文件通过记录第二个更大范围的保留扩大了可供私人使用的ASN的总空间，并通过替换该文件的第10节更新了RFC 1930。
Status of This Memo
关于下段备忘
This memo documents an Internet Best Current Practice.
本备忘录记录了互联网最佳实践。
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). Further information on BCPs is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关BCP的更多信息，请参见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/rfc6996.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6996.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 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许可证中所述的无担保。
The original IANA reservation of Autonomous System Numbers (ASNs) for Private Use was a block of 1023 ASNs. This was also documented by the IETF in Section 10 of [RFC1930]. Since the time that the range was reserved, the Border Gateway Protocol (BGP) [RFC4271] has seen deployment in new application domains, such as data center networks, which require a larger Private Use AS space.
最初IANA为私人使用保留的自治系统编号（ASN）是由1023个ASN组成的区块。IETF在[RFC1930]第10节中也记录了这一点。自保留该范围以来，边界网关协议（BGP）[RFC4271]已部署到新的应用领域，如数据中心网络，这需要更大的专用空间。
Since the introduction of "BGP Support for Four-Octet Autonomous System (AS) Number Space" [RFC6793], the total size of ASN space has increased dramatically. A larger subset of the space is available to network operators to deploy in these Private Use cases. The existing range of Private Use ASNs is widely deployed, and the ability to renumber this resource in existing networks cannot be coordinated given that these ASNs, by definition, are not registered. Therefore, this RFC documents the existing Private Use ASN reservation while also introducing a second, larger range that can also be utilized.
自从引入“四个八位组自治系统（AS）数字空间的BGP支持”[RFC6793]以来，ASN空间的总大小急剧增加。网络运营商可以在这些私有用例中部署更大的空间子集。现有的一系列专用ASN已广泛部署，鉴于这些ASN（根据定义）未注册，因此无法协调在现有网络中重新编号该资源的能力。因此，本RFC记录了现有的专用ASN保留，同时还引入了第二个更大的范围，也可以利用。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
To allow the continued growth of BGP protocol usage in new network applications that utilize Private Use ASNs, two ranges of ASNs are reserved by Section 5 of this document. The first is part of the original 16-bit Autonomous System range previously defined in [RFC1930], and the second is a larger range out of the Four-Octet AS Number Space [RFC6793].
为了使BGP协议在使用专用ASN的新网络应用程序中的使用继续增长，本文件第5节保留了两个ASN范围。第一个是先前在[RFC1930]中定义的原始16位自治系统范围的一部分，第二个是作为数字空间[RFC6793]的四个八位组中更大的范围。
If Private Use ASNs are used and prefixes originate from these ASNs, Private Use ASNs MUST be removed from AS path attributes (including AS4_PATH if utilizing a four-octet AS number space) before being advertised to the global Internet. Operators SHOULD ensure that all External Border Gateway Protocol (EBGP) speakers support the extensions described in [RFC6793] and that implementation-specific features that recognize Private Use ASNs have been updated to recognize both ranges prior to making use of the newer, numerically higher range of Private Use ASNs in the four-octet AS number space. Some existing implementations that remove Private Use ASNs from the AS_PATH are known to not remove Private Use ASNs if the AS_PATH contains a mixture of Private Use and Non-Private Use ASNs. If such
如果使用了专用ASN，且前缀源自这些ASN，则在向全球互联网发布广告之前，必须从AS路径属性中删除专用ASN（如果使用四个八位组作为数字空间，则包括AS4_路径）。运营商应确保所有外部边界网关协议（EBGP）扬声器支持[RFC6793]中所述的扩展，并确保识别专用ASN的实施特定功能已更新，以便在使用较新版本之前识别这两个范围，在四个八位组作为数字空间中，私人使用ASN的数字范围更大。如果AS_路径包含私人使用和非私人使用ASN的混合，则从AS_路径中移除私人使用ASN的一些现有实现不会移除私人使用ASN。如果是这样的话
implementations have not been updated to recognize the new range of ASNs in this document and a mix of old and new range Private Use ASNs exist in the AS4_PATH, these implementations will likely cease to remove any Private Use ASNs from either of the AS path attributes. Normal AS path filtering MAY also be used to prevent prefixes originating from Private Use ASNs from being advertised to the global Internet.
本文档中的实现尚未更新以识别新范围的ASN，并且AS4_路径中存在新旧范围的专用ASN，这些实现可能会停止从任一AS路径属性中删除任何专用ASN。正常AS路径过滤也可用于防止来自专用ASN的前缀被播发到全球互联网。
IANA has reserved, for Private Use, a contiguous block of 1023 Autonomous System numbers from the "16-bit Autonomous System Numbers" registry, namely 64512 - 65534 inclusive.
IANA已从“16位自治系统号”注册表（即64512-65534）中保留1023个自治系统号的连续块供私人使用。
IANA has also reserved, for Private Use, a contiguous block of 94,967,295 Autonomous System numbers from the "32-bit Autonomous System Numbers" registry, namely 4200000000 - 4294967294 inclusive.
IANA还从“32位自治系统号”注册表中保留了一个连续的94967295自治系统号块供私人使用，即4200000000-4294967294（含）。
These reservations have been documented in the IANA "Autonomous System (AS) Numbers" registry [IANA.AS].
这些保留已记录在IANA“自主系统（AS）编号”注册表[IANA.AS]中。
Private Use ASNs do not raise any unique security concerns. Loss of connectivity might result from their inappropriate use, specifically outside of a single organization, since they are not globally unique. This loss of connectivity is limited to the organization using Private Use ASNs inappropriately or without reference to Section 4. General BGP security considerations are discussed in [RFC4271] and [RFC4272]. Identification of the originator of a route with a Private Use ASN in the AS path would have to be done by tracking the route back to the neighboring globally unique AS in the path or by inspecting other attributes.
私用ASN不会引起任何独特的安全问题。由于它们不是全球唯一的，因此它们的不当使用可能会导致连接丢失，特别是在单个组织之外。这种连接损失仅限于不适当或未参考第4节而使用私人ASN的组织。[RFC4271]和[RFC4272]中讨论了一般BGP安全注意事项。在AS路径中具有专用ASN的路由的发起者的识别必须通过将路由跟踪回路径中相邻的全局唯一AS或通过检查其他属性来完成。
[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月。
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4271]Rekhter，Y.，Li，T.，和S.Hares，“边境网关协议4（BGP-4）”，RFC 42712006年1月。
[RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet Autonomous System (AS) Number Space", RFC 6793, December 2012.
[RFC6793]Vohra，Q.和E.Chen，“BGP对四个八位组自治系统（AS）数字空间的支持”，RFC 6793，2012年12月。
[IANA.AS] IANA, "Autonomous System (AS) Numbers", <http://www.iana.org/assignments/as-numbers/>.
[IANA.AS]IANA，“自主系统（AS）编号”<http://www.iana.org/assignments/as-numbers/>.
[RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, selection, and registration of an Autonomous System (AS)", BCP 6, RFC 1930, March 1996.
[RFC1930]霍金森，J.和T.贝茨，“自主系统（AS）的创建、选择和注册指南”，BCP 6，RFC 1930，1996年3月。
[RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", RFC 4272, January 2006.
[RFC4272]Murphy，S.，“BGP安全漏洞分析”，RFC 4272，2006年1月。
The author would like to acknowledge Christopher Morrow, Jason Schiller, and John Scudder for their advice on how to pursue this change. The author would also like to thank Brian Dickson, David Farmer, Jeffrey Haas, Nick Hilliard, Joel Jaeggli, Warren Kumari, and Jeff Wheeler for their comments and suggestions.
作者要感谢Christopher Morrow、Jason Schiller和John Scudder就如何实现这一变化提出的建议。作者还要感谢Brian Dickson、David Farmer、Jeffrey Haas、Nick Hilliard、Joel Jaeggli、Warren Kumari和Jeff Wheeler的评论和建议。
Author's Address
作者地址
Jon Mitchell Microsoft Corporation One Microsoft Way Redmond, WA 98052 USA
Jon Mitchell微软公司美国华盛顿州雷德蒙微软大道一号，邮编：98052
EMail: Jon.Mitchell@microsoft.com
EMail: Jon.Mitchell@microsoft.com