Skip to content

Commit 2a8326f

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 201 new elements (2026-07-12)
1 parent 678061e commit 2a8326f

201 files changed

Lines changed: 1927 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎corpus/elements/rfc-9494__design-rationale-llgr-depreferences-stale-routes-treats-them-as-least.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9494
2+
kind: design-rationale
3+
summary: LLGR depreferences stale routes (treats them as least preferred), whereas conventional GR leaves route preference unchanged. This design choice reflects the expectation that LLGR stale routes may be retained for a potentially unbounded period, making it preferable to advertise new state and use stale information only as a last resort.
4+
section: "1"
5+
topics:
6+
- bgp
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__design-rationale-llgr-was-motivated-by-two-trends-widespread-tunneled.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9494
2+
kind: design-rationale
3+
summary: 'LLGR was motivated by two trends: widespread tunneled forwarding (e.g., MPLS) that reduces forwarding-loop risk from stale state, and BGP''s growing use for non-forwarding data such as auto-discovery (VPLS) and filter programming (FLOWSPEC), where BGP data resembles configuration and does not need to be rapidly removed.'
4+
section: "1"
5+
topics:
6+
- bgp
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__design-rationale-requiring-the-gr-capability-alongside-the-llgr-capability.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9494
2+
kind: design-rationale
3+
summary: Requiring the GR Capability alongside the LLGR Capability allows LLGR to reuse base GR mechanisms—EoR origination, collection, processing, finite-state-machine modifications, and connection-reset logic—without duplicating their specification. The GR phase can effectively be skipped by advertising a Restart Time of zero.
4+
section: "4.1"
5+
topics:
6+
- bgp
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__interoperability-note-for-incremental-deployment-stale-routes-may-be-advertised.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9494
2+
kind: interoperability-note
3+
summary: For incremental deployment, stale routes MAY be advertised to IBGP or Confederation neighbors that have not advertised the LLGR Capability, provided the NO_EXPORT community is attached and LOCAL_PREF is set to zero. This option is not available for EBGP neighbors without the LLGR Capability.
4+
section: "4.6"
5+
topics:
6+
- bgp
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__interoperability-note-in-vpn-deployments-using-ebgp-as-the-pe.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9494
2+
kind: interoperability-note
3+
summary: In VPN deployments using EBGP as the PE-CE protocol, an implementation MAY advertise LLGR stale routes over a PE-CE session to a non-LLGR CE when explicitly configured to do so, bypassing the normal restriction. The NO_EXPORT community SHOULD be attached by default as an additional safeguard against unbounded stale route propagation.
4+
section: 4.7.1
5+
topics:
6+
- bgp
7+
- routing
8+
- vpn
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__interoperability-note-when-a-long-lived-stale-time-timer-expires.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9494
2+
kind: interoperability-note
3+
summary: When a Long-Lived Stale Time timer expires during synchronization (after session re-establishment but before EoR), any stale routes not refreshed by the peer are removed. If the session resets again before synchronization completes for an AFI/SAFI whose LLST timer already expired, all remaining routes for that AFI/SAFI MUST be removed immediately.
4+
section: "4.2"
5+
topics:
6+
- bgp
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__normative-requirement-a-bgp-speaker-configured-to-support-llgr-procedures.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9494
2+
kind: normative-requirement
3+
summary: A BGP speaker configured to support LLGR procedures MUST use BGP Capabilities Advertisement (RFC 5492) to advertise the Long-Lived Graceful Restart Capability. The setting of AFI/SAFI parameters depends on speaker properties, network scale, and local configuration.
4+
section: "4"
5+
rfc2119_level: MUST
6+
topics:
7+
- bgp
8+
- routing
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__normative-requirement-a-least-preferred-route-must-be-treated-as.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9494
2+
kind: normative-requirement
3+
summary: A least-preferred route MUST be treated as less preferred than any non-least-preferred route. Normal tiebreaking applies only when comparing two routes that are both least preferred.
4+
section: "4.4"
5+
rfc2119_level: MUST
6+
topics:
7+
- bgp
8+
- routing
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__normative-requirement-a-speaker-that-has-advertised-the-llgr-capability.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9494
2+
kind: normative-requirement
3+
summary: A speaker that has advertised the LLGR Capability MUST treat any received LLGR_STALE route as the least preferred in route selection. Such routes SHOULD NOT be advertised to any neighbor from which the LLGR Capability has not been received, and the LLGR_STALE community MUST NOT be removed when the route is further advertised.
4+
section: "4.3"
5+
rfc2119_level: MUST
6+
topics:
7+
- bgp
8+
- routing
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9494__normative-requirement-after-a-session-goes-down-and-before-re.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9494
2+
kind: normative-requirement
3+
summary: After a session goes down and before re-establishment, stale routes for each AFI/SAFI MUST be retained for the sum of the GR Restart Time and the Long-Lived Stale Time received in the peer's capabilities. The received LLST timers SHOULD be modifiable by local configuration that may impose upper or lower bounds.
4+
section: "4.2"
5+
rfc2119_level: MUST
6+
topics:
7+
- bgp
8+
- routing
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

0 commit comments

Comments
 (0)