Skip to content

Commit f070da9

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 191 new elements (2026-07-12)
1 parent 40b6de4 commit f070da9

191 files changed

Lines changed: 1787 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-9716__design-rationale-dynamic-return-path-building-section-5-5-was.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9716
2+
kind: design-rationale
3+
summary: Dynamic return path building (Section 5.5) was introduced because head-end nodes may not have complete visibility of inter-AS/inter-domain topology. Domain border nodes (ABRs, ASBRs) dynamically construct and insert their Node-SID and EPE-SID into the Reply Path TLV, enabling traceroute without full topology knowledge at the head-end.
4+
section: "5.5"
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__design-rationale-the-mechanism-uses-mpls-data-plane-forwarding-for.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9716
2+
kind: design-rationale
3+
summary: The mechanism uses MPLS data plane forwarding for echo replies so that any MPLS-capable node can forward echo reply packets in the fast path without changes to the forwarding plane. This is preferred over RFC 7743's relay-based solution, which requires slow-path or bump-in-the-wire processing at every relay node.
4+
section: "1"
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__design-rationale-when-the-srgb-is-not-uniform-across-the.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9716
2+
kind: design-rationale
3+
summary: When the SRGB is not uniform across the network, it is RECOMMENDED to add Type-C or Type-D segments (carrying node IP addresses) rather than Type-A (label-only) segments, because downstream nodes may not know the SRGB of a remote domain needed to translate an IP address to a label.
4+
section: 5.5.1
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__interoperability-note-handling-end-to-end-mpls-oam-for-networks.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9716
2+
kind: interoperability-note
3+
summary: Handling end-to-end MPLS OAM for networks consisting of mixed IPv4-only and IPv6-only domains is out of scope. Dual-stack deployment is recommended, using end-to-end IPv6 addresses for MPLS ping and traceroute procedures in such environments.
4+
section: "3"
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__interoperability-note-the-document-reuses-sub-tlv-code-points-from.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9716
2+
kind: interoperability-note
3+
summary: The document reuses sub-TLV code points from the registry common to TLVs 1, 16, and 21, but defines Type-A, Type-C, and Type-D sub-TLV usage only for TLV 21 (Reply Path TLV). If these sub-TLVs appear in TLV 1 or 16, error codes per RFC 8029 MUST be returned, preventing misuse in other LSP ping contexts.
4+
section: "4"
5+
topics:
6+
- routing
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__normative-requirement-an-asbr-that-receives-an-echo-request-from.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9716
2+
kind: normative-requirement
3+
summary: An ASBR that receives an echo request from a neighbor in the same AS MUST look at the Reply Path TLV; if it contains a Type-C/Type-D segment, it MUST convert it to a Type-A segment by deriving a label from its own SRGB, and MUST set the Reply Path Return Code to 0x0006.
4+
section: 5.5.1
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__normative-requirement-if-the-optional-mpls-sid-is-present-in.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9716
2+
kind: normative-requirement
3+
summary: If the optional MPLS SID is present in Type-C/Type-D segments, the node sending the echo reply MUST use the SID to encode the echo reply with MPLS labels. If the MPLS SID does not match the IPv4 or IPv6 address field, log information should be generated.
4+
section: "5.3"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__normative-requirement-if-the-reply-path-return-code-is-use.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9716
2+
kind: normative-requirement
3+
summary: If the Reply Path Return Code is 'Use Reply Path TLV from this echo reply for building the next echo request' (0x0006), the Reply Path TLV from the echo reply MUST be sent in the next echo request with the TTL incremented by 1. If the TTL is already 255, the traceroute procedure MUST be ended with an appropriate log message.
4+
section: "5.4"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__normative-requirement-if-the-responder-does-not-support-reply-mode.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9716
2+
kind: normative-requirement
3+
summary: If the responder does not support Reply Mode 5 or the echo request contains a malformed Segment sub-TLV (e.g., incorrect length field), an echo reply MUST be sent with Return Code set to 'Malformed echo request received' and Subcode set to zero.
4+
section: "5.2"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9716__normative-requirement-if-these-segment-sub-tlvs-type-a-type.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9716
2+
kind: normative-requirement
3+
summary: If these Segment sub-TLVs (Type-A, Type-C, Type-D) appear in TLVs 1 or 16 (rather than TLV 21), appropriate error codes MUST be returned as defined in RFC 8029.
4+
section: "4"
5+
rfc2119_level: MUST
6+
topics:
7+
- routing
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

0 commit comments

Comments
 (0)