RFC 9764: Bidirectional Forwarding Detection (BFD) Encapsulated in Large Packets
In plain English — editorial summary, not part of the RFC
The Bidirectional Forwarding Detection (BFD) protocol is commonly used to verify connectivity between two systems. BFD packets are typically very small. It is desirable in some circumstances to know not only that the path between two systems is reachable, but also that it is capable of carrying a payload of a particular size. This document specifies how to implement such a mechanism using BFD in Asynchronous mode. YANG modules for managing this mechanism are also defined in this document. These YANG modules augment the existing BFD YANG modules defined in RFC 9314. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA) (RFC 8342).
Document record
- Document ID
- RFC9764
- Published
- April 2025
- Authors
- J. Haas; A. Fu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9757Path Computation Element Communication Protocol (PCEP) Extensions for Native IP NetworksCurrent
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 9772Active Operations, Administration, and Maintenance (OAM) for Use in Generic Network Virtualization Encapsulation (Geneve)Current
May 2025
- RFC 9774Deprecation of AS_SET and AS_CONFED_SET in BGPCurrent
May 2025
- RFC 9753Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) ObjectsCurrent
April 2025
- RFC 9752Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCECurrent
April 2025
- RFC 9776Internet Group Management Protocol, Version 3Current
March 2025
- RFC 9777Multicast Listener Discovery Version 2 (MLDv2) for IPv6Current
March 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?