25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
## Why
|
|
|
|
The RC9 datagram contract limits one encoded media unit to 18,864 bytes, below the bounded complete frames required by the reviewed Apollo adapter and the fixed Phase 3C profiles. A new immutable Protocol release must define complete-frame transport and reassembly bounds before consumers can relay realistic encoded frames without mutation.
|
|
|
|
## What Changes
|
|
|
|
- Add a versioned PMTU-safe media datagram header with wider fragment fields.
|
|
- Bound complete encoded frames, fragments, reassembly state, duplicates, reorder, timeout, and allocation.
|
|
- Preserve RC9 datagram-v1 unchanged and require explicit negotiation of the new framing profile.
|
|
- Add fixed Python, Go, Rust, and Swift conformance vectors for valid and malformed framing.
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
|
|
- `gateway-media-framing`: Versioned complete encoded-frame fragmentation and bounded reassembly contract.
|
|
|
|
### Modified Capabilities
|
|
|
|
None.
|
|
|
|
## Impact
|
|
|
|
Protocol framing documentation, registries, capability schema, fixed conformance fixtures, validators, generated Go/Rust/Swift bindings, and immutable consumer versioning. Requirements: SYS-002, SYS-003, P3C-006, P3C-007, P3C-008, P3C-030, P3C-038, VER-001, VER-002, VER-028.
|