[mpls] RFC 9612 on Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)

rfc-editor@rfc-editor.org Wed, 24 July 2024 01:16 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (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 8FC53C1524DC; Tue, 23 Jul 2024 18:16:14 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id EE2AF7FA61; Tue, 23 Jul 2024 18:16:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240724011613.EE2AF7FA61@rfcpa.rfc-editor.org>
Date: Tue, 23 Jul 2024 18:16:13 -0700
Message-ID-Hash: 2AFXXGC4OS3UQPQGXR64LZOPQEKWCC7D
X-Message-ID-Hash: 2AFXXGC4OS3UQPQGXR64LZOPQEKWCC7D
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [mpls] RFC 9612 on Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/VMcR5KcP6_kHrFv4R3fr0O8FXls>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9612

        Title:      Bidirectional Forwarding Detection (BFD)
                    Reverse Path for MPLS Label Switched Paths (LSPs) 
        Author:     G. Mirsky,
                    J. Tantsura,
                    I. Varlashkin,
                    M. Chen
        Status:     Experimental
        Stream:     IETF
        Date:       July 2024
        Mailbox:    gregimirsky@gmail.com,
                    jefftant.ietf@gmail.com,
                    imv@google.com,
                    mach.chen@huawei.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-bfd-directed-31.txt

        URL:        https://www.rfc-editor.org/info/rfc9612

        DOI:        10.17487/RFC9612

Bidirectional Forwarding Detection (BFD) is expected to be able to
monitor a wide variety of encapsulations of paths between systems.
When a BFD session monitors an explicitly routed unidirectional path,
there may be a need to direct the egress BFD peer to use a specific
path for the reverse direction of the BFD session. This document
describes an extension to the MPLS Label Switched Path (LSP) echo
request that allows a BFD system to request that the remote BFD peer
transmit BFD control packets over the specified LSP.

This document is a product of the Multiprotocol Label Switching 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/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