25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
## Why
|
|
|
|
Provider work identifies an immutable stream-policy version but omits the effective settings, allowing a gateway to launch Apollo with unrelated hard-coded media parameters.
|
|
|
|
## What Changes
|
|
|
|
- Add the effective resolution, frame rate, codec, selected bitrate, and audio policy to authenticated provider work.
|
|
- Represent decode support as an ordered set of registered profiles and generate one canonical intersection operation for consumers.
|
|
- Require generated Go, Rust, and Swift bindings to validate the same bounded stream-policy contract.
|
|
- Keep the new contract unpublished until a new immutable Protocol version is separately authorized.
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
|
|
- `provider-stream-policy`: Authenticated provider work carries the exact effective stream policy consumed by the provider launch, and registered peers negotiate that policy through the shared ordered profile intersection.
|
|
|
|
### Modified Capabilities
|
|
|
|
None.
|
|
|
|
## Impact
|
|
|
|
The control-v1 schema, generated bindings, conformance fixtures, and downstream Server and Data Plane consumers require coordinated local updates. RC6 remains immutable and unchanged.
|