Skip to content

Commit 9e3bed0

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 232 new elements (2026-07-12)
1 parent 7d02c4c commit 9e3bed0

232 files changed

Lines changed: 2185 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-9673__design-rationale-high-speed-routers-cannot-process-hop-by-hop.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9673
2+
kind: design-rationale
3+
summary: High-speed routers cannot process Hop-by-Hop options at Full Forwarding Rate, so they are sent to the Slow Path or Control Plane, creating DoS vulnerability and packet reordering within flows. These problems motivate relaxing the mandatory processing requirement.
4+
section: "4"
5+
topics:
6+
- ip
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__design-rationale-new-hop-by-hop-options-should-set-action.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9673
2+
kind: design-rationale
3+
summary: New Hop-by-Hop options should set action bits to '00' so that routers that do not recognize the option can skip it rather than discard the packet, enabling incremental deployability where early adopters gain benefit even when some paths do not support the option.
4+
section: "6"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__design-rationale-rfc-8200-s-text-allowing-routers-to-skip.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9673
2+
kind: design-rationale
3+
summary: RFC 8200's text allowing routers to skip Hop-by-Hop processing was not intended to change processing semantics but documented existing Internet behavior as a constraint on standardization. This document now formalizes practical procedures that make Hop-by-Hop options deployable.
4+
section: "4"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__design-rationale-the-racing-technique-sending-a-test-packet-with.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9673
2+
kind: design-rationale
3+
summary: The 'racing' technique—sending a test packet with required Hop-by-Hop options first, then waiting for acknowledgment before sending data packets with the option—enables path discovery for option support without requiring all routers to implement the option.
4+
section: "6.1"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__design-rationale-the-router-alert-option-is-kept-as-the.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9673
2+
kind: design-rationale
3+
summary: The Router Alert Option is kept as the single Control Plane exception rather than deprecated because it could support future functions requiring Control Plane processing, representing a reasonable compromise for future flexibility while applying strict protections per RFC 6398.
4+
section: 5.2.1
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__interoperability-note-measurements-from-2015-rfc-7872-and-2023-confirm.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9673
2+
kind: interoperability-note
3+
summary: Measurements from 2015 (RFC 7872) and 2023 confirm that IPv6 packets containing Hop-by-Hop Options headers are dropped by many Internet paths and transit ASes. Packets with Extension Headers totaling less than 40 bytes have higher probability of successful transmission.
4+
section: "4"
5+
topics:
6+
- ip
7+
- measurement
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__interoperability-note-routers-configured-to-drop-packets-with-hop-by.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9673
2+
kind: interoperability-note
3+
summary: Routers configured to drop packets with Hop-by-Hop Options headers (per RFC 9288) to protect downstream devices are an explicit exception to the SHOULD-process rule, maintaining backward compatibility with networks that filter Extension Headers.
4+
section: "5.1"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__interoperability-note-the-hop-by-hop-options-header-is-intended.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-9673
2+
kind: interoperability-note
3+
summary: The Hop-by-Hop Options header is intended to be processed by all destinations including hosts, but constrained hosts are an acceptable exception; any destination that does not process the header MUST still process the remainder of the packet normally.
4+
section: "5.1"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__normative-requirement-a-node-configured-to-process-a-router-alert.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-9673
2+
kind: normative-requirement
3+
summary: A node configured to process a Router Alert Option MUST protect itself from an infrastructure attack that could result from processing in the Control Plane, using some combination of access control lists, rate limiting, or other methods per RFC 6398.
4+
section: 5.2.1
5+
rfc2119_level: MUST
6+
topics:
7+
- ip
8+
- security
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-9673__normative-requirement-a-router-must-not-drop-a-packet-solely.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-9673
2+
kind: normative-requirement
3+
summary: A router MUST NOT drop a packet solely because it contains an Extension Header carrying Hop-by-Hop options. Even if a router does not process the Hop-by-Hop Options header, it MUST forward the packet normally based on the remaining Extension Header(s).
4+
section: "5.1"
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- ip
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-12"

0 commit comments

Comments
 (0)