Internet Engineering Task Force (IETF) J. Dong
Request for Comments: 6608 M. Chen
Updates: 4271 Huawei Technologies
Category: Standards Track A. Suryanarayana
ISSN: 2070-1721 Cisco Systems
May 2012
Subcodes for BGP Finite State Machine Error
BGP 有限状态机错误子代码
Abstract
摘要
This document defines several subcodes for the BGP Finite State Machine (FSM) Error that could provide more information to help network operators in diagnosing BGP FSM issues and correlating network events. This document updates RFC 4271.
本文档定义了 BGP 有限状态机 (FSM) 错误的几个子代码，可提供更多信息，帮助网络操作员诊断 BGP FSM 问题和关联网络事件。本文件更新了 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/rfc6608.
有关本文件的当前状态、任何勘误以及如何提供反馈的信息，请访问 http://www.rfc-editor.org/info/rfc6608。
Copyright Notice
版权声明
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有 (c) 2012 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 许可中所述的担保。
Table of Contents
目录
1. Introduction ....................................................2
2. Requirements Language ...........................................2
3. Definition of Finite State Machine Error Subcodes ...............2
4. Usage of FSM Error Subcodes .....................................2
5. Security Considerations .........................................3
6. IANA Considerations .............................................3
7. Contributors ....................................................4
8. Acknowledgements ................................................4
9. References ......................................................4
9.1. Normative References .......................................4
9.2. Informative References .....................................4
This document defines several subcodes for the BGP [RFC4271] Finite State Machine (FSM) Error that could provide more information to help network operators in diagnosing BGP FSM issues and correlating network events. This information is also helpful to developers in lab situations. This document updates [RFC4271] by requiring that BGP implementations insert appropriate FSM Error subcodes in NOTIFICATION messages for BGP FSM errors.
本文档定义了 BGP [RFC4271] 有限状态机 (FSM) 错误的几个子代码，可提供更多信息，帮助网络操作员诊断 BGP FSM 问题和关联网络事件。这些信息也有助于开发人员在实验室环境中使用。本文档更新了 [RFC4271]，要求 BGP 实现在 BGP FSM 错误的通知消息中插入适当的 FSM 错误子代码。
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].
本文档中的关键词 "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 以及 "OPTIONAL" 应按照RFC 2119 [RFC2119]中的描述进行解释。
This document defines the following subcodes for the BGP Finite State Machine Error:
本文档为 BGP 有限状态机错误定义了以下子代码：
0 - Unspecified Error
0 - 未指定错误
1 - Receive Unexpected Message in OpenSent State
1 - 在 OpenSent 状态下接收意外信息
2 - Receive Unexpected Message in OpenConfirm State
2 - 在 OpenConfirm 状态下收到意外信息
3 - Receive Unexpected Message in Established State
3 - 在已建立状态下接收意外信息
If a BGP speaker receives an unexpected message (e.g., KEEPALIVE/ UPDATE/ROUTE-REFRESH message) on a session in OpenSent state, it MUST send to the neighbor a NOTIFICATION message with the Error Code Finite State Machine Error and the Error Subcode "Receive Unexpected Message in OpenSent State". The Data field is a 1-octet, unsigned integer that indicates the type of the unexpected message.
如果 BGP 发言者在处于 OpenSent 状态的会话上接收到意外消息（如 KEEPALIVE/ UPDATE/ROUTE-REFRESH 消息），它必须向邻居发送一条带有错误代码 "有限状态机错误"（Finite State Machine Error）和错误子代码 "在 OpenSent 状态下接收意外消息"（Receive Unexpected Message in OpenSent State）的通知消息。数据字段是一个 1 八位无符号整数，表示意外报文的类型。
If a BGP speaker receives an unexpected message (e.g., OPEN/UPDATE/ ROUTE-REFRESH message) on a session in OpenConfirm state, it MUST send a NOTIFICATION message with the Error Code Finite State Machine Error and the Error Subcode "Receive Unexpected Message in OpenConfirm State" to the neighbor. The Data field is a 1-octet, unsigned integer that indicates the type of the unexpected message.
如果 BGP 发言者在处于 OpenConfirm 状态的会话上接收到意外消息（如 OPEN/UPDATE/ ROUTE-REFRESH 消息），它必须向邻居发送一条带有错误代码 "Finite State Machine Error（有限状态机错误）"和错误子代码 "Receive Unexpected Message in OpenConfirm State（在 OpenConfirm 状态下接收意外消息）"的通知消息。数据字段是一个 1 八位无符号整数，表示意外消息的类型。
If a BGP speaker receives an unexpected message (e.g., OPEN message) on a session in Established State, it MUST send to the neighbor a NOTIFICATION message with the Error Code Finite State Machine Error and the Error Subcode "Receive Unexpected Message in Established State". The Data field is a 1-octet, unsigned integer that indicates the type of the unexpected message.
如果 BGP 发言者在 "已建立状态"（Established State）会话中收到意外消息（如 OPEN 消息），它必须向邻居发送一条带有 "错误代码有限状态机错误"（Error Code Finite State Machine Error）和 "错误子代码"（Error Subcode "Receive Unexpected Message in Established State"）的通知消息。数据字段是一个 1 八位无符号整数，表示意外报文的类型。
Specification, implementation, and deployment of the proposed BGP FSM Error subcodes could make BGP implementation fingerprinting easier and probably more accurate. Operators using BGP need to consider this as an operational security consideration of their BGP deployment decisions.
建议的 BGP FSM 错误子代码的规范、实施和部署可使 BGP 实施指纹识别变得更容易，也可能更准确。使用 BGP 的运营商需要将此作为其 BGP 部署决策的操作安全考虑因素。
[BFMR2010] discusses a number of BGP security issues and potential solutions that might be relevant both to BGP implementers and BGP operators.
[BFMR2010]讨论了一些 BGP 安全问题以及可能与 BGP 实施者和 BGP 运营者相关的潜在解决方案。
IANA has created the registry "BGP Finite State Machine Error Subcodes", within the "BGP Error Subcodes" registry, with a Registration Procedure of "Standards Action" as defined in [RFC5226] (early allocation of such subcodes is allowed, in accordance with [RFC4020]).
IANA 在 "BGP 错误子代码 "注册表中创建了 "BGP 有限状态机错误子代码 "注册表，注册程序为 [RFC5226] 中定义的 "标准行动"（根据 [RFC4020]，允许提前分配此类子代码）。
The registry has been populated with the following values:
注册表已填入以下值：
Value Name 0 Unspecified Error 1 Receive Unexpected Message in OpenSent State 2 Receive Unexpected Message in OpenConfirm State 3 Receive Unexpected Message in Established State
值 名称 0 未指定错误 1 在 OpenSent 状态下接收意外信息 2 在 OpenConfirm 状态下接收意外信息 3 在 Established 状态下接收意外信息
The following individuals contributed to this document:
以下人员为本文件的撰写做出了贡献：
Xiaoming Gu EMail: [email protected]
Xiaoming Gu EMail: [email protected]
Chong Wang EMail: [email protected]
Chong Wang EMail: [email protected]
The authors would like to thank John Scudder, Jeffrey Haas, Susan Hares, Keyur Patel, Enke Chen, Ruediger Volk, and Ran Atkinson for their valuable suggestions and comments to this document.
作者感谢 John Scudder、Jeffrey Haas、Susan Hares、Keyur Patel、Enke Chen、Ruediger Volk 和 Ran Atkinson 对本文档提出的宝贵建议和意见。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4020] Kompella, K. and A. Zinin, "Early IANA Allocation of Standards Track Code Points", BCP 100, RFC 4020, February 2005.
[RFC4020] Kompella, K. 和 A. Zinin，"标准轨道代码点的早期 IANA 分配"，BCP 100，RFC 4020，2005 年 2 月。
[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., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226] Narten, T. 和 H. Alvestrand，"RFC 中 IANA 考虑部分的编写指南"，BCP 26，RFC 5226，2008 年 5 月。
[BFMR2010] Butler, K., Farley, T., Mcdaniel, P., and J. Rexford, "A Survey of BGP Security Issues and Solutions", January 2010.
[BFMR2010] Butler, K., Farley, T., Mcdaniel, P., and J. Rexford, "A Survey of BGP Security Issues and Solutions", January 2010.
Authors' Addresses
作者地址
Jie Dong Huawei Technologies Huawei Building, No.156 Beiqing Rd Beijing 100095 China
Jie Dong Huawei Technologies Huawei Building, No.156 Beiqing Rd Beijing 100095 China
EMail: [email protected]
Mach Chen Huawei Technologies Huawei Building, No.156 Beiqing Rd Beijing 100095 China
Mach Chen 华为技术有限公司 北京北清路 156 号华为大厦 100095 中国
EMail: [email protected]
Anantharamu Suryanarayana Cisco Systems USA
Anantharamu Suryanarayana 美国思科系统公司
EMail: [email protected]