Subcodes for BGP Finite State Machine Error
RFC 6608
| Document | Type |
RFC - Proposed Standard
(May 2012; No errata)
Updates RFC 4271
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-dong-idr-fsm-subcode | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6608 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Stewart Bryant | ||
| IESG note | Susan Hares is the document shepherd (Susan.Hares@huawei.com or shares@ndzh.com). | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) J. Dong
Request for Comments: 6608 M. Chen
Updates: 4271 Huawei Technologies
Category: Standards Track A. Suryanarayana
ISSN: 2070-1721 Cisco Systems
May 2012
Subcodes for BGP Finite State Machine Error
Abstract
This document defines several subcodes for the 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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 5741.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6608.
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
(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.
Dong, et al. Standards Track [Page 1]
RFC 6608 BGP FSM Error Subcode May 2012
Table of Contents
1. Introduction ....................................................2
2. Requirements Language ...........................................2
3. Definition of Finite State Machine Error Subcodes ...............2
4. Usage of FSM Error Subcodes .....................................2
5. Security Considerations .........................................3
6. IANA Considerations .............................................3
7. Contributors ....................................................4
8. Acknowledgements ................................................4
9. References ......................................................4
9.1. Normative References .......................................4
9.2. Informative References .....................................4
1. Introduction
This document defines several subcodes for the BGP [RFC4271] Finite
State Machine (FSM) 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 that
BGP implementations insert appropriate FSM Error subcodes in
NOTIFICATION messages for BGP FSM errors.
2. 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].
3. Definition of Finite State Machine Error Subcodes
This document defines the following subcodes for the BGP Finite State
Machine Error:
0 - Unspecified Error
1 - Receive Unexpected Message in OpenSent State
2 - Receive Unexpected Message in OpenConfirm State
3 - Receive Unexpected Message in Established State
4. 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
Dong, et al. Standards Track [Page 2]
RFC 6608 BGP FSM Error Subcode May 2012
Finite State Machine Error and the Error Subcode "Receive Unexpected
Message in OpenSent State". The Data field is a 1-octet, unsigned
Show full document text