Media Over QUIC W. Law Internet-Draft Akamai Intended status: Informational S. Nandakumar Expires: 19 May 2027 Cisco 15 November 2026 MOQT Streaming Format draft-ietf-moq-msf-02 Abstract This document specifies the MOQT Streaming Format, designed to operate on Media Over QUIC Transport. About This Document This note is to be removed before publishing as an RFC. The latest revision of this draft can be found at https://moq- wg.github.io/msf/draft-ietf-moq-msf.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft- ietf-moq-msf/. Discussion of this document takes place on the Media Over QUIC Working Group mailing list (mailto:moq@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/moq/. Subscribe at https://www.ietf.org/mailman/listinfo/moq/. Source for this draft and an issue tracker can be found at https://github.com/moq-wg/msf. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 19 May 2027. Law & Nandakumar Expires 19 May 2027 [Page 1] Internet-Draft MOQT Streaming Format November 2026 Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 7 3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Media packaging . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. LOC packaging . . . . . . . . . . . . . . . . . . . . . . 9 4.1.1. LOC to MOQT Stream mapping . . . . . . . . . . . . . 9 4.2. Time-alignment . . . . . . . . . . . . . . . . . . . . . 10 4.3. Packaging for multi-variant track switching . . . . . . . 11 4.4. Content protection and encryption . . . . . . . . . . . . 11 4.4.1. Encryption scheme signaling . . . . . . . . . . . . . 11 4.4.2. Key management . . . . . . . . . . . . . . . . . . . 12 4.4.3. Recommended encryption scheme . . . . . . . . . . . . 12 4.4.4. Encrypted object structure . . . . . . . . . . . . . 12 5. Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.1. Root Catalog Fields . . . . . . . . . . . . . . . . . . . 14 5.1.1. MSF version . . . . . . . . . . . . . . . . . . . . . 14 5.1.2. Generated at . . . . . . . . . . . . . . . . . . . . 15 5.1.3. Is Complete . . . . . . . . . . . . . . . . . . . . . 15 5.1.4. Tracks . . . . . . . . . . . . . . . . . . . . . . . 15 5.1.5. Publish tracks . . . . . . . . . . . . . . . . . . . 15 5.1.6. Delta update . . . . . . . . . . . . . . . . . . . . 15 5.1.7. Initialization Data List . . . . . . . . . . . . . . 16 5.2. Track Object Fields . . . . . . . . . . . . . . . . . . . 17 5.2.1. Tracks object . . . . . . . . . . . . . . . . . . . . 19 5.2.2. Track namespace . . . . . . . . . . . . . . . . . . . 19 5.2.3. Track name . . . . . . . . . . . . . . . . . . . . . 20 5.2.4. Packaging . . . . . . . . . . . . . . . . . . . . . . 21 5.2.5. Packaging metadata . . . . . . . . . . . . . . . . . 22 5.2.6. Event timeline type . . . . . . . . . . . . . . . . . 22 5.2.7. Track role . . . . . . . . . . . . . . . . . . . . . 23 5.2.8. Is Live . . . . . . . . . . . . . . . . . . . . . . . 24 5.2.9. Target latency . . . . . . . . . . . . . . . . . . . 25 Law & Nandakumar Expires 19 May 2027 [Page 2] Internet-Draft MOQT Streaming Format November 2026 5.2.10. Buffers . . . . . . . . . . . . . . . . . . . . . . . 25 5.2.11. Track label . . . . . . . . . . . . . . . . . . . . . 26 5.2.12. Render group . . . . . . . . . . . . . . . . . . . . 26 5.2.13. Alternate group . . . . . . . . . . . . . . . . . . . 26 5.2.14. Initialization reference . . . . . . . . . . . . . . 26 5.2.15. Dependencies . . . . . . . . . . . . . . . . . . . . 27 5.2.16. Template . . . . . . . . . . . . . . . . . . . . . . 27 5.2.17. Temporal ID . . . . . . . . . . . . . . . . . . . . . 27 5.2.18. Spatial ID . . . . . . . . . . . . . . . . . . . . . 27 5.2.19. Codec . . . . . . . . . . . . . . . . . . . . . . . . 28 5.2.20. Mimetype . . . . . . . . . . . . . . . . . . . . . . 28 5.2.21. Framerate . . . . . . . . . . . . . . . . . . . . . . 28 5.2.22. Timescale . . . . . . . . . . . . . . . . . . . . . . 28 5.2.23. Maximum Bitrate . . . . . . . . . . . . . . . . . . . 28 5.2.24. Average Bitrate . . . . . . . . . . . . . . . . . . . 28 5.2.25. Maximum GOP Duration . . . . . . . . . . . . . . . . 29 5.2.26. Maximum Group Duration . . . . . . . . . . . . . . . 29 5.2.27. Width . . . . . . . . . . . . . . . . . . . . . . . . 29 5.2.28. Height . . . . . . . . . . . . . . . . . . . . . . . 29 5.2.29. Audio sample rate . . . . . . . . . . . . . . . . . . 29 5.2.30. Channel configuration . . . . . . . . . . . . . . . . 29 5.2.31. Display width . . . . . . . . . . . . . . . . . . . . 30 5.2.32. Display height . . . . . . . . . . . . . . . . . . . 30 5.2.33. Language . . . . . . . . . . . . . . . . . . . . . . 30 5.2.34. Parent name . . . . . . . . . . . . . . . . . . . . . 30 5.2.35. Parent namespace . . . . . . . . . . . . . . . . . . 30 5.2.36. Track duration . . . . . . . . . . . . . . . . . . . 31 5.2.37. Connection URI . . . . . . . . . . . . . . . . . . . 31 5.2.38. Encryption scheme . . . . . . . . . . . . . . . . . . 31 5.2.39. Cipher suite . . . . . . . . . . . . . . . . . . . . 32 5.2.40. Key ID . . . . . . . . . . . . . . . . . . . . . . . 32 5.2.41. Track Base Key . . . . . . . . . . . . . . . . . . . 33 5.2.42. Authorization Info . . . . . . . . . . . . . . . . . 33 5.2.43. Token Delivery via URI . . . . . . . . . . . . . . . 34 5.2.44. Accessibility . . . . . . . . . . . . . . . . . . . . 34 5.2.45. Accessible Window Time . . . . . . . . . . . . . . . 35 5.2.46. Keyframe spacing . . . . . . . . . . . . . . . . . . 35 5.3. Delta updates . . . . . . . . . . . . . . . . . . . . . . 36 5.4. Variable Substitution . . . . . . . . . . . . . . . . . . 37 5.4.1. Variable Syntax . . . . . . . . . . . . . . . . . . . 37 5.4.2. Variable Resolution . . . . . . . . . . . . . . . . . 37 5.5. Catalog Compression . . . . . . . . . . . . . . . . . . . 38 5.6. Catalog Examples . . . . . . . . . . . . . . . . . . . . 38 5.6.1. Time-aligned Audio/Video Tracks with single quality . . . . . . . . . . . . . . . . . . . . . . . 38 5.6.2. Simulcast video tracks - 3 alternate qualities along with audio . . . . . . . . . . . . . . . . . . . . . 39 Law & Nandakumar Expires 19 May 2027 [Page 3] Internet-Draft MOQT Streaming Format November 2026 5.6.3. SVC video tracks with 2 spatial and 2 temporal qualities . . . . . . . . . . . . . . . . . . . . . . 41 5.6.4. Delta update - adding two tracks . . . . . . . . . . 43 5.6.5. Delta update removing tracks . . . . . . . . . . . . 45 5.6.6. Time-aligned Audio/Video Tracks with custom field values . . . . . . . . . . . . . . . . . . . . . . . 45 5.6.7. Time-aligned VOD Audio/Video Tracks . . . . . . . . . 46 5.6.8. Encrypted Audio/Video Tracks . . . . . . . . . . . . 47 5.6.9. Media timeline and Event timeline . . . . . . . . . . 49 5.6.10. Media timeline template . . . . . . . . . . . . . . . 50 5.6.11. Video track with embedded captions and SCTE-35 events . . . . . . . . . . . . . . . . . . . . . . . 51 5.6.12. Video track with CEA-708 captions . . . . . . . . . . 53 5.6.13. Terminating a live broadcast . . . . . . . . . . . . 53 5.6.14. Variable Substitution for personalized delivery . . . 54 5.6.15. Time-aligned Audio/Video Tracks with Authorization . 55 5.6.16. A catalog referencing other catalogs . . . . . . . . 56 5.6.17. Publish tracks for logs and metrics . . . . . . . . . 57 6. Media transmission . . . . . . . . . . . . . . . . . . . . . 59 6.1. Group numbering . . . . . . . . . . . . . . . . . . . . . 59 6.2. Object Numbering . . . . . . . . . . . . . . . . . . . . 59 6.3. Multi-Variant Fast Track Switching . . . . . . . . . . . 59 6.3.1. Switching Procedure . . . . . . . . . . . . . . . . . 60 6.3.2. Calculating Valid Switch Points . . . . . . . . . . . 60 7. Media Timeline track . . . . . . . . . . . . . . . . . . . . 60 7.1. Media Timeline track payload . . . . . . . . . . . . . . 60 7.1.1. Explicit entry format . . . . . . . . . . . . . . . . 61 7.2. Media Timeline Catalog requirements . . . . . . . . . . . 62 7.3. Media Timeline track updating . . . . . . . . . . . . . . 62 7.4. Media Timeline Template . . . . . . . . . . . . . . . . . 62 7.4.1. Template Format . . . . . . . . . . . . . . . . . . . 62 7.4.2. Template Immutability . . . . . . . . . . . . . . . . 63 8. Event Timeline track . . . . . . . . . . . . . . . . . . . . 64 8.1. Event Timeline header data . . . . . . . . . . . . . . . 64 8.1.1. Example of Event Timeline header data . . . . . . . . 64 8.2. Event Timeline data format . . . . . . . . . . . . . . . 65 8.3. Event Timeline Catalog requirements . . . . . . . . . . . 66 8.4. Event Timeline track updating . . . . . . . . . . . . . . 66 8.5. Well-known event timeline types . . . . . . . . . . . . . 66 8.6. Event timeline track payload examples . . . . . . . . . . 67 8.6.1. Event timeline track with wallclock time indexing . . 67 8.6.2. Event timeline track with MOQT Location indexing . . 67 8.6.3. Event timeline track with media time indexing . . . . 68 9. Log track . . . . . . . . . . . . . . . . . . . . . . . . . . 69 9.1. Log track payload . . . . . . . . . . . . . . . . . . . . 69 9.2. Log track namespace and name . . . . . . . . . . . . . . 69 9.3. Log track Group ID and Object ID . . . . . . . . . . . . 69 9.4. Log track catalog requirements . . . . . . . . . . . . . 69 Law & Nandakumar Expires 19 May 2027 [Page 4] Internet-Draft MOQT Streaming Format November 2026 10. Metrics track . . . . . . . . . . . . . . . . . . . . . . . . 70 10.1. Metrics track payload . . . . . . . . . . . . . . . . . 70 10.2. Metrics track namespace and name . . . . . . . . . . . . 70 10.3. Metrics track Group ID and Object ID . . . . . . . . . . 70 10.4. Metrics track catalog requirements . . . . . . . . . . . 71 11. Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . 71 11.1. URL construction and interpretation . . . . . . . . . . 71 11.1.1. Reserved fragment parameters . . . . . . . . . . . . 74 11.1.2. MSF Namespace-Name String Encoding . . . . . . . . . 75 11.1.3. Example MSF URLs . . . . . . . . . . . . . . . . . . 76 11.2. Mapping catalog strings to MOQT byte values . . . . . . 77 11.2.1. Producing bytes from a JSON string . . . . . . . . . 77 11.2.2. Comparing names . . . . . . . . . . . . . . . . . . 78 11.2.3. Consuming names received from MOQT . . . . . . . . . 78 11.2.4. Relationship to the serialized form . . . . . . . . 79 11.2.5. Examples of string-to-byte mappings . . . . . . . . 79 11.3. Initiating a broadcast . . . . . . . . . . . . . . . . . 79 11.4. Ending a live broadcast . . . . . . . . . . . . . . . . 80 11.5. Authorization . . . . . . . . . . . . . . . . . . . . . 80 11.5.1. Discovering Authorization Requirements . . . . . . . 80 11.5.2. Token Acquisition . . . . . . . . . . . . . . . . . 81 11.5.3. Presenting Authorization . . . . . . . . . . . . . . 81 11.5.4. Handling Authorization Failures . . . . . . . . . . 82 11.6. Wallclock time . . . . . . . . . . . . . . . . . . . . . 82 12. MSF Properties . . . . . . . . . . . . . . . . . . . . . . . 82 12.1. Compression Signaling . . . . . . . . . . . . . . . . . 82 12.1.1. MSF_COMPRESSION Track Property . . . . . . . . . . . 83 12.1.2. MSF_COMPRESSION Object Property . . . . . . . . . . 84 12.2. Initialization properties . . . . . . . . . . . . . . . 84 12.3. Event Timeline Track properties . . . . . . . . . . . . 85 12.3.1. MSF_EVENT_TIMELINE_HEADER Track property . . . . . . 85 13. Security Considerations . . . . . . . . . . . . . . . . . . . 85 13.1. Catalog integrity and authenticity . . . . . . . . . . . 86 13.2. Key material in the catalog . . . . . . . . . . . . . . 86 13.3. Metadata exposure . . . . . . . . . . . . . . . . . . . 86 13.4. Authorization tokens . . . . . . . . . . . . . . . . . . 87 13.5. Variable substitution . . . . . . . . . . . . . . . . . 87 13.6. Publish tracks and connection URIs . . . . . . . . . . . 88 13.7. Resource exhaustion . . . . . . . . . . . . . . . . . . 88 13.8. Timing information . . . . . . . . . . . . . . . . . . . 89 13.9. Track naming . . . . . . . . . . . . . . . . . . . . . . 89 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 89 14.1. "MOQT URI Fragment Types" registry . . . . . . . . . . . 90 14.2. "MSF Event Timeline Types" registry . . . . . . . . . . 90 14.2.1. Guidance for Designated Experts . . . . . . . . . . 90 14.3. MSF Property Type values . . . . . . . . . . . . . . . . 91 14.4. "MSF Compression Algorithms" registry . . . . . . . . . 91 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 92 Law & Nandakumar Expires 19 May 2027 [Page 5] Internet-Draft MOQT Streaming Format November 2026 15.1. Normative References . . . . . . . . . . . . . . . . . . 92 15.2. Informative References . . . . . . . . . . . . . . . . . 94 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 96 A.1. Changes since draft-ietf-moq-msf-01 . . . . . . . . . . . 96 A.1.1. Editorial and structural . . . . . . . . . . . . . . 96 A.1.2. Media packaging and transmission . . . . . . . . . . 97 A.1.3. Catalog . . . . . . . . . . . . . . . . . . . . . . . 97 A.1.4. Media timeline . . . . . . . . . . . . . . . . . . . 98 A.1.5. Event timeline . . . . . . . . . . . . . . . . . . . 98 A.1.6. Log and metrics tracks . . . . . . . . . . . . . . . 99 A.1.7. Workflow . . . . . . . . . . . . . . . . . . . . . . 99 A.1.8. MSF properties and IANA . . . . . . . . . . . . . . . 99 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 100 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 100 1. Introduction Media over QUIC Transport (MOQT) [MOQT] is a publish/subscribe protocol that delivers media and other data as named Tracks, each composed of Groups and Objects, through a network of relays. MOQT deliberately leaves the meaning of Track payloads, the naming of Tracks and the relationships between Tracks to the applications built on top of it. Independently developed publishers, relays and players can only interoperate if they agree on these details. The MOQT Streaming Format (MSF) defines that agreement for the delivery of audio, video and associated timed data. MSF specifies: * how media is packaged into MOQT Objects and Groups, using Low Overhead Container (LOC) [LOC] payloads (Section 4); * a catalog, carried in its own MOQT Track, that describes the tracks produced by an original publisher, their properties and their relationships, and that can be updated incrementally as the broadcast evolves (Section 5); * media timeline and event timeline tracks, which relate MOQT Locations to media time and wallclock time and synchronize ancillary data with the media (Section 7, Section 8); * how subscribers switch between alternate tracks with consistent group durations, for adaptive bitrate playback (Section 5.2.13), as well as across tracks with variable group durations (Section 6.3); * how (Section 4.4) and token-based authorization (Section 11.5) are signalled. Law & Nandakumar Expires 19 May 2027 [Page 6] Internet-Draft MOQT Streaming Format November 2026 * how to initiate subscribers to publish tracks, such as might be used to report logs and metrics to an analytics system (Section 9, Section 10); * a URL format for addressing MSF content, and procedures for starting and ending a broadcast. MSF supports live content across a range of latency targets, from real-time and interactive through to standard broadcast latency, as well as video-on-demand (VOD) content. An event timeline track is defined, as an option for carrying additional data types, such as timed-text captions and ad-insertion signaling. Companion specifications (Section 8.5) may also define custom packaging formats. MSF semantics are interpreted only by original publishers and end subscribers. Relays do not need to understand MSF: they forward and cache MSF Tracks, including the catalog, as they would any other MOQT Track. This document describes version 1 of MSF. While this document is an Internet-Draft, the version is signaled in the catalog as described in Section 5.1.1. 2. Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. This document uses the conventions detailed in [RFC9000], Section 1.3 when describing the binary encoding. 3. Scope The purpose of MSF is to provide an interoperable media streaming format operating over [MOQT]. Interoperability implies that: * An original publisher can package incoming media content into tracks, prepare a catalog and announce the availability of the content to an MOQT relay. Media content refers to audio and video data, as well as ancillary data such as captions, subtitles, accessibility and other timed-text data. Law & Nandakumar Expires 19 May 2027 [Page 7] Internet-Draft MOQT Streaming Format November 2026 * An MOQT relay can process the announcement as well as cache and propagate the tracks, both to other relays or to the final subscriber. * A final subscriber can parse the catalog, request tracks, decode and render the received media data. MSF is intended to provide a format for delivering commercial media content. To that end, the following features are within scope: * Video codecs - all codecs supported by [LOC] * Audio codecs - all audio codecs supported by [LOC] * Catalog track - describes the availability and characteristics of content produced by the original publisher. * Timeline track - describes the relationship between MOQT Group and Object IDs to media time. * Token-based authorization and access control * Captions + Subtitles - support for [WEBVTT] and [IMSC1] transmission * Latency support across multiple regimes (thresholds are informative only and describe the delay between the original publisher placing the content on the wire and the final subscriber rendering it) - Real-time - less than 500ms - Interactive - between 500ms and 2500ms - Standard - above 2500ms - VOD latency - content that was previously produced, is no longer live and is available indefinitely. * Content encryption * ABR between time-synced tracks - subscribers may switch between tracks at different quality levels in order to maximize visual or audio quality under conditions of throughput variability. * Capable of delivering interstitial advertising. Law & Nandakumar Expires 19 May 2027 [Page 8] Internet-Draft MOQT Streaming Format November 2026 * Logs and analytics management - support for the reporting of client-side QoE and relay delivery actions via publish tracks using [MOQLOG] and [MOQMETRICS]. Initial versions of MSF will prioritize basic features necessary to exercise interoperability across delivery systems. Later versions will add commercially necessary features. 4. Media packaging MSF delivers LOC [LOC] packaged media bitstreams. 4.1. LOC packaging This specification references Low Overhead Container (LOC) [LOC] to define how audio and video content is packaged. With this packaging mode, each EncodedAudioChunk or EncodedVideoChunk sample is placed in a separate MOQT Object. All MOQT Objects SHOULD be placed on MOQT Subgroup 0 unless streamMapping Section 4.1.1 indicates otherwise. Samples that belong to the same Group of Pictures (GOP) MUST be placed within the same MOQT Group. When LOC packaging is used for a track, the catalog packaging attribute (Section 5.2.4) MUST be present and it MUST be populated with a value of "loc". 4.1.1. LOC to MOQT Stream mapping LOC [LOC] defines only the payload container carried in each MOQT Object; it does not specify how those Objects are mapped onto MOQT Streams. MSF publishers using LOC packaging MUST select one of the mapping modes listed below, and subscribers MUST be prepared to consume both of them. The chosen mode is signaled per-track via the Section 5.2.5 field using the streamMapping key. Law & Nandakumar Expires 19 May 2027 [Page 9] Internet-Draft MOQT Streaming Format November 2026 +===============+======================================+ | streamMapping | Description | | value | | +===============+======================================+ | group | All MOQT Objects within a MOQT Group | | | are sent in a single MOQT Subgroup, | | | in Object ID order. Default. | +---------------+--------------------------------------+ | object | Each MOQT Object is sent in its own | | | MOQT Subgroup. | +---------------+--------------------------------------+ Table 1: LOC stream-mapping modes signaled via `packagingMetadata` If packagingMetadata is absent, or if it is present but does not carry a streamMapping key, the mode group MUST be assumed. Regardless of the selected mode, the mapping of samples to Objects and Groups defined above (one sample per Object, one GOP per Group) is unchanged. 4.2. Time-alignment MSF Tracks MAY be time-aligned. Those that are, are subject to the following requirements: * Tracks advertised in the catalog as belonging to a common alternate group MUST be time-aligned. * The render duration of the first media object of each equally numbered MOQT Group, after decoding, SHOULD have overlapping presentation time. A consequence of this restriction is that an MSF receiver SHOULD be able to cleanly switch between time-aligned media tracks at group boundaries. If time-aligned media tracks do not have overlapping presentation time at equally-numbered group boundaries, then an alternate mechanism, not defined by this specification, needs to be provided to the client to enable it to switch smoothly between time-aligned, but numerically dissimilar, Group IDs. Law & Nandakumar Expires 19 May 2027 [Page 10] Internet-Draft MOQT Streaming Format November 2026 4.3. Packaging for multi-variant track switching When publishing multiple tracks within an alternate group that have dissimilar keyframe intervals (different GOP sizes), publishers MUST follow these requirements to enable seamless track switching: * Each MOQT Group MUST start with a keyframe. Publishers MUST NOT place multiple keyframes within a single group, as this hides intermediate join points from subscribers. * All tracks within an alternate group MUST be time-aligned at object boundaries, not only at group boundaries. * The keyframeSpacing Section 5.2.46 catalog field MUST be specified for each track, indicating the number of objects per keyframe interval. * The starting Group ID of all tracks within an alternate group MUST be identical. The GroupID of each subsequent group MUST increase by 1. See Section 6.3 for details on how subscribers use keyframeSpacing to calculate valid switch points. 4.4. Content protection and encryption MSF supports end-to-end encryption of media content using MoQ Secure Objects [SecureObjects]. When encryption is enabled, the payload of LOC-packaged media objects is encrypted and authenticated, while relays can still route content based on unencrypted header information. 4.4.1. Encryption scheme signaling The encryption scheme and parameters are signaled in the catalog using the following track-level fields: * encryptionScheme Section 5.2.38 - identifies the encryption mechanism * cipherSuite Section 5.2.39 - specifies the AEAD algorithm * keyId Section 5.2.40 - identifies the key material for decryption * trackBaseKey Section 5.2.41 - the base key material for this track Law & Nandakumar Expires 19 May 2027 [Page 11] Internet-Draft MOQT Streaming Format November 2026 When the encryptionScheme field is present in a track definition, subscribers MUST decrypt the object payload using the specified scheme before processing. 4.4.2. Key management The keyId and trackBaseKey values are obtained from an external key management system and the mechanism for obtaining these values is out of scope for this specification. Examples of key management systems include MLS-based key distribution [E2EE-MLS] or other out-of-band key exchange mechanisms. Depending on the key management mechanism in use, a keyId MAY be scoped to: * A single track * A single MOQT Session * Multiple tracks across one or more MOQT sessions Publishers and subscribers MUST use the same key management system and agree on the keyId scope semantics for interoperable operation. 4.4.3. Recommended encryption scheme The RECOMMENDED encryption scheme for MSF is "moq-secure-objects". Implementations supporting content encryption MUST implement the "moq-secure-objects" scheme as defined in [SecureObjects]. When using the "moq-secure-objects" scheme: * The cipherSuite field MUST be present and set to a supported cipher suite value * The keyId field MUST be present to identify the key material * The trackBaseKey field MUST be present to provide the base key material 4.4.4. Encrypted object structure For LOC-packaged tracks with encryption enabled (see [SecureObjects], Section 4): * The immutable object properties (including Group ID and Object ID) remain in plaintext and are authenticated Law & Nandakumar Expires 19 May 2027 [Page 12] Internet-Draft MOQT Streaming Format November 2026 * The object payload is encrypted and authenticated using the specified cipher * Private object properties (type 0xA) are encrypted alongside the payload 5. Catalog A Catalog is an MOQT Track that provides information about the other tracks being produced by an MSF publisher. A Catalog is used by MSF publishers for advertising their output and for subscribers in consuming that output. The payload of the Catalog object is opaque to Relays and can be end-to-end encrypted. The Catalog provides the names and namespaces of the tracks being produced, along with the relationship between tracks, properties of the tracks that consumers may use for selection and any relevant initialization data. A catalog track MAY reference other catalog tracks. The top-level catalog track MUST have a case-sensitive Track Name of "catalog". A catalog object MAY be independent of other catalog objects or it MAY represent a delta update of a prior catalog object. The first catalog object published within a new group MUST be independent and MUST provide a complete catalog that does not require any prior catalog object for interpretation. Any catalog updates that precede the first Object of the latest Group MUST be ignored. A catalog object SHOULD be published only when the content of the catalog has changed, or after a period of time has passed such that the catalog object might fall out of cache in a delivery network. The catalog track SHOULD have a higher publisher priority than all tracks described within the catalog. A subscriber to a catalog track SHOULD use a higher subscriber priority for the catalog subscription than for any other concurrent subscriptions. Each catalog update MUST be mapped to an MOQT Object. All catalog updates, both independent and delta, MUST be mapped to MOQT Subgroup 0. The first Object (with Object ID 0) in any Group in a catalog track MUST hold an independent copy of the catalog. All subsequent Objects within that Group (i.e Objects IDs >= 1) MUST hold a delta update. As soon as an independent update is produced, it MUST be placed at the start of a new Group. Law & Nandakumar Expires 19 May 2027 [Page 13] Internet-Draft MOQT Streaming Format November 2026 Subscribers accessing the catalog MUST use SUBSCRIBE with a Joining FETCH (offset = 0) in order to obtain the latest complete catalog along with all subsequent catalog objects, including delta updates, that follow. A catalog is a JSON [JSON] document, comprised of a series of mandatory and optional fields. At a minimum, a catalog MUST provide all mandatory fields. Some fields are conditional depending on the type of content carried. A producer MAY add additional fields to the ones described in this draft. Custom field names MUST NOT collide with field names described in this draft. A parser MUST ignore fields it does not understand. 5.1. Root Catalog Fields Table 2 lists the fields defined at the root of the catalog JSON object. +==========================+===============+===============+ | Field | Name | Definition | +==========================+===============+===============+ | MSF version | version | Section 5.1.1 | +--------------------------+---------------+---------------+ | Generated at | generatedAt | Section 5.1.2 | +--------------------------+---------------+---------------+ | Is Complete | isComplete | Section 5.1.3 | +--------------------------+---------------+---------------+ | Tracks | tracks | Section 5.1.4 | +--------------------------+---------------+---------------+ | Publish tracks | publishTracks | Section 5.1.5 | +--------------------------+---------------+---------------+ | Delta update | deltaUpdate | Section 5.1.6 | +--------------------------+---------------+---------------+ | Initialization Data List | initDataList | Section 5.1.7 | +--------------------------+---------------+---------------+ Table 2: Root catalog fields 5.1.1. MSF version Required: Yes JSON Type: String Location: Root Catalog Specifies the version of MSF referenced by this catalog. There is no guarantee that future catalog versions are backwards compatible and field definitions and interpretation may change between versions. A subscriber MUST NOT attempt to parse a catalog version which it does not understand. Law & Nandakumar Expires 19 May 2027 [Page 14] Internet-Draft MOQT Streaming Format November 2026 For usage against IETF Internet-Draft releases, follow the convention of specifying the version as "draft-XX". For example "draft-03" refers to the -03 draft release. 5.1.2. Generated at Required: Optional JSON Type: Number Location: Root Catalog The wallclock time at which this catalog instance was generated, as defined by Section 11.6. 5.1.3. Is Complete Required: Optional JSON Type: Boolean Location: Root Catalog A catalog-level indication that the broadcast is complete. This is a commitment that all tracks are complete, no new tracks will be added to the catalog, and no new content will be published on any track. Note that even if all individual tracks have isLive Section 5.2.8 set to FALSE, new tracks could still be added to the catalog until isComplete is set to TRUE. This field MUST NOT be included if it is FALSE. This field MUST NOT be removed from a catalog once it has been added. 5.1.4. Tracks Required: Yes JSON Type: Array Location: Root Catalog An array of track objects Section 5.2.1. 5.1.5. Publish tracks Required: Optional JSON Type: Array Location: Root Catalog An array of publish track objects. Publish tracks define tracks to which the subscriber can publish data, such as logs, metrics, or other QoE data. This enables bi-directional communication where the subscriber acts as a publisher for specific tracks. Each publish track object follows the same structure as a regular track object Section 5.2.1 but is used for the reverse direction of data flow. 5.1.6. Delta update Required: Optional JSON Type: Array Location: Root Catalog Law & Nandakumar Expires 19 May 2027 [Page 15] Internet-Draft MOQT Streaming Format November 2026 An ordered Array of operation objects that specify changes to apply to the catalog. If this field is present, the catalog represents a delta (or partial) update with a restricted set of fields and special processing rules - see Section 5.3. If this field is absent, the catalog is independent. Operations are applied sequentially in the order they appear in the array. Each operation object MUST contain an "op" field indicating the operation type, and a "tracks" field containing an Array of track objects Section 5.2.1. The following operation types are defined: * "add" - Add new tracks that have not previously been declared. The value of the "tracks" field is an Array of track objects Section 5.2.1. * "remove" - Remove tracks that have been previously declared. The value of the "tracks" field is an Array of track objects Section 5.2.1. Each track object MUST include a Track Name Section 5.2.3 field, MAY include a Track Namespace Section 5.2.2 field, and MUST NOT hold any other fields. * "clone" - Clone new tracks from previously declared tracks. The value of the "tracks" field is an Array of track objects Section 5.2.1. Each track object MUST include a Parent Name Section 5.2.34 field and MAY include a Parent namespace Section 5.2.35 field. The cloned track inherits all attributes from the parent except the Track Name which MUST be new. Attributes redefined in the track object override inherited values. * "update" - update a subset of fields within an existing track. The value of the "tracks" field is an Array of track objects Section 5.2.1. Each track object MUST include a Parent Name Section 5.2.34 field and MAY include a Parent namespace Section 5.2.35 field. Attributes declared in the track object override existing values. 5.1.7. Initialization Data List Required: Optional JSON Type: Array Location: Root Catalog An array of initialization reference objects. Each initialization reference object has the following fields: * id : a string defining a reference to this initialization data which is unique within the scope of the catalog. Law & Nandakumar Expires 19 May 2027 [Page 16] Internet-Draft MOQT Streaming Format November 2026 * type: a string defining the type of reference. This version of the specification defines the following allowed types: +=================+=============================================+ | Type | Data field definition | +=================+=============================================+ | inline | Base64 [BASE64] encoded initialization data | +-----------------+---------------------------------------------+ | track-property | The Track property type in hex notation | +-----------------+---------------------------------------------+ | object-property | An Object property type in hex notation | +-----------------+---------------------------------------------+ Table 3 * data: a string holding the init payload as defined by the type. For both the track-property and object-property types, the initialization data is serialized as raw binary data and carried in the value field of the initialization properties, see Section 12.2. The Initialization Data List, if present, SHOULD be located after the tracks array in the root of the JSON catalog. The purpose of this is to improve the human readability of the catalog tracks by moving the verbose init data towards the end of the document. 5.2. Track Object Fields Table 4 lists the fields defined within each track object. +=========================+======================+================+ | Field | Name | Definition | +=========================+======================+================+ | Track namespace | namespace | Section 5.2.2 | +-------------------------+----------------------+----------------+ | Track name | name | Section 5.2.3 | +-------------------------+----------------------+----------------+ | Packaging | packaging | Section 5.2.4 | +-------------------------+----------------------+----------------+ | Packaging metadata | packagingMetadata | Section 5.2.5 | +-------------------------+----------------------+----------------+ | Event timeline type | eventType | Section 5.2.6 | +-------------------------+----------------------+----------------+ | Is Live | isLive | Section 5.2.8 | +-------------------------+----------------------+----------------+ | Target latency | targetLatency | Section 5.2.9 | +-------------------------+----------------------+----------------+ | Buffers | buffers | Section 5.2.10 | Law & Nandakumar Expires 19 May 2027 [Page 17] Internet-Draft MOQT Streaming Format November 2026 +-------------------------+----------------------+----------------+ | Track role | role | Section 5.2.7 | +-------------------------+----------------------+----------------+ | Track label | label | Section 5.2.11 | +-------------------------+----------------------+----------------+ | Render group | renderGroup | Section 5.2.12 | +-------------------------+----------------------+----------------+ | Alternate group | altGroup | Section 5.2.13 | +-------------------------+----------------------+----------------+ | Initialization ref | initRef | Section 5.2.14 | +-------------------------+----------------------+----------------+ | Dependencies | depends | Section 5.2.15 | +-------------------------+----------------------+----------------+ | Media timeline template | template | Section 5.2.16 | +-------------------------+----------------------+----------------+ | Temporal ID | temporalId | Section 5.2.17 | +-------------------------+----------------------+----------------+ | Spatial ID | spatialId | Section 5.2.18 | +-------------------------+----------------------+----------------+ | Codec | codec | Section 5.2.19 | +-------------------------+----------------------+----------------+ | Mime type | mimeType | Section 5.2.20 | +-------------------------+----------------------+----------------+ | Framerate | framerate | Section 5.2.21 | +-------------------------+----------------------+----------------+ | Timescale | timescale | Section 5.2.22 | +-------------------------+----------------------+----------------+ | Maximum Bitrate | bitrate | Section 5.2.23 | +-------------------------+----------------------+----------------+ | Average Bitrate | avgBitrate | Section 5.2.24 | +-------------------------+----------------------+----------------+ | Maximum GOP Duration | maxGopDuration | Section 5.2.25 | +-------------------------+----------------------+----------------+ | Maximum Group Duration | maxGroupDuration | Section 5.2.26 | +-------------------------+----------------------+----------------+ | Width | width | Section 5.2.27 | +-------------------------+----------------------+----------------+ | Height | height | Section 5.2.28 | +-------------------------+----------------------+----------------+ | Audio sample rate | samplerate | Section 5.2.29 | +-------------------------+----------------------+----------------+ | Channel configuration | channelConfig | Section 5.2.30 | +-------------------------+----------------------+----------------+ | Display width | displayWidth | Section 5.2.31 | +-------------------------+----------------------+----------------+ | Display height | displayHeight | Section 5.2.32 | +-------------------------+----------------------+----------------+ | Language | lang | Section 5.2.33 | Law & Nandakumar Expires 19 May 2027 [Page 18] Internet-Draft MOQT Streaming Format November 2026 +-------------------------+----------------------+----------------+ | Parent name | parentName | Section 5.2.34 | +-------------------------+----------------------+----------------+ | Parent namespace | parentNamespace | Section 5.2.35 | +-------------------------+----------------------+----------------+ | Track duration | trackDuration | Section 5.2.36 | +-------------------------+----------------------+----------------+ | Connection URI | connectionURI | Section 5.2.37 | +-------------------------+----------------------+----------------+ | Encryption scheme | encryptionScheme | Section 5.2.38 | +-------------------------+----------------------+----------------+ | Cipher suite | cipherSuite | Section 5.2.39 | +-------------------------+----------------------+----------------+ | Key ID | keyId | Section 5.2.40 | +-------------------------+----------------------+----------------+ | Track Base Key | trackBaseKey | Section 5.2.41 | +-------------------------+----------------------+----------------+ | Authorization Info | authInfo | Section 5.2.42 | +-------------------------+----------------------+----------------+ | Accessibility | accessibility | Section 5.2.44 | +-------------------------+----------------------+----------------+ | Accessible Window Time | accessibleWindowTime | Section 5.2.45 | +-------------------------+----------------------+----------------+ | Keyframe spacing | keyframeSpacing | Section 5.2.46 | +-------------------------+----------------------+----------------+ Table 4: Track fields 5.2.1. Tracks object A track object is a JSON Object containing a collection of fields whose location is specified in Table 4. 5.2.2. Track namespace Required: Optional JSON Type: String Location: Track Object Law & Nandakumar Expires 19 May 2027 [Page 19] Internet-Draft MOQT Streaming Format November 2026 The Track Namespace under which the track name is defined. See [MOQT], Section 2.4.1. The value is a single JSON string in which the '/' character (U+002F SOLIDUS) delimits the boundaries between Track Namespace Fields. The string is split at each '/' character, and the resulting substrings correspond, in order, to the Track Namespace Fields of the MOQT Track Namespace. Each substring is converted to the bytes of its Track Namespace Field using the rules in Section 11.2. The split is performed on the string value after JSON decoding [JSON], Section 7. Any U+002F character in the decoded value is a field delimiter, regardless of whether it appeared in the JSON text as "/", "\/" or "\u002F". A U+002F character MUST NOT be part of a field value and is always interpreted as a field boundary. For example, the value "example.com/live/channel1" represents a Track Namespace with three fields: "example.com", "live" and "channel1". The string MUST yield between 1 and 32 fields, and every field MUST be non-empty, so that the resulting Track Namespace satisfies the constraints of [MOQT], Section 2.4.1. Consequently, the string MUST NOT be empty, MUST NOT begin or end with a '/' character, and MUST NOT contain two consecutive '/' characters. A parser that encounters a value that is not a string, an empty string, a string yielding more than 32 fields, or a string yielding an empty field MUST treat the catalog as invalid. The track namespace is optional. If it is not declared within a track object, then the track MUST inherit the Track Namespace of the catalog track, that is, the Track Namespace under which the catalog itself was subscribed. A namespace declared in a track object replaces (and does not extend) any inherited namespace. 5.2.3. Track name Required: Yes JSON Type: String Location: Track Object A JSON string defining the MOQT Track Name of the track. See [MOQT], Section 2.4.1. The string is converted to the bytes of the Track Name using the rules in Section 11.2. A Track Name MUST NOT be the empty string. Within a catalog, the combination of Track Namespace and Track Name (the Full Track Name) MUST be unique. Uniqueness, and every other comparison of track names or namespaces required by this document (for example in Section 5.2.15, Section 5.2.34, Section 5.2.35 and Section 5.1.6), is determined by exact comparison of the mapped bytes as described in Section 11.2, never by comparison of the JSON source text. Law & Nandakumar Expires 19 May 2027 [Page 20] Internet-Draft MOQT Streaming Format November 2026 5.2.4. Packaging Required: Yes JSON Type: String Location: Track Object A string defining the type of payload encapsulation. Allowed values are strings as defined in Table 5. +================+===============+==================+ | Name | Value | Reference | +================+===============+==================+ | LOC | loc | [LOC] | +----------------+---------------+------------------+ | Media Timeline | mediatimeline | See Section 7 | +----------------+---------------+------------------+ | Event Timeline | eventtimeline | See Section 8 | +----------------+---------------+------------------+ | MoQ Log | moqlog | See [MOQLOG] | +----------------+---------------+------------------+ | MoQ Metrics | moqmetrics | See [MOQMETRICS] | +----------------+---------------+------------------+ | Catalog | catalog | See Section 5 | +----------------+---------------+------------------+ Table 5: Allowed packaging values Which additional track fields are required depends on the pair (packaging, role) - see Section 5.2.4.1. 5.2.4.1. Required fields per packaging and track type trackName Section 5.2.3, packaging Section 5.2.4, and isLive Section 5.2.8 are required on every track. A track without a namespace Section 5.2.2 inherits the namespace of the catalog. Table 6 lists the fields that MUST also be present for each (packaging, role) pair. Fields not listed remain OPTIONAL. Where an individual field definition sets a stricter constraint (e.g. Conditional), that constraint wins. Fields with no meaning for a given pair SHOULD NOT be included; parsers ignore fields they do not understand. Law & Nandakumar Expires 19 May 2027 [Page 21] Internet-Draft MOQT Streaming Format November 2026 +===============+==================+===========================+ | Packaging | Role | Also required | +===============+==================+===========================+ | loc | audio | codec, bitrate, | | | | samplerate, channelConfig | +---------------+------------------+---------------------------+ | loc | video | codec, bitrate, framerate | +---------------+------------------+---------------------------+ | loc | audiodescription | codec, samplerate, | | | | channelConfig, lang | +---------------+------------------+---------------------------+ | loc | signlanguage | codec, framerate | +---------------+------------------+---------------------------+ | eventtimeline | eventtimeline | eventType | +---------------+------------------+---------------------------+ Table 6: Required track fields per (packaging, role) Packaging and role combinations not listed in the table above have no required fields beyond those required on every track. Specifications defining new packaging values extend this table with their own per-role rows. 5.2.5. Packaging metadata Required: Optional JSON Type: String Location: Track Object Additional parameters for the Section 5.2.4 value in use, encoded as a semicolon-separated list of key=value pairs (e.g. key1=v1;key2=v2). Keys and values are case-sensitive and MUST NOT contain whitespace, = or ;. The permitted keys and their meaning are defined by the specification for the packaging value in use. Subscribers MUST ignore any key that is not defined for the current packaging value. If the same key appears more than once, the first occurrence is used. For packaging value "loc", the following keys are defined: * streamMapping - the LOC to MOQT Stream mapping mode. Permitted values are listed in Section 4.1.1. If this key is absent, the value group is assumed. 5.2.6. Event timeline type Required: Optional JSON Type: String Location: Track Object Law & Nandakumar Expires 19 May 2027 [Page 22] Internet-Draft MOQT Streaming Format November 2026 A String defining the type & structure of the data contained within the data field of the Event timeline track. Types are defined by the application provider and are not centrally registered. Implementers are encouraged to use a unique naming scheme, such as Reverse Domain Name Notation, where domain name components are listed in reverse order (e.g., "com.example.myeventtype"), to avoid naming collisions. This field is required if the Section 5.2.4 value is "eventtimeline". This field MUST NOT be used if the packaging value is not "eventtimeline". 5.2.7. Track role Required: Optional JSON Type: String Location: Track Object A string defining the role of content carried by the track. Specified roles are described in Table 7. These role values are case-sensitive. This role field MAY be used in conjunction with the Mimetype Section 5.2.20 to fully describe the content of the track. See Section 5.2.4.1 for the fields that MUST accompany each role under a given Section 5.2.4. Law & Nandakumar Expires 19 May 2027 [Page 23] Internet-Draft MOQT Streaming Format November 2026 +==================+===================================+ | Role | Description | +==================+===================================+ | audiodescription | An audio description for visually | | | impaired users | +------------------+-----------------------------------+ | video | Visual content | +------------------+-----------------------------------+ | audio | Audio content | +------------------+-----------------------------------+ | mediatimeline | An MSF media timeline Section 7 | +------------------+-----------------------------------+ | eventtimeline | An MSF event timeline Section 8 | +------------------+-----------------------------------+ | caption | A textual representation of the | | | audio track | +------------------+-----------------------------------+ | subtitle | A transcription of the spoken | | | dialogue | +------------------+-----------------------------------+ | signlanguage | A visual track for hearing | | | impaired users. | +------------------+-----------------------------------+ | log | A log publishing track per | | | [MOQLOG]. | +------------------+-----------------------------------+ | metrics | A metrics publishing track per | | | [MOQMETRICS]. | +------------------+-----------------------------------+ | data | A generic descriptor for tracks | | | carrying application-defined data | +------------------+-----------------------------------+ Table 7: Reserved track roles Custom roles MAY be used as long as they do not collide with the specified roles. 5.2.8. Is Live Required: Yes JSON Type: Boolean Location: Track Object Law & Nandakumar Expires 19 May 2027 [Page 24] Internet-Draft MOQT Streaming Format November 2026 A track-level indication of whether new Objects will be added to this specific track. True if new Objects will be added to the track. False if no new Objects will be added to the track. A False value is sent under two possible conditions: * the publisher of a previously live track has ended the track. * the track is Video-On-Demand (VOD) and was never live. A True value MUST NOT follow a False value in a catalog update. 5.2.9. Target latency Required: Optional JSON Type: Number Location: Track Object The target latency in milliseconds. Target latency is defined as the offset in wallclock time between when content entered the encoder and when it is displayed to the end user. Wallclock time is defined by Section 11.6. For example, if a frame of video entered the encoder at 10:08:32.638 UTC and the target latency is 5000, then that frame should be rendered to the end-user at 10:08:37.638 UTC. If isLive is false, this field MUST be ignored. All tracks belonging to the same render group MUST have identical target latencies. All tracks belonging to the same alternate group MUST have identical target latencies. If this field is absent from the track definition, and isLive is TRUE, then the player MAY choose the latency with which it renders the content. This property MUST NOT be present if the buffers Section 5.2.10 property is present within a track definition. 5.2.10. Buffers Required: Optional JSON Type: Object Location: Track Object An object defining a set of target buffers. Buffer is defined as the duration of media data that needs to be buffered before decoding commences. This is typically known as a forward or jitter-buffer in a media player. Players with identical buffer lengths are likely to be synchronized. The target buffer object has these keys: * target : defines the target buffer in integer milliseconds. Players SHOULD attempt to stabilize playback at this value. * min : defines the minimum buffer in milliseconds. Players SHOULD NOT operate below this value. * max : defines the maximum buffer in milliseconds. Players SHOULD NOT operate above this value. Law & Nandakumar Expires 19 May 2027 [Page 25] Internet-Draft MOQT Streaming Format November 2026 Keys are optional. Unknown keys in the target buffer object MUST be ignored. If isLive is FALSE, this target buffer property MUST be ignored. All tracks belonging to the same render group MUST have identical target buffers. All tracks belonging to the same alternate group MUST have identical target buffers. If this field is absent from the track definition, and isLive is TRUE, then the player MAY choose the buffers with which it conducts playback. This property MUST NOT be present if the target latency Section 5.2.9 property is present within a track definition. 5.2.11. Track label Required: Optional JSON Type: String Location: Track Object A string defining a human-readable label for the track. Examples might be "Overhead camera view" or "Deutscher Kommentar". Note that the [JSON] spec requires UTF-8 support by decoders. 5.2.12. Render group Required: Optional JSON Type: Number Location: Track Object An integer specifying a group of tracks which are designed to be rendered together. Tracks with the same group number SHOULD be rendered simultaneously and are designed to accompany one another. A common example would be tying together audio and video tracks. 5.2.13. Alternate group Required: Optional JSON Type: Number Location: Track Object An integer specifying a group of tracks which are alternate versions of one-another. Alternate tracks represent the same media content, but differ in their selection properties. Alternate tracks MUST have matching media time sequences. A subscriber typically subscribes to one track from a set of tracks specifying the same alternate group number. A common example would be a set video tracks of the same content offered in alternate bitrates. 5.2.14. Initialization reference Required: Optional JSON Type: String Location: Track Object A string pointing at the id field of an entry in the Initialization Data List Section 5.1.7. Law & Nandakumar Expires 19 May 2027 [Page 26] Internet-Draft MOQT Streaming Format November 2026 5.2.15. Dependencies Required: Optional JSON Type: Array Location: Track Object Certain tracks may depend on other tracks, for example as a decoding dependency or due to a media timeline relationship. To signal this relationship, Dependencies holds an array of elements on which the current track is dependent. Each element can be either a track name Section 5.2.3 or renderGroup Section 5.2.12. To assist parsers in determining the type of each element, any entry with a JSON type of String MUST reference a track name and any entry with a JSON type of Number MUST reference a renderGroup. Since only the track name is signaled, each String element MUST match the Track Name of exactly one other track object in the catalog. Each Number element MUST match the renderGroup identifier of exactly one renderGroup in the catalog. A catalog in which a dependency does not resolve is invalid. 5.2.16. Template Required: Optional JSON Type: Array Location: Track Object A media timeline template for tracks with fixed-duration segments. It specifies the relationship between media time, MOQT Location, and wallclock time through starting points and intervals. See Section 7.4 for the complete format specification, field definitions, and computation formulas. Tracks that include a template field SHOULD NOT also have a separate media timeline track, as the template provides equivalent functionality. Different tracks (e.g., audio and video) MAY have independent template values to accommodate different group durations. 5.2.17. Temporal ID Required: Optional JSON Type: Number Location: Track Object A number identifying the temporal layer/sub-layer encoding of the track, starting with 0 for the base layer, and increasing by 1 for the next higher temporal fidelity. 5.2.18. Spatial ID Required: Optional JSON Type: Number Location: Track Object Law & Nandakumar Expires 19 May 2027 [Page 27] Internet-Draft MOQT Streaming Format November 2026 A number identifying the spatial layer encoding of the track, starting with 0 for the base layer, and increasing by 1 for the next higher fidelity. 5.2.19. Codec Required: Conditional JSON Type: String Location: Track Object A string defining the codec used to encode the track. For LOC packaged content, the string codec registrations are defined in Section 3 and Section 4 of [WEBCODECS-CODEC-REGISTRY]. This property MUST be specified for tracks which have an inherent codec associated with them (e.g., audio and video tracks). It is not required for raw data tracks or event streams. 5.2.20. Mimetype Required: Optional JSON Type: String Location: Track Object A string defining the mime type [MIME] of the track. 5.2.21. Framerate Required: Optional JSON Type: Number Location: Track Object A number defining the framerate of the track, expressed as frames per second. This property SHOULD only accompany video or other frame- based content. 5.2.22. Timescale Required: Optional JSON Type: Number Location: Track Object The number of time units that pass per second. 5.2.23. Maximum Bitrate Required: Conditional JSON Type: Number Location: Track Object A number defining the maximum bitrate of the track, expressed in bits per second. This property MUST be specified for audio and video tracks. 5.2.24. Average Bitrate Required: Optional JSON Type: Number Location: Track Object Law & Nandakumar Expires 19 May 2027 [Page 28] Internet-Draft MOQT Streaming Format November 2026 A number defining the average bitrate of the track, over the lifetime of the track, expressed in bits per second. 5.2.25. Maximum GOP Duration Required: Optional JSON Type: Number Location: Track Object A number defining the maximum duration, expressed in milliseconds, between successive independently decodable points (random access points) in the media track. This property SHOULD only accompany video tracks. 5.2.26. Maximum Group Duration Required: Optional JSON Type: Number Location: Track Object A number defining the maximum duration, expressed in milliseconds, of any MOQT Group in this track. This value helps subscribers estimate buffer requirements for the track. 5.2.27. Width Required: Optional JSON Type: Number Location: Track Object A number expressing the maximum encoded width of the video frames in pixels. This property SHOULD accompany tracks which have a visual representation. 5.2.28. Height Required: Optional JSON Type: Number Location: Track Object A number expressing the maximum encoded height of the video frames in pixels. This property SHOULD accompany tracks which have a visual representation. 5.2.29. Audio sample rate Required: Conditional JSON Type: Number Location: Track Object The number of audio frame samples per second. This property MUST accompany tracks for which audio codecs are specified. 5.2.30. Channel configuration Required: Conditional JSON Type: String Location: Track Object Law & Nandakumar Expires 19 May 2027 [Page 29] Internet-Draft MOQT Streaming Format November 2026 A string specifying the audio channel configuration. A string is used in order to provide the flexibility to describe complex channel configurations for multi-channel and Next Generation Audio schemas. This property MUST accompany tracks for which audio codecs are specified. 5.2.31. Display width Required: Optional JSON Type: Number Location: Track Object A number expressing the intended display width of the track content in pixels. This property SHOULD only accompany tracks which have a visual representation. 5.2.32. Display height Required: Optional JSON Type: Number Location: Track Object A number expressing the intended display height of the track content in pixels. This property SHOULD only accompany tracks which have a visual representation. 5.2.33. Language Required: Optional JSON Type: String Location: Track Object A string defining the dominant language of the track. The string MUST be one of the standard Tags for Identifying Languages as defined by [LANG]. 5.2.34. Parent name Required: Optional JSON Type: String Location: Track Object A string defining the parent track name Section 5.2.3 to be cloned or updated. This field MUST only be included inside a 'clone' or 'update' operation in a delta update Section 5.1.6. The value is mapped and compared as defined in Section 11.2. 5.2.35. Parent namespace Required: Optional JSON Type: String Location: Track Object Law & Nandakumar Expires 19 May 2027 [Page 30] Internet-Draft MOQT Streaming Format November 2026 A string defining the parent track namespace Section 5.2.2 to be cloned, with the same syntax and constraints as Section 5.2.2, mapped and compared as defined in Section 11.2. This field MUST only be included inside a 'clone' or 'update' operation in a delta update Section 5.1.6. If this field is missing from a clone operation, then the namespace of the catalog is assumed. 5.2.36. Track duration Required: Optional JSON Type: Number Location: Track Object The duration of the track expressed in integer milliseconds. This field MUST NOT be included if the isLive Section 5.2.8 field value is true. 5.2.37. Connection URI Required: Optional JSON Type: String Location: Track Object A string containing the MOQT connection endpoint URI for the publish track. When specified, the subscriber MUST establish a new MOQT connection to this URI for publishing the track data. If this field is absent, the subscriber SHOULD reuse the existing MOQT connection that was used to receive the catalog. The URI MUST be a valid MOQT endpoint URI as defined by [MOQT], Section 6.1. Examples include "moqt://logs.example.com", "moqt://metrics.example.com:8443", or "moqt://logs.example.com/ moqt?a=1&b=2". 5.2.38. Encryption scheme Required: Optional JSON Type: String Location: Track Object A string identifying the encryption scheme used to protect the track content. The RECOMMENDED value is "moq-secure-objects" as defined in [SecureObjects]. If this field is absent, the track content is unencrypted. +====================+====================+=================+ | Name | Value | Reference | +====================+====================+=================+ | MoQ Secure Objects | moq-secure-objects | [SecureObjects] | +--------------------+--------------------+-----------------+ Table 8: Defined encryption schemes Law & Nandakumar Expires 19 May 2027 [Page 31] Internet-Draft MOQT Streaming Format November 2026 Custom encryption schemes MAY be used. Custom scheme names SHOULD use Reverse Domain Name Notation to avoid collisions (e.g., "com.example.custom-encryption"). 5.2.39. Cipher suite Required: Optional JSON Type: String Location: Track Object A string identifying the AEAD cipher suite used for encryption. This field MUST be present when the encryptionScheme is "moq-secure- objects". For the "moq-secure-objects" scheme, the following cipher suites are defined: +============================+============================+======+ | Name | Value | Tag | | | | Size | +============================+============================+======+ | AES-128-GCM-SHA256 | aes-128-gcm-sha256 | 128 | | | | bits | +----------------------------+----------------------------+------+ | AES-256-GCM-SHA512 | aes-256-gcm-sha512 | 128 | | | | bits | +----------------------------+----------------------------+------+ | AES-128-CTR-HMAC-SHA256-80 | aes-128-ctr-hmac-sha256-80 | 80 | | | | bits | +----------------------------+----------------------------+------+ Table 9: Cipher suites for moq-secure-objects Implementations MUST support "aes-128-gcm-sha256". Implementations SHOULD support "aes-128-ctr-hmac-sha256-80" for scenarios requiring smaller authentication tags. 5.2.40. Key ID Required: Optional JSON Type: String Location: Track Object A string identifying the key material used for encryption. This value is transmitted in the Secure Object KID extension header as defined in ([SecureObjects], Section 4.2) of each encrypted object. The keyId and associated trackBaseKey are obtained from an external key management system. The mechanism for obtaining these values is out of scope for this specification. Examples include MLS-based key distribution [E2EE-MLS] or other out-of-band key exchange mechanisms. Law & Nandakumar Expires 19 May 2027 [Page 32] Internet-Draft MOQT Streaming Format November 2026 The scope of a keyId is determined by the key management system in use. A keyId MAY be scoped to a single track, a single MSF session, or multiple tracks and sessions. When multiple tracks share the same Key ID, they MAY share the same base key material, though per-track keys are derived using the track name as defined in ([SecureObjects], Section 5). 5.2.41. Track Base Key Required: Optional JSON Type: String Location: Track Object A base64-encoded [BASE64] string containing the base key material for this track, as defined in ([SecureObjects], Section 5). This field works in conjunction with keyId to provide the cryptographic material needed for decryption. The trackBaseKey is obtained from the same key management system that provides the keyId. When present, this field contains the raw key material that, together with the track name and other parameters defined in ([SecureObjects], Section 5), is used to derive the actual encryption keys. Publishers and subscribers MUST use matching trackBaseKey values for successful decryption. 5.2.42. Authorization Info Required: Optional JSON Type: Object Location: Track Object An object indicating that authorization is required to access this track. The presence of this field signals to subscribers that they need to obtain and present valid authorization tokens when subscribing to this track. The keys of this object are authorization scheme identifiers. Allowed schemes are defined in Table 10. The values are scheme- specific configuration JSON elements defined by the referenced specifications. +==============+==============+===================+ | Scheme | Value | Reference | +==============+==============+===================+ | Privacy Pass | privacy-pass | [PrivacyPassAuth] | +--------------+--------------+-------------------+ | CAT | cat | [C4M] | +--------------+--------------+-------------------+ Table 10: Defined Authorization Schemes Law & Nandakumar Expires 19 May 2027 [Page 33] Internet-Draft MOQT Streaming Format November 2026 Custom authorization schemes MAY be used. Custom scheme names MUST use a unique naming convention, such as Reverse Domain Name Notation (e.g., "com.example.custom-auth"), to avoid naming collisions. Subscribers inspect the authInfo field to determine which authorization scheme to use and then obtain tokens through out-of- band mechanisms. The specific token format, acquisition process, and presentation method are defined by the authorization scheme specification. 5.2.43. Token Delivery via URI Tokens can be delivered to subscribers through the catalog request URI using variable substitution. Fragment parameters (following the # character) are processed client-side and can be substituted into catalog fields using the variable substitution mechanism defined in Section 5.4. For example, given a URI: moqt://relay.example.com/live#msf:namespace--name&token=XYZ789 A catalog with: "authInfo": { "cat": "%token%" } Would be resolved by the subscriber to include "cat": "XYZ789", which is then presented in control messages as specified by the authorization scheme. 5.2.44. Accessibility Required: Optional JSON Type: Array Location: Track Object An array of accessibility descriptors indicating accessibility features embedded within the track. Each descriptor is a JSON Object containing: * A required 'scheme' field (String) identifying the accessibility scheme. * A required 'value' field (String) specifying the accessibility channels or features available. Law & Nandakumar Expires 19 May 2027 [Page 34] Internet-Draft MOQT Streaming Format November 2026 +===============================+=========================+ | Scheme | Description | +===============================+=========================+ | urn:scte:dash:cc:cea-608:2015 | CEA-608 closed captions | +-------------------------------+-------------------------+ | urn:scte:dash:cc:cea-708:2015 | CEA-708 closed captions | +-------------------------------+-------------------------+ Table 11: Defined accessibility schemes The 'value' field for CEA-608/708 schemes uses the format defined by [SCTE214-1], where caption service channels are specified as semicolon-separated pairs of channel identifier and language code (e.g., "CC1=eng;CC3=spa"). A subscriber MAY use this information to determine caption availability and configure an appropriate caption decoder. 5.2.45. Accessible Window Time Required: Optional JSON Type: Number Location: Track Object The accessibleWindowTime defines a time delta in wallclock milliseconds behind the live edge at which content in this track remains accessible. This feature is often used to implement a 'DVR' window in live streams, in which content is only available for a fixed duration window which trails the live edge. To calculate the earliest available content, a client would subtract the accessibleWindowTime value from the current wallclock time to give the trailing threshold and then search the appropriate media timeline track for the earliest Group whose wallclock time is greater than this trailing threshold. If the track content is being encoded at a constant real-time temporal rate, then the accessibleWindowTime delta can be equally applied to the media time data within the media timeline track. Tracks assigned to the same alternate group Section 5.2.13 MUST carry the same accessibleWindowTime value. 5.2.46. Keyframe spacing Required: Optional JSON Type: Number Location: Track Object Law & Nandakumar Expires 19 May 2027 [Page 35] Internet-Draft MOQT Streaming Format November 2026 A number defining the number of objects per keyframe interval. A value of 15 means each group contains a keyframe followed by 14 predicted frames (15 objects total). A value of 600 means each group contains a keyframe followed by 599 predicted frames (600 objects total). This field is used by subscribers to calculate valid switch points when performing adaptive bitrate switching between tracks with different keyframe intervals. See Section 4.3 for publisher requirements and Section 6.3 for details on how to use this field. 5.3. Delta updates A catalog update might contain incremental changes. This is a useful property if many tracks may be initially declared but then there are small changes to a subset of tracks. The producer can issue a delta update to describe these changes. Changes are described incrementally, meaning that a delta update can itself modify a prior delta update. A restricted set of operations are allowed with each delta update: * Add a new track that has not previously been declared. * Add a new track by cloning a previously declared track. * Remove a track that has been previously declared. * Update properties of a previously declared track. The following rules are to be followed in constructing and processing delta updates: * A delta update MUST include the Delta Update Section 5.1.6 field with at least one operation and the generatedAt field Section 5.1.2. It MUST NOT include any other Root Catalog fields Section 5.1. * Operations are applied sequentially in the order they appear in the deltaUpdate array. Each operation is applied to the target document; the resulting document becomes the target of the next operation. Evaluation continues until all operations are successfully applied. * Producers that publish frequent delta updates SHOULD periodically publish a new independent catalog in a new MOQT Group in order to bound the amount of delta processing required for joining subscribers. * Error handling - any illogical update operation, such as adding an existing name, removing or updating an unknown track or cloning to an existing name MUST be rejected as an invalid catalog. Law & Nandakumar Expires 19 May 2027 [Page 36] Internet-Draft MOQT Streaming Format November 2026 5.4. Variable Substitution Catalog field values MAY contain variables that are substituted at delivery time. This mechanism enables a single cached catalog to be customized for each viewer, supporting use cases such as personalized advertising, A/B watermarking, QoE reporting endpoints, and logging identifiers. 5.4.1. Variable Syntax Variables are denoted by enclosing the variable name in percent characters (%). Variable names are case-sensitive. The percent character (%) MUST NOT appear in catalog field values except as part of a variable reference. Literal percent characters are not permitted. Variable values MUST consist only of alphanumeric characters, hyphens, underscores, plus sign, forward slash, equals, period and the at sign (@). Special characters including commas, semicolons, quotes, ampersands, and other punctuation MUST NOT appear in variable values. This restriction prevents injection attacks and ensures safe substitution into catalog field values. The rules of mapping catalog strings to MOQT byte values Section 11.2 are applied after variable substitution has been performed. 5.4.2. Variable Resolution Variables are resolved from the fragment identifier of the URI used to access the catalog. The fragment identifier is the portion following the # character and is processed entirely client-side, making it suitable for per-viewer customization without affecting server-side caching. Query parameters (following the ? character) are reserved for server- side processing and MUST NOT be used for variable substitution. When a subscriber requests a catalog using a URI containing a fragment identifier, the fragment is parsed as key-value pairs, using & as delimiter. Each pair is split at its first = character into a key and a value. Each key becomes available as a variable name, and the variable is replaced with the corresponding value. Law & Nandakumar Expires 19 May 2027 [Page 37] Internet-Draft MOQT Streaming Format November 2026 5.5. Catalog Compression Catalogs can contain significant redundancy, particularly when initialization data is included. To reduce payload size, catalog objects MAY be compressed using the MSF_COMPRESSION property (Section 12.1). If all catalog objects are compressed, the track property (Section 12.1.1) is used. If only some catalog objects are compressed (for example, the complete catalog is compressed while delta updates are not), the object property (Section 12.1.2) is used on each compressed object. 5.6. Catalog Examples The following section provides non-normative JSON examples of various catalogs compliant with this draft. 5.6.1. Time-aligned Audio/Video Tracks with single quality This example shows a catalog for a media producer capable of sending LOC packaged, time-aligned audio and video tracks. Law & Nandakumar Expires 19 May 2027 [Page 38] Internet-Draft MOQT Streaming Format November 2026 { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "1080p-video", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "video", "renderGroup": 1, "codec":"av01.0.08M.10.0.110.09", "width":1920, "height":1080, "framerate":30, "bitrate":1500000 }, { "name": "audio", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "audio", "renderGroup": 1, "codec":"opus", "samplerate":48000, "channelConfig":"2", "bitrate":32000 } ] } 5.6.2. Simulcast video tracks - 3 alternate qualities along with audio This example shows a catalog for a media producer capable of sending 3 time-aligned video tracks for high definition, low definition and medium definition video qualities, along with an audio track. In this example the namespace is absent, which infers that each track needs to inherit the namespace of the catalog. { "version": "draft-02", "generatedAt": 1746104606044, "tracks":[ { "name": "hd", Law & Nandakumar Expires 19 May 2027 [Page 39] Internet-Draft MOQT Streaming Format November 2026 "renderGroup": 1, "packaging": "loc", "isLive": true, "targetLatency": 1500, "role": "video", "codec":"av01.0.05M.08", "width":1920, "height":1080, "bitrate":5000000, "framerate":30, "altGroup":1 }, { "name": "md", "renderGroup": 1, "packaging": "loc", "isLive": true, "targetLatency": 1500, "role": "video", "codec":"av01.0.05M.08", "width":1280, "height":720, "bitrate":3000000, "framerate":30, "altGroup":1 }, { "name": "sd", "renderGroup": 1, "packaging": "loc", "isLive": true, "targetLatency": 1500, "role": "video", "codec":"av01.0.05M.08", "width":192, "height":144, "bitrate":500000, "framerate":30, "altGroup":1 }, { "name": "audio", "renderGroup": 1, "packaging": "loc", "isLive": true, "targetLatency": 1500, "role": "audio", "codec":"opus", Law & Nandakumar Expires 19 May 2027 [Page 40] Internet-Draft MOQT Streaming Format November 2026 "samplerate":48000, "channelConfig":"2", "bitrate":32000 } ] } 5.6.3. SVC video tracks with 2 spatial and 2 temporal qualities This example shows a catalog for a media producer capable of sending scalable video codec with 2 spatial and 2 temporal layers with a dependency relation as shown below: +----------+ +----------->| S1T1 | | | 1080p30 | | +----------+ | ^ | | +----------+ | | S1T0 | | | 1080p15 | | +----------+ +-----+----+ ^ | S0T1 | | | 480p30 | | +----------+ | ^ +----------+ | | S0T0 | | | 480p15 |---------+ +----------+ The corresponding catalog uses "depends" attribute to express the track relationships. { "version": "draft-02", "generatedAt": 1746104606044, "tracks":[ { "name": "480p15", "namespace": "conference.example.com/conference123/alice", "renderGroup": 1, "packaging": "loc", "isLive": true, "buffers": {"target":2000}, "role": "video", "codec":"av01.0.01M.10.0.110.09", Law & Nandakumar Expires 19 May 2027 [Page 41] Internet-Draft MOQT Streaming Format November 2026 "width":640, "height":480, "bitrate":3000000, "spatialId": 0, "temporalId": 0, "framerate":15 }, { "name": "480p30", "namespace": "conference.example.com/conference123/alice", "renderGroup": 1, "packaging": "loc", "isLive": true, "buffers": {"target":2000}, "role": "video", "codec":"av01.0.04M.10.0.110.09", "width":640, "height":480, "bitrate":3800000, "spatialId": 0, "temporalId": 1, "framerate":30, "depends": ["480p15"] }, { "name": "1080p15", "namespace": "conference.example.com/conference123/alice", "renderGroup": 1, "packaging": "loc", "isLive": true, "buffers": {"target":2000}, "role": "video", "codec":"av01.0.05M.10.0.110.09", "width":1920, "height":1080, "bitrate":6000000, "spatialId": 1, "temporalId": 0, "framerate":15, "depends":["480p15"] }, { "name": "1080p30", "namespace": "conference.example.com/conference123/alice", "renderGroup": 1, "packaging": "loc", "isLive": true, Law & Nandakumar Expires 19 May 2027 [Page 42] Internet-Draft MOQT Streaming Format November 2026 "buffers": {"target":2000}, "role": "video", "codec":"av01.0.08M.10.0.110.09", "width":1920, "height":1080, "bitrate":5000000, "spatialId": 1, "temporalId": 1, "framerate":30, "depends": ["480p30", "1080p15"] }, { "name": "audio", "namespace": "conference.example.com/conference123/alice", "renderGroup": 1, "packaging": "loc", "isLive": true, "buffers": {"target":2000}, "role": "audio", "codec":"opus", "samplerate":48000, "channelConfig":"2", "bitrate":32000 } ] } 5.6.4. Delta update - adding two tracks This example shows the catalog delta update for a media producer adding two tracks to an established video conference and modifying a property of an existing track. Of the tracks added, one track is newly declared, the other is cloned from an existing track. Law & Nandakumar Expires 19 May 2027 [Page 43] Internet-Draft MOQT Streaming Format November 2026 { "generatedAt": 1746104606044, "deltaUpdate": [ { "op": "update", "tracks": [ { "parentName": "video-1080", "bitrate": 4000000 } ] }, { "op": "add", "tracks": [ { "name": "slides", "packaging": "loc", "isLive": true, "role": "video", "codec": "av01.0.08M.10.0.110.09", "width": 1920, "height": 1080, "framerate": 15, "bitrate": 750000, "renderGroup": 1 } ] }, { "op": "clone", "tracks": [ { "parentName": "video-1080", "parentNamespace": "example.com/custom", "name": "video-720", "width": 1280, "height": 720, "bitrate": 600000 } ] } ] } Law & Nandakumar Expires 19 May 2027 [Page 44] Internet-Draft MOQT Streaming Format November 2026 5.6.5. Delta update removing tracks This example shows a delta update for a media producer removing two tracks from an established video conference. { "generatedAt": 1746104606044, "deltaUpdate": [ { "op": "remove", "tracks": [{"name": "video"}, {"name": "slides"}] } ] } 5.6.6. Time-aligned Audio/Video Tracks with custom field values This example shows a catalog for a media producer capable of sending LOC packaged, time-aligned audio and video tracks along with custom fields in each track description. Law & Nandakumar Expires 19 May 2027 [Page 45] Internet-Draft MOQT Streaming Format November 2026 { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "1080p-video", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "buffers": {"target":2000, "min": 1500, "max": 5000}, "role": "video", "renderGroup": 1, "codec":"av01.0.08M.10.0.110.09", "width":1920, "height":1080, "framerate":30, "bitrate":1500000, "com.example-billing-code": 3201, "com.example-tier": "premium", "com.example-debug": "h349835bfkjfg82394d945034jsdfn349fns" }, { "name": "audio", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "buffers": {"target":2000, "min": 1500, "max": 5000}, "role": "audio", "renderGroup": 1, "codec":"opus", "samplerate":48000, "channelConfig":"2", "bitrate":32000 } ] } 5.6.7. Time-aligned VOD Audio/Video Tracks This example shows a catalog for a media producer offering VOD (video on-demand) non-live content. The content is LOC packaged, and includes time-aligned audio and video tracks. Law & Nandakumar Expires 19 May 2027 [Page 46] Internet-Draft MOQT Streaming Format November 2026 { "version": "draft-02", "tracks": [ { "name": "video", "namespace": "movies.example.com/assets/boy-meets-girl-season3/episode5", "packaging": "loc", "isLive": false, "trackDuration": 8072340, "renderGroup": 1, "codec":"av01.0.08M.10.0.110.09", "role": "video", "width":1920, "height":1080, "framerate":30, "bitrate":1500000 }, { "name": "audio", "namespace": "movies.example.com/assets/boy-meets-girl-season3/episode5", "packaging": "loc", "isLive": false, "trackDuration": 8072340, "renderGroup": 1, "codec":"opus", "role": "audio", "samplerate":48000, "channelConfig":"2", "bitrate":32000 } ] } 5.6.8. Encrypted Audio/Video Tracks This example shows a catalog for encrypted LOC-packaged audio and video tracks using MoQ Secure Objects with AES-128-GCM. This catalog is encrypted end-to-end and its content cannot be read by relays. Law & Nandakumar Expires 19 May 2027 [Page 47] Internet-Draft MOQT Streaming Format November 2026 { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "1080p-video", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "video", "renderGroup": 1, "codec": "av01.0.08M.10.0.110.09", "width": 1920, "height": 1080, "framerate": 30, "bitrate": 1500000, "encryptionScheme": "moq-secure-objects", "cipherSuite": "aes-128-gcm-sha256", "keyId": "key-2024-q1-premium", "trackBaseKey": "MTIzNDU2Nzg5MDEyMzQ1Ng==" }, { "name": "audio", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "audio", "renderGroup": 1, "codec": "opus", "samplerate": 48000, "channelConfig": "2", "bitrate": 32000, "encryptionScheme": "moq-secure-objects", "cipherSuite": "aes-128-gcm-sha256", "keyId": "key-2024-q1-premium", "trackBaseKey": "MTIzNDU2Nzg5MDEyMzQ1Ng==" } ] } Law & Nandakumar Expires 19 May 2027 [Page 48] Internet-Draft MOQT Streaming Format November 2026 5.6.9. Media timeline and Event timeline This example shows a catalog for a media producer capable of sending LOC packaged, time-aligned audio and video tracks, along with a Media Timeline which describes the history of those tracks and an Event Timeline providing synchronized data. Additionally, the accessibleWindowTime attribute of the video track defines a 5 min 'DVR window'. { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "history", "namespace": "conference.example.com/conference123/alice", "packaging": "mediatimeline", "isLive": true, "mimeType": "application/json", "depends": [1] }, { "name": "identified-objects", "namespace": "another-provider/time-synchronized-data", "packaging": "eventtimeline", "isLive": true, "eventType": "com.ai-extraction/appID/v3", "depends": ["history"] }, { "name": "1080p-video", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "accessibleWindowTime": 300000, "targetLatency": 2000, "role": "video", "renderGroup": 1, "codec":"av01.0.08M.10.0.110.09", "width":1920, "height":1080, "framerate":30, "bitrate":1500000 }, { "name": "audio", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", Law & Nandakumar Expires 19 May 2027 [Page 49] Internet-Draft MOQT Streaming Format November 2026 "isLive": true, "targetLatency": 2000, "role": "audio", "renderGroup": 1, "codec":"opus", "samplerate":48000, "channelConfig":"2", "bitrate":32000 } ] } 5.6.10. Media timeline template This example shows a catalog using inline media timeline templates instead of an explicit media timeline track. The Section 5.2.16 attribute on each track defines a regular pattern where each segment is 2002ms long. Clients can compute any entry using the template parameters. Note that different tracks MAY have different template values to accommodate different group durations. Law & Nandakumar Expires 19 May 2027 [Page 50] Internet-Draft MOQT Streaming Format November 2026 { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "1080p-video", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "video", "renderGroup": 1, "template": [0, 2002, [0, 0], [1, 0], 1759924158381, 2002], "codec":"av01.0.08M.10.0.110.09", "width":1920, "height":1080, "framerate":30, "bitrate":1500000 }, { "name": "audio", "namespace": "conference.example.com/conference123/alice", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "audio", "renderGroup": 1, "template": [0, 2002, [0, 0], [1, 0], 1759924158381, 2002], "codec":"opus", "samplerate":48000, "channelConfig":"2", "bitrate":32000 } ] } 5.6.11. Video track with embedded captions and SCTE-35 events This example shows a live broadcast with CEA-608 closed captions embedded in the video track and a separate SCTE-35 event timeline for ad insertion. { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "video", Law & Nandakumar Expires 19 May 2027 [Page 51] Internet-Draft MOQT Streaming Format November 2026 "packaging": "loc", "isLive": true, "targetLatency": 4000, "role": "video", "renderGroup": 1, "codec": "avc1.4d401f", "width": 1920, "height": 1080, "framerate": 30, "bitrate": 5000000, "accessibility": [ { "scheme": "urn:scte:dash:cc:cea-608:2015", "value": "CC1=eng;CC3=spa" } ] }, { "name": "audio", "packaging": "loc", "isLive": true, "targetLatency": 4000, "role": "audio", "renderGroup": 1, "codec": "opus", "samplerate": 48000, "channelConfig": "2", "bitrate": 128000 }, { "name": "video-timeline", "packaging": "mediatimeline", "isLive": true, "depends": ["video"] }, { "name": "scte35", "packaging": "eventtimeline", "eventType": "urn:scte:scte35:2013:bin", "isLive": true, "depends": ["video-timeline"] } ] } Law & Nandakumar Expires 19 May 2027 [Page 52] Internet-Draft MOQT Streaming Format November 2026 5.6.12. Video track with CEA-708 captions This example shows a live broadcast with CEA-708 closed captions embedded in the video track, demonstrating multiple caption services. { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "video", "packaging": "loc", "isLive": true, "targetLatency": 4000, "role": "video", "renderGroup": 1, "codec": "hev1.1.6.L93.B0", "width": 1920, "height": 1080, "framerate": 30, "bitrate": 4000000, "accessibility": [ { "scheme": "urn:scte:dash:cc:cea-708:2015", "value": "1=lang:eng;2=lang:spa;3=lang:fra" } ] }, { "name": "audio", "packaging": "loc", "isLive": true, "targetLatency": 4000, "role": "audio", "renderGroup": 1, "codec": "mp4a.40.2", "samplerate": 48000, "channelConfig": "2", "bitrate": 128000 } ] } 5.6.13. Terminating a live broadcast This example shows a catalog for a media producer terminating a previously live broadcast containing a video and an audio track. Law & Nandakumar Expires 19 May 2027 [Page 53] Internet-Draft MOQT Streaming Format November 2026 { "version": "draft-02", "generatedAt": 1746104606044, "isComplete": true, "tracks": [] } 5.6.14. Variable Substitution for personalized delivery This example shows a catalog using variable substitution to enable personalized advertising and reporting while maintaining cacheability. Given a catalog request URI of: moqt://sports.example.com/catalog?a=1#msf:namespace-- catalog&token=1234&id=c3e5s7w&event=xyz The fragment parameters (token, id, event) are available for variable substitution. The following catalog template: { "version": "draft-02", "tracks": [ { "name": "video", "codec": "av01.0.08M.10.0.110.09", "bitrate": 5000000, "framerate": 30, "packaging": "loc", "isLive": true, "role": "video", "renderGroup": 1 }, { "name": "tracking-%id%", "namespace": "advertising-decisions/live-sports/%event%", "packaging": "eventtimeline", "isLive": true, "eventType": "com.example.iab.vast", "authInfo": { "cat": "%token%" } } ] } would be resolved by the subscriber as: Law & Nandakumar Expires 19 May 2027 [Page 54] Internet-Draft MOQT Streaming Format November 2026 { "version": "draft-02", "tracks": [ { "name": "video", "codec": "av01.0.08M.10.0.110.09", "bitrate": 5000000, "framerate": 30, "packaging": "loc", "isLive": true, "role": "video", "renderGroup": 1 }, { "name": "tracking-c3e5s7w", "namespace": "advertising-decisions/live-sports/xyz", "packaging": "eventtimeline", "isLive": true, "eventType": "com.example.iab.vast", "authInfo": { "cat": "1234" } } ] } 5.6.15. Time-aligned Audio/Video Tracks with Authorization This example shows a catalog for a media producer requiring authorization for premium content. The premium 4K track uses CAT authorization with a token resolved via variable substitution from %cat-token%. The standard 720p track uses Privacy Pass with a token resolved from %pp-token%. Token presentation timing is determined by the authorization scheme specification. { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "premium-4k-video", "namespace": "streaming.example.com/live/sports", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "video", "renderGroup": 1, "altGroup": 1, Law & Nandakumar Expires 19 May 2027 [Page 55] Internet-Draft MOQT Streaming Format November 2026 "codec": "av01.0.12M.10.0.110.09", "width": 3840, "height": 2160, "framerate": 60, "bitrate": 15000000, "authInfo": { "cat": "%cat-token%" } }, { "name": "standard-720p-video", "namespace": "streaming.example.com/live/sports", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "video", "renderGroup": 1, "altGroup": 1, "codec": "av01.0.05M.10.0.110.09", "width": 1280, "height": 720, "framerate": 30, "bitrate": 2500000, "authInfo": { "privacy-pass": "%pp-token%" } }, { "name": "audio", "namespace": "streaming.example.com/live/sports", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "audio", "renderGroup": 1, "codec": "opus", "samplerate": 48000, "channelConfig": "2", "bitrate": 128000 } ] } 5.6.16. A catalog referencing other catalogs This example shows a catalog referencing three other catalogs, one of which is in a different namespace. Law & Nandakumar Expires 19 May 2027 [Page 56] Internet-Draft MOQT Streaming Format November 2026 { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "premium-catalog", "isLive": true, "packaging": "catalog" }, { "name": "free-catalog", "isLive": true, "packaging": "catalog" }, { "name": "camera33-catalog", "namespace": "example.com/blimps-R-us", "packaging": "catalog", "isLive": true, "label": "Eye From the Sky video feeds" } ] } 5.6.17. Publish tracks for logs and metrics This example shows a catalog that includes publish tracks for client- side logging and metrics collection. The subscriber can publish QoE data and logs back to the delivery system using these track definitions. The namespace and track name formats follow the conventions defined in [MOQLOG] and [MOQMETRICS]. { "version": "draft-02", "generatedAt": 1746104606044, "tracks": [ { "name": "video", "namespace": "broadcast.example.com/live/stream1", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "video", "renderGroup": 1, "codec": "av01.0.08M.10.0.110.09", "width": 1920, "height": 1080, "framerate": 30, Law & Nandakumar Expires 19 May 2027 [Page 57] Internet-Draft MOQT Streaming Format November 2026 "bitrate": 1500000 }, { "name": "audio", "namespace": "broadcast.example.com/live/stream1", "packaging": "loc", "isLive": true, "targetLatency": 2000, "role": "audio", "renderGroup": 1, "codec": "opus", "samplerate": 48000, "channelConfig": "2", "bitrate": 32000 } ], "publishTracks": [ { "namespace": "metrics.moq.arpa/metrics-v1/%resourceId%", "name": "4", "isLive": true, "packaging": "moqmetrics", "role": "metrics", "authInfo": { "cat": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." } }, { "namespace": "moq-syslog.arpa/logs-v1/%resourceId%", "name": "6", "isLive": true, "packaging": "moqlog", "role": "log", "connectionURI": "moqt://logs.example.com:4443", "authInfo": { "cat": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." } } ] } In this example: * The metrics track uses the namespace format defined in [MOQMETRICS] with %resourceId% as a placeholder for the subscriber's unique resource identifier. The track name "4" indicates Warning level granularity. Law & Nandakumar Expires 19 May 2027 [Page 58] Internet-Draft MOQT Streaming Format November 2026 * The log track uses the namespace format defined in [MOQLOG] with %resourceId% as a placeholder. The track name "6" indicates Informational level priority. * Both tracks include authentication tokens for publishing authorization. * The subscriber MUST replace %resourceId% with their actual resource identifier as defined in the respective specifications. 6. Media transmission The MOQT Groups and MOQT Objects need to be mapped to MOQT Streams. This mapping is defined by the packaging Section 4 type of each track. Each MOQT Object SHOULD be placed on MOQT Subgroup 0, unless otherwise defined by the packaging type. For LOC-packaged tracks, the mapping is signaled per-track via Section 5.2.5 as defined in Section 4.1.1. 6.1. Group numbering Group IDs for a track MUST be unique and MUST increase monotonically. Within a continuous publishing session, each subsequent Group ID SHOULD increase by 1. When a publisher restarts (e.g., after connectivity loss or encoder restart), it MUST ensure the new starting Group ID is greater than any previously published Group ID for that track. One approach is to use the current wall clock time in milliseconds since the Unix epoch as the starting Group ID. If a publisher maintains state across a restart and knows the previous Group ID, it SHOULD signal the gap using the PRIOR_GROUP_ID_GAP property [MOQT], Section 10.8. 6.2. Object Numbering Object ID MUST be zero for the first Object within a Group and then MUST increase monotonically by one within that Group. 6.3. Multi-Variant Fast Track Switching This section specifies how a subscriber switches between tracks within an alternate group that have dissimilar keyframeSpacing values. Publishers MUST package such tracks as described in Section 4.3. Additional background, implementation guidance and evaluation of this technique are provided in [MVFTS]. Law & Nandakumar Expires 19 May 2027 [Page 59] Internet-Draft MOQT Streaming Format November 2026 6.3.1. Switching Procedure To minimize join latency when joining an alternate group, a subscriber SHOULD first subscribe to the track with the closest switch point that satisfies the bandwidth constraints. Once playback begins, the subscriber MAY switch to a track with a larger keyframeSpacing at a valid switch point, calculated as described in Section 6.3.2. 6.3.2. Calculating Valid Switch Points Given a source track with keyframeSpacing S and a target track with keyframeSpacing T, a switch from Group ID G and Object ID N of the source track is valid if: (G * S + N) / T yields an integer. That integer is the Group ID in the target track at which the subscriber begins receiving objects, starting at Object ID 0. 7. Media Timeline track The media timeline track provides data about the previously published Groups and their relationship to wallclock time and media time. Media timeline tracks allow players to seek to precise points behind the live head in a live broadcast, or for random access in a VOD asset. Media timeline tracks are optional. Multiple media timeline tracks can exist inside a catalog. A media timeline track MAY describe content that lies outside the accessibility window defined by the Accessible Window Time Section 5.2.45 track property. Publishers of media timeline tracks SHOULD trim their media timeline so as to not describe content outside of the availability window. Subscribers of media timeline tracks MUST apply any Accessible Window Time constraints before attempting to retrieve content based on a media timeline description. 7.1. Media Timeline track payload A media timeline track is a JSON [JSON] document. This document MAY be compressed using the MSF_COMPRESSION property (Section 12.1). The document supports two formats: an explicit entry format and a template format. A media timeline track MUST NOT use both formats. The media timeline payload describes when a Group is published within a track. While usually regular in cadence, this publication may also be sparse and irregular and this sparseness will be reflected in the Law & Nandakumar Expires 19 May 2027 [Page 60] Internet-Draft MOQT Streaming Format November 2026 media and wallclock timestamps associated with each group. Additionally, there is no requirement from a media timeline perspective that the group numbers are sequential or are monotonically increasing. 7.1.1. Explicit entry format The explicit format contains an array of records. Each record consists of an array of three required items, whose ordinal position defines their type: * The first item holds the media presentation timestamp, expressed as a JSON Number. This value MUST match the media presentation timestamp, expressed as the floor in integral milliseconds, of the first media sample in the referenced Object. Implementers who require increased time precision can parse the retrieved media object itself. * The second item holds the MOQT Location of the entry, defined as a tuple of the MOQT Group ID and MOQT Object ID, and expressed as a JSON Array of Numbers, where the first number is the Group ID and the second number is the Object ID. * The third item holds the wallclock time at which the content, represented by the media presentation timestamp, entered the encoder. Wallclock time is defined by Section 11.6. For VOD assets, or if the wallclock time is not known, the value SHOULD be 0. The media timeline track is ordered by media time. An example media timeline is shown below: [ [0, [0,0], 1759924158381], [2002, [1,0], 1759924160383], [4004, [2,0], 1759924162385], [6006, [3,0], 1759924164387], [8008, [4,0], 1759924166389] ] Law & Nandakumar Expires 19 May 2027 [Page 61] Internet-Draft MOQT Streaming Format November 2026 7.2. Media Timeline Catalog requirements A media timeline track MUST carry a 'packaging' Section 5.2.4 attribute with a value of "mediatimeline". A media timeline track MUST carry a 'depends' attribute which contains an array of any track names and renderGroups to which the media timeline track applies. If all tracks in a renderGroup match the media timeline, then the renderGroup MUST be referenced and the individual track names MUST NOT be referenced. If only a subset of tracks in the renderGroup match the media timeline, then the renderGroup MUST NOT be referenced and the individual tracks MUST be referenced. If multiple tracks are referenced and then one of those tracks ceases publication, the publisher MUST produce a catalog update which removes the 'depends' reference of the track that ceased publication. If that track then becomes available as VOD content, a new media timeline track needs to be published to describe the content available in that track. 7.3. Media Timeline track updating The publisher MUST publish an independent media timeline in the first MOQT Object of each MOQT Group of a media timeline track. An independent media timeline object MUST contain all media timeline records accumulated and accessible up to that point, allowing a subscriber joining at any group boundary to receive the accessible timeline history. The publisher MAY publish incremental updates in the second and subsequent Objects within each Group. Incremental updates contain only new media timeline records since the previous media timeline Object in that Group. 7.4. Media Timeline Template When the relationship between media time, MOQT Location and wallclock time follows a regular, predictable pattern, a media timeline template MAY be used instead of an explicit media timeline track. The template approach is best suited for content with fixed-duration segments, such as VOD assets or live broadcasts with constant segment durations. For content with variable segment durations, the explicit media timeline track (Section 7.1) MUST be used instead. 7.4.1. Template Format A media timeline template is expressed as an inline track attribute using the Section 5.2.16 field. The template is a JSON Array containing six mandatory values in the following fixed order: Law & Nandakumar Expires 19 May 2027 [Page 62] Internet-Draft MOQT Streaming Format November 2026 1. startMediaTime - The media presentation timestamp of the first entry, as defined for media timeline entries in Section 7.1.1. 2. deltaMediaTime - The constant interval between media presentation timestamps, expressed as a JSON Number in milliseconds. 3. startLocation - The MOQT Location of the first entry, as defined for media timeline entries in Section 7.1.1. 4. deltaLocation - The constant interval between MOQT Locations, expressed as a JSON Array of two Numbers where the first number is the Group ID delta and the second number is the Object ID delta. 5. startWallclock - The wallclock time of the first entry, as defined for media timeline entries in Section 7.1.1. For VOD assets, or if the wallclock time is not known, the value SHOULD be 0. 6. deltaWallclock - The constant interval between wallclock times, expressed as a JSON Number in milliseconds. For VOD assets, or if the wallclock time is not known, the value SHOULD be 0. All six values are mandatory and MUST appear in the specified order. Clients compute entry values using the following formulas, where n is the zero-based entry index: mediaTime[n] = startMediaTime + (n * deltaMediaTime) location[n] = [startLocation[0] + (n * deltaLocation[0]), startLocation[1] + (n * deltaLocation[1])] wallclock[n] = startWallclock + (n * deltaWallclock) An example template value is shown below: [0, 2002, [0, 0], [1, 0], 1759924158381, 2002] This template indicates that the first entry has media time 0ms, location [0,0], and wallclock time 1759924158381. Each subsequent entry increments media time by 2002ms, location by [1,0] (next group, same object), and wallclock by 2002ms. 7.4.2. Template Immutability Unlike the explicit media timeline track, the media timeline template is intended to be immutable once publishing starts. Publishers MUST NOT change the template values for a track after the first Object has been published. Law & Nandakumar Expires 19 May 2027 [Page 63] Internet-Draft MOQT Streaming Format November 2026 8. Event Timeline track The event timeline track provides a mechanism to associate ad-hoc event metadata with the broadcast. Use-case examples include live sports score data, GPS coordinates of race cars, SAP-types for media segments or active speaker notifications in web conferences. To allow the client to bind this event metadata with the broadcast content described by the media timeline track, each event record MUST contain a reference to one of Media PTS, wallclock time or MOQT Location. Event timeline tracks are optional. Multiple event timeline tracks can exist inside a catalog. The type & structure of the data contained within each event timeline track is declared in the catalog, to facilitate client selection and parsing. Event timeline tracks can be present in both the 'tracks' and 'publishTracks' arrays, implying that they can be both consumed and produced by an endpoint. 8.1. Event Timeline header data Certain event payloads require header data to help initialize or give context to the payload data, which consists solely of an array of records. This header data is typically invariant over the life of the track. This header data is communicated by the MSF_EVENT_TIMELINE_HEADER Track property Section 12.3.1. Subscribers to an Event Timeline Track MUST check for the presence of this track property before parsing the payload of the event timeline track. Usage of this track property is optional. Absence of the MSF_EVENT_TIMELINE_HEADER Track property indicates that no header data is provided for the Event Timeline Track. 8.1.1. Example of Event Timeline header data Consider an example of drone telemetry. The catalog defines the track as an event timeline. Law & Nandakumar Expires 19 May 2027 [Page 64] Internet-Draft MOQT Streaming Format November 2026 { "name": "telemetry", "namespace": "live.example.com/flight/1", "packaging": "eventtimeline", "isLive": true, "eventType": "com.example.dronetelemetry", "depends": ["1080p-video"] } The publisher sends contextual metadata in the MSF_EVENT_TIMELINE_HEADER property, serialized as the following JSON object. {"crs": "WGS84", "fields": ["latitude", "longitude", "altitude"], "altitudeUnit": "meter"} This data is used by the subscriber to correctly interpret the event timeline records. Transmitting this data once in the property is more efficient than repeating it in each record. [ {"L": [0,0], "data": [47.1812, 8.4592, 488.2]}, {"L": [1,0], "data": [47.1662, 8.5155, 502.7]} ] 8.2. Event Timeline data format An event timeline track is a JSON [JSON] document. This document MAY be compressed using the MSF_COMPRESSION property (Section 12.1). The document contains an array of records. Each record consists of a JSON Object containing the following required fields: * An index reference, which MUST be either 'T' for wallclock time, 'L' for Location or 'M' for Media PTS. Only one of these index values may be used within each record. Event timelines SHOULD use the same index reference type for each record. The definitions for wallclock time, Location and Media PTS are identical to those defined for media timeline payload Section 7.1. Wallclock time and media PTS values are JSON Number, while Location value is an Array of Numbers, where the first item represents the MOQT GroupID and the second item the MOQT Object ID. * A 'data' field, a JSON value whose structure is defined by the eventType Section 5.2.6 value declared for this track in the Catalog. Law & Nandakumar Expires 19 May 2027 [Page 65] Internet-Draft MOQT Streaming Format November 2026 8.3. Event Timeline Catalog requirements An event timeline track MUST carry: * a 'packaging' Section 5.2.4 attribute with a value of "eventtimeline". * an 'eventType' Section 5.2.6 attribute declaring the type & structure of data contained in the event timeline track. If an Event Timeline track has an index reference which refers to one or more Media Timeline tracks, then those Media Timeline tracks MUST be listed in a 'depends' Section 5.2.15 field within the Event Timeline track definition. 8.4. Event Timeline track updating The mapping of Event Timeline payloads to MOQT Groups is defined by the 'eventType'. If the data in the event timeline track is to be consumed as a sequence, then the publisher SHOULD publish an independent event timeline in the first MOQT Object of each MOQT Group of an event timeline track. An independent event timeline object SHOULD contain all event timeline records accumulated and accessible up to that point, allowing a subscriber joining at any group boundary to receive the accessible event history. The publisher MAY publish incremental updates in the second and subsequent Objects within each Group. Incremental updates contain only new event timeline records since the previous event timeline Object in that Group. If the data in the event timeline track is independent of its history, then the publisher SHOULD publish each record in its own MOQT Group and use a single MOQT Object per MOQT Group. 8.5. Well-known event timeline types Event timelines can carry various types of broadcast metadata synchronized with media content. The "MSF Event Timeline Types" registry (Section 14.2) is established by this document but has no initial entries; entries are registered by the specifications that define each event type, which are expected to include: * Ad insertion signaling (e.g., SCTE-35 splice points) - see [SCTE35-MSF] * Out-of-band timed-text cues (WebVTT, IMSC1) - see [WebVTT-MSF] and [IMSC1-MSF] Law & Nandakumar Expires 19 May 2027 [Page 66] Internet-Draft MOQT Streaming Format November 2026 Other data types, for example sports scores and game state, GPS coordinates and telemetry, active speaker notifications, and custom application-specific metadata, MAY also be carried on event timeline tracks, defined by their own specifications and registered accordingly. The packaging format and data structure for each event type is defined by the specification referenced in the registry. Custom event types not intended for registration SHOULD use Reverse Domain Name Notation (e.g., "com.example.myeventtype") to avoid naming collisions. 8.6. Event timeline track payload examples 8.6.1. Event timeline track with wallclock time indexing This example shows how sports scores and game information might be defined in a live sports broadcast. [ { "T": 1756885678361, "data": { "status": "in_progress", "period": 1, "clock": "12:00", "homeScore": 0, "awayScore": 0, "lastPlay": "Game Start" } }, { "T": 1756885981542, "data": { "status": "in_progress", "period": 1, "clock": "09:25", "homeScore": 2, "awayScore": 0, "lastPlay": "Team A: #23 makes 2-pt jump shot" } } ] 8.6.2. Event timeline track with MOQT Location indexing This example shows drone GPS coordinates synched with the start of each Group. Law & Nandakumar Expires 19 May 2027 [Page 67] Internet-Draft MOQT Streaming Format November 2026 [ { "L": [0,0], "data": [47.1812,8.4592] }, { "L": [1,0], "data": [47.1662,8.5155] } ] 8.6.3. Event timeline track with media time indexing This example shows an object identification track from a hypothetical video indexing system. [ { "M": 23051, "data": { "object_id": "obj_00123", "class": "human", "attributes": { "sex": "male", "action": "eating dinner" }, "bounding_box": { "x": 312, "y": 140, "width": 180, "height": 260 }, "confidence": 0.94 } }, { "M": 43796, "data": { "object_id": "obj_00124", "class": "object", "attributes": { "type": "dog", "action": "sitting" }, "bounding_box": { "x": 20, "y": 300, "width": 120, "height": 90 }, "confidence": 0.88 } } ] Law & Nandakumar Expires 19 May 2027 [Page 68] Internet-Draft MOQT Streaming Format November 2026 9. Log track Log tracks provide a mechanism for subscribers to publish diagnostic and operational log data back to the delivery system. This enables QoE monitoring, debugging, and analytics collection. Log tracks are defined in the catalog's publishTracks array with a packaging value of "moqlog". 9.1. Log track payload The log track payload format is defined in [MOQLOG]. Each MOQT Object contains a single JSON-formatted log entry. The log entry structure includes optional fields such as severity, timestamp, hostname, application name, process ID, message ID, and the log message itself. Additional structured data fields support distributed tracing integration with TraceID, SpanID, and InstrumentationScope aligned with OpenTelemetry specifications. Implementations MUST follow the object payload format specified in [MOQLOG], Section 4. 9.2. Log track namespace and name The log track's namespace is defined by the Section 5.2.2 field and converted to bytes according to Section 11.2. The Track Name is the ASCII decimal representation of the log priority level (for example, "6" for Informational), mapped to bytes as defined in Section 11.2. Priority levels range from 0 (Emergency) to 7 (Debug), following syslog severity conventions. 9.3. Log track Group ID and Object ID The Group ID represents the timestamp at which the log entry was captured, truncated to a 62-bit binary integer representing microseconds since the Unix epoch. This allows log entries to be naturally ordered by time within the MOQT object model. The Object ID is set to zero for a log entry unless multiple log messages occur within the same microsecond, in which case the Object ID increments to distinguish between messages captured at the same timestamp. 9.4. Log track catalog requirements A log track MUST be declared in the publishTracks array of the catalog with: * a Section 5.2.4 attribute with a value of "moqlog". Law & Nandakumar Expires 19 May 2027 [Page 69] Internet-Draft MOQT Streaming Format November 2026 * a Section 5.2.7 attribute with a value of "log". A log track MAY include: * a Section 5.2.37 attribute if logs should be published to a different endpoint. * an Section 5.2.42 attribute for publish authorization. 10. Metrics track Metrics tracks provide a mechanism for subscribers to publish quantitative measurements back to the delivery system. This enables QoE analytics, performance monitoring, and operational dashboards. Metrics tracks are defined in the catalog's publishTracks array with a packaging value of "moqmetrics". 10.1. Metrics track payload The metrics track payload format is defined in [MOQMETRICS]. The data model consists of Resources (systems generating metrics identified by ResourceID), optional Attributes (dimensional key-value pairs), and Metrics (named measurements with timeseries values). [MOQMETRICS] defines two metric value types - Gauge and Counter. Both value types support either 64-bit floating point or integer representation. Implementations MUST follow the object payload format specified in [MOQMETRICS], Section 3. 10.2. Metrics track namespace and name The metric track's namespace is defined by the Section 5.2.2 field and converted to bytes according to Section 11.2. The Track Name identifies the granularity level for the metrics being published, specified as an ASCII decimal representation, where granularity-level is a value from 0 (Emergency) to 7 (Debug). Higher priority levels (lower numbers) indicate more critical metrics that should always be reported. 10.3. Metrics track Group ID and Object ID The Group ID represents the capture time as the number of milliseconds since January 1, 1970 (Unix epoch). This allows metrics to be naturally grouped and ordered by their capture timestamp within the MOQT object model. Within each Group, Object IDs are assigned as follows: Law & Nandakumar Expires 19 May 2027 [Page 70] Internet-Draft MOQT Streaming Format November 2026 * *Object ID 0*: Contains the capture timestamp as Unix epoch time in nanoseconds, along with any optional attributes for the metrics in this group. * *Object ID 1 and above*: Each subsequent Object contains an individual metric as a name-value pair. This structure allows a single capture event to include multiple metrics while maintaining efficient MOQT caching and distribution. 10.4. Metrics track catalog requirements A metrics track MUST be declared in the publishTracks array of the catalog with: * a Section 5.2.4 attribute with a value of "moqmetrics". * a Section 5.2.7 attribute with a value of "metrics". A metrics track MAY include: * a Section 5.2.37 attribute if metrics should be published to a different endpoint. * a Section 5.2.42 attribute for publish authorization. 11. Workflow 11.1. URL construction and interpretation An MSF URL identifies a MOQT session and an optional sub-resource within that session. It inherits the MOQT URI scheme defined in [MOQT] and extends it to add a fragment definition, which defines the type, the namespace and name of the track along with optional key- value attributes. ; MSF URI Definition ; The following rules are imported from RFC 3986: ; authority (Section 3.2) ; path-abempty (Section 3.3) ; query (Section 3.4) msf-uri = "moqt://" authority path-abempty [ "?" query ] "#" msf-fragment The MOQT specification carries the normative definition of these components, along with processing instructions. They are repeated here for clarity. In the event of any conflict, the definition in [MOQT] is authoritative. Law & Nandakumar Expires 19 May 2027 [Page 71] Internet-Draft MOQT Streaming Format November 2026 * Scheme: This case-insensitive scheme defines the underlying transport. The client may use either a WebTransport or native QUIC connection. A moqt URI can be converted to an https URI by replacing the scheme, so the path-abempty and query components use the same syntax as https URIs. * Authority: Required. Contains the host and optional port (defaulting to 443). This information is used by the client to establish the transport session. * Path: Optional. If present, it provides server-specific configuration or routing information used during connection initialization. * Query: Optional. Contains key-value parameters separated by &. If the query is absent, the ? separator MUST be omitted. Query arguments are intended for the server and SHOULD be ignored by the client. This specification registers a fragment type of "msf" in the "MOQT URI Fragment Types" registry established by [MOQT] (see Section 14). This type is required for any URL defining an MSF resource. The value of this type is the msf-fragment-value. The msf-fragment is defined by the following ABNF: Law & Nandakumar Expires 19 May 2027 [Page 72] Internet-Draft MOQT Streaming Format November 2026 ; MSF Fragment Definition ; The following rules are imported from RFC 3986: ; pchar (Section 3.3) ; unreserved (Section 2.3) ; pct-encoded (Section 2.1) ; sub-delims (Section 2.2) msf-fragment = "msf:" msf-fragment-value msf-fragment-value = track-identifier [ "&" parameter-list ] track-identifier = 1*( pchar-no-amp / "/" ) ; MSF namespace-name string ; MUST NOT contain '&' or '?' ; '?' MUST be percent-encoded as %3F within this component parameter-list = parameter *( "&" parameter ) parameter = param-name "=" param-value param-name = 1*( pchar-no-amp / "/" ) param-value = *( pchar-no-amp / "/" ) ; Derived from RFC 3986 pchar (Section 3.3), excluding '&' and '?': ; pchar = unreserved / pct-encoded / sub-delims / ":" / "@" ; '&' is excluded as it serves as the MSF fragment component delimiter. ; '?' is excluded to avoid ambiguity with the URI query component delimiter. pchar-no-amp = unreserved / pct-encoded / sub-delims-no-amp / ":" / "@" ; Derived from RFC 3986 sub-delims (Section 2.2), excluding '&': ; sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "=" sub-delims-no-amp = "!" / "$" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "=" The msf-fragment-value identifies a specific Track. The track- identifier MUST be formatted as an MSF namespace-name string (see Section 11.1.2). The client uses this identifier to initiate a SUBSCRIBE or FETCH command once the transport session is established. The namespace-name string MAY be followed by a series of key-value parameters, each separated from the preceding element by &. These key-value parameters are intended for processing by the client and, being part of the fragment, are not transferred to the server at connection time. Certain of the fragment key-value parameters have a reserved meaning, as defined by Section 11.1.1. Law & Nandakumar Expires 19 May 2027 [Page 73] Internet-Draft MOQT Streaming Format November 2026 11.1.1. Reserved fragment parameters Table 12 defines reserved key names for the parameter portion of the msf-fragment. Keynames are case-sensitive. +=================+=============================================+ | Name | Description | +=================+=============================================+ | wallclock-range | A subclip defined by a wallclock time range | +-----------------+---------------------------------------------+ | mediatime-range | A subclip defined by a media time range | +-----------------+---------------------------------------------+ | location-range | A subclip defined by a MOQT Location range | +-----------------+---------------------------------------------+ | cat | A base64 encoded C4M token | +-----------------+---------------------------------------------+ | connection | Mandates a connection type | +-----------------+---------------------------------------------+ Table 12: Reserved key names for the parameter portion of the msf-fragment * wallclock-range - a range defined by start and end wallclock times, separated by a "-" dash. Wallclock time is defined by Section 11.6. The dash and end time MAY be omitted to indicate an open range. The range definition is inclusive. * mediatime-range - a range defined by start and end media times, each expressed as milliseconds and separated by a "-" dash. The dash and end time MAY be omitted to indicate an open range. The range definition is inclusive. * location-range - a range defined by start and end media MOQT Location separated by a "-" dash. Range definitions are inclusive. MOQT Location is expressed as Group ID and Object ID separated by a "." dot. End Location may be omitted to indicate an open range which continues to the end of the content. End Object ID may be omitted, indicating the whole end group is included in the range. The "." dot and "-" dash separators MUST be omitted when the second value is omitted. * cat - a base64 encoded token, as defined by [C4M]. * connection - mandates the client to use a particular connection type when connecting to the server. There are two allowed values - "q" or "wt". "q" indicates that a Native QUIC connection MUST be used. "wt" indicates that a WebTransport connection MUST be used. Law & Nandakumar Expires 19 May 2027 [Page 74] Internet-Draft MOQT Streaming Format November 2026 If multiple ranges are specified within the same URL for the same parameter, the client MUST process the union of those ranges. Example fragment parameters: * connection=q * connection=wt * wallclock-range=1761759637565-1761759836189 * wallclock-range=1761751753894 * mediatime-range=0-13421 * mediatime-range=982 * location-range=34.0-2145.16 * location-range=16.24 (open range starting at Group ID 16 Object ID 24) * location-range=16-24 (range from Group ID 16 through to and including all Objects in Group ID 24) * cat=gqhkYWxnIGVzaGFyqGR0eXBNhdZ9hdWQAY3VybGZlbWlzcwZleWV2aW5uZWlhdGVwQWNyZW5lY 11.1.2. MSF Namespace-Name String Encoding To represent MOQT Namespace Tuples (which are sequences of byte strings) within the URL fragment, MSF uses a specific encoding convention, which is normatively defined by MOQT [MOQT] and repeated here for convenience: * Hierarchy: Each element of the Namespace tuple is rendered in order, separated by a single hyphen (-). * Delimiter: The Track Name is appended to the end, separated from the namespace by a double hyphen (--). * Character Escaping: - Unreserved characters (a-z, A-Z, 0-9, _) are represented literally. Law & Nandakumar Expires 19 May 2027 [Page 75] Internet-Draft MOQT Streaming Format November 2026 - All other byte values (including hyphens and periods used as data) MUST be escaped using a period (.) followed by two lowercase hexadecimal digits (e.g., a literal hyphen in a name becomes .2d). Note: This encoding ensures that the structural delimiters (- and --) remain unambiguous. The byte values that are serialized by this encoding are those produced from the catalog's namespace and name strings by Section 11.2. For example, the track object { "namespace": "customer/livestream/123", "name": "catalog" } is rendered as customer-livestream-123--catalog, and a track named "café" in the same namespace is rendered as customer-livestream-123-- caf.c3.a9. This difference between the catalog namespace form and the URL namespace form is intentional: the catalog uses slash- separated namespace fields, whereas URLs use the MOQT namespace-name serialization described above, with hyphen separators and period- based byte escaping. Publishers wanting easily readable URLs SHOULD use [A-Za-z0-9_] in namespace fields and track names, since those characters need no escaping. 11.1.3. Example MSF URLs * URL pointing at a catalog track (either WebTransport or native QUIC may be used): moqt://example.com/server/ config?a=1&b=2#msf:customer-livestream-123--catalog - Session: example.com/server/config?a=1&b=2 - Streaming format type: msf - Namespace: ('customer', 'livestream', '123') - Track Name: 'catalog' * URL with a required raw QUIC connection pointing at a catalog: moqt://example.com/relay-app/relayID#msf:customerID-broadcastID-- catalog&connection=q * URL pointing at a non-catalog track, with a required WebTransport connection moqt://example.com/relay-app/relayID#msf:customerID- broadcastID--video&connection=wt Law & Nandakumar Expires 19 May 2027 [Page 76] Internet-Draft MOQT Streaming Format November 2026 * URL pointing at a subclip: moqt://example.com/relay-app/ relayID#msf:customerID-broadcastID--catalog&location-range=34-64 * URL pointing at a catalog and supplying a token for the client: (linebreaks for display only) moqt://example.com/relay-app/ relayID#msf:customerID-broadcastID-- catalog&cat=gqhkYWxnIGVzaGFyqGR0eXBNhdZ9hdWQAY3VybGZlbWlzcwZleWV2 aW5uZWlhdGVwQWNyZW5lYnJmcmVqMTIzNDU2NzgwMHZpc3VlZF9hdD0xNzMwNDM * URL pointing at a catalog and supplying a token for the client along with a separate token for the server: (linebreaks for display only) moqt://example.com/relay-app/ relayID?token=HTRCII74GHFT@JHBCV SW56HKKneH2Dbyq6NHBI2#msf:customerID-broadcastID--catalog&cat=gqh kYWxnIGVzaGFyqGR0eXBNhdZ9hdWQAY3VybGZlbWlzcwZleWV2aW5uZWlhdGVwQWN yZW5lYnJmcmVqMTIzNDU2NzgwMHZpc3VlZF9hdD0xNzMwNDM 11.2. Mapping catalog strings to MOQT byte values MOQT Track Namespace Fields and Track Names are sequences of bytes, compared byte-for-byte, and [MOQT], Section 2.4.1 requires any specification that constrains them to define the canonical mapping into those bytes. This section defines that mapping for every catalog field that carries a Track Namespace Field or a Track Name: Section 5.2.2, Section 5.2.3, Section 5.2.15, Section 5.2.34 and Section 5.2.35. Extension fields that carry track names or namespaces MUST use the same mapping. 11.2.1. Producing bytes from a JSON string The MOQT byte value corresponding to a JSON string is the UTF-8 [UTF8] encoding of the sequence of Unicode scalar values obtained by parsing the JSON string per [JSON], Section 7. In particular: * JSON escape sequences are resolved before encoding. The string "café" and the string "caf\u00e9" denote the same sequence of scalar values and therefore map to the same bytes (63 61 66 c3 a9). Whether a producer writes a character literally or escaped has no effect on the resulting Track Name. * No Unicode normalization (NFC, NFD, NFKC, NFKD), case folding, or other transformation is applied, either by the producer when serializing or by the consumer when parsing. The scalar values in the catalog are encoded exactly as given. Consequently, "é" written as U+00E9 and "é" written as U+0065 U+0301 are different Track Names. Producers that need two catalogs, or a catalog and an out-of-band reference, to agree on a name, are responsible for emitting identical scalar value sequences. Law & Nandakumar Expires 19 May 2027 [Page 77] Internet-Draft MOQT Streaming Format November 2026 * Producers MUST NOT emit a JSON string in any of the fields listed above that, after resolving escapes, contains a code point that is not a Unicode scalar value; that is, an unpaired surrogate code point in the range U+D800 to U+DFFF (for example "\uDEAD") is not permitted. Such a value has no UTF-8 encoding. A consumer that encounters one MUST treat the catalog as invalid. * Producers MUST NOT emit a U+0000 (NUL) code point in these fields. (This restriction is a conservative interoperability measure; NUL is valid UTF-8 but is rejected or truncated by many string libraries.) The catalog document itself MUST be encoded in UTF-8, as required by [JSON], Section 8.1, and MUST NOT begin with a byte order mark. 11.2.2. Comparing names Two Track Names, or two Track Namespace Fields, are equal if and only if their mapped byte sequences are identical. Two Track Namespaces are equal if and only if they have the same number of fields and each corresponding field is equal. Implementations MUST NOT use locale- aware, case-insensitive, or normalization-aware string comparison when matching track names or namespaces within a catalog, between a catalog and a delta update, or between a catalog and the names carried in MOQT control messages. Note that the JSON string comparison guidance in [JSON], Section 8.3 yields the same result as byte comparison for strings that satisfy the constraints above. 11.2.3. Consuming names received from MOQT The mapping in this section is a partial function from JSON strings to bytes, not a bijection from bytes to JSON strings: a Track Name or Track Namespace Field that is not valid UTF-8 cannot be expressed in an MSF catalog. When an implementation needs to compare a name obtained from an MOQT control message (for example the Track Namespace of a PUBLISH_NAMESPACE, or the Full Track Name in a SUBSCRIBE) against a catalog, it MUST compare the raw MOQT bytes against the mapped bytes of the catalog string; it MUST NOT decode the MOQT bytes as UTF-8 and compare the result as text. A name received from MOQT that is not valid UTF-8 can never match an entry in a catalog. Consequently, an MSF publisher MUST only publish tracks whose Track Namespace Fields and Track Names are valid UTF-8 and satisfy the constraints of this section. Tracks that use names outside this space (for example, names defined by other specifications as raw binary values) cannot be described in a catalog track object. Law & Nandakumar Expires 19 May 2027 [Page 78] Internet-Draft MOQT Streaming Format November 2026 11.2.4. Relationship to the serialized form The hyphen-and-period serialization defined in [MOQT], Section 8.8 and used in MSF URL fragments (Section 11.1.2) is an encoding of the byte values produced by this section, not of the JSON source text. To render a catalog Full Track Name in that form, an implementation first maps each namespace element and the track name to bytes as defined above, then applies the MOQT encoding to those bytes. 11.2.5. Examples of string-to-byte mappings +==============+====================+===============================+ | JSON value | Mapped | Note | | | bytes (hex) | | +==============+====================+===============================+ | "video" | 76 69 64 65 | | | | 6f | | +--------------+--------------------+-------------------------------+ | "café" | 63 61 66 c3 | U+00E9 (precomposed), written | | | a9 | literally | +--------------+--------------------+-------------------------------+ | "caf\u00e9" | 63 61 66 c3 | same JSON escape rules: same | | | a9 | track as above | +--------------+--------------------+-------------------------------+ | "cafe\u0301" | 63 61 66 65 | U+0065 + U+0301 (decomposed); | | | cc 81 | different track | +--------------+--------------------+-------------------------------+ | "Video" | 56 69 64 65 | different track from "video" | | | 6f | | +--------------+--------------------+-------------------------------+ | "" | (empty) | invalid Track Name; invalid | | | | namespace field | +--------------+--------------------+-------------------------------+ | "\uDEAD" | none | invalid; catalog MUST be | | | | rejected | +--------------+--------------------+-------------------------------+ Table 13: Example string-to-byte mappings 11.3. Initiating a broadcast An MSF publisher MUST publish a catalog track object before publishing any media track objects. Law & Nandakumar Expires 19 May 2027 [Page 79] Internet-Draft MOQT Streaming Format November 2026 11.4. Ending a live broadcast After publishing a catalog and defining tracks carrying live content, an original publisher can deliver a deterministic signal to all subscribers that the broadcast is complete by taking the following steps: * Send a PUBLISH_DONE [MOQT], Section 9.9 message for all active tracks. * If the live stream is being converted instantly to a VOD asset, then publish an independent (non-delta) catalog update which, for each track, sets isLive Section 5.2.8 to FALSE and adds a track duration Section 5.2.36 field. * If the live stream is being terminated permanently without conversion to VOD, then publish an independent catalog update which signals isComplete Section 5.1.3 as TRUE and which contains an empty Tracks Section 5.1.4 field. 11.5. Authorization MSF supports token-based authorization through pluggable authentication schemes. Both original publishers and end subscribers can independently acquire authorization tokens and present them to relays. Relays use these tokens to authorize whether an end subscriber is permitted to set up the connection, as well as to receive content and/or to send content. 11.5.1. Discovering Authorization Requirements End subscribers discover authorization requirements by parsing the catalog. For each track of interest, examine the authInfo field. If present, the track requires authorization and the subscriber needs to obtain appropriate credentials for one of the schemes listed in the field. Original publishers and end subscribers may obtain authorization tokens from multiple sources, including out-of-band provisioning or as a parameter in the connection URI. These tokens can be presented either in the connection setup message (CLIENT_SETUP) or in control messages (SUBSCRIBE, FETCH, PUBLISH, PUBLISH_NAMESPACE) as described in Section 11.5.3. Law & Nandakumar Expires 19 May 2027 [Page 80] Internet-Draft MOQT Streaming Format November 2026 11.5.2. Token Acquisition Token acquisition is out of scope for this specification. Both original publishers and end subscribers independently obtain tokens through mechanisms such as: * Direct authentication with a distribution service * OAuth 2.0 or OpenID Connect flows * Out-of-band provisioning The token acquisition endpoint and flow depend on the authorization scheme and deployment configuration. Original publishers and end subscribers MAY use the same or different authorization services depending on the deployment. Tokens MAY also be supplied as parameters in the connection URI. When a connection URI contains token parameters, the subscriber extracts the token value and includes it in the appropriate MOQT message. For example: moqt://relay.example.com/moqt#msf:namespace--name&cat=eyJhbGciOiJFZERTQSJ9... URI parameters provide a convenient mechanism for distributing pre- authorized playback links. The parameter name and format are deployment-specific. 11.5.3. Presenting Authorization Once tokens are obtained, both original publishers and end subscribers present them to relays according to the scheme specification. Tokens MAY be presented in the SETUP message (CLIENT_SETUP or SERVER_SETUP) using the AUTHORIZATION TOKEN setup parameter, or in individual control messages using the AUTHORIZATION TOKEN message parameter. When a token is associated with a track, it MUST be included in ALL control messages that accept the AUTHORIZATION TOKEN parameter and are associated with that track. For end subscribers, this includes SUBSCRIBE, SUBSCRIBE_NAMESPACE, FETCH, and REQUEST_UPDATE messages. For original publishers, this includes PUBLISH and PUBLISH_NAMESPACE messages. This requirement applies regardless of whether the token was also provided in SETUP. Law & Nandakumar Expires 19 May 2027 [Page 81] Internet-Draft MOQT Streaming Format November 2026 11.5.4. Handling Authorization Failures When a relay rejects an authorization token, subscribers SHOULD handle the failure gracefully: * If a SUBSCRIBE or FETCH request is rejected due to invalid or expired authorization, the subscriber MAY attempt to obtain a fresh token and retry the request. * If a token is rejected due to insufficient scope, the subscriber SHOULD NOT retry with the same token. * For interactive applications, subscribers MAY prompt users to re- authenticate when authorization fails. * Subscribers SHOULD implement exponential backoff when retrying failed authorization attempts to avoid overwhelming the relay or token issuer. The specific error codes and retry semantics are defined by the authorization scheme specifications. See [PrivacyPassAuth] for Privacy Pass error handling and [C4M] for CAT error handling. 11.6. Wallclock time When wallclock time is referenced in this specification, it is expressed as the number of milliseconds elapsed since the Unix epoch (1970-01-01T00:00:00Z), excluding leap seconds, as defined for "Seconds Since the Epoch" in [POSIX], scaled to milliseconds. This time scale is derived from Coordinated Universal Time (UTC) [ITU-R-TF.460-6]. Publishers and subscribers that use wallclock values SHOULD synchronize their clocks to UTC, for example using NTP [RFC5905] or PTP [IEEE1588]. 12. MSF Properties MSF uses MOQT Track Properties and Object Properties (see [MOQT]) to signal metadata about MSF tracks and objects. These properties are carried in MOQT control messages and object headers, allowing endpoints to learn track and object characteristics before processing payload data. 12.1. Compression Signaling MSF provides two mutually exclusive mechanisms to signal compression of track payloads, including catalogs (Section 5), media timeline tracks (Section 7), and event timeline tracks (Section 8). Publishers MUST use one of the following approaches: Law & Nandakumar Expires 19 May 2027 [Page 82] Internet-Draft MOQT Streaming Format November 2026 * *Track Property* (Section 12.1.1): Signals that ALL objects in the track are compressed using the specified algorithm. * *Object Property* (Section 12.1.2): Signals compression on individual objects, allowing a mixture of compressed and uncompressed objects within the same track. A publisher MUST NOT use both mechanisms on the same track. If the track property is set, then every object in the track is compressed and the object property MUST NOT be present. If compression varies between objects, then the track property MUST NOT be set and the object property MUST be used on each compressed object. The compression algorithm values used by both mechanisms are: +=======+=======================+===============+ | Value | Compression Algorithm | Reference | +=======+=======================+===============+ | 0 | None (uncompressed) | This document | +-------+-----------------------+---------------+ | 1 | GZIP | [GZIP] | +-------+-----------------------+---------------+ Table 14: MSF Compression Values All MSF implementations MUST support both uncompressed payloads (value 0 or property absent) and GZIP compressed payloads (value 1). 12.1.1. MSF_COMPRESSION Track Property Track Property type: 0x78 The MSF_COMPRESSION track property signals that ALL objects in the track are compressed using the specified algorithm. This mechanism is appropriate when every object published on the track uses the same compression. If used, publishers MUST include the MSF_COMPRESSION track property in the PUBLISH message (publisher-initiated flow) or SUBSCRIBE_OK or FETCH_OK (subscriber-initiated flows). Subscribers MUST check for this property in the corresponding message before processing the track payload. Law & Nandakumar Expires 19 May 2027 [Page 83] Internet-Draft MOQT Streaming Format November 2026 If the property is absent, and no per-object compression is signaled, the subscriber MUST treat the payload as uncompressed. If the property is present with a value the subscriber does not support, the subscriber MUST NOT attempt to process the payload and SHOULD unsubscribe from the track. 12.1.2. MSF_COMPRESSION Object Property Object Property type: 0x78 The MSF_COMPRESSION object property signals that an individual object is compressed. This mechanism is appropriate when a track contains a mixture of compressed and uncompressed objects. For example, a catalog track where the first object in a group (the complete catalog) is compressed, but subsequent delta update objects within the same group are uncompressed. If used, publishers MUST include the MSF_COMPRESSION object property on each compressed object. Subscribers MUST check for this property on each received object before processing its payload. If the property is absent on an object, the subscriber MUST treat that object's payload as uncompressed. If the property is present with a value the subscriber does not support, the subscriber MUST NOT attempt to process that object. 12.2. Initialization properties MSF leverages Track properties and Object properties to carry media initialization data. These properties are registered in the [MOQT], Section 16.8. * VIDEO_CONFIG type 0x0D * AUDIO_CONFIG type 0x0F The VIDEO_CONFIG Track & Object property carries the initialization data for a track with a track role type of "video". The AUDIO_CONFIG Track & Object property carries the initialization data for a track with a track role type of "audio". Law & Nandakumar Expires 19 May 2027 [Page 84] Internet-Draft MOQT Streaming Format November 2026 If this initialization data is immutable over the life of the track, then the property MUST be added as a Track property and there MUST be an initRef Section 5.2.14 Track field referencing an Initialization Data List Section 5.1.7 entry with a type of 'track-property'. If used, publishers MUST include the Track property in the PUBLISH message (publisher-initiated flow) or SUBSCRIBE_OK or FETCH_OK message (subscriber-initiated flow). If this initialization data might change over the life of the track, then the property MUST be added as an Object property. Since subscription might occur at any time, this Object property needs to be repeated. Publishers SHOULD add this Object property to the first Object in each Group. Tracks which choose to transmit initialization data using this Object property MUST include an initRef Section 5.2.14 field referencing an Initialization Data List Section 5.1.7 entry with a type of 'object-property'. 12.3. Event Timeline Track properties 12.3.1. MSF_EVENT_TIMELINE_HEADER Track property Track Property type: 0x7B The MSF_EVENT_TIMELINE_HEADER Track property carries header data for an Event Timeline track. This initialization data is immutable over the life of the track. The serialization of the value of the property is defined by the Event timeline type Section 5.2.6. If used, publishers MUST include the MSF_EVENT_TIMELINE_HEADER track property in the PUBLISH message (publisher-initiated flow) or SUBSCRIBE_OK message or FETCH_OK (subscriber-initiated flow). 13. Security Considerations MSF inherits the security properties of [MOQT] and of the underlying QUIC or WebTransport session, which provide confidentiality and integrity on each hop between endpoints and relays. MSF does not, by itself, provide end-to-end integrity or confidentiality between the original publisher and the final subscriber. Relays are in a position to read, cache, drop, delay or alter any content that is not protected end-to-end, including catalogs, timeline tracks and unencrypted media. The considerations below describe the additional risks introduced by the features defined in this document. Law & Nandakumar Expires 19 May 2027 [Page 85] Internet-Draft MOQT Streaming Format November 2026 13.1. Catalog integrity and authenticity The catalog (Section 5) controls how a subscriber locates, selects, decodes, decrypts and authorizes access to content. An attacker able to modify a catalog in transit or in a relay cache could, for example, substitute track names or namespaces, alter codec or initialization data, remove or alter authorization and encryption fields, or insert publish tracks and connection URIs that direct the subscriber to an endpoint of the attacker's choosing. MSF does not define a catalog signature mechanism. Where relays are not fully trusted, publishers SHOULD protect catalog objects end-to- end, for example by using [SecureObjects] on the catalog track, and subscribers SHOULD reject catalog objects that fail authentication. Subscribers SHOULD treat every catalog field as untrusted input and validate it against the constraints in this document before acting on it. A catalog that violates those constraints, such as a delta update that fails to apply (Section 5.3) or a name that cannot be mapped (Section 11.2), MUST be treated as invalid. 13.2. Key material in the catalog The trackBaseKey field (Section 5.2.41) carries raw key material from which content encryption keys are derived. Any party that can read a catalog containing this field can decrypt the corresponding tracks. Because catalogs are routinely cached and forwarded by relays, publishing a trackBaseKey in a catalog that is not itself encrypted end-to-end defeats the purpose of content encryption (Section 4.4) with respect to every relay on the path. Publishers MUST NOT include a trackBaseKey in a catalog unless that catalog is encrypted end-to-end such that only authorized subscribers can read it, or is delivered to subscribers over a channel that relays cannot observe. Deployments that require relays to be excluded from access to content keys SHOULD deliver key material through the key management system ([E2EE-MLS] or equivalent) rather than through the catalog. The keyId field (Section 5.2.40) is not secret, but it can reveal information about key rotation and entitlement tiers and SHOULD NOT encode sensitive information. 13.3. Metadata exposure When media is encrypted with [SecureObjects], Group IDs, Object IDs, object sizes, timing, priorities, Track Namespaces and Track Names remain visible to relays. These can reveal the content type, bitrate, frame structure, scene complexity and, through track and namespace naming, the identity of the broadcast or of individual participants. An unencrypted catalog additionally exposes codec Law & Nandakumar Expires 19 May 2027 [Page 86] Internet-Draft MOQT Streaming Format November 2026 parameters, labels, languages and the relationships between tracks. Publishers concerned about traffic analysis SHOULD avoid placing identifying information in Track Namespaces, Track Names and catalog labels, and SHOULD encrypt the catalog end-to-end. 13.4. Authorization tokens Authorization tokens (Section 11.5) may appear in the authInfo catalog field, in URI fragment parameters (Section 11.1.1, Section 5.2.43) and in MOQT control messages (Section 11.5.3). Each location carries distinct risks: * Tokens written directly into a catalog are visible to every relay that caches the catalog and to every subscriber that receives it. Such tokens are effectively shared bearer credentials. Publishers SHOULD NOT place per-subscriber credentials directly in a cacheable catalog; per-subscriber tokens SHOULD instead be supplied through variable substitution or out-of-band provisioning. Any token placed in a catalog SHOULD be narrowly scoped and short-lived. * URI fragments are not sent to the server during connection establishment, but they are commonly retained in browser history, application logs, bookmarks and shared links. Tokens supplied in fragments SHOULD be short-lived and scoped to the specific content they authorize. * Tokens presented in MOQT control messages are visible to the relay that terminates the session. Relays are therefore trusted with the tokens they receive. MOQT ({MOQT, section 15.3}} details specific security requirements for relays in this regard. Bearer tokens are susceptible to replay by any party that obtains them. The replay protections, binding mechanisms and validation rules of the selected authorization scheme ([C4M], [PrivacyPassAuth]) apply. 13.5. Variable substitution Variable substitution (Section 5.4) inserts values taken from the URI fragment into catalog fields. The restricted character set for variable values limits structural injection into the catalog, but substituted values remain attacker-controlled whenever the URI was crafted or modified by a third party. A malicious link could, for example, cause a subscriber to subscribe to a different Track Namespace, present a token to an unintended track, or publish logs and metrics under an identifier of the attacker's choosing. Law & Nandakumar Expires 19 May 2027 [Page 87] Internet-Draft MOQT Streaming Format November 2026 Subscribers MUST validate the catalog after substitution, including applying the rules of Section 11.2 to any substituted name or namespace. Subscribers SHOULD NOT apply variable substitution to fields that determine a network endpoint, such as Connection URI (Section 5.2.37), unless the application explicitly trusts the source of the URI. Personalization values, such as viewer identifiers, become visible to relays when they are substituted into Track Namespaces or Track Names, since those names are carried in MOQT control messages. Applications SHOULD use opaque, non-identifying values for this purpose. 13.6. Publish tracks and connection URIs Publish tracks (Section 5.1.5) and the Connection URI field (Section 5.2.37) allow a catalog to instruct a subscriber to open new connections and to upload data. A malicious or tampered catalog could use these to direct subscribers to connect to arbitrary hosts, to generate unwanted load against a third party, or to exfiltrate client-side data. Subscribers SHOULD only publish to endpoints permitted by local application policy, for example endpoints within the same administrative domain as the catalog source, and SHOULD ignore publish tracks that do not satisfy that policy. Subscribers SHOULD rate-limit the data they publish on log (Section 9) and metrics (Section 10) tracks. Log and metrics data may contain identifiers, network information, device characteristics and viewing behavior. Applications SHOULD collect only the data necessary for their purpose, SHOULD obtain any user consent required by applicable policy, and SHOULD avoid including direct personal identifiers in Track Namespaces, Track Names or payloads. 13.7. Resource exhaustion Several MSF mechanisms allow a publisher, or an attacker able to modify content, to cause a subscriber to consume excessive resources: * Compressed payloads (Section 12.1) may expand to a size far larger than the transmitted object. Subscribers MUST enforce an upper bound on the decompressed size of any catalog, media timeline or event timeline object and SHOULD abort decompression when that bound is exceeded. Law & Nandakumar Expires 19 May 2027 [Page 88] Internet-Draft MOQT Streaming Format November 2026 * Catalogs, media timelines and event timelines are JSON documents that can be arbitrarily large or deeply nested. Subscribers SHOULD bound the document size, nesting depth, number of tracks and number of timeline records they are willing to process. * Long chains of delta updates (Section 5.3) increase processing cost for joining subscribers. Subscribers MAY bound the number of delta updates they will apply before requiring a new independent catalog. * A catalog may reference other catalogs. Subscribers MUST detect reference cycles and SHOULD bound the depth of catalog references they will follow. * Independent media timeline objects (Section 7) and event timeline objects (Section 8) contain the accumulated history of the track and can grow without limit over long broadcasts. Publishers SHOULD trim timelines to the accessible window, and subscribers SHOULD bound the size of timeline objects they will retain. 13.8. Timing information Target latency, buffer and wallclock values (Section 11.6) influence when subscribers render content. Manipulated values, or clocks that are not synchronized to UTC, can cause excessive buffering, playback stalls or loss of synchronization between subscribers. Subscribers SHOULD apply sanity bounds to these values and SHOULD NOT rely on them for any security decision. 13.9. Track naming Track names and namespaces are compared as raw bytes (Section 11.2). Because no Unicode normalization or case folding is applied, visually confusable names (for example, names differing only in composed versus decomposed accents, or in characters from different scripts that render identically) are distinct tracks. Catalog producers SHOULD avoid emitting distinct tracks whose names are confusable to a human reader, and applications that display track names to users SHOULD NOT rely on visual inspection to establish identity. 14. IANA Considerations This document requests IANA to create a new registry group titled "MOQT Streaming Format (MSF) Parameters", containing the "MSF Event Timeline Types" registry (Section 14.2) and the "MSF Compression Algorithms" registry (Section 14.4) defined below. It also registers one entry in the existing "MOQT URI Fragment Types" registry and documents two Property Type values that require no IANA action. Law & Nandakumar Expires 19 May 2027 [Page 89] Internet-Draft MOQT Streaming Format November 2026 14.1. "MOQT URI Fragment Types" registry This document registers the following entry in the "MOQT URI Fragment Types" registry established by [MOQT], Section 16.3: +===============+=======================+===============+ | Fragment Type | Description | Specification | +===============+=======================+===============+ | msf | MOQT Streaming Format | This document | +---------------+-----------------------+---------------+ Table 15 14.2. "MSF Event Timeline Types" registry This document establishes the "MSF Event Timeline Types" registry, part of the "MOQT Streaming Format (MSF) Parameters" registry group. This registry lists the event types that can be used with the eventType field (Section 5.2.6) in MSF catalogs. New entries in this registry are subject to Expert Review policy as defined in [RFC8126]. Each entry contains the following fields: * Event Type: the string identifier used in the eventType field. * Description: a short human-readable summary of the event type. * Change Controller: the entity authorized to modify the entry. For registrations made via an IETF-stream document, this is "IETF". For other registrations, this is the name and contact information of the registrant. * Specification: a stable reference to a publicly available document defining the format and semantics of the data carried under this event type. The initial contents of this registry are empty. Entries are added by the specifications that define each event type; see Section 8.5 for known examples. 14.2.1. Guidance for Designated Experts Designated experts should evaluate registration requests against the following criteria, per [RFC8126], Section 4.5: * The requested Event Type string is unique within the registry and does not collide with, or create ambiguity against, an existing entry. Law & Nandakumar Expires 19 May 2027 [Page 90] Internet-Draft MOQT Streaming Format November 2026 * Requests using the "urn:" scheme conform to an appropriate URN namespace ([RFC8141]). Requests intended for narrow or vendor- specific use should instead use Reverse Domain Name Notation and do not need to be registered at all. * The referenced specification is stable, publicly available, and describes the data format and semantics carried in the Event Timeline track in enough detail to support independent, interoperable implementations. * The registration does not duplicate the function of an existing registered type without adequate justification, such as a materially different encoding or use case. Experts should reject requests that lack a public specification, that reuse an existing Event Type string with different semantics, or that leave the data format ambiguous. Registrations are expected to be infrequent, and experts MAY consult the MoQ working group mailing list (moq@ietf.org) when in doubt. 14.3. MSF Property Type values The MSF_COMPRESSION Track and Object properties (Section 12.1) use Property Type value 0x78. This value falls within the range that [MOQT], Section 8.4 reserves for application-specific use, for which IANA registration is not permitted. Accordingly, this document requests no IANA action for these Property Type values; they are defined directly by this specification and require no coordination with IANA. The MSF_EVENT_TIMELINE_HEADER Track property (Section 12.3.1) uses Property Type value 0x7B, which falls within the same range and likewise requires no IANA action. Implementers should note the caveat in [MOQT], Section 8.4 regarding this range: because application-specific codepoints are not coordinated across independently developed extensions, an endpoint processing tracks from uncoordinated sources could encounter the same Property Type value used with different semantics. 14.4. "MSF Compression Algorithms" registry This document establishes the "MSF Compression Algorithms" registry, part of the "MOQT Streaming Format (MSF) Parameters" registry group. This registry lists the values used by the MSF_COMPRESSION Track and Object properties (Section 12.1) to identify a compression algorithm. Law & Nandakumar Expires 19 May 2027 [Page 91] Internet-Draft MOQT Streaming Format November 2026 New entries with values 2-127 are registered via Standards Action. Values 128 and above are reserved for private use and MUST NOT be registered. The initial contents of this registry are: +=======+=======================+===============+ | Value | Compression Algorithm | Reference | +=======+=======================+===============+ | 0 | None (uncompressed) | This document | +-------+-----------------------+---------------+ | 1 | GZIP | [GZIP] | +-------+-----------------------+---------------+ Table 16 15. References 15.1. Normative References [BASE64] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, . [C4M] Lemmons, C., Simon, G., Nandakumar, S., and W. Law, "Authorization scheme for MOQT using Common Access Tokens", Work in Progress, Internet-Draft, draft-ietf-moq- c4m-02, 2 November 2026, . [GZIP] Deutsch, P., "GZIP file format specification version 4.3", RFC 1952, DOI 10.17487/RFC1952, May 1996, . [ITU-R-TF.460-6] ITU-R, "Standard-frequency and time-signal emissions", ITU-R Recommendation TF.460-6, February 2002, . [JSON] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", STD 90, RFC 8259, DOI 10.17487/RFC8259, December 2017, . [LANG] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, September 2009, . Law & Nandakumar Expires 19 May 2027 [Page 92] Internet-Draft MOQT Streaming Format November 2026 [LOC] Zanaty, M., Nandakumar, S., and P. Thatcher, "Low Overhead Media Container", Work in Progress, Internet-Draft, draft- ietf-moq-loc-05, 2 November 2026, . [MIME] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, January 2013, . [MOQLOG] Jennings, C. F. and S. Nandakumar, "Logging over Media over QUIC Transport", Work in Progress, Internet-Draft, draft-jennings-moq-log-04, 2 November 2026, . [MOQMETRICS] Jennings, C. F. and S. Nandakumar, "Metrics over MOQT", Work in Progress, Internet-Draft, draft-jennings-moq- metrics-03, 2 November 2026, . [MOQT] Nandakumar, S., Vasiliev, V., Swett, I., and A. Frindell, "Media over QUIC Transport", Work in Progress, Internet- Draft, draft-ietf-moq-transport-23, 2 November 2026, . [POSIX] IEEE and The Open Group, "IEEE Standard for Information Technology--Portable Operating System Interface (POSIX(TM)) Base Specifications, Issue 8", IEEE Std 1003.1-2024, 2024, . [PrivacyPassAuth] Nandakumar, S., Jennings, C. F., and T. Meunier, "Privacy Pass Authentication for Media over QUIC (MoQ)", Work in Progress, Internet-Draft, draft-ietf-moq-privacy-pass- auth-04, 1 November 2026, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Law & Nandakumar Expires 19 May 2027 [Page 93] Internet-Draft MOQT Streaming Format November 2026 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, May 2021, . [SCTE214-1] "SCTE 214-1: MPEG DASH for IP-Based Cable Services Part 1 - MPD Constraints and Extensions", 2022, . [SecureObjects] Jennings, C. F., Nandakumar, S., and R. Barnes, "End-to- End Secure Objects for Media over QUIC Transport", Work in Progress, Internet-Draft, draft-jennings-moq-secure- objects-04, 8 February 2026, . [UTF8] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 2003, . [WEBCODECS-CODEC-REGISTRY] "WebCodecs Codec Registry", September 2024, . 15.2. Informative References [E2EE-MLS] Jennings, C. F., Nandakumar, S., and R. Barnes, "End-to- end Security for Media over QUIC", Work in Progress, Internet-Draft, draft-jennings-moq-e2ee-mls-03, 30 June 2025, . Law & Nandakumar Expires 19 May 2027 [Page 94] Internet-Draft MOQT Streaming Format November 2026 [IEEE1588] IEEE, "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", IEEE Std 1588-2019, DOI 10.1109/IEEESTD.2020.9120376, June 2020, . [IMSC1] "W3C, TTML Profiles for Internet Media Subtitles and Captions 1.0 (IMSC1)", April 2016, . [IMSC1-MSF] Law, W. and S. Nandakumar, "IMSC1 Packaging for MOQT Streaming Format", Work in Progress, Internet-Draft, draft-law-moq-imsc1-msf-00, 6 July 2026, . [MVFTS] Ugur, D., Gürel, Z., and A. C. Begen, "Subscriber-Side Multi-Variant Fast Track Switching for MOQT", Work in Progress, Internet-Draft, draft-ugur-moq-fast-switching- 00, 13 October 2026, . [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, "Network Time Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, . [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, . [SCTE35-MSF] Law, W. and S. Nandakumar, "SCTE35 transmission over MSF Event Timeline", Work in Progress, Internet-Draft, draft- wilaw-moq-scte35-event-timeline-00, 6 July 2026, . [WEBVTT] "World Wide Web Consortium (W3C), WebVTT: The Web Video Text Tracks Format", April 2019, . Law & Nandakumar Expires 19 May 2027 [Page 95] Internet-Draft MOQT Streaming Format November 2026 [WebVTT-MSF] Law, W. and S. Nandakumar, "WebVTT Packaging for MOQT Streaming Format", Work in Progress, Internet-Draft, draft-wilaw-moq-webvtt-msf-00, 6 July 2026, . Appendix A. Change Log RFC Editor's Note: Please remove this section prior to publication of a final version of this document. A.1. Changes since draft-ietf-moq-msf-01 A.1.1. Editorial and structural * Introduction rewritten to describe the problem MSF solves on top of MOQT, summarize what MSF specifies, and clarify that relays do not need to understand MSF. * Security Considerations section added (previously a placeholder). It covers catalog integrity, key material in the catalog, metadata exposure, authorization tokens, variable substitution, publish tracks and connection URIs, resource exhaustion, timing information and track naming. New normative requirements include: a trackBaseKey MUST NOT be carried in a catalog unless the catalog is encrypted end-to-end so that only authorized subscribers can read it, or delivered over a channel that relays cannot observe; subscribers MUST bound decompressed object size; subscribers MUST detect catalog reference cycles; and catalogs MUST be validated after variable substitution. * Aligned with draft-ietf-moq-transport-23 terminology: header extensions are now object properties, SUBSCRIBE_DONE is now PUBLISH_DONE, and the PRIOR_GROUP_ID_GAP property replaces the Prior Group ID Gap extension. References were updated to current versions of MOQT, LOC, C4M, MOQLOG, MOQMETRICS and PrivacyPassAuth. * Catalog examples were corrected, and they now use "draft-02" as the version string. Law & Nandakumar Expires 19 May 2027 [Page 96] Internet-Draft MOQT Streaming Format November 2026 A.1.2. Media packaging and transmission * Added LOC to MOQT Stream mapping (Section 4.1.1). Publishers select "group" (default) or "object" mode, signaled via the new streamMapping key, and subscribers MUST support both modes. This replaces the -01 requirement that each Object be mapped to a new MOQT Stream. Objects SHOULD be placed on Subgroup 0 unless the mapping mode indicates otherwise. * Added Multi-Variant Fast Track Switching. This consists of publisher packaging requirements (Section 4.3) and a subscriber switching procedure with switch-point calculation (Section 6.3), and enables switching between alternate tracks with dissimilar keyframe intervals. A.1.3. Catalog * A catalog MAY now reference other catalogs, via a new "catalog" packaging value. Only the top-level catalog track MUST be named "catalog". * The catalog track SHOULD have a higher publisher priority than the tracks it describes. Subscribers SHOULD use a higher subscriber priority for the catalog subscription. * Added an "update" delta operation for modifying fields of an existing track. This removes the -01 rule that track attributes are immutable once declared. Delta updates MUST now carry generatedAt and no other root fields. Illogical operations, such as adding an existing track or removing an unknown one, MUST cause the catalog to be rejected. * Added a table of required fields per (packaging, role) pair (Section 5.2.4.1). * Track namespace is now a '/'-delimited string that maps to MOQT Track Namespace Fields, with 1-32 non-empty fields. Malformed values invalidate the catalog. A declared namespace replaces, rather than extends, the inherited one. Track names MUST be non- empty, and uniqueness now applies to the Full Track Name. * depends entries may now reference a renderGroup (JSON Number) as well as a track name (JSON String). Every entry MUST resolve, or the catalog is invalid. * New track fields: - packagingMetadata (Section 5.2.5) Law & Nandakumar Expires 19 May 2027 [Page 97] Internet-Draft MOQT Streaming Format November 2026 - accessibleWindowTime (Section 5.2.45), which defines a DVR window - keyframeSpacing (Section 5.2.46) * New "data" track role. * The track-level token field was removed. Publish tracks now use authInfo. The connectionURI and encryption fields were added to the track field table. * initDataList gains "track-property" and "object-property" types. Its placement after the tracks array is relaxed from MUST to SHOULD. * cipherSuite is now required only when encryptionScheme is "moq- secure-objects". * targetLatency and timeline wallclock values are now defined relative to when content entered the encoder. The generatedAt restriction for non-live content was removed. * Variable substitution: the restriction on variable-name characters was removed, and '+', '/', '=' and '.' are now permitted in values. Fragment pairs are split at the first '='. Name mapping is applied after substitution. A.1.4. Media timeline * A media timeline track MUST NOT mix the explicit and template formats (-01 allowed both). Entries are ordered by media time, and Group IDs need not be sequential. * Catalog requirements now use the packaging field and drop the mimeType requirement. * depends may reference renderGroups, with rules on when to reference a renderGroup versus individual tracks. Publishers MUST update depends when a referenced track ceases. * Publishers SHOULD trim timelines to the accessible window, and subscribers MUST apply accessibleWindowTime constraints. A.1.5. Event timeline * Index keys changed from lowercase ('t', 'l', 'm') to uppercase ('T', 'L', 'M'). The 'data' field may be any JSON value. Law & Nandakumar Expires 19 May 2027 [Page 98] Internet-Draft MOQT Streaming Format November 2026 * Added event timeline header data, carried in the new MSF_EVENT_TIMELINE_HEADER track property (Section 12.3.1). * depends and mimeType are no longer required. depends MUST list any media timeline tracks that the index references. * The mapping of records to Groups is now defined per eventType. Sequential data SHOULD use independent objects at group start, and history-independent data SHOULD use one record per Group. * Event timeline tracks may appear in publishTracks. * Added a media-time indexing example. * Well-known event types (Section 8.5) moved into this section. A.1.6. Log and metrics tracks * Namespaces are now taken from the catalog namespace field via the standard name mapping. Track names are the ASCII decimal priority or granularity level (previously a single binary byte). * Publish authorization uses authInfo instead of token. A.1.7. Workflow * New section defining the mapping of catalog strings to MOQT byte values (Section 11.2). It specifies UTF-8 encoding with no normalization or case folding, byte-exact comparison, prohibition of unpaired surrogates and NUL in naming fields, prohibition of a BOM at the beginning of the catalog document, and comparison of raw MOQT bytes against mapped catalog bytes. * New wallclock time definition (Section 11.6): POSIX milliseconds since the epoch, UTC-derived. Clocks SHOULD be synchronized via NTP or PTP. * The reserved fragment parameter "c4m" was renamed "cat". The namespace-name encoding section now clarifies its relationship to catalog strings. * Ending a live broadcast now uses PUBLISH_DONE. A.1.8. MSF properties and IANA * MSF_COMPRESSION was assigned type 0x78 (track and object). It may also be carried in FETCH_OK. Law & Nandakumar Expires 19 May 2027 [Page 99] Internet-Draft MOQT Streaming Format November 2026 * New initialization properties (Section 12.2): VIDEO_CONFIG (0x0D) and AUDIO_CONFIG (0x0F) carry init data as track or object properties. * IANA: a new "MOQT Streaming Format (MSF) Parameters" registry group was added. - The "MSF Event Timeline Types" registry is now initially empty and adds Designated Expert guidance. - MSF_COMPRESSION and MSF_EVENT_TIMELINE_HEADER use the application-specific range and require no IANA action. Draft -01 requested registration. Acknowledgments * the MoQ Workgroup and mailing lists. Contributors The following persons were the co-authors of the individual draft (draft-law-moq-warpstreamingformat) this document is based on: * Luke Curley * Victor Vasiliev * Suhas Nandakumar * Kirill Pugin * Will Law Authors' Addresses Will Law Akamai Email: wilaw@akamai.com Suhas Nandakumar Cisco Email: snandaku@cisco.com Law & Nandakumar Expires 19 May 2027 [Page 100]