RFC 9687 on Border Gateway Protocol 4 (BGP-4) Send Hold Timer
rfc-editor@rfc-editor.org Wed, 06 November 2024 09:57 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26089C1D6200; Wed, 6 Nov 2024 01:57:56 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 96BB33B874; Wed, 6 Nov 2024 01:57:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9687 on Border Gateway Protocol 4 (BGP-4) Send Hold Timer
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20241106095755.96BB33B874@rfcpa.rfc-editor.org>
Date: Wed, 06 Nov 2024 01:57:55 -0800
Message-ID-Hash: JCBN3ZCEW4X4HX7KWQ775MYVAOOJDLL6
X-Message-ID-Hash: JCBN3ZCEW4X4HX7KWQ775MYVAOOJDLL6
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, idr@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jQjMIp5pwjGDQ4Skgyp3lOTpjpw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9687
Title: Border Gateway Protocol 4 (BGP-4) Send Hold Timer
Author: J. Snijders,
B. Cartwright-Cox,
Y. Qu
Status: Standards Track
Stream: IETF
Date: November 2024
Mailbox: job@fastly.com,
ben@benjojo.co.uk,
yingzhen.ietf@gmail.com
Pages: 8
Updates: RFC 4271
I-D Tag: draft-ietf-idr-bgp-sendholdtimer-15.txt
URL: https://www.rfc-editor.org/info/rfc9687
DOI: 10.17487/RFC9687
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.
This document is a product of the Inter-Domain Routing Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC