[Editorial Errata Reported] RFC5882 (8922)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 19 May 2026 09:46 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: rtg-bfd@ietf.org
Delivered-To: rtg-bfd@mail2.ietf.org
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 mail2.ietf.org (Postfix) with ESMTPS id 321FCF09A47E; Tue, 19 May 2026 02:46:40 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id E033D31D74E; Tue, 19 May 2026 02:46:39 -0700 (PDT)
To: rfc-editor@rfc-editor.org
Subject: [Editorial Errata Reported] RFC5882 (8922)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20260519094639.E033D31D74E@rfcpa.rfc-editor.org>
Date: Tue, 19 May 2026 02:46:39 -0700
Message-ID-Hash: HXS6OKF2WHT6QL5QDV2BKI77HDNVY67R
X-Message-ID-Hash: HXS6OKF2WHT6QL5QDV2BKI77HDNVY67R
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-bfd.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dkatz@juniper.net, dward@juniper.net, rtg-bfd@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection" <rtg-bfd.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/kQRlxjzuBhivToenFEiEEL4v-T4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-bfd-owner@ietf.org>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Subscribe: <mailto:rtg-bfd-join@ietf.org>
List-Unsubscribe: <mailto:rtg-bfd-leave@ietf.org>
The following errata report has been submitted for RFC5882, "Generic Application of Bidirectional Forwarding Detection (BFD)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8922 -------------------------------------- Type: Editorial Reported by: Xiao Min <xiao.min2@zte.com.cn> Section: 10.1.2 Original Text ------------- The basic mechanisms are covered in Section 3 above. At this time, OSPFv2 and OSPFv3 carry routing information for a single data protocol (IPv4 and IPv6, respectively) so when it is desired to signal a topology change after a BFD session failure, this should be done by tearing down the corresponding OSPF neighbor. IS-IS may be used to support only one data protocol, or multiple data protocols. [ISIS] specifies a common topology for multiple data protocols, but work is under way to support multiple topologies. If multiple topologies are used to support multiple data protocols (or multiple classes of service of the same data protocol), the topology- specific path associated with a failing BFD session should no longer be advertised in IS-IS Label Switched Paths (LSPs) in order to signal a lack of connectivity. Otherwise, a failing BFD session should be signaled by simulating an IS-IS adjacency failure. OSPF has a planned restart signaling mechanism, whereas IS-IS does not. The appropriate mechanisms outlined in Section 3.3 should be used. Corrected Text -------------- The basic mechanisms are covered in Section 4 above. At this time, OSPFv2 and OSPFv3 carry routing information for a single data protocol (IPv4 and IPv6, respectively) so when it is desired to signal a topology change after a BFD session failure, this should be done by tearing down the corresponding OSPF neighbor. IS-IS may be used to support only one data protocol, or multiple data protocols. [ISIS] specifies a common topology for multiple data protocols, but work is under way to support multiple topologies. If multiple topologies are used to support multiple data protocols (or multiple classes of service of the same data protocol), the topology- specific path associated with a failing BFD session should no longer be advertised in IS-IS Label Switched Paths (LSPs) in order to signal a lack of connectivity. Otherwise, a failing BFD session should be signaled by simulating an IS-IS adjacency failure. OSPF has a planned restart signaling mechanism, whereas IS-IS does not. The appropriate mechanisms outlined in Section 4.3 should be used. Notes ----- In this section, Section 3 should read as Section 4 and Section 3.3 should read as Section 4.3. From the history of this document, it can be seen that draft-ietf-bfd-generic-04 introduced a new section 3 while the references to the original section 3 and section 3.3 were not updated. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC5882 (draft-ietf-bfd-generic-05) -------------------------------------- Title : Generic Application of Bidirectional Forwarding Detection (BFD) Publication Date : June 2010 Author(s) : D. Katz, D. Ward Category : PROPOSED STANDARD Source : Bidirectional Forwarding Detection Stream : IETF Verifying Party : IESG
- [Editorial Errata Reported] RFC5882 (8922) RFC Errata System