Skip to content

Commit b1fdfd1

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 203 new elements (2026-07-06)
1 parent 5946f1b commit b1fdfd1

203 files changed

Lines changed: 1871 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-8759__design-rationale-existing-rtp-text-payload-types-rfc-4103-for.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8759
2+
kind: design-rationale
3+
summary: Existing RTP text payload types (RFC 4103 for text conversation, RFC 4396 for 3GPP timed text) lack the formatting capabilities required for television closed-caption workflows. The absence of a suitable format for TTML or generic XML necessitated this new payload format.
4+
section: "3.1"
5+
topics:
6+
- rtp
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__design-rationale-the-rtp-timestamp-does-not-encode-constant-duration.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8759
2+
kind: design-rationale
3+
summary: The RTP Timestamp does not encode constant-duration media; it encodes the document epoch. Combined with possible fragmentation across packets, the RTCP jitter calculation is rendered unusable for this payload format.
4+
section: "6"
5+
topics:
6+
- rtp
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__interoperability-note-this-payload-format-uses-the-existing-application-ttml.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8759
2+
kind: interoperability-note
3+
summary: This payload format uses the existing 'application/ttml+xml' media type rather than defining a new one; the clock rate parameter is specific to RTP usage and has not been added to the media type definition because it is inapplicable outside RTP contexts.
4+
section: "11"
5+
topics:
6+
- rtp
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__normative-requirement-applications-implementing-this-standard-must-comply-with-rfc.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8759
2+
kind: normative-requirement
3+
summary: Applications implementing this standard MUST comply with RFC 8083 (RTP Circuit Breakers), with particular attention to Section 4.4 on Media Usability. Congestion control SHALL follow RFC 3550 and any applicable RTP profile.
4+
section: "10"
5+
rfc2119_level: MUST
6+
topics:
7+
- rtp
8+
- congestion
9+
- realtime
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__normative-requirement-documents-spread-across-multiple-rtp-packets-must-use.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8759
2+
kind: normative-requirement
3+
summary: Documents spread across multiple RTP packets MUST use the same timestamp but different consecutive Sequence Numbers. Sequential documents MUST NOT use the same timestamp.
4+
section: "4.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- rtp
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__normative-requirement-documents-using-character-encodings-where-characters-are-not.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8759
2+
kind: normative-requirement
3+
summary: Documents using character encodings where characters are not represented by a single byte MUST be serialised in big-endian (network byte) order.
4+
section: "4.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- rtp
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__normative-requirement-if-a-ttml-document-is-assessed-to-be.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8759
2+
kind: normative-requirement
3+
summary: If a TTML document is assessed to be invalid (including zero-length/empty documents), it MUST be discarded.
4+
section: "6"
5+
rfc2119_level: MUST
6+
topics:
7+
- rtp
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__normative-requirement-multiple-ttml-subtitle-streams-must-not-be-interleaved.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8759
2+
kind: normative-requirement
3+
summary: Multiple TTML subtitle streams MUST NOT be interleaved in a single RTP stream.
4+
section: "5"
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- rtp
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__normative-requirement-the-document-epoch-e-must-be-set-equal.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8759
2+
kind: normative-requirement
3+
summary: The document epoch E MUST be set equal to the RTP Timestamp in the header of the packet carrying the TTML document; computed TTML media times are offset relative to E.
4+
section: "6"
5+
rfc2119_level: MUST
6+
topics:
7+
- rtp
8+
- realtime
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8759__normative-requirement-the-length-of-user-data-words-must-match.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8759
2+
kind: normative-requirement
3+
summary: The length of User Data Words MUST match the value specified in the Length field.
4+
section: "4.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- rtp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

0 commit comments

Comments
 (0)