[rfc-dist] RFC 9494 on Long-Lived Graceful Restart for BGP

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

        RFC 9494

        Title:      Long-Lived Graceful Restart for BGP 
        Author:     J. Uttaro,
                    E. Chen,
                    B. Decraene,
                    J. Scudder
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2023
        Mailbox:    juttaro@ieee.org,
                    enchen@paloaltonetworks.com,
                    bruno.decraene@orange.com,
                    jgs@juniper.net
        Pages:      20
        Updates:    RFC 6368

        I-D Tag:    draft-ietf-idr-long-lived-gr-06.txt

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

        DOI:        10.17487/RFC9494

This document introduces a BGP capability called the "Long-Lived
Graceful Restart Capability" (or "LLGR Capability").  The benefit of
this capability is that stale routes can be retained for a longer
time upon session failure than is provided for by BGP Graceful
Restart (as described in RFC 4724). A well-known BGP community called
"LLGR_STALE" is introduced for marking stale routes retained for a
longer time. A second well-known BGP community called "NO_LLGR" is
introduced for marking routes for which these procedures should not
be applied. We also specify that such long-lived stale routes be
treated as the least preferred and that their advertisements be
limited to BGP speakers that have advertised the capability. Use of
this extension is not advisable in all cases, and we provide
guidelines to help determine if it is. 

This memo updates RFC 6368 by specifying that the LLGR_STALE
community must be propagated into, or out of, the path attributes
exchanged between the Provider Edge (PE) and Customer Edge (CE)
routers.

This document is a product of the Inter-Domain Routing 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