A new Request for Comments is now available in online RFC libraries.
RFC 9468
Title: Unsolicited Bidirectional Forwarding Detection (BFD)
for Sessionless Applications
Author: E. Chen,
N. Shen,
R. Raszuk,
R. Rahman
Status: Standards Track
Stream: IETF
Date: August 2023
Mailbox: [email protected],
[email protected],
[email protected],
[email protected]
Pages: 16
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bfd-unsolicited-16.txt
URL: https://www.rfc-editor.org/info/rfc9468
DOI: 10.17487/RFC9468
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.
This document is a product of the Bidirectional Forwarding Detection Working
Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
