Re: RFC 9985 on Optimizing Bidirectional Forwarding Detection (BFD) Authentication

And similarly congratulations to the authors and the WG for RFC 9986, the
companion document for the ISAAC mechanism of implementing the optimized
procedures.

-- Jeff

On Fri, Jun 19, 2026 at 06:38:03PM -0700, Mahesh Jethanandani wrote:
> Congratulations to everyone. For some, it is their first RFC.
> 
> > On Jun 19, 2026, at 1:45 PM, rfc-editor@rfc-editor.org wrote:
> > 
> > A new Request for Comments is now available in online RFC libraries.
> > 
> >        RFC 9985
> > 
> >        Title:      Optimizing Bidirectional Forwarding Detection (BFD) Authentication
> >        Author:     M. Jethanandani,
> >                    A. Mishra,
> >                    J. Haas,
> >                    A. Saxena,
> >                    M. Bhatia
> >        Status:     Experimental
> >        Stream:     IETF
> >        Date:       June 2026
> >        Mailbox:    mjethanandani@gmail.com,
> >                    mishra.ashesh@outlook.com,
> >                    jhaas@pfrc.org,
> >                    ankurpsaxena@gmail.com,
> >                    manav@ionosnetworks.com
> >        Pages:      20
> > 
> > 
> >        I-D Tag:    draft-ietf-bfd-optimizing-authentication-36
> > 
> >        URL:        https://www.rfc-editor.org/info/rfc9985
> > 
> >        DOI:        10.17487/RFC9985
> > 
> > This document describes an experimental optimization to Bidirectional Forwarding Detection (BFD) Authentication. This optimization enables BFD to scale better when there is a desire to use authentication where applying the same authentication mechanism to every BFD Control Packet may adversely impact performance. This optimization partitions BFD Authentication into a more computationally intensive (MCI) mechanism that is applied to BFD significant changes and a less computationally intensive (LCI) mechanism that is applied to the majority of BFD Control Packets.
> > 
> > This document is a product of the Bidirectional Forwarding Detection Working Group of the IETF.
> > 
> > EXPERIMENTAL: This memo defines an Experimental Protocol for the
> > Internet community. It does not specify an Internet standard of any
> > kind. Discussion and suggestions for improvement are requested.
> > 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/series/rfc-download/
> > 
> > Requests for special distribution should be addressed to either the
> > author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> > specifically noted otherwise on the RFC itself, all RFCs are for
> > unlimited distribution.
> > 
> > 
> > The RFC Editor Team
> > 
> 
> 
> Mahesh Jethanandani
> mjethanandani@gmail.com
> 
> 
> 
> 
> 
> 