Internet DRAFT - draft-ietf-idr-fsm-subcode
draft-ietf-idr-fsm-subcode
Network Working Group J. Dong
Internet-Draft M. Chen
Updates: 4271 (if approved) Huawei Technologies
Intended status: Standards Track A. Suryanarayana
Expires: August 17, 2012 Cisco Systems
February 14, 2012
Subcodes for BGP Finite State Machine Error
draft-ietf-idr-fsm-subcode-03
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. This document updates RFC 4271.
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 August 17, 2012.
Copyright Notice
Copyright (c) 2012 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 August 17, 2012 [Page 1]
Internet-Draft BGP FSM Error Subcode February 2012
(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. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
Dong, et al. Expires August 17, 2012 [Page 2]
Internet-Draft BGP FSM Error Subcode February 2012
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. This document updates [RFC4271] by requiring BGP
implementations to insert appropriate FSM Error subcodes in
NOTIFICATION messages for BGP FSM errors.
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 August 17, 2012 [Page 3]
Internet-Draft BGP FSM Error Subcode February 2012
4. Security Considerations
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.
[BFMR2010]discusses a number of BGP security issues and potential
solutions that might be relevant both to BGP implementers and BGP
operators.
5. IANA Considerations
IANA is requested to create 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])
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, Ruediger Volk and Ran Atkinson for
their valuable suggestions and comments to this document.
8. References
Dong, et al. Expires August 17, 2012 [Page 4]
Internet-Draft BGP FSM Error Subcode February 2012
8.1. Normative References
[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.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "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.
8.2. Informative References
[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
Email: jie.dong@huawei.com
Mach Chen
Huawei Technologies
Huawei Building, No.156 Beiqing Rd
Beijing 100095
China
Email: mach.chen@huawei.com
Dong, et al. Expires August 17, 2012 [Page 5]
Internet-Draft BGP FSM Error Subcode February 2012
Anantharamu Suryanarayana
Cisco Systems
USA
Email: asuryana@cisco.com
Dong, et al. Expires August 17, 2012 [Page 6]
