idnits 2.17.1 draft-dong-idr-fsm-subcode-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 7, 2010) is 5014 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC5226' is defined on line 164, but no explicit reference was found in the text == Unused Reference: 'RFC4486' is defined on line 173, but no explicit reference was found in the text ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network working group J. Dong 2 Internet Draft M. Chen 3 Intended status: Standards Track Huawei Technologies 4 Expires: January 2011 A. Suryanarayana 5 Juniper Networks 7 July 7, 2010 9 Subcodes for BGP Finite State Machine Error 11 draft-dong-idr-fsm-subcode-01.txt 13 Abstract 15 This document defines several subcodes for BGP Finite State Machine 16 Error that could provide more information to help network operators 17 in diagnosing BGP FSM issues and correlating network events. 19 Status of this Memo 21 This Internet-Draft is submitted to IETF in full conformance with 22 the provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six 30 months and may be updated, replaced, or obsoleted by other documents 31 at any time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 This Internet-Draft will expire on January 7, 2011. 42 Copyright Notice 44 Copyright (c) 2010 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with 52 respect to this document. Code Components extracted from this 53 document must include Simplified BSD License text as described in 54 Section 4.e of the Trust Legal Provisions and are provided without 55 warranty as described in the Simplified BSD License. 57 Conventions used in this document 59 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 60 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 61 document are to be interpreted as described in RFC-2119 [RFC2119]. 63 Table of Contents 65 1. Introduction..................................................2 66 2. Definition of Finite State Machine Error Subcodes.............2 67 3. Usage of FSM Error Subcodes...................................3 68 4. Security Considerations.......................................3 69 5. IANA Considerations...........................................3 70 6. Contributors..................................................4 71 7. Acknowledgments...............................................4 72 8. References....................................................4 73 8.1. Normative References.....................................4 74 8.2. Informative References...................................4 75 Authors' Addresses...............................................5 77 1. Introduction 79 This document defines several subcodes for BGP [RFC4271] Finite 80 State Machine Error that could provide more information to help 81 network operators in diagnosing BGP FSM issues and correlating 82 network events. This information is also helpful to developers in 83 lab situations. 85 2. Definition of Finite State Machine Error Subcodes 87 This document defines following subcodes for BGP Finite State 88 Machine Error: 90 0 - Unspecific Error 91 1 - Receive Unexpected Message in OpenSent State 93 2 - Receive Unexpected Message in OpenConfirm State 95 3 - Receive Unexpected Message in Established State 97 3. Usage of FSM Error Subcodes 99 If a BGP speaker receives an unexpected message 100 (KEEPALIVE/UPDATE/ROUTE-REFRESH message) on a session in OpenSent 101 state, it MUST send to the neighbor a Notification message with the 102 Error Code Finite State Machine Error and the Error Subcode "Receive 103 Unexpected Message in OpenSent State". The Data field is a 1-octet 104 unsigned integer which indicates type of the unexpected message. 106 If a BGP speaker receives an unexpected message (OPEN/UPDATE/ROUTE- 107 REFRESH message) on a session in OpenConfirm state, it MUST send to 108 the neighbor a Notification message with the Error Code Finite State 109 Machine Error and the Error Subcode "Receive Unexpected Message in 110 OpenConfirm State". The Data field is a 1-octet unsigned integer 111 which indicates type of the unexpected message. 113 If a BGP speaker receives an unexpected message (OPEN message) on a 114 session in Established state, it MUST send to the neighbor a 115 Notification message with the Error Code Finite State Machine Error 116 and the Error Subcode "Receive Unexpected Message in Established 117 State". The Data field is a 1-octet unsigned integer which indicates 118 type of the unexpected message. 120 4. Security Considerations 122 This document does not change the security properties of BGP. 124 5. IANA Considerations 126 IANA is requested to make the following allocations from registries 127 under its control. 129 This document defines Error Subcodes 0 - 3 for BGP Finite State 130 Machine Error. 132 0 - Unspecific Error 134 1 - Receive Unexpected Message in OpenSent State 136 2 - Receive Unexpected Message in OpenConfirm State 137 3 - Receive Unexpected Message in Established State 139 6. Contributors 141 The following individuals contributed to this document: 143 Xiaoming Gu 145 EMail: guxiaoming@huawei.com 147 Chong Wang 149 EMail: chongwang@huawei.com 151 7. Acknowledgments 153 The authors would like to thank John Scudder, Jeffrey Haas, Susan 154 Hares, Keyur Patel, Enke Chen and Ruediger Volk for their valuable 155 suggestions and comments to this document. 157 8. References 159 8.1. Normative References 161 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 162 Requirement Levels", BCP 14, RFC 2119, March 1997. 164 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 165 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 166 May 2008. 168 [RFC4271] Rekhter, Y., Li, T. and Hares, S., "A Border Gateway 169 Protocol 4 (BGP-4)", RFC 4271, January 2006. 171 8.2. Informative References 173 [RFC4486] Chen, E. and Gillet, V., "Subcodes for BGP Cease 174 Notification Message", RFC 4486, April 2006. 176 Authors' Addresses 178 Jie Dong 179 Huawei Technologies Co.,Ltd. 180 Huawei Building, No.3 Xinxi Rd., 181 Hai-Dian District 182 Beijing, 100085 183 P.R. China 185 EMail: dongjie_dj@huawei.com 187 Mach(Guoyi) Chen 188 Huawei Technologies Co.,Ltd. 189 Huawei Building, No.3 Xinxi Rd., 190 Hai-Dian District 191 Beijing, 100085 192 P.R. China 194 EMail: mach@huawei.com 196 Anantharamu Suryanarayana 197 Juniper Networks 199 EMail: anantha@juniper.net