Re: [Idr] I-D Action: draft-ietf-idr-long-lived-gr-06.txt

[John Scudder <[e-mail]>]

This version has changes related to the SECDIR and GENART reviews.

- Upgraded MAY to SHOULD in Section 4.2, regarding local configuration to modify LLST.
- Downgraded MUST NOT to ‘must not’ in Section 6 (we weren’t actually creating new normative text, the 2119 keyword was inappropriate).
- Tightened up Security Considerations text, made safety condition more specific.

Thanks,

—John

> On Jul 12, 2023, at 3:57 PM, [e-mail] wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This Internet-Draft is a work item of the Inter-Domain Routing
> (IDR) WG of the IETF.
> 
>   Title           : Support for Long-lived BGP Graceful Restart
>   Authors         : James Uttaro
>                     Enke Chen
>                     Bruno Decraene
>                     John G. Scudder
>   Filename        : draft-ietf-idr-long-lived-gr-06.txt
>   Pages           : 24
>   Date            : 2023-07-12
> 
> Abstract:
>   In this document, we introduce a new BGP capability termed "Long-
>   lived Graceful Restart Capability" so that stale routes can be
>   retained for a longer time upon session failure than is provided for
>   by BGP Graceful Restart (RFC 4724).  A well-known BGP community
>   "LLGR_STALE" is introduced for marking stale routes retained for a
>   longer time.  A second well-known BGP community, "NO_LLGR", is
>   introduced to mark 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 their advertisements be limited
>   to BGP speakers that have advertised the new 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 PE and CE.
...