Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Updates:

RFC 6368

Authors:

J. Uttaro
E. Chen
B. Decraene
J. Scudder

Stream:

IETF

Source:

idr (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9494

Discuss this RFC: Send questions or comments to the mailing listidr@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9494

Abstract

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

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

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.