RFC 6286 - Autonomous-System-Wide Unique BGP Identifier for BGP-4 中文翻译

原文URL : https://datatracker.ietf.org/doc/html/rfc6286
文档标题 : RFC 6286 - BGP-4 的全自治系统唯一 BGP 标识符
翻译方式 : 自动生成

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。

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 许可中所述的担保。

1. Introduction

1. 导言

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 标识符在整个 AS 范围内唯一。对基本 BGP 规范的这些修订不会引入任何向后兼容性问题。

2. Protocol Revisions

2. 协议修订

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 唯一 BGP 标识符的 BGP 发言者的程序。

2.1. Definition of the BGP Identifier

2.1. BGP 标识符的定义

For a BGP speaker that supports the AS-wide Unique BGP Identifier, the BGP Identifier is specified as the following:

对于支持全 AS 唯一 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 八位、无符号、非零的整数，在 AS 中应该是唯一的。BGP 说话者的 BGP 标识符值在启动时确定，对每个本地接口和每个 BGP 对等节点都一样。

2.2. Open Message Error Handling

2.2. 开放信息错误处理

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 范围唯一 BGP 标识符的 BGP 说话者，与 BGP 标识符有关的 OPEN 消息错误处理修改如下：

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".

如果 OPEN 报文的 BGP Identifier（BGP 标识符）字段为零，或与本地 BGP 说话者的 BGP Identifier（BGP 标识符）相同，且报文来自内部对等体，则错误子代码将被设置为 "Bad BGP Identifier（错误的 BGP 标识符）"。

2.3. Connection Collision Resolution

2.3. 连接碰撞解决

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 唯一 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 标识相同，则保留由 AS 号较大的 BGP 说话者发起的连接。

This extension covers cases in which the 4-octet AS numbers are involved [RFC4893].

该扩展涵盖了涉及 4 八位 AS 号码的情况 [RFC4893]。

3. Remarks

3. 备注

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，以支持 AS 范围内的唯一 BGP 标识符。

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.

支持全 AS 唯一 BGP 标识符的 BGP 说话者不能与其外部邻居共享 BGP 标识符，直到远程 BGP 说话者升级到支持指定版本的软件。

In addition to the OPEN message, the BGP Identifier is currently also used in the following areas:

除 OPEN 消息外，BGP Identifier 目前还用于以下领域：

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 在路由的 AGGREAGTOR 属性中，BGP Identifier（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 Identifier。此外，还处理了来自具有相同 BGP Identifiers 的 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 标识符的当前用法不存在任何向后兼容性问题。

4. Security Considerations

4. 安全考虑因素

This extension to BGP does not introduce new security considerations. BGP security considerations are discussed in [RFC4271].

对 BGP 的这一扩展不会引入新的安全考虑因素。BGP 安全考虑因素在 [RFC4271] 中讨论。

5. Acknowledgments

5. 致谢

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 网络 "相关问题的讨论，正是这些讨论激发了本文档的写作。

6. Normative References

6. 规范性文献

[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.

[RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS Number Space", RFC 4893, May 2007.

Authors' Addresses

作者地址

Enke Chen Cisco Systems, Inc. 170 W. Tasman Dr. San Jose, CA 95134

Enke Chen Cisco Systems, Inc.170 W. Tasman Dr. San Jose, CA 95134

   EMail: [email protected]

Jenny Yuan Cisco Systems, Inc. 170 W. Tasman Dr. San Jose, CA 95134

Jenny Yuan 思科系统公司170 W. Tasman Dr. San Jose, CA 95134

   EMail: [email protected]