[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-dong-idr-fsm-subcode) 00 01 02 03 RFC 6608

Network Working Group                                            J. Dong
Internet-Draft                                                   M. Chen
Intended status: Standards Track                     Huawei Technologies
Expires: February 12, 2012                              A. Suryanarayana
                                                           Cisco Systems
                                                         August 11, 2011


              Subcodes for BGP Finite State Machine Error
                     draft-ietf-idr-fsm-subcode-02

Abstract

   This document defines several subcodes for BGP Finite State Machine
   (FSM) Error that could provide more information to help network
   operators in diagnosing BGP FSM issues and correlating network
   events.

Requirements Language

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

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

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

   This Internet-Draft will expire on February 12, 2012.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents



Dong, et al.            Expires February 12, 2012               [Page 1]

Internet-Draft            BGP FSM Error Subcode              August 2011


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


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Definition of Finite State Machine Error Subcodes . . . . . . . 3
   3.  Usage of FSM Error Subcodes . . . . . . . . . . . . . . . . . . 3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . 4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 4































Dong, et al.            Expires February 12, 2012               [Page 2]

Internet-Draft            BGP FSM Error Subcode              August 2011


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

   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 (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 which indicates type of the unexpected message.

   If a BGP speaker receives an unexpected message (e.g.  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 (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 which indicates
   type of the unexpected message.






Dong, et al.            Expires February 12, 2012               [Page 3]

Internet-Draft            BGP FSM Error Subcode              August 2011


4.  Security Considerations

   This document does not change the security properties of BGP.


5.  IANA Considerations

   IANA is requested to create the registry "BGP Finite State Machine
   Error Subcodes", within the "BGP Error Subcodes" registry, with
   Registration Procedures "Standards Action process or the Early IANA
   Allocation process".

   The registry should be 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


6.  Contributors

   The following individuals contributed to this document:

   Xiaoming Gu    EMail: guxiaoming@huawei.com

   Chong Wang     EMail: chongwang@huawei.com


7.  Acknowledgements

   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.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

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







Dong, et al.            Expires February 12, 2012               [Page 4]

Internet-Draft            BGP FSM Error Subcode              August 2011


Authors' Addresses

   Jie Dong
   Huawei Technologies
   Huawei Building, No.3 Xinxi Rd
   Beijing  100085
   China

   Email: jie.dong@huawei.com


   Mach Chen
   Huawei Technologies
   Huawei Building, No.3 Xinxi Rd
   Beijing  100085
   China

   Email: mach.chen@huawei.com


   Anantharamu Suryanarayana
   Cisco Systems
   USA

   Email: asuryana@cisco.com


























Dong, et al.            Expires February 12, 2012               [Page 5]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/