wai/research: 2030 transport landscape — what the field ratified while we were not looking #80

Merged
dcharlot merged 1 commit from wai/2030-transport-landscape into main 2026-09-10 12:23:49 -04:00

2026-09-10

Transaction Science
wai/research: add §4.4 — the MoQ streaming-format slot the sweep missed
Some checks failed
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (pull_request) Successful in 1m0s
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 2s
standards workspaces build + test / aac-rs (pull_request) Successful in 1m6s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 37s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m46s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m13s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 3m2s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m9s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 48s
standards workspaces build + test / map-rs (pull_request) Successful in 40s
standards workspaces build + test / mesh-rs (pull_request) Successful in 33s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m1s
standards workspaces build + test / openpay (pull_request) Successful in 2m34s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m34s
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 30s
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 1m9s
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 14s
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 28s
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 40s
standards workspaces build + test / arl-rs (pull_request) Successful in 12m35s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 17m8s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 10m49s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 10m8s
standards workspaces build + test / sense-rs (pull_request) Successful in 9m52s
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 1m14s
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 19s
WAI conformance / cargo-class corpora · windows (pull_request) Has been cancelled
WAI conformance / cross-arch byte-equality · windows (pull_request) Has been cancelled
The automated survey found MoQ only through the confidentiality binding WAI
already has, and never reached the streaming-format layer. That layer is where
WAI actually belongs, and the slot is open.

MoQ separates transport (MOQT) from streaming format (MSF). The catalog's
`packaging` field names the format, and MSF fixes its value set — loc,
mediatimeline, eventtimeline, moqlog, moqmetrics, catalog — with no central
registry. That reads closed.

CMSF proves it is not. `draft-ietf-moq-cmsf` is a sibling I-D that declares
packaging value `cmaf`, states in §3.5.1 that it "extends the allowed packaging
values defined in [MSF]", inherits MSF wholesale, adds two track-level catalog
fields, and registers nothing: "This document has no IANA actions." A sibling
draft, no registry action, no permission sought — the cheapest standards path in
the survey, and already walked twice counting LOCMAF.

What CMSF did NOT take is the per-object slot. MSF §12 defines MSF Properties at
Track AND Object scope with an IANA property-type registry holding essentially
one entry (MSF_COMPRESSION); CMSF adds track-level fields only. A per-object
property carrying a content commitment and a measured-energy figure is the shape
jwp-receipts already has — the one place in this survey where WAI's existing
artifact fits an existing extension point without redesign.

Bounded by §4.5: what would be bound is field semantics and the rule over them,
never MOQT's extension-header byte encoding. And MOQT is pre-Last-Call, so the
honest form is a draft that tracks the transport, not a normative extension that
pins it.

Sourced from direct reads of draft-ietf-moq-msf and draft-ietf-moq-cmsf-00, not
from the sweep. The subsection says so, because the miss is itself informative: a
survey keyed to what is NEW can walk past a slot that is old, open and unclaimed.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-10 10:24:58 -04:00