RFC 9468 on Unsolicited Bidirectional Forwarding Detection (BFD) for Sessionless Applications
rfc-editor@rfc-editor.org Fri, 01 September 2023 04:36 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF09C1519B4; Thu, 31 Aug 2023 21:36:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ffLQsP4-KzYO; Thu, 31 Aug 2023 21:36:44 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90786C1519B7; Thu, 31 Aug 2023 21:36:44 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 670F5CD7E7; Thu, 31 Aug 2023 21:36:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9468 on Unsolicited Bidirectional Forwarding Detection (BFD) for Sessionless Applications
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtg-bfd@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230901043644.670F5CD7E7@rfcpa.amsl.com>
Date: Thu, 31 Aug 2023 21:36:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/fxlYMEC-lYzUJzM85B8qw8TOkIE>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2023 04:36:48 -0000
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: enchen@paloaltonetworks.com,
naiming@zededa.com,
robert@raszuk.net,
reshad@yahoo.com
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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC