From b4196b70c4463d78f8f202ef4ad65c24f240e1a2 Mon Sep 17 00:00:00 2001
From: Maria Matejka <mq@ucw.cz>
Date: Wed, 6 Nov 2024 13:05:32 +0100
Subject: [PATCH] BGP: SendHoldTimer became an RFC, updating docs

---
 doc/bird.sgml       | 3 +--
 proto/bgp/packets.c | 2 +-
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/doc/bird.sgml b/doc/bird.sgml
index e964ff06d..a9c623a5c 100644
--- a/doc/bird.sgml
+++ b/doc/bird.sgml
@@ -3219,8 +3219,7 @@ using the following configuration parameters:
 	Send hold timer drops the session if the neighbor is sending keepalives,
 	but does not receive our messages, causing the TCP connection to stall.
 	This may happen due to malfunctioning or overwhelmed neighbor. See
-	<HTMLURL URL="https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-sendholdtimer/"
-	name="draft-ietf-idr-bgp-sendholdtimer"> for more details.
+	<rfc id="9687"> for more details.
 
 	Like the option <cf/keepalive time/, the effective value depends on the
 	negotiated hold time, as it is scaled to maintain proportion between the
diff --git a/proto/bgp/packets.c b/proto/bgp/packets.c
index f1e03621e..30da32948 100644
--- a/proto/bgp/packets.c
+++ b/proto/bgp/packets.c
@@ -3290,7 +3290,7 @@ static struct {
   { 6, 8, "Out of Resources" },
   { 7, 0, "Invalid ROUTE-REFRESH message" }, /* [RFC7313] */
   { 7, 1, "Invalid ROUTE-REFRESH message length" }, /* [RFC7313] */
-  { 8, 0, "Send hold timer expired" }, /* [draft-ietf-idr-bgp-sendholdtimer] */
+  { 8, 0, "Send hold timer expired" }, /* [RFC9687] */
 };
 
 /**
-- 
2.47.2