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
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
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问题并关联网络事件。此信息对实验室环境中的开发人员也很有帮助。本文件通过要求BGP实施在BGP FSM错误通知消息中插入适当的FSM错误子代码来更新[RFC4271]。
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]中所述进行解释。
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
如果BGP演讲者在OpenSent状态的会话上收到意外消息（例如KEEPALIVE/UPDATE/ROUTE-REFRESH消息），则必须向邻居发送带有错误代码的通知消息
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.
有限状态机错误和错误子代码“在OpenSent状态下接收意外消息”。数据字段是一个1-octet的无符号整数，表示意外消息的类型。
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状态下的会话上接收到意外消息（例如，打开/更新/路由-刷新消息），则必须向邻居发送带有错误代码“有限状态机错误”和错误子代码“在OpenConfirm状态下接收意外消息”的通知消息。数据字段是一个1-octet的无符号整数，表示意外消息的类型。
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扬声器在已建立状态的会话上接收到意外消息（例如，打开消息），则必须向邻居发送一条通知消息，错误代码为有限状态机错误，错误子代码为“在已建立状态下接收意外消息”。数据字段是一个1-octet的无符号整数，表示意外消息的类型。
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在已建立状态下接收意外消息
The following individuals contributed to this document:
以下个人对本文件作出了贡献：
Xiaoming Gu EMail: guxiaoming@huawei.com
顾晓明电邮：guxiaoming@huawei.com
Chong Wang EMail: chongwang@huawei.com
王冲电邮：chongwang@huawei.com
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.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[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.，和S.Hares，Ed.，“边境网关协议4（BGP-4）”，RFC 42712006年1月。
[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，“在RFCs中编写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.，和J.Rexford，“BGP安全问题和解决方案调查”，2010年1月。
Authors' Addresses
作者地址
Jie Dong Huawei Technologies Huawei Building, No.156 Beiqing Rd Beijing 100095 China
中国北京市北青路156号华为大厦华东华为技术有限公司100095
EMail: jie.dong@huawei.com
EMail: jie.dong@huawei.com
Mach Chen Huawei Technologies Huawei Building, No.156 Beiqing Rd Beijing 100095 China
中国北京市北青路156号华为大厦Mach Chen华为技术有限公司100095
EMail: mach.chen@huawei.com
EMail: mach.chen@huawei.com
Anantharamu Suryanarayana Cisco Systems USA
美国思科系统公司
EMail: asuryana@cisco.com
EMail: asuryana@cisco.com