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:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to