Skip to content

Commit aea2c3e

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 186 new elements (2026-07-06)
1 parent d17fbda commit aea2c3e

186 files changed

Lines changed: 1755 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-8817__design-rationale-the-number-of-frames-in-an-rtp-packet.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8817
2+
kind: design-rationale
3+
summary: The number of frames in an RTP packet is not transmitted explicitly; the receiver determines frame count by identifying each frame type and length from the rate code bits, then summing octets across the packet. This avoids a redundant count field.
4+
section: "3.3"
5+
topics:
6+
- rtp
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8817__design-rationale-the-preferred-tsvcis-packing-format-uses-mtc-tc.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8817
2+
kind: design-rationale
3+
summary: The preferred TSVCIS packing format uses MTC = TC − 15 (minimum parameter set is 15 octets) to extend the 6-bit MTC field's effective range to 77 octets; the alternate two-trailing-byte format accommodates all other NRL VDR configurations without an upper bound.
4+
section: "3.2"
5+
topics:
6+
- rtp
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8817__design-rationale-tsvcis-is-designed-as-an-augmentation-to-melpe.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8817
2+
kind: design-rationale
3+
summary: 'TSVCIS is designed as an augmentation to MELPe rather than a standalone codec: a complete TSVCIS speech frame always pairs TSVCIS augmented data with temporally matched MELPe 2400 bps parameters, enabling graceful fallback to MELPe alone on severely bandwidth-constrained links.'
4+
section: "2"
5+
topics:
6+
- rtp
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8817__interoperability-note-codb-for-melpe-600-bps-may-deviate-from.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8817
2+
kind: interoperability-note
3+
summary: CODB for MELPe 600 bps MAY deviate from Table 1 when bit 55 is used as an alternating 1/0 end-to-end framing bit; frame decoding remains distinct because CODA=0 alone identifies a 7-byte frame, and 600 bps can be deduced from the RTP timestamp and SDP negotiation.
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-8817__interoperability-note-the-sdp-ptime-parameter-cannot-be-used-to.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8817
2+
kind: interoperability-note
3+
summary: The SDP 'ptime' parameter cannot be used to specify the TSVCIS operating mode because certain values are ambiguous; for example, ptime=68 cannot distinguish one 67.5 ms frame from three 22.5 ms frames.
4+
section: "4.2"
5+
topics:
6+
- rtp
7+
- realtime
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8817__interoperability-note-tsvcis-rtp-packetization-of-melpe-follows-rfc-8130.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8817
2+
kind: interoperability-note
3+
summary: TSVCIS RTP packetization of MELPe follows RFC 8130, with RFC 8130 recommendations now treated as requirements. The bits previously labeled RSVA, RSVB, RSVC in RFC 8130 SHOULD be filled with rate code bits CODA, CODB, CODC as defined in Table 1.
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-8817__normative-requirement-any-unfilled-bits-in-the-last-octet-of.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-8817
2+
kind: normative-requirement
3+
summary: Any unfilled bits in the last octet of a byte-packed TSVCIS parameter field MUST be filled with zero. Parameters may be split between octets with the most significant bits in the earlier octet.
4+
section: "2"
5+
rfc2119_level: MUST
6+
topics:
7+
- rtp
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8817__normative-requirement-applications-using-rtp-over-udp-should-implement-their.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8817
2+
kind: normative-requirement
3+
summary: Applications using RTP over UDP SHOULD implement their own congestion control above the UDP layer per RFC 8085, and MAY also implement a transport circuit breaker per RFC 8083. TSVCIS supports congestion management by adjusting the target bitrate or frames per packet.
4+
section: "3.4"
5+
rfc2119_level: SHOULD
6+
topics:
7+
- rtp
8+
- congestion
9+
- udp
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8817__normative-requirement-frames-must-not-be-split-between-rtp-packets.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8817
2+
kind: normative-requirement
3+
summary: Frames MUST NOT be split between RTP packets. All MELPe frames within a single RTP packet MUST be of the same coder bitrate.
4+
section: "3.3"
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-8817__normative-requirement-if-the-bitrate-parameter-is-absent-from-the.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8817
2+
kind: normative-requirement
3+
summary: If the 'bitrate' parameter is absent from the SDP fmtp attribute, the fixed MELPe coder bitrate of 2400 bps MUST be used.
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"

0 commit comments

Comments
 (0)