BGP: SendHoldTimer became an RFC, updating docs

diff --git a/doc/bird.sgml b/doc/bird.sgml
index e964ff06de52c05064af95b9abb517ad8ef1fb46..a9c623a5c1eef51ded9cf7779ae69bc805bc8b49 100644 (file)
--- 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 f1e03621ebadaafd4e307ff4518d65ccddd9eb4d..30da32948ed7acddeee93a3336e4bd957076cb36 100644 (file)
--- 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] */
 };
 
 /**