RFC 9985 on Optimizing Bidirectional Forwarding Detection (BFD) Authentication

rfc-editor@rfc-editor.org Fri, 19 June 2026 20:45 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: rtg-bfd@ietf.org
Delivered-To: rtg-bfd@mail2.ietf.org
Received: from celery-65b5b7b776-nks7b (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id E17A710433E9E; Fri, 19 Jun 2026 13:45:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781901941; bh=5x6NZkVY+BNy4QXx2di+cIQ+Wzmuz7HvznIDHAs9bSE=; h=Subject:From:To:Cc:Date; b=RxYsfLbzHqg6XLjiuEm3CAE/ZHsB/Zt+eEUHUhV7uqGnua7/N+piDfW8wsvZ715pa YQDUgbyVV9PDPBkQtIil9o/AqitzMg2R5c5rzlf31R7C61Icu+4t4quUi1ffa8J/zp o1iDTtqTo7N45atzBGl+6cS5EE7NIB1REcOjvvCU=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 9985 on Optimizing Bidirectional Forwarding Detection (BFD) Authentication
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Fri, 19 Jun 2026 20:45:40 -0000
message-id: <178190194065.15.4215247475115449406@rfc-editor.org>
Message-ID-Hash: ORMHROGNKVSKZJZNPDT4LFO3KYWVYV24
X-Message-ID-Hash: ORMHROGNKVSKZJZNPDT4LFO3KYWVYV24
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-bfd.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org, rtg-bfd@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection" <rtg-bfd.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/ZO0o82_h2hNmPRst4nACXcpKCBM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-bfd-owner@ietf.org>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Subscribe: <mailto:rtg-bfd-join@ietf.org>
List-Unsubscribe: <mailto:rtg-bfd-leave@ietf.org>

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