Another of the WG's drafts has completed the RFC process. Thanks everyone for the work.
And thank you, Albert, for driving the use case. -- Jeff > Begin forwarded message: > > From: rfc-edi...@rfc-editor.org > Subject: RFC 9764 on Bidirectional Forwarding Detection (BFD) Encapsulated in > Large Packets > Date: April 4, 2025 at 1:43:40 PM EDT > To: ietf-annou...@ietf.org, rfc-d...@rfc-editor.org > Cc: rfc-edi...@rfc-editor.org, drafts-update-...@iana.org, rtg-bfd@ietf.org > > A new Request for Comments is now available in online RFC libraries. > > > RFC 9764 > > Title: Bidirectional Forwarding Detection (BFD) Encapsulated > in Large Packets > Author: J. Haas, > A. Fu > Status: Standards Track > Stream: IETF > Date: April 2025 > Mailbox: jh...@juniper.net, > af...@bloomberg.net > Pages: 14 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-bfd-large-packets-16.txt > > URL: https://www.rfc-editor.org/info/rfc9764 > > DOI: 10.17487/RFC9764 > > 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). > > 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 rfc-edi...@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team >
