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
Owner

A landscape survey for wai/research/ — not a normative extension, nothing implemented.

How it was made. A global sweep across standards bodies (SC 29 WG 2/3/4/5, ITU-T SG21/JVET, IETF AVTCORE/MOQ/SCITT/COSE/GREEN, AMWA, C2PA, Fórum SBTVD/ABNT, Komdigi, WorldDAB) including non-English primary sources, then two adversarial verification lenses — reality (does the designation exist, at the stage and with the content claimed) and bearing (is there something to register, bind or specify against, and is it already in the tree under another name).

71 candidates verified → 19 survived → 52 refuted. The refuted ones are deliberately absent, with their failure modes recorded so they are not re-litigated.

The uncomfortable findings — §3 is the point of the document

  • §3.1 "The wire carries instructions" is not novel. ISO/IEC 23001-16:2021 ratified derived visual tracks — a track carrying a derivation graph the receiver evaluates — five years ago, inside ISOBMFF. The honest, narrower claim: what Part 16 leaves unspecified is a byte-exact determinism contract per operation and a signed receipt binding the executed graph to measured joules.
  • §3.2 determinism-tiers.md has a live conformance hole, twice over. H.274 nnpfa post-filters change output pixels after a conformant decode; and an object honouring a power-saving hint can still claim byte-exactness. A defect in our own shipped text, no external dependency — ranked #1 for that reason.
  • §3.4 A receipt does not travel with its object; a hard container-scoped binding dies at the first re-encode, which is normal distribution.
  • §3.6 No transparency log, no key discovery — every WAI signature presumes the verifier already holds the key.

Energy, stated correctly rather than flatteringly

The field is contested, not empty: ISO/IEC 23001-11 (3rd ed. in force) actuates joules in-band before decode; 23001-19 carries it in ISOBMFF/DASH; draft-ietf-avtcore-rtcp-green-metadata makes it a request/commit exchange; IETF GREEN models device energy with a graded accuracy taxonomy. None carries a measured per-object figure bound to a reproducible output under a signature. That remains ours — flanked on both sides, which makes the work reconciliation rather than invention.

One item has a deadline

ISO/IEC 23888-6 (Media authenticity and provenance indication) — CfP responses due 13 January 2027 to MPEG 157, Brisbane; then CD/CDAM at 158, DIS at 159, FDIS early 2028. The only square in the survey where our mechanism could enter normative text instead of being registered after someone else's.

Verification status

Five flagged designations resolved; one corrected (there is no confirmable MPEG-AI Part 7); one narrowed (H.274 signatures survive remux, not transcode — they are computed over NAL units). Two flags remain open by design: the NNC signed-data-unit amendment is uncorroborated, and ABNT NBR 25608 is paywalled and was read through public companions only.

Nothing here is a conformance statement about WAI. §9 lists what would falsify each conclusion.

🤖 Generated with Claude Code

A landscape survey for `wai/research/` — not a normative extension, nothing implemented. **How it was made.** A global sweep across standards bodies (SC 29 WG 2/3/4/5, ITU-T SG21/JVET, IETF AVTCORE/MOQ/SCITT/COSE/GREEN, AMWA, C2PA, Fórum SBTVD/ABNT, Komdigi, WorldDAB) including non-English primary sources, then two adversarial verification lenses — *reality* (does the designation exist, at the stage and with the content claimed) and *bearing* (is there something to register, bind or specify against, and is it already in the tree under another name). **71 candidates verified → 19 survived → 52 refuted.** The refuted ones are deliberately absent, with their failure modes recorded so they are not re-litigated. ### The uncomfortable findings — §3 is the point of the document - **§3.1 "The wire carries instructions" is not novel.** ISO/IEC 23001-16:2021 ratified derived visual tracks — a track carrying a derivation graph the receiver evaluates — five years ago, inside ISOBMFF. The honest, narrower claim: what Part 16 leaves unspecified is a byte-exact determinism contract per operation and a signed receipt binding the executed graph to measured joules. - **§3.2 `determinism-tiers.md` has a live conformance hole, twice over.** H.274 `nnpfa` post-filters change output pixels *after* a conformant decode; and an object honouring a power-saving hint can still claim byte-exactness. A defect in our own shipped text, no external dependency — ranked #1 for that reason. - **§3.4** A receipt does not travel with its object; a hard container-scoped binding dies at the first re-encode, which is normal distribution. - **§3.6** No transparency log, no key discovery — every WAI signature presumes the verifier already holds the key. ### Energy, stated correctly rather than flatteringly The field is **contested, not empty**: ISO/IEC 23001-11 (3rd ed. in force) actuates joules in-band *before* decode; 23001-19 carries it in ISOBMFF/DASH; `draft-ietf-avtcore-rtcp-green-metadata` makes it a request/commit exchange; IETF GREEN models device energy with a graded accuracy taxonomy. None carries a **measured per-object figure bound to a reproducible output under a signature**. That remains ours — flanked on both sides, which makes the work reconciliation rather than invention. ### One item has a deadline **ISO/IEC 23888-6** (Media authenticity and provenance indication) — CfP responses due **13 January 2027** to MPEG 157, Brisbane; then CD/CDAM at 158, DIS at 159, FDIS early 2028. The only square in the survey where our mechanism could enter normative text instead of being registered after someone else's. ### Verification status Five flagged designations resolved; **one corrected** (there is no confirmable MPEG-AI *Part 7*); **one narrowed** (H.274 signatures survive remux, not transcode — they are computed over NAL units). Two flags remain open by design: the NNC signed-data-unit amendment is uncorroborated, and ABNT NBR 25608 is paywalled and was read through public companions only. Nothing here is a conformance statement about WAI. §9 lists what would falsify each conclusion. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
wai/research: 2030 transport landscape — what the field ratified while we weren't looking
All checks were successful
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 3s
standards workspaces build + test / aac-rs (pull_request) Successful in 38s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 40s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m47s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m17s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 2m34s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m15s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 47s
standards workspaces build + test / map-rs (pull_request) Successful in 48s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m1s
standards workspaces build + test / mesh-rs (pull_request) Successful in 39s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m31s
standards workspaces build + test / openpay (pull_request) Successful in 2m29s
standards workspaces build + test / arl-rs (pull_request) Successful in 8m28s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 6m48s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 7m13s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 8m45s
standards workspaces build + test / sense-rs (pull_request) Successful in 8m36s
c56970150d
A landscape survey for the WAI tree, in the register of the existing research
docs. Not a normative extension; nothing here is implemented.

Produced by a global sweep across standards bodies (SC 29 WG 2/3/4/5, ITU-T
SG21/JVET, IETF AVTCORE/MOQ/SCITT/COSE/GREEN, AMWA, C2PA, Fórum SBTVD/ABNT,
Komdigi, WorldDAB) including non-English primary sources, then two adversarial
verification lenses: reality (does the designation exist, at the stage and with
the content claimed) and bearing (is there something to register, bind or
specify against, and is it already in the tree under another name). Seventy-one
candidates reached verification; nineteen survived; fifty-two were refuted and
are deliberately absent, with their failure modes recorded so they are not
re-litigated.

The uncomfortable findings, which are the point of the document:

  * §3.1 "The wire carries instructions" is NOT novel. ISO/IEC 23001-16:2021
    ratified derived visual tracks — a track carrying a derivation graph the
    receiver evaluates — five years ago, inside ISOBMFF. The honest claim is
    narrower: what Part 16 leaves unspecified is a byte-exact determinism
    contract per operation and a signed receipt binding the executed graph to
    measured joules.
  * §3.2 determinism-tiers.md has a live conformance hole, twice over — H.274
    NNPFA post-filters change output pixels after a conformant decode, and an
    object honouring a power-saving hint can still claim byte-exactness. This is
    a defect in our own shipped text with no external dependency, and it is
    ranked first in the queue for that reason.
  * §3.4 A receipt does not travel with its object. A hard container-scoped
    binding dies at the first re-encode, which is normal distribution.
  * §3.6 No transparency log, no key discovery. Every WAI signature presumes the
    verifier already holds the key.

Energy is stated correctly rather than flatteringly: the field is contested, not
empty. ISO/IEC 23001-11 (3rd ed. in force) actuates joules in-band before decode;
23001-19 carries it in ISOBMFF/DASH; the AVTCORE RTCP draft makes it a
request/commit exchange; IETF GREEN models device energy with a graded accuracy
taxonomy. What none of them carries is a measured per-object figure bound to a
reproducible output under a signature. That remains our lane — flanked on both
sides, which makes the work reconciliation rather than invention.

One item has a deadline: ISO/IEC 23888-6 (Media authenticity and provenance
indication), CfP responses due 13 January 2027 to MPEG 157. It is the only
square in the survey where our mechanism could enter normative text instead of
being registered after someone else's.

Verification pass recorded in the provenance note: five flagged designations
resolved, one corrected (there is no confirmable MPEG-AI Part 7), one narrowed
(H.274 signatures survive remux, not transcode — they are computed over NAL
units). Two flags remain open by design and are listed in §9.5.

Co-Authored-By: Claude Opus 5 <[email protected]>
wai/research: add §4.4 — the MoQ streaming-format slot the sweep missed
Some checks failed
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 3s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m47s
standards workspaces build + test / aac-rs (pull_request) Successful in 52s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m14s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m10s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m26s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m0s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m31s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 4m31s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 45s
standards workspaces build + test / map-rs (pull_request) Successful in 45s
standards workspaces build + test / mesh-rs (pull_request) Successful in 38s
standards workspaces build + test / arl-rs (pull_request) Successful in 8m44s
standards workspaces build + test / openpay (pull_request) Failing after 19m8s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 9m17s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 9m8s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 9m35s
standards workspaces build + test / sense-rs (pull_request) Successful in 8m45s
3c2ac875ca
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]>
dcharlot force-pushed wai/2030-transport-landscape from 3c2ac875ca
Some checks failed
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 3s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m47s
standards workspaces build + test / aac-rs (pull_request) Successful in 52s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m14s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m10s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m26s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m0s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m31s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 4m31s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 45s
standards workspaces build + test / map-rs (pull_request) Successful in 45s
standards workspaces build + test / mesh-rs (pull_request) Successful in 38s
standards workspaces build + test / arl-rs (pull_request) Successful in 8m44s
standards workspaces build + test / openpay (pull_request) Failing after 19m8s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 9m17s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 9m8s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 9m35s
standards workspaces build + test / sense-rs (pull_request) Successful in 8m45s
to 584a9bd735
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
2026-09-10 10:25:41 -04:00
Compare
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!80
No description provided.