]> IANA Registrations for the BGP Finite State Machine (FSM) HPE
jeffrey.haas@hpe.com
Hickory Hill Consulting
7453 Hickory Hill Saline MI 48176 USA +1-734-604-0332 shares@ndzh.com
Arrcus
2077 Gateway Place Suite #400 San Jose CA 95119 United States of America keyur@arrcus.com
Routing IDR BGP Border Gateway Protocol FSM Finite State Machine The Border Gateway Protocol, version 4 (BGP-4) finite state machine (FSM) is defined in RFC 4271. Over the years, various extensions to BGP have been authored that update the protocol's FSM. Some elements of the FSM are enumerated. Those elements are referred to across BGP extensions in their respective state machine changes, and may also be used for management purposes in things such as YANG (RFC 7950). To provide consistent naming and enumeration of these FSM elements, this document requests IANA to create and maintain registries for elements in the BGP FSM.
Introduction defines BGP's finite state machine (FSM). Some elements of the FSM are enumerated. These include:
  • Session attributes (variables), which may be:
    • Mandatory and MUST be supported by all BGP-4 implementations on all BGP connections.
    • Optional and MAY be supported, either per connection or per local system.
  • Events, which may be:
    • Administrative events.
    • Timer events.
    • TCP connection-based events.
    • BGP message-based events.
While the core FSM is defined in , extensions specified in other BGP documents may update FSM procedures. Consistent enumeration and naming of these FSM elements is necessary for procedural clarity. Additionally, management mechanisms such as YANG modules may expose BGP protocol state covered by these elements. This document requests IANA to create and maintain appropriate registries for these FSM elements.
Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.
IANA Considerations
Border Gateway Protocol (BGP-4) FSM Elements Registry IANA is requested to create a new registry, titled, "BGP-4 Finite State Machine (FSM) Elements". This is a new registry grouping distinct from the existing Border Gateway Protocol (BGP) Parameters registry group. The registration policy for the contents of this registry and its sub-registries shall be "IETF Review with Designated Experts". The designated experts for these registries are the IDR WG chairs. The "Border Gateway Protocol (BGP-4) Finite State Machine (FSM) Elements" registry will contain the following sub-registries:
Border Gateway Protocol (BGP-4) FSM Session Attribute Sub-Registries The Border Gateway Protocol (BGP-4) FSM Session Attribute Sub-Registries will consist of entries with the following fields:
  • Value (a 16-bit unsigned integer)
  • Name
  • Reference
Border Gateway Protocol (BGP-4) FSM Mandatory Session Attributes
Value Name Reference
0 Reserved This document
1 State
2 ConnectRetryCounter
3 ConnectRetryTimer
4 ConnectRetryTime
5 HoldTimer
6 HoldTime
7 KeepaliveTimer
8 KeepaliveTime
Border Gateway Protocol (BGP-4) FSM Optional Session Attributes
Value (a 16-bit unsigned integer) Name Reference
0 Reserved This document.
1 AcceptConnectionsUnconfiguredPeers
2 AllowAutomaticStart
3 AllowAutomaticStop
4 CollisionDetectEstablishedState
5 DampPeerOscillations
6 DelayOpen
7 DelayOpenTime
8 DelayOpenTimer
9 IdleHoldTime
10 IdleHoldTimer
11 PassiveTcpEstablishment
12 SendNOTIFICATIONwithoutOPEN
13 TrackTcpState
14 SendHoldTimer
15 SendHoldTime
16 BfdEnabled
17 BfdStrictEnabled
18 BfdHoldTime
19 BfdHoldTimer
20 BfdStrictNegotiated
Border Gateway Protocol (BGP-4) FSM Events Sub-Registry The Border Gateway Protocol (BGP-4) FSM Events Sub-Registries will consist of entries with the following fields:
  • Value
  • Name
  • Event Type
  • Reference
Border Gateway Protocol (BGP-4) FSM Administrative Events
Value Name Event Type Reference
0 Reserved - This document.
1 ManualStart Administrative
2 ManualStop Administrative
3 AutomaticStart Administrative
4 ManualStart with PassiveTcpEstablishment Administrative
5 AutomaticStart with PassiveTcpEstablishment Administrative
6 AutomaticStart with DampPeerOscillations Administrative
7 AutomaticStart with DampPeerOscillations and PassiveTcpEstablishment Administrative
8 AutomaticStop Administrative
9 ConnectRetryTimer Expires Timer
10 HoldTimer Expires Timer
11 KeepaliveTimer Expires Timer
12 DelayOpenTimer Expires Timer
13 IdleHoldTimer Expires Timer
14 TcpConnection Valid TCP Connection
15 Tcp CR Invalid TCP Connection
16 Tcp CR Acked TCP Connection
17 TcpConnectionConfirmed TCP Connection
18 TcpConnectionFails TCP Connection
19 BGPOpen BGP Message
20 BGPOpen with DelayOpenTimer running BGP Message
21 BGPHeaderErr BGP Message
22 BGPOpenMsgErr BGP Message
23 OpenCollisionDump BGP Message
24 NotifMsgVerErr BGP Message
25 NotifMsg BGP Message
26 KeepAliveMsg BGP Message
27 UpdateMsg BGP Message
28 UpdateMsgErr BGP Message
29 SendHoldTimer Expires Timer
30 BfdAdminDown BFD Protocol Event
31 BfdDown BFD Protocol Event
32 BfdUp BFD Protocol Event
33 Bfd_Disabled Configuration
34 BfdHoldTimer_Expires Timer
35 BfdStrict_ConfigChanged Configuration
Security Considerations This document does not introduce any new security considerations to the BGP protocol.
References Normative References Informative References
Acknowledgements Thanks to Tom Petch and Ketan Talaulikar for their review on this document.
Contributors TBD