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

        
        RFC 9705

        Title:      Refresh-Interval Independent RSVP Fast Reroute 
                    Facility Protection 
        Author:     C. Ramachandran,
                    T. Saad,
                    D. Pacella
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2025
        Mailbox:    [email protected],
                    [email protected],
                    [email protected]
        Pages:      24
        Updates:    RFC 4090

        I-D Tag:    draft-ietf-mpls-ri-rsvp-frr-22.txt

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

        DOI:        10.17487/RFC9705

The RSVP-TE Fast Reroute (FRR) extensions specified in RFC 4090
define two local repair techniques to reroute Label Switched Path
(LSP) traffic over pre-established backup tunnels. Facility backup
method allows one or more LSPs traversing a connected link or node to
be protected using a bypass tunnel. The many-to-one nature of local
repair technique is attractive from a scalability point of view. This
document enumerates facility backup procedures in RFC 4090 that rely
on refresh timeout, hence, making facility backup method
refresh-interval dependent. The RSVP-TE extensions defined in this
document will enhance the facility backup protection mechanism by
making the corresponding procedures refresh-interval independent, and
hence, compatible with the Refresh-Interval Independent RSVP
(RI-RSVP) capability specified in RFC 8370. Hence, this document
updates RFC 4090 in order to support the RI-RSVP capability specified
in RFC 8370.

This document is a product of the Multiprotocol Label Switching 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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team


_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org

Reply via email to