RFC 9687: Border Gateway Protocol 4 (BGP-4) Send Hold Timer
In plain English — editorial summary, not part of the RFC
This document defines the SendHoldTimer, along with the SendHoldTimer_Expires event, for the Border Gateway Protocol (BGP) Finite State Machine (FSM). Implementation of the SendHoldTimer helps overcome situations where a BGP connection is not terminated after the local system detects that the remote system is not processing BGP messages. This document specifies that the local system should close the BGP connection and not solely rely on the remote system for connection closure when the SendHoldTimer expires. This document updates RFC 4271.
Document record
- Document ID
- RFC9687
- Published
- November 2024
- Authors
- J. Snijders; B. Cartwright-Cox; Y. Qu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 4271
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2385Protection of BGP Sessions via the TCP MD5 Signature OptionObsoleted
August 1998
- RFC 9703Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data PlaneCurrent
December 2024
- RFC 9716Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing NetworksCurrent
February 2025
- RFC 9819Argument Signaling for BGP Services in Segment Routing over IPv6 (SRv6)Current
July 2025
- RFC 9857Advertisement of Segment Routing Policies Using BGP - Link StateCurrent
October 2025
- RFC 9514Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6)Current
December 2023
- RFC 9314YANG Data Model for Bidirectional Forwarding Detection (BFD)Current
September 2022
- RFC 9252BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)Updated
July 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?