Network Working Group E. Chen
Request for Comments: 4486 Cisco Systems
Category: Standards Track V. Gillet
France Telecom
April 2006
Network Working Group E. Chen
Request for Comments: 4486 Cisco Systems
Category: Standards Track V. Gillet
France Telecom
April 2006
Subcodes for BGP Cease Notification Message
BGP停止通知消息的子代码
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in correlating network events and diagnosing BGP peering issues.
本文档定义了BGP停止通知消息的若干子代码，这些子代码将提供更多信息，以帮助网络运营商关联网络事件和诊断BGP对等问题。
This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in correlating network events and diagnosing BGP peering issues. It also recommends that a BGP speaker implement a backoff mechanism in re-trying a BGP connection after the speaker receives a NOTIFICATION message with certain CEASE subcode.
本文档定义了BGP停止通知消息的若干子代码，这些子代码将提供更多信息，以帮助网络运营商关联网络事件和诊断BGP对等问题。它还建议BGP演讲者在收到带有特定停止子代码的通知消息后，在重新尝试BGP连接时实施退避机制。
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 [RFC-2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC-2119]中的说明进行解释。
The following subcodes are defined for the Cease NOTIFICATION message:
为停止通知消息定义了以下子代码：
Subcode Symbolic Name
子代码符号名
1 Maximum Number of Prefixes Reached 2 Administrative Shutdown 3 Peer De-configured 4 Administrative Reset 5 Connection Rejected 6 Other Configuration Change 7 Connection Collision Resolution 8 Out of Resources
1达到最大前缀数2管理关闭3对等取消配置4管理重置5连接被拒绝6其他配置更改7连接冲突解决8资源不足
If a BGP speaker decides to terminate its peering with a neighbor because the number of address prefixes received from the neighbor exceeds a locally configured upper bound (as described in [BGP-4]), then the speaker MUST send to the neighbor a NOTIFICATION message with the Error Code Cease and the Error Subcode "Maximum Number of Prefixes Reached". The message MAY optionally include the Address Family information [BGP-MP] and the upper bound in the "Data" field, as shown in Figure 1, where the meaning and use of the <AFI, SAFI> tuple is the same as defined in [BGP-MP], Section 7.
如果BGP演讲者决定终止与邻居的对等，因为从邻居接收的地址前缀数量超过了本地配置的上限（如[BGP-4]所述），则演讲者必须向邻居发送通知消息，错误代码停止，错误子代码“已达到最大前缀数量”. 该消息可以选择性地包括地址族信息[BGP-MP]和“数据”字段中的上限，如图1所示，其中<AFI，SAFI>元组的含义和用法与[BGP-MP]第7节中的定义相同。
+-------------------------------+
| AFI (2 octets) |
+-------------------------------+
| SAFI (1 octet) |
+-------------------------------+
| Prefix upper bound (4 octets) |
+-------------------------------+
+-------------------------------+
| AFI (2 octets) |
+-------------------------------+
| SAFI (1 octet) |
+-------------------------------+
| Prefix upper bound (4 octets) |
+-------------------------------+
Figure 1: Optional Data Field
图1：可选数据字段
If a BGP speaker decides to administratively shut down its peering with a neighbor, then the speaker SHOULD send a NOTIFICATION message with the Error Code Cease and the Error Subcode "Administrative Shutdown".
如果BGP演讲者决定以管理方式关闭其与邻居的对等，则演讲者应发送带有错误代码STOP和错误子代码“管理关闭”的通知消息。
If a BGP speaker decides to de-configure a peer, then the speaker SHOULD send a NOTIFICATION message with the Error Code Cease and the Error Subcode "Peer De-configured".
如果BGP演讲者决定取消配置对等方，则演讲者应发送一条带有错误代码STOP和错误子代码“peer de configured”的通知消息。
If a BGP speaker decides to administratively reset the peering with a neighbor, then the speaker SHOULD send a NOTIFICATION message with the Error Code Cease and the Error Subcode "Administrative Reset".
如果BGP演讲者决定以管理方式重置与邻居的对等，则演讲者应发送带有错误代码STOP和错误子代码“管理重置”的通知消息。
If a BGP speaker decides to disallow a BGP connection (e.g., the peer is not configured locally) after the speaker accepts a transport protocol connection, then the BGP speaker SHOULD send a NOTIFICATION message with the Error Code Cease and the Error Subcode "Connection Rejected".
如果BGP演讲者在接受传输协议连接后决定不允许BGP连接（例如，对等方未在本地配置），则BGP演讲者应发送一条通知消息，其中包含错误代码STOP和错误子代码“connection Rejected”。
If a BGP speaker decides to administratively reset the peering with a neighbor due to a configuration change other than the ones described above, then the speaker SHOULD send a NOTIFICATION message with the Error Code Cease and the Error Subcode "Other Configuration Change".
如果BGP演讲者由于上述配置更改以外的配置更改而决定管理性地重置与邻居的对等，则演讲者应发送带有错误代码STOP和错误子代码“其他配置更改”的通知消息。
If a BGP speaker decides to send a NOTIFICATION message with the Error Code Cease as a result of the collision resolution procedure (as described in [BGP-4]), then the subcode SHOULD be set to "Connection Collision Resolution".
如果BGP演讲者决定发送错误代码为STOP的通知消息作为冲突解决程序的结果（如[BGP-4]中所述），则子代码应设置为“连接冲突解决”。
If a BGP speaker runs out of resources (e.g., memory) and decides to reset a session, then the speaker MAY send a NOTIFICATION message with the Error Code Cease and the Error Subcode "Out of Resources".
如果BGP演讲者耗尽资源（例如，内存）并决定重置会话，则演讲者可发送带有错误代码STOP和错误子代码“资源不足”的通知消息。
It is RECOMMENDED that a BGP speaker behave as though the DampPeerOscillations attribute [BGP-4] were true for this peer when re-trying a BGP connection after the speaker receives a Cease NOTIFICATION message with a subcode of "Administrative Shutdown", "Peer De-configured", "Connection Rejected", or "Out of Resources". An implementation SHOULD impose an upper bound on the number of consecutive automatic retries. Once this bound is reached, the implementation would stop re-trying any BGP connections until some administrative intervention, i.e., set the AllowAutomaticStart attribute [BGP-4] to FALSE.
建议BGP演讲者在收到子代码为“管理关闭”、“对等方取消配置”、“连接被拒绝”或“资源不足”的停止通知消息后，重新尝试BGP连接时，其行为应与此对等方的DampPeerOscillations属性[BGP-4]为真一样。实现应该对连续自动重试的次数施加上限。一旦达到该界限，实现将停止重新尝试任何BGP连接，直到一些管理干预，即将AllowAutomaticStart属性[BGP-4]设置为FALSE。
This document defines the subcodes 1 - 8 for the BGP Cease NOTIFICATION message. Future assignments are to be made using either the Standards Action process defined in [RFC-2434], or the Early IANA Allocation process defined in [RFC-4020]. Assignments consist of a name and the value.
本文件定义了BGP停止通知消息的子代码1-8。未来分配将使用[RFC-2434]中定义的标准行动流程或[RFC-4020]中定义的早期IANA分配流程进行。赋值由名称和值组成。
This extension to BGP does not change the underlying security issues inherent in the existing BGP.
BGP的此扩展不会改变现有BGP中固有的基本安全问题。
The authors would like to thank Yakov Rekhter, Pedro Marques, Andrew Lange, and Don Goodspeed for their review and suggestions.
作者要感谢雅科夫·雷克特、佩德罗·马尔克斯、安德鲁·兰格和唐·古德斯皮德的评论和建议。
[BGP-4] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
[BGP-4]Rekhter，Y.，Li，T.，和S.Hares，“边境网关协议4（BGP-4）”，RFC 42712006年1月。
[BGP-MP] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000.
[BGP-MP]Bates，T.，Rekhter，Y.，Chandra，R.，和D.Katz，“BGP-4的多协议扩展”，RFC 28582000年6月。
[RFC-2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC-2434]Narten，T.和H.Alvestrand，“在RFC中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC-2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC-4020] Kompella, K. and A. Zinin, "Early IANA Allocation of Standards Track Code Points", BCP 100, RFC 4020, February 2005.
[RFC-4020]Kompella，K.和A.Zinin，“早期IANA标准轨道代码点分配”，BCP 100，RFC 4020，2005年2月。
Authors' Addresses
作者地址
Enke Chen Cisco Systems, Inc. 170 W. Tasman Dr. San Jose, CA 95134 USA
Enke Chen思科系统有限公司170 W.Tasman Dr.San Jose，CA 95134美国
EMail: enkechen@cisco.com
EMail: enkechen@cisco.com
Vincent Gillet France Telecom Longues Distances 61, rue des Archives 75003 Paris FRANCE
Vincent Gillet法国电信长距离61号，法国巴黎档案街75003号
EMail: vgi@opentransit.net
EMail: vgi@opentransit.net
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。