Skip to content

Commit eba3521

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 227 new elements (2026-07-06)
1 parent a77693d commit eba3521

227 files changed

Lines changed: 2069 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-8667__design-rationale-multiple-srgb-descriptor-entries-define-an-ordered-set.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8667
2+
kind: design-rationale
3+
summary: Multiple SRGB Descriptor entries define an ordered set of label ranges that together form the full SRGB; SID indexes span across all ranges in advertisement order. The ordering is load-bearing — changing it changes the label each index resolves to — which motivates the strict append-only requirement for new descriptors.
4+
section: "3.1"
5+
topics:
6+
- routing
7+
- mpls
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__interoperability-note-php-behavior-cannot-be-determined-solely-from-a.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8667
2+
kind: interoperability-note
3+
summary: PHP behavior cannot be determined solely from a Mapping Server advertisement because the originator of the prefix is not identified. PHP MAY be applied if a prefix reachability advertisement exists with a Prefix Attribute Flags sub-TLV where X-Flag and R-Flag are both 0. In the absence of such a sub-TLV, the A-Flag in the Binding TLV indicates direct connectivity and PHP MUST be performed by neighbors of the prefix originator.
4+
section: 2.4.4.2
5+
topics:
6+
- routing
7+
- mpls
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__normative-requirement-a-prefix-sid-must-be-unique-within-a.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8667
2+
kind: normative-requirement
3+
summary: A Prefix-SID MUST be unique within a given IGP domain when the L-Flag is not set.
4+
section: "2.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__normative-requirement-in-the-sid-label-binding-tlv-if-the.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8667
2+
kind: normative-requirement
3+
summary: In the SID/Label Binding TLV, if the S-Flag is not set, the TLV MUST NOT be leaked between levels and the S-Flag MUST NOT be altered during TLV leaking. The D-Flag MUST be set when the TLV is leaked from Level-2 to Level-1; TLVs with D-Flag set MUST NOT be leaked from Level-1 to Level-2, preventing looping.
4+
section: 2.4.1
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__normative-requirement-the-algorithm-field-in-an-originated-prefix-sid.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8667
2+
kind: normative-requirement
3+
summary: The Algorithm field in an originated Prefix-SID MUST be set to 0 or to a value advertised in the SR-Algorithm sub-TLV. A router receiving a Prefix-SID with an algorithm value not advertised by the remote node in its SR-Algorithm sub-TLV MUST ignore the Prefix-SID sub-TLV.
4+
section: "2.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__normative-requirement-the-prefix-sid-sub-tlv-must-be-included.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8667
2+
kind: normative-requirement
3+
summary: The Prefix-SID sub-TLV MUST be included when the associated Prefix Reachability TLV is propagated across IS-IS level boundaries. The Level-1-2 router maintains the content (flags and SID) except as specified for N-Flag, R-Flag, P-Flag, and E-Flag handling.
4+
section: 2.1.2
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__normative-requirement-the-prefix-sid-sub-tlv-must-be-present.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8667
2+
kind: normative-requirement
3+
summary: The Prefix-SID sub-TLV MUST be present in the SID/Label Binding TLV when the M-Flag is clear (normal SRMS use), and MUST NOT be present when the M-Flag is set (Mirror Context). The SID/Label sub-TLV (Type 1) MUST be present in the Binding TLV when the M-Flag is set.
4+
section: 2.4.4
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__normative-requirement-the-r-flag-must-be-set-for-prefixes.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8667
2+
kind: normative-requirement
3+
summary: The R-Flag MUST be set for prefixes not local to the router that are advertised due to level propagation, leaking, or redistribution from another protocol. A Level-1-2 router propagating its own configured interface addresses to another level MUST NOT set the R-Flag.
4+
section: 2.1.1.2
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__normative-requirement-the-sr-capabilities-sub-tlv-must-be-propagated.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8667
2+
kind: normative-requirement
3+
summary: The SR-Capabilities sub-TLV MUST be propagated throughout the IS-IS level and MUST NOT be advertised across level boundaries (Router Capability TLV S-Flag MUST be unset). A router MUST NOT advertise more than one SR-Capabilities sub-TLV and MUST NOT advertise overlapping SRGB ranges.
4+
section: "3.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8667__normative-requirement-v-flag-and-l-flag-combinations-are-constrained.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8667
2+
kind: normative-requirement
3+
summary: 'V-Flag and L-Flag combinations are constrained: both set to 0 means the SID/Index/Label is a 4-octet global index; both set to 1 means a 3-octet local label (20 rightmost bits). All other combinations are invalid and any SID advertisement with an invalid V-Flag/L-Flag setting MUST be ignored.'
4+
section: 2.1.1.1
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

0 commit comments

Comments
 (0)