28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
## Context
|
|
|
|
RC8's canonical requirement names a terminal receipt, but its frame grammar, fixed fixture, and all Protocol validators reject the exact receipt accepted by Data Plane. The existing VGF1 envelope and generated conformance machinery already cover the required boundary.
|
|
|
|
## Goals / Non-Goals
|
|
|
|
**Goals:**
|
|
|
|
- Make one fixed empty client-direction type `0x03` receipt valid in every Protocol validator.
|
|
- Preserve all existing VGF1 direction, type, size, and payload validation.
|
|
- Make independent clients able to construct the receipt from Protocol-owned evidence.
|
|
|
|
**Non-Goals:**
|
|
|
|
- No new envelope, feedback framework, transport, or acknowledgement protocol.
|
|
- No change to gateway-to-client termination, rumble, HDR, client IDR, or FEC payloads.
|
|
|
|
## Decisions
|
|
|
|
- Extend the existing VGF1 grammar and fixed TSV corpus; generated and native validators remain consumers of that single contract.
|
|
- Reserve type `0x03` only for client direction with a zero-length payload. Direction and exact-length checks remain prior trust-boundary requirements.
|
|
- Publish the verified change as a new immutable version; RC8 remains unchanged.
|
|
|
|
## Risks / Trade-offs
|
|
|
|
- [A validator diverges from the fixed corpus] → Require normalized cross-language conformance in `make verify`.
|
|
- [Receipt handling is accepted outside terminal state] → Keep state authorization in Data Plane; Protocol validates only the wire shape.
|