Skip to content

Commit 63527df

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 83 new elements (2026-07-12)
1 parent 4e2cd76 commit 63527df

83 files changed

Lines changed: 815 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-9703__design-rationale-bgp-confederation-member-as-numbers-are-used-in.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9703
2+
kind: design-rationale
3+
summary: BGP Confederation member AS numbers are used in the Local AS and Remote AS fields rather than the Confederation Identifier, because EPE-SIDs within a confederation operate between Member-ASes, not between a member and the confederation as a whole.
4+
section: "4.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-9703__design-rationale-for-multi-hop-ebgp-sessions-with-peernode-sids.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9703
2+
kind: design-rationale
3+
summary: For multi-hop EBGP sessions with PeerNode SIDs where traffic may be load-balanced across multiple interfaces, the advertising node sends a Downstream Detailed Mapping (DDMAP) TLV specifying next-hop interface details, allowing a controller to verify actual forwarding state against topology information. Discrepancies between controller state and forwarding state are not detected by the OAM procedures alone.
4+
section: "4.1"
5+
topics:
6+
- mpls
7+
- bgp
8+
- routing
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9703__design-rationale-the-epe-sid-fec-sub-tlvs-are-defined.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9703
2+
kind: design-rationale
3+
summary: The EPE-SID FEC sub-TLVs are defined for the Target FEC Stack TLV to enable control plane to forwarding plane synchronization validation for inter-AS EPE SIDs; without this, mismatches (e.g., a PeerAdj SID bound to the wrong adjacency in the data plane) could go unnoticed by network operators.
4+
section: "1"
5+
topics:
6+
- mpls
7+
- bgp
8+
- routing
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9703__interoperability-note-during-as-migration-scenarios-using-procedures-from-rfc.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9703
2+
kind: interoperability-note
3+
summary: During AS migration scenarios using procedures from RFC 7705, if the local and remote AS fields in the FEC carry the globally configured AS Number rather than the 'local AS', the FEC validation procedures may fail.
4+
section: "2"
5+
topics:
6+
- bgp
7+
- routing
8+
- mpls
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9703__interoperability-note-if-a-ping-or-traceroute-packet-enters-a.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9703
2+
kind: interoperability-note
3+
summary: If a ping or traceroute packet enters a non-cooperating AS domain it might be dropped; while complete path validation cannot be done across non-cooperating domains, the mechanism still provides useful information that the packet entered a non-cooperating domain.
4+
section: "2"
5+
topics:
6+
- mpls
7+
- bgp
8+
- routing
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9703__interoperability-note-unnumbered-interfaces-anycast-and-multicast-addresses-and-scenarios.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9703
2+
kind: interoperability-note
3+
summary: Unnumbered interfaces, anycast and multicast addresses, and scenarios involving EPE-SIDs in ingress SR policies for remote ASes of completely different ownership are explicitly out of scope for this document.
4+
section: "2"
5+
topics:
6+
- mpls
7+
- bgp
8+
- routing
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9703__normative-requirement-for-peerset-sid-the-remote-as-number-and.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-9703
2+
kind: normative-requirement
3+
summary: For PeerSet SID, the remote AS number and the Router ID of each associated PeerNode SID and PeerAdj SID MUST be included in the FEC.
4+
section: "4.3"
5+
rfc2119_level: MUST
6+
topics:
7+
- mpls
8+
- bgp
9+
- routing
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9703__normative-requirement-if-a-malformed-fec-sub-tlv-is-received.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-9703
2+
kind: normative-requirement
3+
summary: If a malformed FEC sub-TLV is received, a return code of 1 ('Malformed echo request received') as defined in RFC 8029 MUST be sent.
4+
section: "5"
5+
rfc2119_level: MUST
6+
topics:
7+
- mpls
8+
- bgp
9+
- routing
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9703__normative-requirement-it-is-recommended-to-send-the-optional-local.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-9703
2+
kind: normative-requirement
3+
summary: It is RECOMMENDED to send the optional local and remote interface address descriptors in PeerAdj SID sub-TLV and use them to validate incoming interfaces; when unavailable, an ingress node can send 0 in those fields.
4+
section: "4.2"
5+
rfc2119_level: RECOMMENDED
6+
topics:
7+
- mpls
8+
- bgp
9+
- routing
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9703__normative-requirement-mpls-ping-and-traceroute-procedures-may-be-initiated.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-9703
2+
kind: normative-requirement
3+
summary: MPLS Ping and Traceroute procedures MAY be initiated by the head-end of the SR path or a centralized topology-aware data plane monitoring system as described in RFC 8403.
4+
section: "2"
5+
rfc2119_level: MAY
6+
topics:
7+
- mpls
8+
- bgp
9+
- routing
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-12"

0 commit comments

Comments
 (0)