rfc-6608

Subcodes for BGP Finite State Machine Error

J. Dong, M. Chen, A. Suryanarayana
date2012-05 streamIETF areartg wgidr statusPROPOSED STANDARD pages5 canonicalhttps://www.rfc-editor.org/rfc/rfc6608 doi10.17487/RFC6608
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. [STANDARDS-TRACK]

updates

Extracted elements (7)

design-rationale §1

More specific FSM error subcodes were introduced to provide additional diagnostic information to network operators and developers when BGP FSM issues occur, enabling better correlation of network events beyond what the generic FSM Error code alone could convey.

bgp, routing

normative-requirement §4 MUST

If a BGP speaker receives an unexpected message (e.g., OPEN) in Established state, it MUST send a NOTIFICATION with Error Code Finite State Machine Error and subcode 'Receive Unexpected Message in Established State'. The Data field is a 1-octet unsigned integer indicating the type of the unexpected message.

bgp, routing

protocol-element §3

RFC 6608 defines four 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), and 3 (Receive Unexpected Message in Established State).

bgp, routing

registry §6

IANA created the 'BGP Finite State Machine Error Subcodes' registry within the 'BGP Error Subcodes' registry, with Registration Procedure 'Standards Action'. Initial values are: 0 (Unspecified Error), 1 (Receive Unexpected Message in OpenSent State), 2 (Receive Unexpected Message in OpenConfirm State), 3 (Receive Unexpected Message in Established State).

bgp, routing, registry

security-consideration §5

Specification, implementation, and deployment of BGP FSM Error subcodes could make BGP implementation fingerprinting easier and more accurate, since different implementations may send distinct subcodes. Operators should consider this as an operational security concern when making BGP deployment decisions.

bgp, routing, security

state-machine §3

BGP FSM error subcodes map to three session states where unexpected messages may be received: OpenSent (subcode 1), OpenConfirm (subcode 2), and Established (subcode 3). Receipt of an unexpected message in any of these states triggers a NOTIFICATION and session teardown.

bgp, routing

wire-format §4

The Data field in NOTIFICATION messages for FSM Error subcodes is a 1-octet unsigned integer that encodes the BGP message type of the unexpected message that triggered the error.

bgp, routing