Skip to content

Commit e656167

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 168 new elements (2026-05-24)
1 parent 0d92209 commit e656167

168 files changed

Lines changed: 1584 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-2507__design-rationale-a-soft-state-scheme-using-periodic-header-refreshes.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2507
2+
kind: design-rationale
3+
summary: A soft-state scheme using periodic header refreshes with exponential backoff (compression slow-start) is chosen over a hard-state scheme requiring acknowledgment of full headers. The soft-state approach needs no handshake, works over simplex links (satellite, cable TV), and handles mobiles going out of range transparently, at the cost of slightly higher bandwidth for header refreshes.
4+
section: 3.3.4
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__design-rationale-after-a-context-change-in-a-non-tcp.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2507
2+
kind: design-rationale
3+
summary: After a context change in a non-TCP stream, full headers are sent with an exponentially increasing interval (F_PERIOD starts at 1, doubles each time, up to F_MAX_PERIOD=256). The default F_MAX_PERIOD of 256 means full headers contribute less than 1.4 bits to the average header size at steady state, a negligible overhead.
4+
section: 3.3.1
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__design-rationale-the-fragment-header-identification-field-is-classified-as.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2507
2+
kind: design-rationale
3+
summary: The Fragment Header Identification field is classified as RANDOM rather than NOCHANGE to avoid triggering a compression slow-start for every new original IP packet. Fragment streams are identified by source and destination address alone, not the Identification field.
4+
section: "7.6"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__design-rationale-the-r-octet-carrying-ecn-bits-bits-6.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-2507
2+
kind: design-rationale
3+
summary: The R-octet carrying ECN bits (bits 6–7 of TOS/Traffic Class) and the TCP Reserved field MUST NOT update the context because if it did, the TCP checksum would no longer reliably catch erroneously decompressed headers. ECN bits are expected to change frequently due to Explicit Congestion Notification.
4+
section: "6"
5+
topics:
6+
- ip
7+
- tcp
8+
- ecn
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__interoperability-note-header-compression-requires-that-the-link-layer-provide.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2507
2+
kind: interoperability-note
3+
summary: Header compression requires that the link layer provide accurate packet length and add no deliverable padding to payloads, and that UDP packets and tunneled packets contain no extra padding. These properties are needed to infer length field values and embed CID and generation in full headers without increasing packet size.
4+
section: "5.3"
5+
topics:
6+
- ip
7+
- udp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__interoperability-note-on-multi-access-links-multiple-compressors-share-a.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2507
2+
kind: interoperability-note
3+
summary: On multi-access links, multiple compressors share a single decompressor's CID space, creating collision risk. Resolution approaches include per-compressor CID namespaces (using link-layer sender identity) or including a compressor-assigned enumeration number as part of the CID, which requires the 16-bit CID size.
4+
section: "5.1"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__interoperability-note-this-compression-scheme-is-compatible-with-tcp-s.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2507
2+
kind: interoperability-note
3+
summary: 'This compression scheme is compatible with TCP''s repair mechanisms: the compressor inspects TCP headers to detect retransmissions and sends a full header on retransmit, assuming the retransmission was caused by mismatched compression state. The compression method does not require that all packets in the same stream traverse the compressed link.'
4+
section: "3.2"
5+
topics:
6+
- ip
7+
- tcp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__interoperability-note-when-an-esp-header-is-used-in-tunnel.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-2507
2+
kind: interoperability-note
3+
summary: When an ESP header is used in tunnel mode, inner IP packet headers MAY be compressed before encryption at the tunnel entry point. The reordering mechanisms from section 11 MUST also be applied, since packets can be reordered inside the tunnel.
4+
section: "7.10"
5+
topics:
6+
- ip
7+
- ipsec
8+
- vpn
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__normative-requirement-a-compressor-must-ensure-that-the-generation-value.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2507
2+
kind: normative-requirement
3+
summary: A compressor MUST ensure that the generation value for a non-TCP CID does not wrap around in less than MIN_WRAP seconds. The generation MUST NOT be reset when a CID is reused for a new packet stream; instead it MUST be incremented by one.
4+
section: "8"
5+
rfc2119_level: MUST
6+
topics:
7+
- ip
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2507__normative-requirement-a-decompressor-should-not-send-a-context-state.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-2507
2+
kind: normative-requirement
3+
summary: A decompressor SHOULD NOT send a CONTEXT_STATE packet every time a compressed packet refers to an invalid context; instead it should rate-limit such transmissions. Multiple invalid CIDs SHOULD be batched into a single CONTEXT_STATE packet rather than sending separate packets.
4+
section: "10.2"
5+
rfc2119_level: SHOULD NOT
6+
topics:
7+
- ip
8+
- tcp
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-05-24"

0 commit comments

Comments
 (0)