RFC 9468: Unsolicited Bidirectional Forwarding Detection (BFD) for Sessionless Applications
In plain English — editorial summary, not part of the RFC
For operational simplification of "sessionless" applications using Bidirectional Forwarding Detection (BFD), in this document, we present procedures for "unsolicited BFD" that allow a BFD session to be initiated by only one side and established without explicit per-session configuration or registration by the other side (subject to certain per-interface or global policies). We also introduce a new YANG module to configure and manage "unsolicited BFD". The YANG module in this document is based on YANG 1.1, as defined in RFC 7950, and conforms to the Network Management Datastore Architecture (NMDA), as described in RFC 8342. This document augments RFC 9314.
Document record
- Document ID
- RFC9468
- Published
- August 2023
- Authors
- E. Chen; N. Shen; R. Raszuk; R. Rahman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9469Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) NetworksCurrent
September 2023
- RFC 9467Relaxed Packet Counter Verification for Babel MAC AuthenticationCurrent
January 2024
- RFC 9466PIM Assert Message PackingCurrent
October 2023
- RFC 9465PIM Null-Register PackingCurrent
September 2023
- RFC 9479IS-IS Application-Specific Link AttributesCurrent
October 2023
- RFC 9454Update to OSPF TerminologyCurrent
August 2023
- RFC 9452Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) DataCurrent
August 2023
- RFC 9451Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH)Current
August 2023
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?