RFC 9985: Optimizing Bidirectional Forwarding Detection (BFD) Authentication
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9985
- Published
- June 2026
- Authors
- M. Jethanandani; A. Mishra; J. Haas; A. Saxena; M. Bhatia
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9780Bidirectional Forwarding Detection (BFD) for Multipoint Networks over Point-to-Multipoint MPLS Label Switched Paths (LSPs)Current
May 2025
- RFC 9612Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)Current
July 2024
- RFC 9467Relaxed Packet Counter Verification for Babel MAC AuthenticationCurrent
January 2024
- RFC 9247BGP - Link State (BGP-LS) Extensions for Seamless Bidirectional Forwarding Detection (S-BFD)Current
June 2022
- RFC 9186Fast Failover in Protocol Independent Multicast - Sparse Mode (PIM-SM) Using Bidirectional Forwarding Detection (BFD) for Multipoint NetworksCurrent
January 2022
- RFC 9026Multicast VPN Fast Upstream FailoverCurrent
April 2021
- RFC 8971Bidirectional Forwarding Detection (BFD) for Virtual eXtensible Local Area Network (VXLAN)Current
December 2020
- RFC 8967MAC Authentication for the Babel Routing ProtocolUpdated
January 2021
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?