Internet Engineering Task Force (IETF) E. Chen
Request for Comments: 6286 J. Yuan
Updates: 4271 Cisco Systems
Category: Standards Track June 2011
ISSN: 2070-1721
Internet Engineering Task Force (IETF) E. Chen
Request for Comments: 6286 J. Yuan
Updates: 4271 Cisco Systems
Category: Standards Track June 2011
ISSN: 2070-1721
Autonomous-System-Wide Unique BGP Identifier for BGP-4
BGP-4的自治系统范围唯一BGP标识符
Abstract
摘要
To accommodate situations where the current requirements for the BGP Identifier are not met, this document relaxes the definition of the BGP Identifier to be a 4-octet, unsigned, non-zero integer and relaxes the "uniqueness" requirement so that only Autonomous-System-wide (AS-wide) uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any backward compatibility issues. This document updates RFC 4271.
为适应当前BGP标识符要求未得到满足的情况，本文件将BGP标识符的定义放宽为4个八位组、无符号、非零整数，并放宽了“唯一性”要求，以便只需要BGP标识符的自治系统范围（AS-wide）唯一性。对基本BGP规范的这些修订不会引入任何向后兼容性问题。本文档更新了RFC 4271。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
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 Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（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/rfc6286.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6286.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 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许可证中所述的无担保。
Currently, the BGP Identifier of a BGP speaker is specified as a valid IPv4 host address assigned to the BGP speaker [RFC4271]. In addition, the deployed BGP code requires that two BGP speakers be of distinct BGP Identifiers in order to establish a BGP connection.
目前，BGP扬声器的BGP标识符被指定为分配给BGP扬声器的有效IPv4主机地址[RFC4271]。此外，部署的BGP代码要求两个BGP扬声器具有不同的BGP标识符，以便建立BGP连接。
To accommodate situations where the current requirements for the BGP Identifier are not met (such as in the case of an IPv6-only network), this document relaxes the definition of the BGP Identifier to be a 4-octet, unsigned, non-zero integer and relaxes the "uniqueness" requirement so that only AS-wide uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any backward compatibility issues.
为适应当前BGP标识符要求未得到满足的情况（例如在仅限IPv6的网络中），本文档将BGP标识符的定义放宽为4个八位组、无符号、非零整数，并放宽了“唯一性”这样就只需要BGP标识符的广泛唯一性。对基本BGP规范的这些修订不会引入任何向后兼容性问题。
The revisions to the base BGP specification [RFC4271] include the definition of the BGP Identifier and procedures for a BGP speaker that supports the AS-wide Unique BGP Identifier.
对基本BGP规范[RFC4271]的修订包括BGP标识符的定义以及支持AS-wide-Unique BGP标识符的BGP扬声器的程序。
For a BGP speaker that supports the AS-wide Unique BGP Identifier, the BGP Identifier is specified as the following:
对于支持AS-wide唯一BGP标识符的BGP扬声器，BGP标识符指定如下：
The BGP Identifier is a 4-octet, unsigned, non-zero integer that should be unique within an AS. The value of the BGP Identifier for a BGP speaker is determined on startup and is the same for every local interface and every BGP peer.
BGP标识符是一个4-octet、无符号、非零整数，在AS中应该是唯一的。BGP扬声器的BGP标识符的值在启动时确定，并且对于每个本地接口和每个BGP对等方都是相同的。
For a BGP speaker that supports the AS-wide Unique BGP Identifier, the OPEN message error handling related to the BGP Identifier is modified as follows:
对于支持AS-wide唯一BGP标识符的BGP扬声器，与BGP标识符相关的打开消息错误处理修改如下：
If the BGP Identifier field of the OPEN message is zero, or if it is the same as the BGP Identifier of the local BGP speaker and the message is from an internal peer, then the Error Subcode is set to "Bad BGP Identifier".
如果打开消息的BGP标识符字段为零，或者如果它与本地BGP扬声器的BGP标识符相同且消息来自内部对等方，则错误子代码设置为“坏BGP标识符”。
For a BGP speaker that supports the AS-wide Unique BGP Identifier, the procedures for connection collision resolution are extended as follows to deal with the case in which the two BGP speakers share the same BGP Identifier (thus, it is only applicable to an external peer):
对于支持AS-wide唯一BGP标识符的BGP扬声器，连接冲突解决程序扩展如下，以处理两个BGP扬声器共享相同BGP标识符的情况（因此，它仅适用于外部对等方）：
If the BGP Identifiers of the peers involved in the connection collision are identical, then the connection initiated by the BGP speaker with the larger AS number is preserved.
如果参与连接冲突的对等方的BGP标识符相同，则保留由BGP说话者以较大AS号启动的连接。
This extension covers cases in which the 4-octet AS numbers are involved [RFC4893].
此扩展包括涉及4-八位组AS数字的情况[RFC4893]。
It is noted that a BGP Identifier allocated based on [RFC4271] fits the revised definition.
需要注意的是，基于[RFC4271]分配的BGP标识符符合修订后的定义。
In case of BGP Confederation, the whole confederation is considered as one AS for the purpose of supporting the AS-wide Unique BGP Identifier.
在BGP联盟的情况下，为了支持as广域唯一BGP标识符，整个联盟被视为一个as。
A BGP speaker that supports the AS-wide Unique BGP Identifier cannot share a BGP Identifier with its external neighbor until the remote BGP speaker is upgraded with software that supports the specified revisions.
在使用支持指定版本的软件升级远程BGP扬声器之前，支持AS-wide唯一BGP标识符的BGP扬声器无法与其外部邻居共享BGP标识符。
In addition to the OPEN message, the BGP Identifier is currently also used in the following areas:
除了开放消息外，BGP标识符目前还用于以下领域：
o In the AGGREAGTOR attribute of a route where the combination of a BGP Identifier and an AS number uniquely identifies the BGP speaker that performs the route aggregation.
o 在路由的聚合器属性中，BGP标识符和AS编号的组合唯一地标识执行路由聚合的BGP说话人。
o In the Route Reflection within an AS, where only the BGP Identifier of an internal neighbor may be propagated in the route reflection related attributes.
o 在AS内的路由反射中，只有内部邻居的BGP标识符可以在路由反射相关属性中传播。
o In the route selection, where the BGP Identifier is not used in comparing a route from an internal neighbor and a route from an external neighbor. In addition, routes from BGP speakers with identical BGP Identifiers have been dealt with (e.g., parallel BGP sessions between two BGP speakers).
o 在路由选择中，BGP标识符不用于比较来自内部邻居的路由和来自外部邻居的路由。此外，还处理了来自具有相同BGP标识符的BGP扬声器的路由（例如，两个BGP扬声器之间的并行BGP会话）。
Therefore, it is concluded that the revisions specified in this document do not introduce any backward compatibility issues with the current usage of the BGP Identifier.
因此，可以得出结论，本文件中规定的修订不会对BGP标识符的当前使用引入任何向后兼容性问题。
This extension to BGP does not introduce new security considerations. BGP security considerations are discussed in [RFC4271].
BGP的此扩展没有引入新的安全注意事项。[RFC4271]中讨论了BGP安全注意事项。
The authors would like to thank members of the IDR Working Group for discussions on the "IPv6-only Network" related issues that inspired this document.
作者要感谢IDR工作组成员就“仅限IPv6网络”相关问题进行的讨论，这些问题激发了本文档的灵感。
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4271]Rekhter，Y.，Ed.，Li，T.，Ed.，和S.Hares，Ed.，“边境网关协议4（BGP-4）”，RFC 42712006年1月。
[RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS Number Space", RFC 4893, May 2007.
[RFC4893]Vohra，Q.和E.Chen，“BGP支持四个八位组作为数字空间”，RFC 4893，2007年5月。
Authors' Addresses
作者地址
Enke Chen Cisco Systems, Inc. 170 W. Tasman Dr. San Jose, CA 95134
Enke Chen思科系统公司170 W.Tasman Dr.San Jose，CA 95134
EMail: enkechen@cisco.com
EMail: enkechen@cisco.com
Jenny Yuan Cisco Systems, Inc. 170 W. Tasman Dr. San Jose, CA 95134
詹妮·袁思科系统有限公司170 W.塔斯曼加利福尼亚州圣何塞博士95134
EMail: jenny@cisco.com
EMail: jenny@cisco.com