Skip to content

Commit 0904774

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

233 files changed

Lines changed: 2218 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-8684__design-rationale-address-ids-are-used-instead-of-raw-ip.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8684
2+
kind: design-rationale
3+
summary: Address IDs are used instead of raw IP addresses to identify endpoints, so that address removal and subflow association work correctly through NATs that change the source IP address. The Address ID is locally assigned by the sender and must map uniquely to a source address.
4+
section: "2.7"
5+
topics:
6+
- multipath
7+
- tcp
8+
- nat
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__design-rationale-mptcp-uses-a-shared-receive-window-across-all.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8684
2+
kind: design-rationale
3+
summary: 'MPTCP uses a shared receive window across all subflows rather than per-subflow windows to prevent subflow starvation: with per-subflow windows, slower or temporarily stalled subflows would consume receive window that faster subflows could use, reducing aggregate throughput.'
4+
section: 3.3.4
5+
topics:
6+
- multipath
7+
- tcp
8+
- congestion
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__design-rationale-the-data-sequence-mapping-covers-a-range-of.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8684
2+
kind: design-rationale
3+
summary: The Data Sequence Mapping covers a range of bytes (subflow sequence space + length) rather than using per-packet signaling, to handle TCP segmentation offloading on NICs and Performance Enhancing Proxies that split or coalesce segments independently of the stack generating the data.
4+
section: 3.3.1
5+
topics:
6+
- multipath
7+
- tcp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__interoperability-note-mptcp-v1-is-not-backward-compatible-with-v0.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8684
2+
kind: interoperability-note
3+
summary: MPTCP v1 is not backward compatible with v0 (RFC 6824). When a v1 initiator contacts a v0-only listener, the listener ignores the v1 SYN (which lacks a key) and replies without MP_CAPABLE. The v1 initiator MAY then retry with v0 if it supports it, or fall back to plain TCP.
4+
section: "3.1"
5+
topics:
6+
- multipath
7+
- tcp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__normative-requirement-a-crypto-algorithm-must-be-specified-in-the.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8684
2+
kind: normative-requirement
3+
summary: A crypto algorithm MUST be specified in the MP_CAPABLE flags (bits D–H). If all five flag bits are 0, the MP_CAPABLE option MUST be treated as invalid and ignored, falling back to regular TCP. The responder selects from the initiator's proposal by setting exactly one bit.
4+
section: "3.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- multipath
8+
- tcp
9+
- crypto
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__normative-requirement-a-host-must-not-close-all-functioning-subflows.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8684
2+
kind: normative-requirement
3+
summary: A host MUST NOT close all functioning subflows unless all outstanding data has been DATA_ACKed or the DATA_FIN segment is the only outstanding segment. Once a DATA_FIN has been acknowledged, all remaining subflows MUST be closed with standard FIN exchanges.
4+
section: 3.3.3
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- multipath
8+
- tcp
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__normative-requirement-a-host-must-store-the-mappings-between-address.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8684
2+
kind: normative-requirement
3+
summary: A host MUST store the mappings between Address IDs and addresses for both itself and the remote host. The Address IDs of the initial subflow are implicit and have value zero.
4+
section: "3.2"
5+
rfc2119_level: MUST
6+
topics:
7+
- multipath
8+
- tcp
9+
- nat
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__normative-requirement-a-host-s-mptcp-key-must-be-hard.yaml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
document: rfc-8684
2+
kind: normative-requirement
3+
summary: A host's MPTCP key MUST be hard to guess and MUST be unique across all current MPTCP connections on that host. An implementation SHOULD check its list of connection tokens for collisions before sending a key and generate a new key if a collision is found.
4+
section: "3.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- multipath
8+
- tcp
9+
- security
10+
- crypto
11+
extracted_by: claude-sonnet-4-6
12+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__normative-requirement-a-sender-must-not-change-a-declared-data.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8684
2+
kind: normative-requirement
3+
summary: A sender MUST NOT change a declared Data Sequence Mapping after it has been sent. A TCP subflow MUST NOT use the Urgent Pointer to interrupt an existing DSS mapping.
4+
section: 3.3.1
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- multipath
8+
- tcp
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8684__normative-requirement-an-implementation-must-not-use-the-rcv-wnd.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8684
2+
kind: normative-requirement
3+
summary: An implementation MUST NOT use the RCV.WND field of a TCP segment at the connection level if the segment does not also carry a DSS option with a Data ACK field. A receiver MUST NOT shrink the right edge of the receive window (DATA_ACK + receive window).
4+
section: 3.3.4
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- multipath
8+
- tcp
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

0 commit comments

Comments
 (0)