Network working group J. Dong
Internet Draft M. Chen
Intended status: Standards Track Huawei Technologies
Expires: September 2011 A. Suryanarayana
Juniper Networks
March 14, 2011
Subcodes for BGP Finite State Machine Error
draft-ietf-idr-fsm-subcode-01.txt
Abstract
This document defines several subcodes for BGP Finite State Machine
Error that could provide more information to help network operators
in diagnosing BGP FSM issues and correlating network events.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 14, 2011.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
Dong, et al. Expires September 14, 2011 [Page 1]
Internet-Draft BGP FSM Error Subcode September 2011
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.
Conventions used in this document
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].
Table of Contents
1. Introduction ................................................ 2
2. Definition of Finite State Machine Error Subcodes ........... 2
3. Usage of FSM Error Subcodes ................................. 3
4. Security Considerations ..................................... 3
5. IANA Considerations ......................................... 3
6. Contributors ................................................ 4
7. Acknowledgments ............................................. 4
8. References .................................................. 4
8.1. Normative References ................................... 4
8.2. Informative References ................................. 4
Authors' Addresses ............................................. 5
1. Introduction
This document defines several subcodes for BGP [RFC4271] Finite
State Machine 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.
2. Definition of Finite State Machine Error Subcodes
This document defines following subcodes for BGP Finite State
Machine Error:
0 - Unspecific Error
Dong, et al. Expires September 14, 2011 [Page 2]
Internet-Draft BGP FSM Error Subcode September 2011
1 - Receive Unexpected Message in OpenSent State
2 - Receive Unexpected Message in OpenConfirm State
3 - Receive Unexpected Message in Established State
3. Usage of FSM Error Subcodes
If a BGP speaker receives an unexpected message
(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 which indicates type of the unexpected message.
If a BGP speaker receives an unexpected message (OPEN/UPDATE/ROUTE-
REFRESH message) on a session in OpenConfirm 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
OpenConfirm State". The Data field is a 1-octet unsigned integer
which indicates type of the unexpected message.
If a BGP speaker receives an unexpected message (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 which indicates
type of the unexpected message.
4. Security Considerations
This document does not change the security properties of BGP.
5. IANA Considerations
IANA is requested to make the following allocations from registries
under its control.
This document defines Error Subcodes 0 - 3 for BGP Finite State
Machine Error.
0 - Unspecific Error
1 - Receive Unexpected Message in OpenSent State
2 - Receive Unexpected Message in OpenConfirm State
Dong, et al. Expires September 14, 2011 [Page 3]
Internet-Draft BGP FSM Error Subcode September 2011
3 - Receive Unexpected Message in Established State
6. Contributors
The following individuals contributed to this document:
Xiaoming Gu
EMail: guxiaoming@huawei.com
Chong Wang
EMail: chongwang@huawei.com
7. Acknowledgments
The authors would like to thank John Scudder, Jeffrey Haas, Susan
Hares, Keyur Patel, Enke Chen and Ruediger Volk for their valuable
suggestions and comments to this document.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC4271] Rekhter, Y., Li, T. and Hares, S., "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006.
8.2. Informative References
[RFC4486] Chen, E. and Gillet, V., "Subcodes for BGP Cease
Notification Message", RFC 4486, April 2006.
Dong, et al. Expires September 14, 2011 [Page 4]
Internet-Draft BGP FSM Error Subcode September 2011
Authors' Addresses
Jie Dong
Huawei Technologies Co.,Ltd.
Huawei Building, No.3 Xinxi Rd.,
Hai-Dian District
Beijing, 100085
P.R. China
EMail: jie.dong@huawei.com
Mach(Guoyi) Chen
Huawei Technologies Co.,Ltd.
Huawei Building, No.3 Xinxi Rd.,
Hai-Dian District
Beijing, 100085
P.R. China
EMail: mach.chen@huawei.com
Anantharamu Suryanarayana
Juniper Networks
EMail: anantha@juniper.net
Dong, et al. Expires September 14, 2011 [Page 5]