[Errata Verified] RFC5882 (8921)

rfc-editor@rfc-editor.org Thu, 16 July 2026 05:59 UTC

Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [Errata Verified] RFC5882 (8921)
From: rfc-editor@rfc-editor.org
To: wardd@cisco.com, dkatz@juniper.com, xiao.min2@zte.com.cn
Date: Thu, 16 Jul 2026 05:59:01 -0000
message-id: <178418154109.12.11082584896317032460@rfc-editor.org>
Message-ID-Hash: BL7INTIYNN4PWAAGASTO5CTCWMNTF7IJ
CC: iana@iana.org, iesg@ietf.org, rtg-bfd@ietf.org, rfc-editor@rfc-editor.org
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/w_p72DmhYjZf0Sa31e4sZPPGatw>

The following errata report has been verified for RFC5882,
"Generic Application of Bidirectional Forwarding Detection (BFD)"

--------------------------------------
You may review the report below and at:
https://errata.rfc-editor.org/eid8921/

--------------------------------------

Status: Verified
Type: Editorial
Reported by: Xiao Min <xiao.min2@zte.com.cn>
Date Reported: May 19, 2026, 7 p.m.
Verified by: Ketan Talaulikar (IESG)

Section 4.3.2.2 says:

Original Text
-------------
Control protocols that cannot signal a planned restart depend on the
   recently restarted system to signal the Graceful Restart prior to the
   control protocol adjacency timeout.  In most cases, whether the
   restart is planned or unplanned, it is likely that the BFD session
   will time out prior to the onset of Graceful Restart, in which case a
   topology change SHOULD be signaled in the control protocol as
   specified in Section 3.2.

Corrected Text
--------------
Control protocols that cannot signal a planned restart depend on the
   recently restarted system to signal the Graceful Restart prior to the
   control protocol adjacency timeout.  In most cases, whether the
   restart is planned or unplanned, it is likely that the BFD session
   will time out prior to the onset of Graceful Restart, in which case a
   topology change SHOULD be signaled in the control protocol as
   specified in Section 4.2.

Notes
-----
In this paragraph Section 3.2 should read as Section 4.2. From the history of this document, it can be seen that draft-ietf-bfd-generic-04 introduced a new section 3 while the reference to the original section 3.2 was not updated.

--------------------------------------
RFC5882 (draft-ietf-bfd-generic)
--------------------------------------
Title               : Generic Application of Bidirectional Forwarding Detection (BFD)
Publication Date    : June 2010
Author(s)           : D. Katz, D. Ward
Category            : Proposed Standard
Source              : bfd (rtg)
Stream              : IETF

[Errata Verified] RFC5882 (8921) rfc-editor