IETF MOQ WG: MSF updates

Message Snapshot

• List: moq@ietf.org
• Thread subject: MSF updates
• Message subject: [Moq] MSF updates
• Author: Law, Will
• Published: 2026-06-03T12:03:46.000Z
• Source tag: ietf-mailing-list
• Message URL: Open in IETF Mail Archive

Summary

Law, Will posted to the MOQ working group mailing list on June 3, 2026. We are pleased to announce that the -01 update to the MOQT Streaming Format draft has been released and is available at This is a significant impro…

Why It Matters

This message came from the public MOQ working group archive and captures active discussion, meeting coordination, or implementation feedback around Media over QUIC.

Message Excerpt

We are pleased to announce that the -01 update to the MOQT Streaming Format draft has been released and is available at This is a significant improvement in the specification over draft-00 . Below is a summary of the new features and syntax changes between -00 and -01. MSF is being actively developed. Please file issu…

Plain-Text Body

We are pleased to announce that the -01 update to the MOQT Streaming Format draft has been released and is available at

https://datatracker.ietf.org/doc/draft-ietf-moq-msf/01/ This is a significant improvement in the specification over draft-00 . Below is a summary of the new features and syntax changes between -00 and -01. MSF is being actively developed. Please file issueshttps://github.com/moq-wg/msf/issues. We are especially interested in feedback from early implementations. New Features

1. End-to-End Encryption (Section 4.3, expanded)

A full encryption framework was added built on MoQ Secure Objects. New subsections cover:

• Encryption scheme signaling — scheme, cipher suite, key ID, and base key signaled in the catalog
• Key management — keyId scoping (per-track, per-session, or multi-session)
• Recommended scheme — moq-secure-objects with AES-128-GCM-SHA256 (mandatory), AES-256-GCM-SHA512, and AES-128-CTR-HMAC-SHA256-80
• Encrypted object structure — immutable headers (Group/Object ID) stay plaintext; payload + private extensions (type 0xA) are encrypted

2. Publish Tracks / Subscriber-Initiated Publishing (Section 5.1.5)

A new publishTracks array at the root catalog level allows publishers to define tracks to which subscribers publish data back (logs, metrics, QoE). This enables bidirectional communication.

3. Log Track (Section 9, new)

A new track type (packaging: "moqlog", role: "log") for subscribers to send diagnostic/operational log data upstream. Group ID = capture timestamp (µs since epoch); Object ID distinguishes sub-microsecond entries. Payload format references [MOQLOG], with OpenTelemetry-aligned fields (TraceID, SpanID, etc.).

4. Metrics Track (Section 10, new)

A new track type (packaging: "moqmetrics", role: "metrics") for subscribers to publish QoE/performance metrics. Group ID = capture time (ms epoch); Object 0 holds timestamp + attributes, Object 1+ hold individual metrics (Gauge/Counter, int or float64). References [MOQMETRICS].

5. Media Timeline Template (Section 7.4, new)

For content with fixed-duration segments, a compact inline template field on a track replaces the need for a separate media timeline track. The template is a 6-element JSON array [startMediaTime, deltaMediaTime, startLocation, deltaLocation, startWallclock, deltaWallclock] from which clients compute all entries algebraically.

6. MSF URL Scheme (Section 11.1, new)

A formal ABNF grammar for MSF URIs (moqt://authority/path#msf:namespace--name&params). Includes:

• Fragment type msf registered in the MOQT URI Fragment Types registry
• wallclock-range reserved fragment parameter for subclip selection
• MSF Namespace-Name String Encoding (Section 11.1.2)
• Variable substitution via URI fragment key-value pairs (Section 5.4)

7. Token-Based Authorization Framework (Section 11.4, new)

Full authorization workflow covering discovery (via authInfo catalog field), token acquisition (OAuth 2.0, out-of-band, URI para…