open-standards/wai/live-conformance/http-egress

live-conformance/http-egress — a live HTTP egress's traces

The corpus of extensions/live-http-egress.md §12, in one file, vectors.json.

Provenance. Generated here by wai_live_egress_vectors gen (wai-rs, feature live_egress), from an Ed25519 key on a fixed 32-byte seed (0x17 thirty-two times; one case signs a group with another, 0x71 thirty-two times, and one a running receipt), a constant clock, and synthetic CMAF: headers and chunks that hold the boxes an egress reads (§3.1) and a few payload bytes written by the generator. No media and no input from outside this repository; nothing in it decodes.

• traces are the base traces by name, each in §10.1's form: a room's video (12,800 ticks a second, five objects of 200 ms to a group) and audio (48,000, the same cut), what arrived of them, and a client's requests with what the reference egress answered.
• cases name a trace, or a base and the edits that plant a fault in it (§12), and expect: ok, or the reason of §11 a checker refuses it with. A case with no base also states withheld, each object the egress withheld with its reason of §3.3, and reanchored, how often a receipt chain was anchored again; and, where its trace takes running receipts (it has a room), running_refused, each running receipt refused with its reason of §3.5.

The base traces plant what a room can send: receipts after their objects, a changed byte, a proof that does not reach its root, receipts missing, signed by another key and unreadable, a skipped group, a missing object, a group that does not start at a sync sample, one that starts early, an object that is not CMAF, a long part, a long group, a short group (off the grid), unlinked receipts, and a room's breaks; and, for a publisher that signs running receipts (§3.5), a run that serves each part as it arrives, receipts that contradict their run, a running receipt that skips an object, one of another group, one that continues another group's leaves, a wrong root, an object stated twice, records that are not the owner's word about the track, a changed byte, and a group whose receipts never come. The fault cases plant what an egress can do wrong: a part listed before it was held, a blocking reload answered early, a withheld object served and listed, a part served before its receipts, a part served that its group's run does not cover, a segment sent ahead and ended while open, and changed playlists, MPDs, bytes and sidecars.

Eleven traces carry a track of WAI envelopes (§4.4) beside the sound: small WAI1 envelopes the generator writes, of capabilities whose payloads are a few bytes and decode to nothing. One is served as Mode F; the others plant an envelope changed after signing, half an envelope, a capability the catalog does not list, another media class, two objects in a group, a track that states no time (alone and beside a served one), a frame stream and a layer track. Their fault cases plant a sample that is not the held envelope, an mdat with more than it, and a header, a playlist and an MPD that are not the state's.

cargo run --no-default-features --features live_egress --bin wai_live_egress_vectors -- verify live-conformance/http-egress
python3 -I live-conformance/http_egress_verify.py live-conformance/http-egress