Protocols, envelopes and standards that a WAI extension or registration binds. The chip
gives where WAI's binding stands, not the status of the external document.
The MoQ working group's milestone for sending MOQT to the IESG is December 2026. A
milestone is a date for requesting publication, not a publication: MOQT, MSF and their
companion drafts are Internet-Drafts, not RFCs.
MoQ working group charter and milestones.
draft-ietf-moq-transport-22 · IETF, MoQ working group
- Status
- Active Internet-Draft, working-group document
- Date
- 2026-10-01
WAI: In the standard WAI's MoQ Streaming Format extension declares how WAI is carried over MOQT; it tracks the draft, and its current text reads revision 22. Nothing in it depends on the revision that carries the objects: the reference implementation speaks revision 22 and, for interoperation, draft-ietf-moq-transport-18 and draft-ietf-moq-transport-16, chosen per session, and carries the extension's envelopes, receipt properties and receipts tracks unchanged on each (moq-streaming-format §6); its README records the other implementations' relays and clients it has run against, and when. The live rooms extensions name a room's tracks in MOQT's namespace (live-rooms §6) and bind a grant to a MOQT session (live-rooms §10.2 and §10.5); the reference browser client speaks revision 22. WAI defines no transport of its own.
Issuing body's page: datatracker.ietf.org
draft-ietf-moq-msf-01 · IETF, MoQ working group
- Status
- Active Internet-Draft, working-group document
- Date
- 2026-06-02
WAI: In the standard The same extension declares WAI's catalog fields, prefixed wai_, under MSF's rule for custom catalog fields. The live events extension carries a room's events as an MSF event timeline (live-events §8.1), and the timed text extension carries captions on the MoQ caption timelines built on it (timed-text §7).
Issuing body's page: datatracker.ietf.org
draft-ietf-moq-secure-objects-01 · IETF, MoQ working group
- Status
- Active Internet-Draft, working-group document; replaces draft-jennings-moq-secure-objects
- Date
- 2026-07-06
WAI: In the standard The confidentiality extension seals every object of an end-to-end encrypted room's media tracks as a secure object, as this draft specifies, on the objects of MOQT revision 22 (confidentiality §4); its §11 says how it reads the points where this draft and the documents beside it differ. Its corpus carries this draft's own test vectors.
Issuing body's page: datatracker.ietf.org
draft-jennings-moq-mocha-mls-keying-00 · IETF, individual submission
- Status
- Active Internet-Draft (individual)
- Date
- 2026-07-06
WAI: In the standard The confidentiality extension keys an end-to-end encrypted room from one MLS group as this draft keys secure objects: each epoch's exported secret, and from it each sender's track base key and Key ID (confidentiality §5.7).
Issuing body's page: datatracker.ietf.org
RFC 9420 · IETF
- Status
- Proposed Standard
- Date
- July 2023
WAI: In the standard The confidentiality extension keys each end-to-end encrypted room from one MLS group, whose credentials are the principals' room keys, whose one external sender is the room's clock and whose membership follows the room's grants and lifecycle (confidentiality §5).
Issuing body's page: rfc-editor.org
RFC 9605 · IETF
- Status
- Proposed Standard
- Date
- August 2024
WAI: In the standard A secure object, as the confidentiality extension seals one, is SFrame's authenticated encryption on an MoQ object, with SFrame's ciphersuites and key derivation (confidentiality §4). Its corpus carries this RFC's own test vectors.
Issuing body's page: rfc-editor.org
RFC 9725 · IETF
- Status
- Proposed Standard
- Date
- March 2025
WAI: In the standard The live ingest extension binds WHIP into a room's tracks: a publisher admitted under its room grant with a proof of its key, each frame one envelope on a MoQ track, its time placed on the room clock within a stated bound, and every group's receipts signed by the gateway as the first hop (live-ingest §3 to §11). Its reference gateway is in the standard's repository.
Issuing body's page: rfc-editor.org
draft-ietf-wish-whep-05 · IETF, WISH working group
- Status
- Active Internet-Draft, working-group document, in AD Evaluation, intended Proposed Standard
- Date
- 2026-10-12
WAI: In the standard The live ingest extension binds WHEP out of a room's tracks: a player joins at a group, and every object is verified against its receipt before the player gets it (live-ingest §9).
Issuing body's page: datatracker.ietf.org
draft-pantos-content-steering-04 · IETF, Independent Submission stream
- Status
- Active Internet-Draft, Independent Submission, intended Informational, sent to the RFC Editor; not an IETF standard
- Date
- 2026-05-01
- Source
- The energy-aware content steering extension reads revision 04, of 2026-05-01; the issuing body's current revision is 05, of 2026-05-18. The status is the document's.
WAI: In the standard The energy-aware content steering extension writes the steering manifest this draft defines, byte for byte, with the steering decision's URI in one key players ignore, and reads a client's steering request as this draft gives it (energy-steering §4 and §8).
Issuing body's page: datatracker.ietf.org
CTA-5004-B · CTA WAVE
- Status
- Published
- Date
- 2026-04-14
WAI: In the standard WAI's delivery telemetry maps its observations onto CMCD version 2 Event-mode reports (delivery-telemetry §3). The live metering extension carries them on the CMCD event timeline and in an application/cmcd batch into a room-session receipt's quality cell (live-metering §6), and the energy-aware content steering extension reads a client's buffer length and measured throughput from its CMCD keys (energy-steering §4.4).
Issuing body's page: cta.tech
RFC 9651 · IETF
- Status
- Proposed Standard; obsoletes RFC 8941
- Date
- September 2024
WAI: In the standard The energy-aware content steering extension reads a client's CMCD keys as an RFC 9651 Dictionary (energy-steering §4.4), and the live metering extension writes CMCD Event-mode reports as RFC 9651 Dictionaries in an application/cmcd batch (live-metering §6.3).
Issuing body's page: rfc-editor.org
AMWA BCP-004-01 · AMWA (Networked Media Open Specifications)
- Status
- Published Best Common Practice, v1.0.0; BCP-004-02 (Sender Capabilities) is also published
- Date
- v1.0.0
WAI: In the standard WAI's capability-constraints extension adopts the constraint-set grammar and register pattern of BCP-004-01 and BCP-004-02, so a sink can check a capability's parameters before dispatch. It does not adopt their transport or discovery model.
Issuing body's page: specs.amwa.tv
C2PA 2.4 · Coalition for Content Provenance and Authenticity (C2PA)
- Status
- Specification, version 2.4
- Date
- April 2026
WAI: In the standard WAI's reconstruction-binding and energy-binding extensions carry WAI assertions in a C2PA manifest for a decoded image, and the reference implementation signs such manifests. The live metering extension maps a room-session receipt onto the environmental-sustainability assertion (live-metering §7), the timed text extension carries a machine caption's disclosure in C2PA's terms (timed-text §10.3), and the live provenance extension writes live video provenance for room tracks and takes (section 19; see its row below). The synthesis, contribution and direction extensions compute a manifest's actions and AI disclosures from their records, and the deriving edge carries forward, by digest, every manifest store bound to or embedded in an input (deriving-edge §6.1).
Issuing body's page: spec.c2pa.org
C2PA 2.4, section 19 · Coalition for Content Provenance and Authenticity (C2PA)
- Status
- Added in version 2.3 (December 2025) and kept in version 2.4
- Date
- April 2026 (version 2.4)
WAI: In the standard The live provenance extension writes section 19's live video provenance as that section defines it, for a room's CMAF tracks and a device's CMAF take, by both methods: a manifest per segment that names its group's receipt, so the segment's hard binding and the receipt commit to the same chunks, and Verifiable Segment Info signed by a session key that also signs the group's receipts (live-provenance §3, §6 to §8). Its reference implementation writes and verifies both; capture binding §11 points to it for a take.
Issuing body's page: spec.c2pa.org
draft-pantos-hls-rfc8216bis-22 · IETF, Independent Submission stream
- Status
- Active Internet-Draft, Independent Submission, intended Informational, in RFC Editor processing; not an IETF standard
- Date
- 2026-05-01
WAI: In the standard The capability wai.video.manifest renders an HLS media playlist per session class and seals it in a signed receipt. For live rooms, the live events extension carries an event in an EXT-X-DATERANGE tag (live-events §8.3), the timed text extension maps captions and their disclosure onto HLS (timed-text §10.2), the live recording extension presents a recording (live-recording §7), the live ads extension writes each break as one interstitial date range of Appendix D with a preload date range of Appendix F (live-ads §5), and the energy-aware content steering extension writes the content-steering tag and its manifest (energy-steering §8).
Issuing body's page: datatracker.ietf.org
draft-ietf-green-power-and-energy-yang-04 · IETF, GREEN working group
- Status
- Active Internet-Draft, working-group document
- Date
- 2026-09-09
WAI: In the standard WAI's energy-measurement extension says how a WAI acquisition class relates to this draft's data-source-accuracy identities: an implementation that also reports under the network-layer model should derive its class from that model's identity and state which one. WAI does not adopt that model, and names the draft by its designation.
Issuing body's page: datatracker.ietf.org
draft-ietf-moq-cmsf-01 · IETF, MoQ working group
- Status
- Active Internet-Draft, working-group document
- Date
- 2026-06-03
WAI: In the standard The live provenance extension carries a room track packaged as CMAF under CMSF, each MoQ group one CMAF segment and each object one CMAF chunk, so a segment's C2PA hard binding and its group's receipt commit to the same chunks (live-provenance §3). WAI's MoQ Streaming Format extension points CMAF-packaged media to CMSF and does not replace it.
Issuing body's page: datatracker.ietf.org
WebCodecs · W3C, Media working group
- Status
- W3C Working Draft
- Date
- 2026-10-19
WAI: In the standard The browser sink extension puts an object to the browser's decoder only through a codec string the WebCodecs Codec Registry lists, asked with isConfigSupported, and takes that decoder only where it is exact for the tier the object needs (browser-sink §4). Every frame a page decodes carries a content binding, the content hash of the receipted object it came from, the group receipt it verified under and its tier, kept in a side table until the VideoFrame Metadata Registry lists the member; the registry entry is a draft, not filed (browser-sink §7 to §9).
Issuing body's page: w3.org
Media Capabilities · W3C, Media working group
- Status
- W3C Working Draft
- Date
- 2026-10-18
WAI: In the standard The browser sink extension asks Media Capabilities only about a codec string the browser answered supported, and reports a measured energy figure, with its acquisition class, beside powerEfficient, which stays the browser's word and is never read as energy (browser-sink §4.6 and §6).
Issuing body's page: w3.org
ETSI TS 104 002 V1.1.1 · ETSI (a PAS produced by DASH-IF)
- Status
- Published Technical Specification
- Date
- 2023-08
WAI: In the standard The forensic watermark extension has the edge that chooses A/B variants for a viewer, as this TS has an edge choose them, sign a record of each session, naming the TS's watermark token by its digest; it matches a recovered variant sequence to the one session that agrees with it, and opens that session's commitment to its grant for a third party (forensic-watermark §4 to §8). Lane A only: an end-to-end encrypted room has no edge that can mark it.
Issuing body's page: etsi.org
CTA-5006 · CTA WAVE
- Status
- Published (original edition)
- Date
- November 2022
WAI: In the standard WAI's delivery telemetry maps an origin's or edge's description of a WAI object onto CMSD-Static, with custom keys for its content hash, its layer and stage count and a delivery receipt's link hash, and each node's state onto CMSD-Dynamic, with the objects the node discarded on delivery timeout, all written as RFC 9651 Structured Field Values (delivery-telemetry §6). CMSD carries no joule figure, and telemetry binds no receipt to it (delivery-telemetry §1.3 and §6.5).
Issuing body's page: cta.tech
WebTransport; draft-ietf-webtrans-http3-16 · W3C, WebTransport working group; IETF, WEBTRANS working group
- Status
- W3C Candidate Recommendation Snapshot; the protocol is an Internet-Draft in working-group last call
- Date
- 2026-07-30 (W3C); 2026-07-06 (Internet-Draft)
WAI: In the standard The live rooms extension binds a grant's proof of possession to the URL of the WebTransport session a client opened (live-rooms §10.5), and the reference relay and browser client carry MOQT over WebTransport over HTTP/3 as revision 16 gives it.
Issuing body's page: w3.org
RFC 7937 · IETF
- Status
- Proposed Standard
- Date
- August 2016
WAI: In the standard The delivery settlement extension maps each acknowledged item of an HTTP delivery onto one cdni_http_request_v1 record, or RFC 9246's v2 record where URI Signing is used, with the acknowledgement's digest in a remark directive. Every record of a log is the serving side's statement, so a log maps onto declarations, never onto acknowledgements (settlement §9.1 and §9.2).
Issuing body's page: rfc-editor.org
SVTA Open Caching · Streaming Video Technology Alliance (SVTA), Open Caching working group
- Status
- Active specification work (for example SVTA2074)
- Date
- April 2026 (SVTA2074)
WAI: In the standard The delivery settlement extension maps the logs of SVTA2050 only through the RFC 7937 fields they carry, since only its published summary was read, and a request router that delegates or redirects a request under SVTA2007 and SVTA2006 moves no bytes and is not a party of a settlement (settlement §9.3).
Issuing body's page: svta.org
RFC 9576; RFC 9577; RFC 9578 · IETF
- Status
- RFC 9576 Informational; RFC 9577 and RFC 9578 Proposed Standard
- Date
- June 2024
WAI: In the standard The age assurance extension admits a viewer by a publicly verifiable token from an issuer with one key per age threshold, so a relay learns only the threshold and the issuer, and a room's service may redeem the token over HTTP as RFC 9577 gives it (age-assurance §4 and §5). The ad presentation extension binds a token's challenge to one impression as a device attestation (ad-presentation §7). A room's scope over MoQ follows draft-ietf-moq-privacy-pass-auth-03 (live-rooms §10.4).
Issuing body's page: rfc-editor.org