25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
## Why
|
||
|
||
The production gateway cannot forward complete encoded video frames larger than 18,864 bytes, and its native video queue is bounded only by entry count. Realistic Phase 3C frame distributions therefore fail before QUIC delivery or can consume unreviewed memory.
|
||
|
||
## What Changes
|
||
|
||
- Implement the Protocol-owned complete-frame datagram profile and independent bounded client reassembly.
|
||
- Relay full recovered Apollo frames without mutation or unrelated sequence splitting.
|
||
- Bound native video queuing by frame count, encoded bytes, and residence time with latest-frame replacement and truthful drops.
|
||
- Preserve independent audio and event bounds and all no-transcode/provider isolation rules.
|
||
|
||
## Capabilities
|
||
|
||
### New Capabilities
|
||
|
||
- `complete-encoded-frame-transport`: Production fragmentation, reassembly, and byte/latency/count-bounded native frame queuing.
|
||
|
||
### Modified Capabilities
|
||
|
||
None.
|
||
|
||
## Impact
|
||
|
||
Gateway framing, native Apollo media queues, QUIC send/receive tests, telemetry, and bounded resource checks. No new dependency or Server change. Requirements: P3C-006–P3C-009, P3C-025, P3C-026, P3C-028, P3C-030, P3C-038, VER-001, VER-006, VER-010.
|