draft-ietf-idr-fsm-subcode-02.txt   draft-ietf-idr-fsm-subcode-03.txt 
Network Working Group J. Dong Network Working Group J. Dong
Internet-Draft M. Chen Internet-Draft M. Chen
Intended status: Standards Track Huawei Technologies Updates: 4271 (if approved) Huawei Technologies
Expires: February 12, 2012 A. Suryanarayana Intended status: Standards Track A. Suryanarayana
Cisco Systems Expires: August 17, 2012 Cisco Systems
August 11, 2011 February 14, 2012
Subcodes for BGP Finite State Machine Error Subcodes for BGP Finite State Machine Error
draft-ietf-idr-fsm-subcode-02 draft-ietf-idr-fsm-subcode-03
Abstract Abstract
This document defines several subcodes for BGP Finite State Machine This document defines several subcodes for BGP Finite State Machine
(FSM) Error that could provide more information to help network (FSM) Error that could provide more information to help network
operators in diagnosing BGP FSM issues and correlating network operators in diagnosing BGP FSM issues and correlating network
events. events. This document updates RFC 4271.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 12, 2012. This Internet-Draft will expire on August 17, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 21 skipping to change at page 2, line 21
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definition of Finite State Machine Error Subcodes . . . . . . . 3 2. Definition of Finite State Machine Error Subcodes . . . . . . . 3
3. Usage of FSM Error Subcodes . . . . . . . . . . . . . . . . . . 3 3. Usage of FSM Error Subcodes . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
8. Normative References . . . . . . . . . . . . . . . . . . . . . 4 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
This document defines several subcodes for BGP [RFC4271] Finite State This document defines several subcodes for BGP [RFC4271] Finite State
Machine Error that could provide more information to help network Machine Error that could provide more information to help network
operators in diagnosing BGP FSM issues and correlating network operators in diagnosing BGP FSM issues and correlating network
events. This information is also helpful to developers in lab events. This information is also helpful to developers in lab
situations. 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 2. Definition of Finite State Machine Error Subcodes
This document defines following subcodes for BGP Finite State Machine This document defines following subcodes for BGP Finite State Machine
Error: Error:
0 - Unspecific Error 0 - Unspecific Error
1 - Receive Unexpected Message in OpenSent State 1 - Receive Unexpected Message in OpenSent State
skipping to change at page 4, line 7 skipping to change at page 4, line 7
If a BGP speaker receives an unexpected message (e.g. OPEN 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 on a session in Established state, it MUST send to the neighbor a
NOTIFICATION message with the Error Code Finite State Machine Error NOTIFICATION message with the Error Code Finite State Machine Error
and the Error Subcode "Receive Unexpected Message in Established and the Error Subcode "Receive Unexpected Message in Established
State". The Data field is a 1-octet unsigned integer which indicates State". The Data field is a 1-octet unsigned integer which indicates
type of the unexpected message. type of the unexpected message.
4. Security Considerations 4. Security Considerations
This document does not change the security properties of BGP. 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 5. IANA Considerations
IANA is requested to create the registry "BGP Finite State Machine IANA is requested to create the registry "BGP Finite State Machine
Error Subcodes", within the "BGP Error Subcodes" registry, with Error Subcodes", within the "BGP Error Subcodes" registry, with a
Registration Procedures "Standards Action process or the Early IANA Registration Procedure of "Standards Action" as defined in [RFC5226].
Allocation process". (early allocation of such subcodes is allowed, in accordance with
[RFC4020])
The registry should be populated with the following values: The registry should be populated with the following values:
Value Name Value Name
0 Unspecified Error 0 Unspecified Error
1 Receive Unexpected Message in OpenSent State 1 Receive Unexpected Message in OpenSent State
2 Receive Unexpected Message in OpenConfirm State 2 Receive Unexpected Message in OpenConfirm State
3 Receive Unexpected Message in Established State 3 Receive Unexpected Message in Established State
6. Contributors 6. Contributors
The following individuals contributed to this document: The following individuals contributed to this document:
Xiaoming Gu EMail: guxiaoming@huawei.com Xiaoming Gu EMail: guxiaoming@huawei.com
Chong Wang EMail: chongwang@huawei.com Chong Wang EMail: chongwang@huawei.com
7. Acknowledgements 7. Acknowledgements
The authors would like to thank John Scudder, Jeffrey Haas, Susan The authors would like to thank John Scudder, Jeffrey Haas, Susan
Hares, Keyur Patel, Enke Chen and Ruediger Volk for their valuable Hares, Keyur Patel, Enke Chen, Ruediger Volk and Ran Atkinson for
suggestions and comments to this document. their valuable suggestions and comments to this document.
8. Normative References 8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. 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 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. 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 Authors' Addresses
Jie Dong Jie Dong
Huawei Technologies Huawei Technologies
Huawei Building, No.3 Xinxi Rd Huawei Building, No.156 Beiqing Rd
Beijing 100085 Beijing 100095
China China
Email: jie.dong@huawei.com Email: jie.dong@huawei.com
Mach Chen Mach Chen
Huawei Technologies Huawei Technologies
Huawei Building, No.3 Xinxi Rd Huawei Building, No.156 Beiqing Rd
Beijing 100085 Beijing 100095
China China
Email: mach.chen@huawei.com Email: mach.chen@huawei.com
Anantharamu Suryanarayana Anantharamu Suryanarayana
Cisco Systems Cisco Systems
USA USA
Email: asuryana@cisco.com Email: asuryana@cisco.com
 End of changes. 18 change blocks. 
25 lines changed or deleted 53 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/