RFC 9747: Unaffiliated Bidirectional Forwarding Detection (BFD) Echo
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the Bidirectional Forwarding Detection (BFD) protocol that enables the use of the BFD Echo function without the need for an associated BFD control session. This "Unaffiliated BFD Echo" mechanism allows rapid detection of forwarding path failures in networks where establishing BFD control sessions is impractical or undesirable. By decoupling the Echo function from the control plane, network devices can utilize BFD's fast failure detection capabilities in a simplified manner, enhancing network resiliency and operational efficiency. This document updates RFC 5880 by defining a new Unaffiliated BFD Echo mechanism.
Document record
- Document ID
- RFC9747
- Published
- March 2025
- Authors
- W. Cheng; R. Wang; X. Min; R. Rahman; R. Boddireddy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
- Updates:
- RFC 5880
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9746BGP EVPN Multihoming Extensions for Split-Horizon FilteringCurrent
March 2025
- RFC 9744EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) ServiceCurrent
March 2025
- RFC 9752Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCECurrent
April 2025
- RFC 9753Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) ObjectsCurrent
April 2025
- RFC 9739Protocol Independent Multicast Light (PIM Light)Current
March 2025
- RFC 9756Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error CodesCurrent
March 2025
- RFC 9757Path Computation Element Communication Protocol (PCEP) Extensions for Native IP NetworksCurrent
March 2025
- RFC 9735Locator/ID Separation Protocol (LISP) Distinguished Name EncodingCurrent
February 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?