Media over QUIC Transport

Media over QUIC Transport Cisco

snandaku@cisco.com

Google

vasilvv@google.com

Google

ianswett@google.com

Meta

afrind@meta.com

Web and Internet Transport Media Over QUIC media over quic This document defines Media over QUIC Transport (MOQT), a publish/subscribe protocol that runs over QUIC and WebTransport. MOQT leverages the features of these transports, such as streams, datagrams, priorities, and partial reliability. MOQT operates both point-to-point and through intermediate relays, enabling scalable low-latency delivery. Despite its name, MOQT is media agnostic and can be used for a wide range of use cases. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Media Over QUIC Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction Media Over QUIC Transport (MOQT) is a publish/subscribe protocol that runs over QUIC or WebTransport . Publishers produce data that is delivered to subscribers either point-to-point or through intermediate relays. MOQT leverages transport features such as streams, datagrams, priorities, and partial reliability to support a wide range of use cases with different resiliency and latency needs, from live to interactive, without compromising scalability. Despite its name, MOQT is content agnostic. MoQ Streaming Formats define how specific content types are encoded, packaged, and mapped to MOQT objects, along with policies for discovery and subscription.

Document Structure This document describes the MOQT protocol and is structured as follows:

The core concepts and functionality are described first
- Section 2 Object Data Model describes how Objects, Tracks and Namespaces relate
- Section 3 Describes how Objects in Tracks are Published and Retrieved.
- Section 4 Describes mechanisms for discovering Namespaces and Tracks
Next, the document describes how Objects are transmitted and MOQT Sessions
- Section 5 Describes ways MOTQ allows a subscriber to influence Object transmission order
- Section 6 Describes how to initiate a session and key properties of a session, such as extensibility.
- Section 7 Describes key properties and requirements of MOQT relays
Then the document describes how Control Messages and Objects are serialized and sent
- Section 8 Notational Conventions and Common Structures details structures used by subsequent sections
- Section 9 Control Messages details how Control Messages are sent, including their wire encoding
- Section 10 MOQT Properties describes Track and Object properties defined in the core protocol
- Section 11 Data streams describes the mapping and serialization of Objects onto streams and datagrams
Finally, the document discusses deployment related considerations
- Section 12 Discusses MOQT errors and how to best handle them
- Section 13 Describes how to utilize unspecified codepoints to prevent protocol ossification.
- Section 14 Discusses transport related considerations, including congestion control
- Section 15 Discusses security considerations, including denial-of-service and authentication

Motivation The development of MOQT is driven by goals in a number of areas - specifically latency, the robust feature set of QUIC and relay support.

Latency Latency is necessary to correct for variable network throughput. Ideally live content is consumed at the same bitrate it is produced. End-to-end latency would be fixed and only subject to encoding and transmission delays. Unfortunately, networks have variable throughput, primarily due to congestion. Attempting to deliver content encoded at a higher bitrate than the network can cause queuing along the path from producer to consumer. The speed at which a protocol can detect and respond to congestion determines the overall latency. TCP-based protocols are simple but are slow to detect congestion and suffer from head-of-line blocking. Protocols utilizing UDP directly can avoid queuing, but the application is then responsible for the complexity of fragmentation, congestion control, retransmissions, receiver feedback, reassembly, and more. One goal of MOQT is to achieve the best of both these worlds: leverage the features of QUIC to create a simple yet flexible low latency protocol that can rapidly detect and respond to congestion.

Leveraging QUIC The parallel nature of QUIC streams can provide improvements in the face of loss. A goal of MOQT is to design a streaming protocol to leverage the transmission benefits afforded by parallel QUIC streams as well as exercising options for flexible loss recovery.

Convergence Some live media architectures today have separate protocols for ingest and distribution, for example RTMP and HTTP based HLS or DASH. Switching protocols necessitates intermediary origins which re-package the media content. While specialization can have its benefits, there are efficiency gains to be had in not having to re-package content. A goal of MOQT is to develop a single protocol which can be used for transmission from contribution to distribution. A related goal is the ability to support existing encoding and packaging schemas, both for backwards compatibility and for interoperability with the established content preparation ecosystem.

Relays An integral feature of a protocol being successful is its ability to deliver media at scale. Greatest scale is achieved when third-party networks, independent of both the publisher and subscriber, can be leveraged to relay the content. These relays must cache content for distribution efficiency while simultaneously routing content and deterministically responding to congestion in a multi-tenant network. A goal of MOQT is to treat relays as first-class citizens of the protocol and ensure that objects are structured such that information necessary for distribution is available to relays while the media content itself remains opaque and private.

Terms 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 when, and only when, they appear in all capitals, as shown here. The following terms are used with the first letter capitalized.

Application:: The entity using MOQT to transmit and receive data.
Client:: The party initiating a Transport Session.
Server:: The party accepting an incoming Transport Session.
Endpoint:: A Client or Server.
Peer:: The other endpoint than the one being described.
Publisher:: An endpoint that handles subscriptions by sending requested Objects from the requested track.
Subscriber:: An endpoint that subscribes to and receives tracks.
Original Publisher:: The initial publisher of a given track.
End Subscriber:: A subscriber that initiates a subscription and does not send the data on to other subscribers.
Relay:: An entity that is both a Publisher and a Subscriber, is not the Original Publisher or End Subscriber, and conforms to all requirements in .
Upstream:: In the direction of the Original Publisher.
Downstream:: In the direction of the End Subscriber(s).
Transport Session:: A raw QUIC connection or a WebTransport session.
Stream:: A bidirectional or unidirectional bytestream provided by the QUIC transport or WebTransport.
Congestion:: Packet loss and queuing caused by degraded or overloaded networks.
Group:: A collection of objects within a track. A group represents a join point in a track. See ().
Subgroup:: A sequence of one or more objects from the same group, sent on a single transport stream whenever possible. See ().
Object:: An object is an addressable unit whose payload is a sequence of bytes. Objects form the base element in the MOQT data model. See ().
Track:: A track is a collection of groups. See ().

Stream Management Terms This document uses stream management terms described in including STOP_SENDING, RESET_STREAM, and FIN. It also uses RESET_STREAM_AT from . RESET_STREAM_AT can be used by MOQT, but the protocol is also designed to work correctly when the extension is not supported. When this document says an endpoint "resets" a stream, it means the endpoint sends a RESET_STREAM or RESET_STREAM_AT frame on that stream (see for considerations on choosing between them).

Modularity MOQT defines all messages necessary to implement both simple publishing or subscribing endpoints as well as fully capable Relays. Non-Relay endpoints MAY implement only the subset of functionality required to perform necessary tasks. For example, a limited media player could operate using only SUBSCRIBE related messages. Limited endpoints SHOULD respond to any unsupported messages with the appropriate NOT_SUPPORTED error code, rather than ignoring them. Relays MUST implement all MOQT messages defined in this document, as well as processing rules described in .

Object Data Model MOQT has a hierarchical data model, comprised of tracks which contain groups, and groups that contain objects. Inside of a group, the objects can be organized into subgroups. To give an example of how an application might use this data model, consider an application sending high and low resolution video using a codec with temporal scalability. Each resolution is sent as a separate track to allow the subscriber to pick the appropriate resolution given the display environment and available bandwidth. Each independently coded sequence of pictures in a resolution is sent as a group as the first picture in the sequence can be used as a random access point. This allows the client to join at the logical points where decoding of the media can start without needing information before the join points. The temporal layers are sent as separate subgroups to allow the priority mechanism to favor lower temporal layers when there is not enough bandwidth to send all temporal layers. Each frame of video is sent as a single object.

Objects The basic data element of MOQT is an object. An object is an addressable unit whose payload is a sequence of bytes. All objects belong to a group, indicating ordering and potential dependencies (see ). An object is uniquely identified by its track namespace, track name, group ID, and object ID, and must be an identical sequence of bytes regardless of how or where it is retrieved. An Object can become unavailable, but its contents MUST NOT change over time.

Canonical Object Fields Objects are comprised of two parts: metadata and a payload. The metadata is never encrypted and is always visible to relays (see ). The payload portion may be encrypted, in which case it is only visible to the Original Publisher and End Subscribers. The Original Publisher is solely responsible for the content of the object payload. This includes the underlying encoding, compression, any end-to-end encryption, or authentication. From the perspective of a subscriber or a cache, an Object can be in three possible states:

The Object is known to not exist. This state is permanent. All signals that an Object does not exist are authoritative.
The Object is known to exist. From this state, it can transition to not existing, but not vice versa.
The state of the Object is unknown, either because it has not yet been received, or it has not yet been produced.

A gap in the observed Object IDs does not by itself convey any information about the skipped Objects. Skipped Objects remain in the unknown state until they are received or their non-existence is signalled, for example in a FETCH stream (see ) or via a Prior Object ID Gap (see ). Since Objects can be delivered out of order, an endpoint can receive an Object after it has already recorded that the Object does not exist (e.g., via a FETCH gap from one source and delayed delivery via a subscription). This is not a protocol error and the Track is not malformed. Whenever the publisher communicates that certain objects do not exist, this fact is expressed as a contiguous range of non-existent objects and by including Properties indicating the group/object gaps; MOQT implementers should take that into account when selecting appropriate data structures.

Subgroups A subgroup is a sequence of one or more objects from the same group () in ascending order by Object ID. Objects in a subgroup have a dependency and priority relationship consistent with sharing a stream and are sent on a single stream whenever possible. A Group is delivered using at least as many streams as there are Subgroups in the Group, typically with a one-to-one mapping between Subgroups and streams. When an Object's forwarding preference (see ) is "Datagram", it is not sent in Subgroups, does not belong to a Subgroup in any way, and the description in the remainder of this section does not apply. Streams offer in-order reliable delivery and the ability to cancel sending and retransmission of data. Furthermore, many QUIC and WebTransport implementations offer the ability to control the relative scheduling priority of pending stream data. Every Object within a Group belongs to exactly one Subgroup or Datagram. When Objects are sent in a subscription (see ), Objects from two subgroups MUST NOT be sent on the same stream, and Objects from the same Subgroup MUST NOT be sent on different streams, unless one of the streams was reset prematurely, or upstream conditions have forced objects from a Subgroup to be sent out of Object ID order. Original publishers assign each Subgroup a Subgroup ID, and do so as they see fit. The scope of a Subgroup ID is a Group, so Subgroups from different Groups MAY share a Subgroup ID without implying any relationship between them. In general, publishers assign objects to subgroups in order to leverage the features of streams as described above. In general, if Object B is dependent on Object A, then delivery of B can follow A, i.e. A and B can be usefully delivered over a single stream. If an Object is dependent on all previous Objects in a Subgroup, it likely fits best in that Subgroup. If an Object is not dependent on any of the Objects in a Subgroup, it likely belongs in a different Subgroup. When assigning Objects to different Subgroups, the Original Publisher makes a reasonable tradeoff between having an optimal mapping of Object relationships in a Group and minimizing the number of streams used. When the Original Publisher opens a new subgroup, it MUST set the FIRST_OBJECT bit () to indicate that the first object in the subgroup stream is the first object ever published in that subgroup. A relay forwarding a subgroup that begins with the first object ever published in that subgroup MUST set the FIRST_OBJECT bit.

Groups A group is a collection of Objects and is a sub-unit of a Track (). Groups SHOULD be independently useful, so Objects within a Group SHOULD NOT depend on Objects in other Groups. A Group provides a join point for subscriptions, so a subscriber that does not want to receive the entire Track can opt to receive only Groups starting from a given Group ID. Groups can contain any number of Objects.

Group IDs Within a track, the original publisher SHOULD publish Group IDs which increase with time (where "time" is defined according to the internal clock of the media being sent). In some cases, Groups will be produced in increasing order, but sent to subscribers in a different order, for example when the subscription's Group Order is Descending. Due to network reordering and the partial reliability features of MOQT, Objects from different Groups can always be received out of order. As a result, subscribers cannot infer the existence of a Group until an object in the Group is received. This can create gaps in a cache that can be filled by doing a Fetch upstream, if necessary. Applications that do not produce Group IDs that increase with time are limited to the subset of MOQT that does not compare group IDs. Subscribers to these Tracks SHOULD NOT use Location filters which span multiple Groups in FETCH or SUBSCRIBE. SUBSCRIBE and FETCH delivery use Group Order, so they could have an unexpected delivery order if Group IDs do not increase with time. The amount of time elapsed between publishing an Object in Group ID N and in a Group ID > N, or even which will be published first, is not defined by this specification and is defined by the applications using MOQT.

Track A track is a sequence of groups (). It is the entity against which a subscriber issues a subscription request. A subscriber can request to receive individual tracks starting at a group boundary, including any new objects pushed by the publisher while the track is active.

Track Naming In MOQT, every track is identified by a Full Track Name, consisting of a Track Namespace and a Track Name. Track Namespace is an ordered set of between 0 and 32 Track Namespace Fields, encoded as described in . The structured nature of Track Namespace allows relays and applications to manipulate prefixes of a namespace. Track Name is a sequence of bytes, possibly empty, that identifies an individual track within the namespace. In this specification, both the Track Namespace Fields and the Track Name are not constrained to a specific encoding. They carry a sequence of bytes and comparison between two Track Namespace Fields or Track Names is done by exact comparison of the bytes. Specifications that use MOQT may constrain the information in these fields, for example by restricting them to UTF-8. Any such specification needs to specify the canonicalization into the bytes in the Track Namespace Fields or Track Name such that exact comparison works.

Reserved Namespaces MOQT reserves all Track Namespace values whose first tuple field begins with a period (0x2e, .). These namespaces MUST NOT be used unless their meaning is defined through IANA registration. Unless otherwise specified, an endpoint that receives a request for an unrecognized reserved namespace MUST pass it to the Application, so that future extensions can define new reserved namespaces without breaking older implementations. A Track Namespace whose first field is exactly . (a single period, 0x2e) is reserved and MUST NOT be used for any purpose; endpoints MUST NOT publish tracks or namespaces under it and MUST reject requests referencing it with DOES_NOT_EXIST.

Scope An MOQT scope is a set of servers (as identified by their connection URIs) for which a Full Track Name is guaranteed to be unique and identify a specific track. It is up to the application using MOQT to define how broad or narrow the scope is. An application that deals with connections between devices on a local network may limit the scope to a single connection; by contrast, an application that uses multiple CDNs to serve media may require the scope to include all of those CDNs. A single MOQT transport session is tied to the scope that is negotiated in the beginning of the session. Unless the application has additional information, two tracks are assumed to belong to the same scope if and only if the authority and path-abempty components () of their connection URIs are equal. These values are communicated through the SETUP message in case of raw QUIC, and through HTTP request header fields in case of WebTransport. The query component of the connection URI is not part of the scope; two connection URIs that differ only in their query components identify the same scope. Because each Full Track Name is unique within an MOQT scope, they can be used as a cache key for the track. If, at a given moment in time, two tracks within the same scope contain different data, they MUST have different names and/or namespaces. MOQT provides subscribers with the ability to alter the specific manner in which tracks are delivered via Parameters, but the actual content of the tracks does not depend on those parameters; this is in contrast to protocols like HTTP, where request headers can alter the server response. A publisher that loses state (e.g. crashes) and intends to resume publishing on the same Track risks colliding with previously published Objects and violating the above requirements. A publisher can handle this in application specific ways, for example:

Select a unique Track Name or Track Namespace whenever it resumes publishing. For example, it can base one of the Namespace Fields on the current time, or select a sufficiently large random value.
Resume publishing under a previous Track Name and Namespace and set the initial Group ID to a unique value guaranteed to be larger than all previously used groups. This can be done by choosing a Group ID based on the current time.
Use TRACK_STATUS or similar mechanism to query the previous state to determine the largest published Group ID.

Publishing and Receiving Tracks

Subscriptions All subscriptions begin in the Idle state. A subscription can be initiated and moved to the Pending state by either a publisher or a subscriber. A publisher initiates a subscription to a track by sending the PUBLISH message. The subscriber either accepts or rejects the subscription using PUBLISH_OK () or REQUEST_ERROR. A subscriber initiates a subscription to a track by sending the SUBSCRIBE message. The publisher either accepts or rejects the subscription using SUBSCRIBE_OK or REQUEST_ERROR. Once either of these sequences is successful, the subscription moves to the Established state and can be updated by the subscriber using REQUEST_UPDATE. Either endpoint can terminate an Established subscription, moving it to the Terminated state. The subscriber terminates a subscription in the Pending (Subscriber) or Established states by sending STOP_SENDING. The publisher terminates a subscription in the Pending (Publisher) or Established states by sending PUBLISH_DONE and closing the stream. This diagram shows the subscription state machine: | Terminated | <------------+ +-------------+ ]]> A publisher MUST send exactly one SUBSCRIBE_OK or REQUEST_ERROR in response to a SUBSCRIBE. A subscriber MUST send exactly one PUBLISH_OK () or REQUEST_ERROR in response to a PUBLISH. The peer SHOULD close the session with a protocol error if it receives more than one. All Established subscriptions have a Forward State which is either 0 or 1. The publisher does not send Objects if the Forward State is 0, and does send them if the Forward State is 1. The initiator of the subscription sets the initial Forward State in either PUBLISH or SUBSCRIBE. The subscriber can send REQUEST_UPDATE to update the Forward State. Control messages, such as PUBLISH_DONE () are sent regardless of the forward state. Either endpoint can initiate a subscription to a track without exchanging any prior messages other than SETUP. Relays MUST NOT send any PUBLISH messages without knowing the client is interested in and authorized to receive the content. The communication of intent and authorization can be accomplished by the client sending SUBSCRIBE_NAMESPACE, or conveyed in other mechanisms out of band. An endpoint MAY SUBSCRIBE to a Track it is publishing, though only Relays are required to handle such a SUBSCRIBE. Such self-subscriptions are identical to subscriptions initiated by other endpoints, and all published Objects will be forwarded back to the endpoint, subject to priority and congestion response rules. An endpoint MAY have multiple concurrent subscriptions to the same Track, each identified by a unique Request ID. A publisher MAY assign the same or different Track Aliases to these subscriptions. When an Object matches the filters of multiple subscriptions to the same Track, the publisher MUST send the Object once for each matching subscription, even when those subscriptions share the same Track Alias. Because subscriptions can share a Track Alias, the subscriber re-applies each subscription's filter to determine which subscription a received Object belongs to. Subscribers SHOULD avoid overlapping filters across subscriptions to the same Track, as they are responsible for deduplicating any resulting duplicate Objects. A publisher SHOULD begin sending incomplete objects when available to avoid incurring additional latency. Publishers MAY start sending Objects on PUBLISH-initiated subscriptions before receiving a PUBLISH_OK response to reduce latency. Doing so can consume unnecessary resources in cases where the Subscriber rejects the subscription with REQUEST_ERROR or sets Forward=0 in REQUEST_UPDATE. It can also result in the Subscriber dropping Objects if its buffering limits are exceeded (see and ). An object published or received in a subgroup or datagram is subscription-delivered.

Subscription State Management A subscriber keeps subscription state until it cancels the request (see ), or until receipt of a PUBLISH_DONE or REQUEST_ERROR. Note that PUBLISH_DONE does not usually indicate that state can immediately be removed, see . The Publisher can remove subscription state as soon as it has received STOP_SENDING. It MUST reset any open streams associated with the SUBSCRIBE. The Publisher can also immediately delete subscription state after sending PUBLISH_DONE, but MUST NOT send it until it has closed all related streams. A REQUEST_ERROR indicates no objects will be delivered, and both endpoints can immediately remove relevant state. Objects MUST NOT be sent for requests that end with an error.

Track Alias To optimize wire efficiency, Subgroups and Datagrams refer to a track by a numeric identifier, rather than the Full Track Name. Track Alias is chosen by the publisher and included in SUBSCRIBE_OK () or PUBLISH (). The same Track Alias MUST NOT be used by a publisher to refer to two different Tracks simultaneously in the same session. If a subscriber receives a PUBLISH or SUBSCRIBE_OK that uses the same Track Alias as a different Track with an Established subscription, it MUST close the session with error DUPLICATE_TRACK_ALIAS. Objects can be sent before the Subscriber knows the Track Alias, requiring buffering Objects with an unknown Track Alias. If a Track Alias is used for two concurrent subscriptions to the same Track, an Object that arrives with the Track Alias could be for either Subscription. Reusing the same Track Alias for concurrent subscriptions to the same Track can lead to missed delivery if objects for the new subscription arrive before the control message establishing the shared Alias. The Subscriber can assume the Track Alias is reused until told otherwise, in order to avoid missing Objects. To avoid a protocol violation and to ensure the Subscriber knows which Track Objects are from, Publishers SHOULD NOT reuse a Track Alias for different Tracks within a session, unless it is certain the prior Subscription has been completely closed and no Objects are scheduled to be sent or in flight. Objects can arrive after a subscription has been cancelled. Subscribers SHOULD retain sufficient state to quickly discard these unwanted Objects, rather than treating them as belonging to an unknown Track Alias.

Largest Object The Largest Object is the Object with the largest Location () in the Track from the perspective of the publisher processing the message. Largest Object updates when the first byte of an Object with a Location larger than the previous value is published or received through a subscription. The Next Object is the Location immediately following Largest Object, which is {Largest Object.Group, Largest Object.Object + 1}, or {0, 0} if no content has been delivered yet.

Fetch

Fetch State Management The publisher MUST send exactly one FETCH_OK or REQUEST_ERROR in response to a FETCH. A subscriber keeps FETCH state until it cancels the request (see ), receives REQUEST_ERROR, or the FETCH data stream receives a FIN or is reset. If the data stream is already open, the subscriber wishing to cancel the FETCH MAY send STOP_SENDING for the data stream as well as the bidi request stream. It MUST send STOP_SENDING for the bidi request stream. The Publisher can remove fetch state as soon as it has received a STOP_SENDING. It MUST reset the bidi request stream and unidirectional data stream associated with the FETCH. It can also remove state after closing the FETCH data stream. It can remove all FETCH state after closing the data stream with a FIN. A REQUEST_ERROR indicates that both endpoints can immediately remove state. Since a relay can start delivering FETCH Objects from cache before determining the result of the request, some Objects could be received even if the FETCH results in error.

Filtering Tracks and Objects

Location Filters A Location filter specifies an inclusive range of Locations. Only objects with Locations within the inclusive range pass the filter. A Location filter is encoded as specified in . Subscribers can specify a Location filter on a subscription indicating to the publisher which Objects to send. Subscriptions without a filter pass all Objects published or received via upstream subscriptions. Fetch requests can also specify a Location filter. Fetch requests without a filter include all Locations from {0, 0} up to Largest Object (). Some Location filters are defined to be relative to the Largest Object (). A Location Filter on a subscription is always valid, even if it specifies a range entirely before Largest Object. Note that due to network reordering or prioritization, relays can receive Objects with Locations smaller than Largest Object after the filter is processed, but these Objects do not pass a filter that starts at the Next Object. A publisher MUST NOT send subscription-delivered objects from outside the requested range. Because updating filters is asynchronous, subscribers can receive objects outside the current filter. A publisher does not end a subscription solely because the Largest Object advances past the end of the current Location Filter. Fill-delivered objects are governed by the Location filter in FILL_PARAMETERS (see ).

Range Filters Range Filters are parameters in SUBSCRIBE, FETCH, or SUBSCRIBE_TRACKS that tell a publisher to filter tracks (via TRACK PROPERTY FILTER) and objects according to subscriber-provided criteria. Range filters are specified as ranges of integer values in Track and Object Properties and other Object header fields (Subgroup ID, Object ID, and Publisher Priority). There are five Range Filter parameter types, 0x25-0x29. They share the encoding specified in . An object matches the filter if its value falls within any Range (i.e., Ranges are OR'd within a filter parameter). Filter parameters with the same SetID are AND'd; distinct SetIDs are OR'd. The final result is SetID=0 OR SetID=1 OR ... SetID=255, where each SetID=i is the AND of all filter parameters carrying that SetID. The Track Property filter parameter MAY appear multiple times in a SUBSCRIBE_TRACKS message or REQUEST_UPDATE for it. All other filter parameters MAY appear multiple times in a FETCH, SUBSCRIBE, SUBSCRIBE_TRACKS, or REQUEST_UPDATE (on a subscription, from the subscriber only) message. If the same combination of Parameter Type, SetID, and Property Type (only in the Track and Object Property Filters) repeat in any message, an endpoint MUST reject this with REQUEST_ERROR with error code INVALID_FILTER. In REQUEST_UPDATE, Length of 0 removes the filter; non-zero replaces it entirely. If a filter parameter is omitted from REQUEST_UPDATE, it is unchanged. If omitted from other messages, the default is no filter. Range Filters are only allowed if the setup option MAX_FILTER_RANGES is non-zero, which limits the total number of Ranges allowed in all Range Filter parameters for a given subscription or fetch. If this limit is exceeded, an endpoint MUST reject this with REQUEST_ERROR with error code INVALID_FILTER. The Track Property Filter can be used in SUBSCRIBE_TRACKS to filter PUBLISH messages with required Track Property types and values. PUBLISH messages which pass the filter will be forwarded while those which do not pass it will not be forwarded nor will any Objects. The Object Property Filter can be used to filter Objects with required Object Property types and values. It only filters Object Properties in the Object header, and does not evaluate Track Properties in PUBLISH messages.

Combining Filters All filter types are combined using logical "AND" operations to further restrict which tracks and objects pass all filter criteria. This includes all Range Filters and Location Filters , which can be evaluated in any order. The Forward parameter is also a type of filter. The publisher MUST forward only objects that pass all filters.

Fill Semantics A subscription that carries a FILL_PARAMETERS parameter (see ) causes the publisher to open a unidirectional stream beginning with a FETCH_HEADER (see ) and delivered as a FETCH response (see ). This is called a fill fetch stream. The fill range is the range of Locations selected by the Location filter inside FILL_PARAMETERS, or the subscription's Location filter if it is omitted. The filter is evaluated using the rules for a Fetch in , so the fill range never extends beyond Largest Object. When the subscription has no Location filter, or the LOCATION_FILTER inside FILL_PARAMETERS is zero-length, the fill range is the entire track up to Largest Object. The subscriber learns the Largest Object from the LARGEST_OBJECT parameter in SUBSCRIBE_OK or REQUEST_UPDATE_OK. Because the fill range is specified independently of the subscription's Location filter, a subscriber can retrieve a range of Groups prior to the live edge while the subscription itself starts at the Next Group. If the fill range is empty, or starts after Largest Object, the publisher does not open a fill fetch stream. The fill fetch stream inherits the subscription's parameters, including subscriber priority, range filters and authorization; parameters carried inside FILL_PARAMETERS override them for the fill fetch stream. FILL_TIMEOUT (see ) applies to fill fetch streams in the same way it applies to a FETCH. The FETCH_HEADER on the fill fetch stream carries the Request ID of the message that initiated it: the SUBSCRIBE Request ID for the initial fill, or the REQUEST_UPDATE Request ID for a subsequent fill. As a result of REQUEST_UPDATE, a subscription can have multiple fill fetch streams open at once, each identified by its Request ID; opening a new fill fetch stream does not implicitly cancel any previously opened fill fetch streams. An object delivered on the fill fetch stream is fill-delivered. When the fill range overlaps the subscription's Location filter, an object can be both fill-delivered and subscription-delivered. A subscriber that wants each Object delivered exactly once uses the Next Object Subscription Location Filter coupled with an open-ended fill range, which the publisher will end at Largest Object.

Opening and Closing Fill Fetch Streams A publisher opens a fill fetch stream when it processes a SUBSCRIBE or REQUEST_UPDATE that carries FILL_PARAMETERS while Forward State is 1.

FILL_PARAMETERS carried while Forward State is 0 opens no fill fetch stream. Transitioning to Forward State 1 without re-sending FILL_PARAMETERS does not open one either.
A REQUEST_UPDATE that does not carry FILL_PARAMETERS does not open a new fill fetch stream.
When the subscription is cancelled, the publisher MUST reset any open fill fetch streams.

The publisher signals that the fill is complete by closing the stream with a FIN once all objects in the fill range have been delivered. Because there is no REQUEST_ERROR associated with a fill fetch stream, the publisher signals a fill failure by resetting the stream; it MUST open a fill fetch stream and reset it immediately after the FETCH_HEADER if necessary. A subscriber can cancel a fill fetch stream independently using STOP_SENDING. Resetting or cancelling a fill fetch stream, by either endpoint, does not affect the subscription, which continues to deliver objects using subscribe subgroups and datagrams.

Joining an Ongoing Track The MOQT Object model is designed with the concept that the beginning of a Group is a join point, so in order for a subscriber to join a Track, it needs to request an existing Group or wait for a future Group. Different applications will have different approaches for when to begin a new Group. To join a Track immediately, the subscriber sends a SUBSCRIBE with a Location Filter that starts at the Next Object. Delivery begins with the next Object and can begin mid-group. To join a Track at the current Group, the subscriber sends a SUBSCRIBE with a Location Filter that starts at the Next Object and a FILL_PARAMETERS parameter (see ) whose Location filter has StartGroup=1, which fills the current Group from its start. To join a Track at a past Group, the subscriber sends a SUBSCRIBE with a FILL_PARAMETERS parameter whose Location filter selects the intended Groups, which can be relative. The publisher delivers the fill range on a fill fetch stream and subscription-delivered Objects in subgroups or datagrams (see ). To join a Track at the next Group, the subscriber sends a SUBSCRIBE with a Location Filter that starts at the Next Group.

Dynamically Starting New Groups While some publishers will deterministically create new Groups, other applications might want to only begin a new Group when needed. A subscriber joining a Track might detect that it is more efficient to request the Original Publisher create a new group than to fill the current group. Publishers indicate a Track supports dynamic group creation using the DYNAMIC_GROUPS Track Property (). One possible subscriber pattern is to SUBSCRIBE to a Track using a Location Filter that starts at the Next Object and observe the Largest Object in the response. If the Object ID is below the application's threshold, the subscriber sends a FETCH for the beginning of the Group. If the Object ID is above the threshold and the Track supports dynamic groups, the subscriber sends a REQUEST_UPDATE message with the NEW_GROUP_REQUEST parameter equal to the Next Group (see ). Another possible subscriber pattern is to send a SUBSCRIBE with a Location Filter that starts at the Next Group and NEW_GROUP_REQUEST equal to 0. The value of DYNAMIC_GROUPS in SUBSCRIBE_OK will indicate if the publisher supports dynamic groups. A publisher that does will begin the next group as soon as practical.

Mandatory Track Properties Property types in the range 0x4000-0x7FFF are designated as Mandatory Track Properties. These properties MUST have Track scope. Mandatory Track Properties have special handling rules that prevent tracks with required properties from being forwarded to or processed by endpoints that do not understand them. An Object received with a Mandatory Track Property as an Object Property is malformed (see ). When an endpoint receives a Mandatory Track Property in PUBLISH, SUBSCRIBE_OK, or FETCH_OK that it does not understand, it MUST NOT process or forward that track:

For PUBLISH messages: the subscriber MUST respond with REQUEST_ERROR with error code UNSUPPORTED_EXTENSION.
For SUBSCRIBE_OK messages: the subscriber MUST cancel the subscription (see ). If the subscriber is a relay with pending downstream subscribers, it MUST send REQUEST_ERROR with error code UNSUPPORTED_EXTENSION to the downstream subscribers.
For FETCH_OK messages: the subscriber MUST cancel the fetch (see ). If the subscriber is a relay and has not yet sent a FETCH_OK or REQUEST_ERROR downstream, it MUST send REQUEST_ERROR with error code UNSUPPORTED_EXTENSION to the downstream fetch requester. If the relay has already forwarded data on a fetch stream, it MUST reset the stream.

A publisher that knows a subscriber does not support a Mandatory Track Property SHOULD take the following action:

For SUBSCRIBE: respond with REQUEST_ERROR with error code UNSUPPORTED_EXTENSION.
For FETCH: respond with REQUEST_ERROR with error code UNSUPPORTED_EXTENSION.
For PUBLISH: do not publish the track to that subscriber.

Namespace Discovery Discovery of MOQT servers is always done out-of-band. Namespace discovery can be done in the context of an established MOQT session using SUBSCRIBE_NAMESPACE (see ). Given sufficient out of band information, it is valid for a subscriber to send a SUBSCRIBE or FETCH message to a publisher (including a relay) without any previous MOQT messages besides SETUP. However, SUBSCRIBE_NAMESPACE, SUBSCRIBE_TRACKS, PUBLISH and PUBLISH_NAMESPACE messages provide an in-band means of discovery of publishers for a namespace. The syntax of these messages is described in .

Subscribing to Namespaces If the subscriber is aware of a namespace of interest, it can send SUBSCRIBE_NAMESPACE or SUBSCRIBE_TRACKS to publishers/relays it has established a session with. The Track Namespace Prefix carried in these messages is compared against the namespaces known to the receiver using Namespace Prefix Matching (). SUBSCRIBE_NAMESPACE requests namespace discovery: the publisher sends relevant NAMESPACE and NAMESPACE_DONE messages for namespaces matching the prefix, including echoing back Track Namespaces under the prefix that have been published to it. SUBSCRIBE_TRACKS requests track subscriptions: the publisher sends PUBLISH messages for tracks within matching namespaces, excluding tracks published by the subscriber. Either message with zero Track Namespace fields indicates the sender is interested in all namespaces or all tracks from the receiver, respectively. By sending SUBSCRIBE_NAMESPACE, the subscriber indicates that it trusts the relay to be authoritative for namespaces matching the requested prefix. NAMESPACE messages received on the SUBSCRIBE_NAMESPACE response stream inherit this trust and do not independently carry authorization. The subscriber sends SUBSCRIBE_NAMESPACE or SUBSCRIBE_TRACKS on a new bidirectional stream and the publisher MUST send a single REQUEST_OK or REQUEST_ERROR as the first message on the bidirectional stream in response. If a Subscription cannot be created because there are no available bidirectional streams or any other reason, the Publisher sends a PUBLISH_SKIPPED message on the SUBSCRIBE_TRACKS response stream to indicate the Full Track Name of the Subscription that was not created. The Publisher MUST NOT send a PUBLISH for a Track for a given SUBSCRIBE_TRACKS after PUBLISH_SKIPPED has been sent, scoped to a single PUBLISH. If, for example, the publisher disconnects from a relay and later reconnects and sends a new PUBLISH, the relay MAY send the new PUBLISH downstream. If desired, the subscriber can issue a SUBSCRIBE to establish a subscription to that track. The receiver of a REQUEST_OK or REQUEST_ERROR ought to forward the result to the application, so the application can decide which other publishers to contact, if any. A SUBSCRIBE_NAMESPACE or SUBSCRIBE_TRACKS is cancelled as described in , by resetting or sending STOP_SENDING on the stream. Cancelling SUBSCRIBE_TRACKS does not prohibit original publishers from sending further PUBLISH messages, but relays MUST NOT send any further PUBLISH messages to a client without knowing the client is interested in and authorized to receive the content.

Publishing Namespaces A publisher MAY send PUBLISH_NAMESPACE messages to any subscriber. A PUBLISH_NAMESPACE indicates to the subscriber that the publisher has tracks available in that namespace. A subscriber MAY send SUBSCRIBE or FETCH for tracks in a namespace without having received a PUBLISH_NAMESPACE for it. If a publisher is the Original Publisher for one or more tracks in a given namespace, or is a relay that has received an authorized PUBLISH_NAMESPACE for that namespace from an upstream publisher, it MUST send a NAMESPACE message that includes this namespace to any subscriber that has sent a SUBSCRIBE_NAMESPACE whose prefix matches this namespace. A subscriber can receive a PUBLISH_NAMESPACE on a request stream for a namespace that falls within an active SUBSCRIBE_NAMESPACE prefix. This occurs when SUBSCRIBE_NAMESPACE or its response is in flight at the same time as a PUBLISH_NAMESPACE, or when an original publisher sends PUBLISH_NAMESPACE to advertise namespaces within the prefix being discovered. Such a PUBLISH_NAMESPACE is valid and MAY carry an AUTHORIZATION TOKEN parameter. Its lifetime is independent of the SUBSCRIBE_NAMESPACE stream. An endpoint SHOULD report the reception of a REQUEST_OK or REQUEST_ERROR to the application to inform the search for additional subscribers for a namespace, or to abandon the attempt to publish under this namespace. A subscriber MUST send exactly one REQUEST_OK or REQUEST_ERROR as the first message on the bidi stream in response to a PUBLISH_NAMESPACE. The publisher SHOULD close the session with a protocol error if it receives more than one. A PUBLISH_NAMESPACE is withdrawn by cancelling the request (see ), although it is not a protocol error for the subscriber to send a SUBSCRIBE or FETCH message for a track in a namespace after the namespace is withdrawn. A subscriber can cancel the request (see ) to revoke acceptance of a PUBLISH_NAMESPACE. If the reason for cancellation is expiration of authorization credentials, the publisher can send PUBLISH_NAMESPACE again on a new bidi stream with refreshed authorization, or close the stream and discard associated state. While PUBLISH_NAMESPACE indicates to relays how to connect publishers and subscribers, it is not a full-fledged routing protocol and does not protect against loops and other phenomena. In particular, PUBLISH_NAMESPACE SHOULD NOT be used to find paths through richly connected networks of relays. A subscriber MAY send a SUBSCRIBE or FETCH for a track to any publisher. If it has accepted a PUBLISH_NAMESPACE with a namespace that exactly matches the namespace for that track, it SHOULD only request it from the senders of those PUBLISH_NAMESPACE messages.

Filtering SUBSCRIBE_TRACKS Range Filters can be used in SUBSCRIBE_TRACKS to filter Tracks in a namespace using the Track Property Filter. Objects published in the resulting Subscriptions can be filtered by any Range Filter.

Relay Resource Protection in Large Namespaces Relays SHOULD aggregate and propagate filters upstream on subscriptions, especially namespace subscriptions, to conserve and protect their resources from excessive load. They MAY also impose limits on the number of publishers in a namespace, by rejecting or closing namespace subscriptions with the error NAMESPACE_TOO_LARGE, or CONFLICTING_FILTERS if too many disjoint filters are requested on downstream subscriptions across a large number of subscribers, or PREFIX_OVERLAP if different subscribers force an aggregated upstream subscription to overlap.

Object Transmission

Priorities MOQT priorities allow a subscriber and original publisher to influence the transmission order of Objects within a session in the presence of congestion.

Definitions MOQT maintains priorities between different schedulable objects. A schedulable object in MOQT is either:

The first or next Object in a Subgroup that is in response to a subscription.
An Object with forwarding preference Datagram.
An Object in response to a FETCH where that Object is the next Object in the response.

An Object is not schedulable if it is known that no part of it can be written due to underlying transport flow control limits. A single subgroup or datagram has a single publisher priority. Within a subscription, it can be useful to conceptualize this process as scheduling subgroups or datagrams instead of individual objects on them. FETCH responses however can contain objects with different publisher priorities. A priority numberis an unsigned integer with a value between 0 and 255. A lower priority number indicates higher priority; the highest priority is 0. Subscriber Priority is a priority number associated with an individual request. It is carried in the SUBSCRIBER_PRIORITY parameter (), and can be updated. The subscriber priority of an individual schedulable object is the subscriber priority of the request that caused that object to be sent. When subscriber priority is changed, a best effort SHOULD be made to apply the change to all objects that have not been scheduled, but it is implementation dependent what happens to objects that have already been scheduled. Publisher Priority is a priority number associated with an individual schedulable object. A default for the subscription is specified in the DEFAULT_PUBLISHER_PRIORITY Track Property (). Publisher priority can also be set per subgroup or datagram in the subgroup header or datagram (see ), which overrides the default. Group Order is a property of an individual subscription. It can be either 'Ascending' (groups with lower group ID are sent first), or 'Descending' (groups with higher group ID are sent first). The subscriber optionally communicates its group order preference in the SUBSCRIBE or SUBSCRIBE_TRACKS message; the publisher's preference, carried in the DEFAULT_PUBLISHER_GROUP_ORDER Track Property (), is used if the subscriber did not express one (by omitting the Group Order parameter). The group order of an existing subscription cannot be changed.

Scheduling Algorithm When an MOQT publisher has multiple schedulable objects it can choose between, the objects SHOULD be selected as follows:

If two objects have different subscriber priorities associated with them, the one with the highest subscriber priority is scheduled to be sent first.
If two objects have the same subscriber priority, but different publisher priorities, the one with the highest publisher priority is scheduled to be sent first.
If two objects in the same subscription have the same subscriber and publisher priority, but belong to two different groups of the same track, the group order of the subscription is used to decide the one that is scheduled to be sent first. When a subscription fill's Group Order differs from the subscription's Group Order, the subscription-delivered object is scheduled first.
If two objects in the same subscription have the same subscriber and publisher priority and belong to the same group of the same track, and one is delivered by the fill fetch stream while the other is subscription-delivered, the fill-delivered object is scheduled first. Otherwise, the one with the lowest Subgroup ID (for objects with forwarding preference Subgroup), or the lowest Object ID (for objects with forwarding preference Datagram) is scheduled to be sent first. If the two objects have different Forwarding Preferences the datagram is sent first.

Within the same group, fill-delivered objects win the tie-break over subscription-delivered objects (rule 4) because objects with smaller Locations are assumed to be needed before those with larger Locations. The definition of "scheduled to be sent first" in the algorithm is implementation dependent and is constrained by the prioritization interface of the underlying transport. For some implementations, it could mean that the object is serialized and passed to the underlying transport first. Other implementations can control the order packets are initially transmitted. This algorithm does not provide a well-defined ordering for objects that belong to different subscriptions or FETCH responses, but have the same subscriber and publisher priority. The ordering in those cases is implementation-defined, though the expectation is that all subscriptions will be able to send some data. A publisher might not utilize the entire available congestion window, session flow control, or all available streams for lower priority Objects if it expects higher priority Objects will be available to send in the near future or it wants to reserve some bandwidth for control messages. Given the critical nature of control messages and their relatively small size, the control streams SHOULD be prioritized highest, followed by the bidi request streams and then all Objects. Bidi request streams MAY be prioritized within themselves by Subscriber Priority if specified.

Considerations for Setting Priorities For downstream subscriptions, relays SHOULD respect the subscriber and original publisher's priorities. Relays can receive subscriptions with conflicting subscriber priorities or Group Order preferences. Relays SHOULD NOT directly use Subscriber Priority or Group Order from incoming subscriptions for upstream subscriptions. A Relay's use of these fields for upstream subscriptions can be based on factors specific to it, such as the popularity of the content or policy, or relays can specify the same value for all upstream subscriptions. MOQT Sessions can span multiple namespaces, and priorities might not be coordinated across namespaces. The subscriber's priority is considered first, so there is a mechanism for a subscriber to fix incompatibilities between different namespaces prioritization schemes. Additionally, it is anticipated that when multiple namespaces are present within a session, the namespaces could be coordinating, possibly part of the same application. In cases when pooling among namespaces is expected to cause issues, multiple MOQT sessions, either within a single connection or on multiple connections can be used. Implementations that have a default priority SHOULD set it to a value in the middle of the range (eg: 128) to allow non-default priorities to be set either higher or lower.

Delivery Timeouts and Data Reliability Each MOQT subscription has two timeout values associated with it: a SUBGROUP_DELIVERY_TIMEOUT and an OBJECT_DELIVERY_TIMEOUT. Both of those values are expressed in milliseconds and both are optional; a value of 0 means that there is no timeout set. The publisher communicates both timeout values as a Track Property; the subscriber communicates them as Message Parameters. Either timeout value can also be set as an Object Property on the first object in a subgroup, overriding the Track-level value for that subgroup. If either timeout is set as an Object Property on any object other than the first in a subgroup, it is ignored. For each type of timeout, the publisher's value is the Object Property when present on the first object of the subgroup, and the Track Property otherwise. If both the publisher's value and the subscriber's value are non-zero, the smaller of the two is used. If the OBJECT_DELIVERY_TIMEOUT is not zero, the MOQT implementation MUST retain the time at which the last header byte of every object has been either received from the upstream subscription, or provided by the original publisher application. The actual mechanism by which the timeout works depends on the Object Forwarding Preference:

For subgroups, the implementation MUST check the time elapsed before attempting to pass it to the underlying transport for transmission; if the time elapsed exceeds OBJECT_DELIVERY_TIMEOUT, it MUST reset the underlying transport stream with the reset stream code DELIVERY_TIMEOUT (see ) and SHOULD NOT attempt to open a new stream to deliver additional Objects in that Subgroup. The implementation SHOULD check object delivery timeouts before retransmitting object data if the underlying transport implementation allows. The implementations SHOULD minimize the amount of data buffered at the underlying transport layer, as any data buffered at this layer can no longer be timed out, potentially leading to transmission of expired data.
For datagrams, the implementation MUST drop the datagrams if the time elapsed exceeds OBJECT_DELIVERY_TIMEOUT. Similar to subgroups, implementations SHOULD either minimize datagram queueing, or use datagram queueing mechanisms that support time bounds (such as the outgoingMaxAge parameter in the W3C WebTransport API).

If the Object Forwarding Preference is Subgroup and the value of SUBGROUP_DELIVERY_TIMEOUT is not zero, the MOQT implementation MUST start a timer of SUBGROUP_DELIVERY_TIMEOUT duration once it becomes aware that all of the objects on the subgroup have been published (either by receiving a FIN from the upstream subscription, or, in case of the original publisher, through being notified of this fact by the application). If the timer expires before the underlying transport stream reaches "all data committed" state (), the implementation MUST reset the stream. This ensures that MOQT can time out subgroups where all of the data has been sent but not yet fully delivered due to packet loss. For objects whose Object Forwarding Preference is Datagram, the SUBGROUP_DELIVERY_TIMEOUT acts the same way as OBJECT_DELIVERY_TIMEOUT; if both are non-zero, the smaller of the two is used. Comparison of the delivery timeout mechanisms

	SUBGROUP_DELIVERY_TIMEOUT	OBJECT_DELIVERY_TIMEOUT
Timeout starts	When the FIN for the subgroup is received	When the last byte of the object header is received
Timeout checked at	Via a timer until all data is acknowledged	When the object is sent to the underlying transport
Action upon timeout	Reset for subgroups, drop for datagrams	Reset for subgroups, drop for datagrams

Publishers can, at their discretion, discontinue forwarding Objects before either timeout occurs, subject to stream closure and ordering constraints described in . However, if neither timeout is set to a non-zero value, all Objects in the track matching the subscription filter are delivered as indicated by their Group Order and Priority. If a subscriber fails to consume Objects at a sufficient rate, causing the publisher to exceed its resource limits, the publisher MAY terminate the subscription using PUBLISH_DONE with error TOO_FAR_BEHIND.

Sessions

MOQT URI Scheme An MOQT server is identified using a URI with the "moqt" scheme. The "moqt" URI scheme is defined as follows, using definitions from : The authority portion MUST NOT contain an empty host portion. The moqt URI scheme supports the /.well-known/ path prefix defined in . The moqt URI scheme follows the generic URI syntax of for the authority, path-abempty, and query components, including the use of reserved characters and percent-encoding defined therein. A moqt URI can be converted to an https URI by replacing the scheme (see ), so the path-abempty and query components use the same syntax as https URIs.

Fragment Identifiers The media type for resources identified by moqt URIs is application/moqt (see ). Fragment identifiers MAY be used with moqt URIs. The fragment is not transmitted to the server; it is processed locally by the client after establishing the MOQT session. A moqt URI fragment MUST begin with a registered fragment type identifier, followed by a colon (:), followed by a type-specific value: : ]]> Fragment type identifiers MUST consist of ASCII lowercase letters, digits, and hyphens (a-z, 0-9, -). The semantics of the value after the colon are defined by the specification that registers the fragment type. Fragment type identifiers are registered in the "MOQT URI Fragment Types" registry ().

Dereferencing a MOQT URI The default operation for dereferencing a moqt URI is to establish a MOQT session to the identified server. The moqt URI scheme has the following security considerations:

The authority component is sent in the TLS SNI extension during connection establishment, exposing the target server identity to on-path observers. Encrypted Client Hello (ECH) can mitigate this exposure.
The path-abempty and query components are visible to the relay that terminates the client's connection.

TODO: Add internationalization statement per RFC 7595 Section 3.6. The client resolves the host subcomponent of the authority to one or more network addresses, most commonly using DNS A and AAAA records. When SVCB-compatible records are published for the authority, a client MAY use them to learn the server's endpoints and supported ALPN protocols before connecting. A client using WebTransport resolves the https URI derived in using HTTPS resource records as for any https origin. TODO: reference moqt SVCB record draft once available. If the port is omitted in the URI, a default port of 443 is used. The client MAY use either native QUIC or WebTransport. On a QUIC connection, the client offers any combination of MOQT ALPNs (e.g. moqt-1, moqt-2) and h3 that it supports in its TLS ClientHello, in preference order. If the server selects an MOQT ALPN, the session proceeds as described in . If the server selects h3, the client establishes a WebTransport session as described in . On a TCP+TLS connection, the client offers h2 in its TLS ClientHello and establishes a WebTransport session as described in .

Session establishment This document defines a protocol that can be used interchangeably both over a QUIC connection directly , and over WebTransport . Both provide streams and datagrams with similar semantics (see ); thus, the main difference lies in how the servers are identified and how the connection is established. The QUIC DATAGRAM extension () MUST be supported and negotiated in the QUIC connection used for MOQT, which is already a requirement for WebTransport over HTTP/3. There is no definition of the protocol over other transports, such as TCP, and applications using MOQT might need to fallback to another protocol when QUIC or WebTransport aren't available. MOQT uses ALPN in QUIC and "WT-Available-Protocols" in WebTransport () to perform version negotiation. The ALPN value for the final version of this specification is moqt. [[RFC editor: please remove the remainder of this section before publication.]] ALPNs used to identify IETF drafts are created by appending the draft number to "moqt-". For example, draft-ietf-moq-transport-13 would be identified as "moqt-13". Note: Draft versions prior to -15 all used moq-00 ALPN, followed by version negotiation in the SETUP messages.

WebTransport When the client uses WebTransport, it constructs an https URI from the moqt URI by replacing the scheme with https. For example, moqt://example.com/path becomes https://example.com/path. The client sends an extended CONNECT request to this URI to establish a WebTransport session, as described in (). The client includes MOQT protocol identifiers in the WT-Available-Protocols header ().

Native QUIC The client establishes a QUIC connection to the host and port identified by the authority section of the URI. When the client uses native QUIC, the authority, path-abempty and query portions of the URI are transmitted in Setup Options (see ).

Session initialization MOQT uses a pair of unidirectional streams for creating the session and exchanging control messages. Each peer opens one control stream beginning with a SETUP message. Using a pair of unidirectional streams rather than a single bidirectional stream allows either peer to send data as soon as it is able. Depending on whether 0-RTT is available on the QUIC connection, either the client or the server might be able to send stream data first. In addition to the control streams, this specification uses bidirectional streams to carry requests. A request stream begins with one of these seven message types: TRACK_STATUS, SUBSCRIBE, PUBLISH, FETCH, PUBLISH_NAMESPACE, SUBSCRIBE_NAMESPACE, and SUBSCRIBE_TRACKS. Bidirectional streams MUST NOT begin with any other message type unless negotiated. If they do, the peer MUST close the Session with a PROTOCOL_VIOLATION. Objects are sent on unidirectional streams. As such, a client can initiate a MOQT session, subscribe, and start publishing Objects all in parallel. When this is done before the handshake completes using 0-RTT, the security implications described in apply. Unidirectional streams containing Objects or bidirectional stream(s) beginning with a request message could arrive prior to the control streams, in which case the data SHOULD be buffered until both control streams arrive and setup is complete. If an implementation does not want to buffer or if the message type is not supported, it MAY reset such bidirectional streams before the session and control streams are established. A control stream MUST NOT be closed at the underlying transport layer during the session's lifetime. Doing so results in the session being closed as a PROTOCOL_VIOLATION. Prior to receiving the peer's SETUP message, it's unknown what extensions a peer will support. Message Parameters requiring negotiation SHOULD NOT be used prior to receiving the peer's SETUP message unless the application requires the extension or the endpoint knows the peer supports the extension. If an unsupported Message Parameter is used, the peer will be unable to process it and the session will be terminated. See .

0-RTT QUIC supports 0-RTT (), but WebTransport over QUIC is not expected to use 0-RTT, because initializing a WebTransport session uses CONNECT, which is not a safe method. describes the use of 0-RTT with HTTP in more detail. If 0-RTT is used with an existing or future version of WebTransport, the following would apply to it as well as QUIC. MOQT Messages and Objects as defined in this draft are safe to replay in most circumstances.

TRACK_STATUS gets the Largest Object and Track Properties, but does not change the state of a Track or any Object in the Track.
SUBSCRIBE requests Objects be delivered, but does not change the Objects being requested.
PUBLISH initiates a Subscription. Objects can be immediately sent to the Subscriber. Processing the same Objects multiple times is idempotent, as the subscriber or relay can identify and discard duplicates based on the Group ID and Object ID.
SUBSCRIBE_NAMESPACE requests a list of namespaces and the establishment of new subscriptions, but does not change the available Namespaces, Tracks, or Objects contained within a Track.
PUBLISH_NAMESPACE requests that Subscriptions under the namespace be sent to that Publisher. If a Subscription was sent to the replaying endpoint, it would fail because the endpoint cannot complete the handshake.

Some potential side effects of replay are:

Publishing Objects that were previously published could cause those Objects to be distributed to active Subscriptions if the relays do not identify them as already having been published. This re-distribution could also make them available in cache again after they previously expired.

Replays could increase load on the MOQT network. For relay to client traffic, this is no worse than 0-RTT in HTTP/3, since the server is limited by the amplification factor until address validation. However, it could cause the relay to initiate new upstream Subscriptions. For a SUBSCRIBE_TRACKS request, sending that upstream could cause the Relay to receive a number of new Subscriptions on the replaying client's behalf. Relays MAY defer initiating upstream subscriptions until the handshake is complete or reject 0-RTT entirely to mitigate resource exhaustion from replayed packets.

Extension Negotiation Endpoints use the exchange of Setup messages to negotiate MOQT extensions. Extensions can define new Message types, new Parameters, new Properties, new Parameter values, or new framing for Streams and Datagrams. The client and server MUST include all Setup Options required for the negotiated MOQT version in SETUP. Each endpoint declares the extensions it supports and provides any initial values required by those extensions as Setup Options in SETUP. Once an endpoint has both sent and received SETUP messages, it determines the set of negotiated extensions. New versions of MOQT MUST specify which existing extensions can be used with that version. New extensions MUST specify the existing versions with which they can be used.

Stream Usage

Unidirectional Streams All unidirectional MOQT streams start with a variable-length integer indicating the type of the stream.

ID	Type
0x05	FETCH_HEADER ()
0b0XX1XXXX	SUBGROUP_HEADER ()
0x2F00	SETUP ()
0x132B3E28	PADDING ()

An endpoint that receives an unknown stream type MUST close the session. Control streams (SETUP) are described in . Data streams (FETCH_HEADER, SUBGROUP_HEADER) are described in . Padding streams are described in .

Bidirectional Request Streams

Request ID Request ID is included in request messages and is used to identify requests across messages. For example, fetch streams reference the Request ID of a SUBSCRIBE, PUBLISH, FETCH, or REQUEST_UPDATE. The client generates even numbered Request IDs, starting at 0, and the server generates odd numbered Request IDs, starting at 1. Each endpoint increments its Request ID by 2 for each new request. Each SUBSCRIBE, PUBLISH, FETCH, SUBSCRIBE_NAMESPACE, SUBSCRIBE_TRACKS, PUBLISH_NAMESPACE, REQUEST_UPDATE, and TRACK_STATUS message consumes a Request ID. Only request messages include a Request ID; response messages do not, since they are sent on the same bidirectional stream as the request. If an endpoint receives a Request ID where the least significant bit is incorrect for the sender, or a duplicate Request ID, it MUST close the session with INVALID_REQUEST_ID.

Graceful Request Stream Closure A request stream is bidirectional and each direction is closed independently, either gracefully with a FIN or abruptly with RESET_STREAM. A FIN only indicates that an endpoint will send no further messages in that direction; it is not a request cancellation. An endpoint MUST NOT send a FIN on a direction of a request stream until it has sent all required messages on that direction for its request type. In particular, an endpoint sending a response to a request MUST send the corresponding response message, and the publisher of an Established subscription MUST send PUBLISH_DONE, before sending a FIN. A FIN sent by the responder after its response and any subsequent messages for the request signals that the request is complete; if it has not already done so, the requester SHOULD then send a FIN on its direction, gracefully closing the stream. An endpoint that receives a FIN before all required messages have arrived treats the request as failed. An endpoint SHOULD send a FIN promptly after a message when it has nothing further to send on that direction and will not need to respond to a future REQUEST_UPDATE. A requester, with the exception of the sender of PUBLISH, MAY FIN immediately after sending a message if it will not send a REQUEST_UPDATE.

Request Cancellation and Rejection Once a request stream has been opened, the request MAY be cancelled by either endpoint. Senders cancel requests if the response is no longer of interest; Receivers cancel requests if they are unable to or choose not to respond. Implementations cancel a request by abruptly terminating any directions of the stream that are still open, using RESET_STREAM for a direction they are sending and STOP_SENDING for a direction they are receiving. An endpoint that has already sent a FIN on its sending direction and subsequently wishes to cancel sends STOP_SENDING on the receiving direction. When an endpoint rejects a request without performing any application processing, it SHOULD send a REQUEST_ERROR and FIN the stream.

Session-Level Tracks and Namespaces MOQT defines the .session namespace (the bytes 0x2e, 0x73, 0x65, 0x73, 0x73, 0x69, 0x6f, 0x6e) in the first position of the Track Namespace for session-level tracks and namespaces. Session-level tracks and namespaces are managed by the MOQT implementation, not the Application. They provide a mechanism for extending MOQT transport functionality using existing subscription and object delivery machinery, without defining new control messages or stream types. The Application MUST NOT publish tracks or namespaces whose first field is .session. Relays MUST NOT forward requests for session-level tracks and namespaces to other sessions. The empty track name in the .session namespace is defined to not exist. A request with a Track Namespace whose first field is .session and an empty Track Name MUST be rejected with DOES_NOT_EXIST. An endpoint that receives a request for an unrecognized session-level track or namespace MUST reject it with REQUEST_ERROR using error code DOES_NOT_EXIST rather than passing it to the Application. The track names and namespaces available under the .session namespace are defined by extensions to this specification and registered with IANA (see ).

Termination The Transport Session can be terminated at any point. When native QUIC is used, the session is closed using the CONNECTION_CLOSE frame (). When WebTransport is used, the session is closed using the CLOSE_WEBTRANSPORT_SESSION capsule (). The error codes used when terminating a Session are defined in . An endpoint MAY choose to treat a subscription or request specific error as a session error under certain circumstances, closing the entire session in response to a condition with a single subscription or message. Implementations need to consider the impact on other outstanding subscriptions before making this choice.

Graceful Session Migration MOQT requires a long-lived and stateful session. However, a service provider needs the ability to shutdown/restart a server without waiting for all sessions to drain naturally, as that can take days for long-form media. MOQT enables proactively draining sessions via the GOAWAY message (). A GOAWAY on the control stream migrates the entire session, as described in this section. A GOAWAY on a single request stream instead migrates only that request, leaving the rest of the session in place; see . The server sends a GOAWAY message, signaling the client to establish a new session and migrate any Established subscriptions. The GOAWAY message optionally contains a new URI for the new session, otherwise the current URI is reused. The GOAWAY message contains a Timeout indicating how long, in milliseconds, the sender intends to wait before closing the session. The sender SHOULD close the session with GOAWAY_TIMEOUT after the indicated timeout if there are still open subscriptions or fetches on a connection. When the server is a subscriber, it SHOULD send a GOAWAY message to downstream subscribers prior to unsubscribing from upstream publishers. After the client receives a GOAWAY, it's RECOMMENDED that the client waits until there are no more Established subscriptions before closing the session with NO_ERROR. Ideally this is transparent to the application using MOQT, which involves establishing a new session in the background and migrating Established subscriptions and published namespaces. The client can choose to delay closing the session if it expects more OBJECTs to be delivered. The sender closes the session with a GOAWAY_TIMEOUT if the peer doesn't close the session within the indicated Timeout.

Relays Relays are leveraged to enable distribution scale in the MOQT architecture. Relays can be used to form an overlay delivery network, similar in functionality to Content Delivery Networks (CDNs). Additionally, relays serve as policy enforcement points by validating subscribe and publish requests at the edge of a network. Relays are endpoints, which means they terminate Transport Sessions in order to have visibility of MOQT Object metadata.

Caching Relays Relays MAY cache Objects, but are not required to. A caching relay saves Objects to its cache identified by the Object's Full Track Name, Group ID and Object ID. If multiple objects are received with the same Full Track Name, Group ID and Object ID, Relays MAY ignore subsequently received Objects or MAY use them to update certain cached fields. Implementations that update the cache need to protect against cache poisoning. The only Object fields that can be updated are the following:

Object can transition from existing to not existing in cases where the object is no longer available.
Object Properties can be added, removed or updated, subject to the constraints of the specific property.

An endpoint that receives a duplicate Object with a different Forwarding Preference, Subgroup ID, Priority or Payload MUST treat the track as Malformed. For ranges of objects that do not exist, relays MAY change the representation of a missing range to a semantically equivalent one. For instance, a relay may change an End-of-Group="Y" Subgroup Header to an equivalent object with an End of Group status, or a Prior Group ID Gap property could be removed in FETCH, where it's redundant. As described in , an endpoint can receive an Object after it has already recorded that the Object does not exist. A caching relay SHOULD NOT cache or forward the Object in this case. A cache MUST store all fields of an Object defined in , with the exception of any Object Properties () that specify otherwise.

Forward Handling If one or more downstream subscribers to a track have Forward=1, the relay MUST set Forward=1 upstream in order to receive and forward the requested Objects. When no downstream subscriber has Forward=1, the relay chooses the upstream Forward value at its discretion, considering the following tradeoffs and deployment considerations:

Setting Forward=1 upstream starts object delivery and pre-warms the relay's cache, so objects are available when a downstream subscriber sets Forward=1. This reduces latency but consumes upstream and publisher resources for content no downstream subscriber is currently receiving.
Setting Forward=0 upstream avoids that work, at the cost of higher latency when forwarding is later enabled.

Multiple Publishers A Relay can receive PUBLISH_NAMESPACE for the same Track Namespace or PUBLISH messages for the same Track from multiple publishers. The following sections explain how Relays maintain subscriptions to all available publishers for a given Track. There is no specified limit to the number of publishers of a Track Namespace or Track. An implementation can use mechanisms such as REQUEST_ERROR or unsubscribing (see ) if it cannot accept an additional publisher due to implementation constraints. Implementations can consider the establishment or idle time of the session or subscription to determine which publisher to reject or disconnect. Relays MUST handle Objects for the same Track from multiple publishers and forward them to matching Established subscriptions. The Relay SHOULD attempt to deduplicate Objects before forwarding, subject to implementation constraints.

Subscriber Interactions Subscribers request Tracks by sending a SUBSCRIBE (see ) or FETCH (see ) control message for each Track of interest. Relays MUST ensure subscribers are authorized to access the content associated with the Track. The authorization information can be part of request itself or part of the encompassing session. The specifics of how a relay authorizes a user are outside the scope of this specification. The relay MUST have an Established upstream subscription before sending SUBSCRIBE_OK in response to a downstream SUBSCRIBE. If a relay does not have sufficient information to send a FETCH_OK immediately in response to a FETCH, it MUST withhold sending FETCH_OK until it does. Relays MUST follow the constraints on LARGEST_OBJECT defined in . Publishers maintain a list of Established downstream subscriptions for each Track. Relays use the Track Alias () of an incoming Object to identify its Track and find the current subscribers. Each new Object belonging to the Track is forwarded to each subscriber, as allowed by the subscription's filter (see ), and delivered according to the priority (see ) and delivery timeout (see ). A relay MUST NOT reorder or drop objects received on a multi-object stream when forwarding to subscribers. Relays MAY aggregate authorized subscriptions for a given Track when multiple subscribers request the same Track. Subscription aggregation allows relays to make only a single upstream subscription for the Track. The published content received from the upstream subscription request is cached and shared among the pending subscribers. Relays that aggregate subscriptions MAY combine filters from downstream subscribers on the upstream subscription, up to the peer's MAX_FILTER_RANGES. If adding filters to an upstream subscription is not possible, the relay can either remove some or all filters, or make additional subscriptions to the same Track. Multiple subscriptions to the same Track with non-disjoint filter sets will result in duplicate objects arriving at the relay. Using wider upstream filters can protect the relay from churn as subscribers with disparate filters subscribe and unsubscribe from a Track, at the cost of receiving more objects. A subscriber remains subscribed to a Track at a Relay until it unsubscribes, the upstream publisher terminates the subscription, or the subscription expires (see ). A subscription with a filter can reach a state where all possible Objects matching the filter have been delivered to the subscriber. Since tracking this can be prohibitively expensive, Relays are not required or expected to do so.

Graceful Subscriber Relay Switchover This section describes a behavior that a Subscriber MAY implement to improve user experience when a relay sends a GOAWAY or the Subscriber switches between networks, such as WiFi to Cellular, and QUIC Connection Migration is not possible. When a subscriber receives the GOAWAY message, it starts the process of connecting to a new relay and sending the SUBSCRIBE requests for all Established subscriptions to the new relay. The new relay will send a response to the subscribes and if they are successful, the subscriptions to the old relay can be cancelled (see ).

Publisher Interactions There are two ways to publish through a relay:

Send a PUBLISH message for a specific Track to the relay. The relay MAY pause the Subscription with REQUEST_UPDATE in Forward State=0 until there are known subscribers for new Tracks.
Send a PUBLISH_NAMESPACE message for a Track Namespace to the relay. This enables the relay to send SUBSCRIBE or FETCH messages to publishers for Tracks in this Namespace in response to requests received from subscribers.

Relays MUST verify that publishers are authorized to publish the set of Tracks whose Track Namespace matches the namespace in a PUBLISH_NAMESPACE, or the Full Track Name in PUBLISH. Relays MUST NOT assume that an authorized publisher of a single Track is implicitly authorized to publish any other Tracks or Track Namespaces. If a Publisher would like Subscriptions in a Namespace routed to it, it MUST send an explicit PUBLISH_NAMESPACE. The authorization and identification of the publisher depends on the way the relay is managed and is application specific. When a publisher wants to stop new subscriptions for a published namespace, it cancels the request (see ) to withdraw the PUBLISH_NAMESPACE. A subscriber indicates it will no longer subscribe to Tracks in a namespace it previously responded PUBLISH_NAMESPACE_OK to by cancelling the PUBLISH_NAMESPACE request. A Relay connects publishers and subscribers by managing sessions based on the Track Namespace or Full Track Name. When a SUBSCRIBE message is sent, its Full Track Name is matched exactly against existing upstream subscriptions. Namespace Prefix Matching is further used to decide which publishers receive a SUBSCRIBE and which subscribers receive a PUBLISH. In this process, the fields in the Track Namespace are matched sequentially, requiring an exact match for each field. If the published or subscribed Track Namespace has the same or fewer fields than the Track Namespace in the message, it qualifies as a match. For example: A SUBSCRIBE message with namespace=(foo, bar) and name=x will match sessions that sent PUBLISH_NAMESPACE messages with namespace=(foo) or namespace=(foo, bar). It will not match a session with namespace=(foobar). Relays MUST send SUBSCRIBE messages to all matching publishers. This includes matching both Established subscriptions on the Full Track Name and Namespace Prefix Matching against published Namespaces. Relays MUST forward PUBLISH_NAMESPACE or PUBLISH messages to all matching subscribers. When a Relay needs to make an upstream FETCH request, it determines the available publishers using the same matching rules as SUBSCRIBE. When more than one publisher is available, the Relay MUST send the FETCH to at least one of them. When a Relay receives a SUBSCRIBE with FILL_PARAMETERS, it serves the fill range from its cache and retrieves any missing objects upstream using a SUBSCRIBE with FILL_PARAMETERS or FETCHes (see ). When a Relay receives an authorized SUBSCRIBE for a Track with one or more Established upstream subscriptions, it MUST reply with SUBSCRIBE_OK. If the SUBSCRIBE has Forward State=1 and the upstream subscriptions are in Forward State=0, the Relay MUST send REQUEST_UPDATE with Forward=1 to all publishers. If there are no Established upstream subscriptions for the requested Track, the Relay MUST send a SUBSCRIBE request to each publisher that has published the subscription's namespace or prefix thereof. If the SUBSCRIBE has Forward=1, then the Relay MUST use Forward=1 when subscribing upstream. When a relay receives an incoming PUBLISH message, it MUST send a PUBLISH request to each subscriber that has sent SUBSCRIBE_TRACKS for the Track's namespace or a prefix thereof. However, if the relay is holding a downstream SUBSCRIBE awaiting a publisher for this Track (see ), it MUST proceed with the SUBSCRIBE and MUST NOT also forward the PUBLISH to that subscriber. When a relay receives an authorized PUBLISH_NAMESPACE for a namespace that matches one or more existing subscriptions to other upstream sessions, it MUST send a SUBSCRIBE to the publisher that sent the PUBLISH_NAMESPACE for each matching subscription. When it receives an authorized PUBLISH message for a Track that has Established downstream subscriptions, it MUST respond with PUBLISH_OK. If at least one downstream subscriber for the Track has Forward State=1, the Relay MUST change the Forward State to 1 with REQUEST_UPDATE. If a Session is closed due to an unknown or invalid control message or Object, the Relay MUST NOT propagate that message or Object to another Session, because it would enable a single Session error to force an unrelated Session, which might be handling other subscriptions, to be closed.

Graceful Publisher Relay Switchover This section describes a behavior that a publisher MAY implement to improve user experience when a relay sends a GOAWAY or the publisher switches between networks, such as WiFi to Cellular, and QUIC Connection Migration is not possible. A new Session is established, to a new URI if specified in a GOAWAY. The publisher sends PUBLISH_NAMESPACE and/or PUBLISH messages to begin publishing on the new Session, but it does not immediately stop publishing Objects on the old Session. Once the subscriptions have migrated over to the new session, the publisher can stop publishing Objects on the old session. The relay will attempt to deduplicate Objects received on both subscriptions. Ideally, the subscriptions downstream from the relay do not observe this change, and keep receiving the Objects on the same subscription.

Relay Track Handling A relay MUST include all Properties associated with a Track when sending any PUBLISH, SUBSCRIBE_OK, TRACK_STATUS_OK, or FETCH_OK, unless allowed by the property's specification (see ).

Relay Object Handling MOQT encodes the delivery information in the Object header (). A relay MUST NOT modify Object fields when forwarding, except for Object Properties as specified in . A relay MUST treat the object payload as opaque. A relay MUST NOT combine, split, or otherwise modify object payloads. Relays prioritize forwarded Objects as described in .

Notational Conventions and Common Structures This document uses the conventions detailed in () when describing the binary encoding.

Variable-Length Integers MOQT requires a variable-length integer encoding with the following properties:

The encoded length can be determined from the first encoded byte.
The range of 1 byte values is as large as possible.
All 64 bit numbers can be encoded.

The variable-length integer encoding uses the number of leading 1 bits of the first byte to indicate the length of the encoding in bytes. The remaining bits after the first 0 and subsequent bytes, if any, represent the integer value, encoded in network byte order. Integers are encoded in 1 to 9 bytes and can encode up to 64 bit unsigned integers. The following table summarizes the encoding properties. Summary of Integer Encodings

Leading Bits	Length (bytes)	Usable Bits	Range
0	1	7	0-127
10	2	14	0-16383
110	3	21	0-2097151
1110	4	28	0-268435455
11110	5	35	0-34359738367
111110	6	42	0-4398046511103
1111110	7	49	0-562949953421311
11111110	8	56	0-72057594037927935
11111111	9	64	0-18446744073709551615

The following table contains some example encodings: Example Integer Encodings

Byte Sequence	Decimal Value
0x25	37
0x8025	37
0xbbbd	15,293
0xed7f3e7d	226,442,877
0xfaa1a0e403d8	2,893,212,287,960
0xfc8998abc66bc0	151,288,809,941,952
0xfefa318fa8e3ca11	70,423,237,261,249,041
0xffffffffffffffffff	18,446,744,073,709,551,615

Variable-length integers do not need to be encoded using the minimum number of bytes; any encoding length that can represent the value is valid. Note that, as a result, the same numeric value can be represented by more than one byte sequence. For example, the value 0 can be encoded as 0x00, 0x8000, 0xc00000, or any longer form.

x (vi64):: Indicates that x holds an integer value using the variable-length encoding as described above.

Location Structure Location identifies a particular Object in a Group within a Track.

Location structure In this document, a Location can be expressed in the form of {GroupID, ObjectID}, where GroupID and ObjectID indicate the Group ID and Object ID of the Location, respectively. The constituent parts of any Location A can be referred to using A.Group or A.Object. Location A < Location B if: A.Group < B.Group || (A.Group == B.Group && A.Object < B.Object)

Key-Value-Pair Structure Key-Value-Pair is a flexible structure that carries key/value pairs in which the key is a variable-length integer and the value is either a variable-length integer or a byte field of arbitrary length. Key-Value-Pairs encode a Type value as a delta from the previous Type value, or from 0 if there is no previous Type value. This is efficient on the wire and makes it easy to ensure there is only one instance of a type when needed. The previous Type value plus the Delta Type MUST NOT be greater than 2^64 - 1. If a Delta Type is received that would be too large, the Session MUST be closed with a PROTOCOL_VIOLATION. Key-Value-Pair is used in both the data plane and control plane, but is optimized for use in the data plane.

MOQT Key-Value-Pair

Delta Type: an unsigned variable-length integer identifying the Type as a delta encoded value from the previous Type, if any. The Type identifies the type of value and also the subsequent serialization.
Length: Only present when Type is odd. Specifies the length of the Value field in bytes. The maximum length of a value is 2^16-1 bytes. If an endpoint receives a length larger than the maximum, it MUST close the session with a PROTOCOL_VIOLATION.
Value: A single variable-length integer when Type is even, otherwise a sequence of Length bytes.

If a receiver understands a Type, and the following Value or Length/Value does not match the serialization defined by that Type, the receiver MUST close the session with error code KEY_VALUE_FORMATTING_ERROR. Key-Value-Pairs are always parsed with a known byte length, which bounds the sequence. The source of this length varies by context.

Track and Object Properties Tracks and Objects can have additional relay-visible fields, known as Properties, which do not require negotiation, and can be used to alter MOQT Object distribution. Properties are defined in as well as external specifications and are registered in an IANA table . These specifications define the type and value of the property, along with any rules concerning processing, modification, caching and forwarding. If a Relay does not support a Property, it MUST NOT be modified, MUST be forwarded, and MUST be cached with the Track or Object, unless it is a Mandatory Track Property as described in . If a Track or Object arrives with a different set of unknown properties than previously cached, the most recent set SHOULD replace any cached values, removing any unknown values not present in the new set. Relays MUST NOT attempt to merge sets of unknown properties received in different messages. If a Relay supports a Property, it MUST follow the processing rules in the Property's definition. Unless those rules permit otherwise, a Relay MUST NOT modify, add, or remove the Property; it MUST forward the Property to downstream subscribers and MUST cache it with the Track or Object if the Track or Object is cached. Properties are serialized as Key-Value-Pairs (see ). Track Properties always appear as the final field in the messages that carry them; their length is the remaining bytes of the message after all preceding fields have been consumed. Object Properties () are preceded by an explicit length field. Property types are registered in the IANA table 'MOQ Properties'. See . Certain Property type ranges are reserved for application-specific use and will never be allocated by IANA in future MOQT specifications:

0x78 to 0x7F (1-byte encoding): 8 code points for applications with tight space constraints
0x3800 to 0x3FFF (2-byte encoding): 2048 code points (including grease ) for applications with moderate space constraints

Applications MAY use code points in these ranges without registration for format-specific metadata or other application-defined purposes. Relays that do not understand the application format MUST forward these properties unchanged but MUST NOT attempt to interpret their semantic meaning. Different applications using the same code point in these ranges may assign different meanings; the interpretation depends on the track or application context known to the publisher and subscriber.

Reason Phrase Structure Reason Phrase provides a way for the sender to encode additional diagnostic information about an error condition, where appropriate.

Reason Phrase Length: A variable-length integer specifying the length of the reason phrase in bytes. The reason phrase length has a maximum value of 1024 bytes. If an endpoint receives a length exceeding the maximum, it MUST close the session with a PROTOCOL_VIOLATION
Reason Phrase Value: Additional diagnostic information about an error condition. The reason phrase value is encoded as UTF-8 string and does not carry information, such as language tags, that would aid comprehension by any entity other than the one that created the text.

Range Filter Structure Each Range Filter parameter (see ) carries a sequence of Ranges, encoded as follows: Length (vi64) is the byte count of all fields after itself. When Length is 0, there is no filter and no further fields are present. This can be used in REQUEST_UPDATE to remove a filter. The Object Property and Track Property Filters include a Property Type (vi64) which follows SetID. Each Range is an inclusive Start/End pair. End is optional in the last pair; if omitted it indicates the last Range is open-ended. Each Start is delta encoded from the prior Range's End (or from 0 for the first Range), and End is delta encoded from its own Start. If adding the delta would exceed 2^64-1, the request MUST be rejected with INVALID_FILTER. For example, ranges 3-5 and 10-15 encode as: Start=3, End=2, Start=5, End=5.

Track Namespace Structure Track Namespace () is encoded as follows:

Number of Track Namespace Fields: A variable-length integer specifying the number of Track Namespace Fields in the Track Namespace.

Each Track Namespace Field is encoded as follows:

Track Namespace Field Length: A variable-length integer specifying the length of the Track Namespace Field in bytes.
Track Namespace Field Value: A sequence of bytes that forms a Track Namespace Field.

Each Track Namespace Field Value MUST contain at least one byte. If an endpoint receives a Track Namespace Field with a Track Namespace Field Length of 0, it MUST close the session with a PROTOCOL_VIOLATION. If an endpoint receives a Track Namespace consisting of greater than 32 Track Namespace Fields, it MUST close the session with a PROTOCOL_VIOLATION. The maximum total length of a Full Track Name is 4,096 bytes. The length of a Full Track Name is computed as the sum of the Track Namespace Field Length fields and the Track Name Length field. The length of a Track Namespace is the sum of the Track Namespace Field Length fields. If an endpoint receives a Track Namespace or a Full Track Name exceeding 4,096 bytes, it MUST close the session with a PROTOCOL_VIOLATION.

Representing Namespace and Track Names There is often a need to render namespace tuples and track names for purposes such as logging, representing track filenames, or use in certain authorization verification schemes. The namespace and track name are binary and need to be converted to a safe form. The following format is RECOMMENDED:

Each of the namespace tuples are rendered in order with a hyphen (-) between them followed by the track name with a double hyphen (--) between the last namespace and track name.
Bytes in the range a-z, A-Z, 0-9 as well as _ (0x5f) are output verbatim, while all other bytes are encoded as a period (.) symbol followed by exactly two lowercase hexadecimal digits.

This format allows many common names to be rendered in an easily human readable form while still supporting binary values. Note that while the character set is chosen to be generally both filename and URL safe, filename safety is platform specific; for instance, on case-insensitive filesystems, track names can collide.

Parsing Serialized Names When parsing a serialized namespace or track name back to its binary form, implementations MUST apply the following rules to ensure a canonical encoding:

A period (.) MUST be followed by exactly two hexadecimal digits. A trailing period or a period followed by fewer than two hexadecimal digits is invalid.
The hexadecimal digits following a period (.) MUST be lowercase (a-f). Uppercase hexadecimal digits (A-F) are invalid and MUST cause parsing to fail.
Bytes that can be represented literally (a-z, A-Z, 0-9, _) MUST NOT appear in their hex-encoded form. For example, .61 is invalid because a must be represented as the literal character a. A parser MUST reject such redundant encodings.

These rules ensure that the encoding is bijective: every binary value has exactly one valid serialized representation, and every valid serialized string maps to exactly one binary value. This property simplifies comparison of serialized names without requiring full deserialization. Implementations that receive an invalid serialized name SHOULD treat it as an error. The specific error handling behavior is application-defined. Example:

Authorization Token Compression Authorization tokens are carried in the AUTHORIZATION TOKEN message parameter (see ) and the AUTHORIZATION TOKEN Setup Option (see ). Both use the wire format and semantics defined in this section. The value is a Token structure containing an optional Session-specific Alias. The Alias allows the sender to reference a previously transmitted Token Type and Token Value in future messages. The Token structure is serialized as follows:

Token structure

Alias Type - an integer defining both the serialization and the processing behavior of the receiver. This Alias type has the following code points:

DELETE (0x0):: There is an Alias but no Type or Value. This Alias and the Token Value it was previously associated with MUST be retired. Retiring removes them from the pool of actively registered tokens.
REGISTER (0x1):: There is an Alias, a Type and a Value. This Alias MUST be associated with the Token Value for the duration of the Session or it is deleted. This action is termed "registering" the Token.
USE_ALIAS (0x2):: There is an Alias but no Type or Value. Use the Token Type and Value previously registered with this Alias.
USE_VALUE (0x3):: There is no Alias and there is a Type and Value. Use the Token Value as provided. The Token Value MAY be discarded after processing.

Token Alias - a Session-specific integer identifier that references a Token Type and Token Value. There are separate Alias spaces for the client and server (e.g.: they can each register Alias=1). Once a Token Alias has been registered, it cannot be re-registered by the same endpoint in the Session without first being deleted. Use of the Token Alias is optional.
Token Type - a numeric identifier for the type of Token payload being transmitted. This type is defined by the IANA table "MOQT Auth Token Type" (see ). Type 0 is reserved to indicate that the type is not defined in the table and is negotiated out-of-band between client and receiver.
Token Value - the payload of the Token. The contents and serialization of this payload are defined by the Token Type.

If the Token structure cannot be decoded, the receiver MUST close the Session with KEY_VALUE_FORMATTING_ERROR. The receiver of a message attempting to register an Alias which is already registered MUST close the Session with DUPLICATE_AUTH_TOKEN_ALIAS. The receiver of a message referencing an Alias that is not currently registered MUST reject the message with UNKNOWN_AUTH_TOKEN_ALIAS. The receiver of a message containing a well-formed Token structure that is otherwise invalid MUST reject that message with an MALFORMED_AUTH_TOKEN error. The receiver of a message carrying an Authorization Token with Alias Type REGISTER that does not result in a Session error MUST register the Token Alias in the token cache, even if the message fails for other reasons, including Unauthorized. This allows senders to pipeline messages that refer to previously registered tokens without potentially terminating the entire Session. A receiver MAY store an error code (eg: UNAUTHORIZED or MALFORMED_AUTH_TOKEN) in place of the Token Type and Token Alias if any future message referencing the Token Alias will result in that error. However, it is important to not store an error code for a token that might be valid in the future or due to some other property becoming fulfilled which currently isn't. The size of a registered cache entry includes the length of the Token Value, regardless of whether it is stored. If a receiver detects that an authorization token has expired, it MUST retain the registered Alias until it is deleted by the sender, though it MAY discard other state associated with the token that is no longer needed. Expiration does not affect the size occupied by a token in the token cache. Any message that references an expired token with Alias Type USE_ALIAS fails with EXPIRED_AUTH_TOKEN. Using an Alias to refer to a previously registered Token Type and Value is for efficiency only and has the same effect as if the Token Type and Value was included directly. Retiring an Alias that was previously used to authorize a message has no retroactive effect on the original authorization, nor does it prevent that same Token Type and Value from being re-registered. Senders of tokens SHOULD only register tokens which they intend to re-use during the Session and SHOULD retire previously registered tokens once their utility has passed. By registering a Token, the sender is requiring the receiver to store the Token Alias and Token Value until they are deleted, or the Session ends. The receiver can protect its resources by sending a Setup Option defining the MAX_AUTH_TOKEN_CACHE_SIZE limit (see ) it is willing to accept. If a registration is attempted which would cause this limit to be exceeded, the receiver MUST terminate the Session with a AUTH_TOKEN_CACHE_OVERFLOW error. An Authorization Token MAY be repeated within a message as long as the combination of Token Type and Token Value are unique after resolving any aliases. Messages carrying an Authorization Token can appear on different control streams. Because stream processing order can be different than send order, the receiver and sender can have inconsistent views of the token cache state. Senders MUST NOT send USE_ALIAS on one control stream for an alias registered on a different stream until the sender has received a response to the message containing the REGISTER. Senders MAY use USE_ALIAS on the same control stream as the REGISTER without waiting for a response. Senders MUST NOT send DELETE for an alias while any message using USE_ALIAS with that alias has not received a response.

Control Messages MOQT uses a pair of unidirectional streams to exchange control messages, as defined in . Every message on a control or request stream is formatted as follows:

MOQT Control Message The following Message Types are defined. The Stream column indicates which stream type each message is sent on: Control indicates the control stream (), and Request indicates a bidirectional request stream. Messages marked "First" MUST be the first message on a new request stream.

ID	Messages	Stream
0x01	RESERVED (SETUP for version 00)
0x40	RESERVED (CLIENT_SETUP for <= 10)
0x41	RESERVED (SERVER_SETUP for <= 10)
0x20	RESERVED (CLIENT_SETUP in <= 16)
0x21	RESERVED (SERVER_SETUP in <= 16)
0x2F00	SETUP ()	Control
0x10	GOAWAY ()	Control, Request
0x3	SUBSCRIBE ()	Request, First
0x4	SUBSCRIBE_OK ()	Request
0x22	PUBLISH_STATE_NOTIFY ()	Request
0x1D	PUBLISH ()	Request, First
0x1E	RESERVED (PUBLISH_OK in <= 17)	Request
0xB	PUBLISH_DONE ()	Request
0x16	FETCH ()	Request, First
0x18	FETCH_OK ()	Request
0xD	TRACK_STATUS ()	Request, First
0x6	PUBLISH_NAMESPACE ()	Request, First
0x50	SUBSCRIBE_NAMESPACE ()	Request, First
0x51	SUBSCRIBE_TRACKS ()	Request, First
0x8	NAMESPACE ()	Request
0xE	NAMESPACE_DONE ()	Request
0xF	PUBLISH_SKIPPED ()	Request
0x2	REQUEST_UPDATE ()	Request
0x7	REQUEST_OK ()	Request
0x5	REQUEST_ERROR ()	Request

An endpoint that receives an unknown message type MUST close the session. Control messages have a length to simplify parsing, but no control messages are intended to be ignored. The length is set to the number of bytes in the Message Body, which is defined by each message type. If the length does not match the length of the Message Body, the receiver MUST close the session with a PROTOCOL_VIOLATION.

SETUP The SETUP message is the first message each endpoint sends on its control stream (see ); it allows the endpoints to agree on the initial configuration before any other control messages are exchanged. An endpoint that is not offering extensions which modify control message semantics MAY pipeline other control messages after SETUP without waiting for the peer's SETUP. The messages contain a sequence of key-value pairs called Setup Options; the semantics and format of which can vary based on whether the client or server is sending. To ensure future extensibility of MOQT, endpoints MUST ignore unknown Setup Options. The wire format of the Setup message is as follows:

MOQT SETUP Message Setup Options are serialized as Key-Value-Pairs , spanning the entire message payload, bounded by the message Length field. Setup Options use a namespace that is constant across all MOQT versions, separate from Message Parameters. Receivers MUST ignore unrecognized Setup Options. Senders MUST NOT repeat the same Option Type in a message unless the option definition explicitly allows multiple instances. Receivers MUST allow duplicates of unknown Setup Options. The available Setup Options are detailed in the next sections.

AUTHORITY The AUTHORITY option (Option Type 0x05) allows the client to specify the authority component of the MoQ URI when using native QUIC (). It MUST NOT be used by the server, or when WebTransport is used. When an AUTHORITY option is received from a server, or when an AUTHORITY option is received while WebTransport is used, or when an AUTHORITY option is received by a server but the server does not support the specified authority, the session MUST be closed with INVALID_AUTHORITY. The AUTHORITY option follows the URI formatting rules . When connecting to a server using a URI with the "moqt" scheme, the client MUST set the AUTHORITY option to the authority portion of the URI. If an AUTHORITY option does not conform to these rules, the session MUST be closed with MALFORMED_AUTHORITY.

PATH The PATH option (Option Type 0x01) allows the client to specify the path of the MoQ URI when using native QUIC (). It MUST NOT be used by the server, or when WebTransport is used. When a PATH setup option is received from a server, or when a PATH parameter is received while WebTransport is used, or when a PATH parameter is received by a server but the server does not support the specified path, the session MUST be closed with INVALID_PATH. The PATH option follows the URI formatting rules . When connecting to a server using a URI with the "moqt" scheme, the client MUST set the PATH option to the path-abempty portion of the URI; if query is present, the client MUST concatenate ?, followed by the query portion of the URI to the option. If a PATH does not conform to these rules, the session MUST be closed with MALFORMED_PATH.

MAX_AUTH_TOKEN_CACHE_SIZE The MAX_AUTH_TOKEN_CACHE_SIZE option (Option Type 0x04) communicates the maximum size in bytes of all actively registered Authorization tokens that the endpoint is willing to store per Session. This option is optional. The default value is 0 which prohibits the use of token Aliases. The token size is calculated as 16 bytes + the size of the Token Value field (see ). The total size as restricted by the MAX_AUTH_TOKEN_CACHE_SIZE option is calculated as the sum of the token sizes for all registered tokens (Alias Type value of 0x01) minus the sum of the token sizes for all deregistered tokens (Alias Type value of 0x00), since Session initiation.

AUTHORIZATION TOKEN The AUTHORIZATION TOKEN Setup Option (Option Type 0x03) is functionally equivalent to the AUTHORIZATION TOKEN message parameter, see . The endpoint can specify one or more tokens in SETUP that the peer can use to authorize MOQT session establishment. The option value is a Token structure, whose wire format and semantics are defined in . If a server receives Alias Type DELETE (0x0) or USE_ALIAS (0x2) in a SETUP message, it MUST close the session with a PROTOCOL_VIOLATION. If an endpoint receives an AUTHORIZATION TOKEN option in SETUP with Alias Type REGISTER that exceeds its MAX_AUTH_TOKEN_CACHE_SIZE, it MUST NOT fail the session with AUTH_TOKEN_CACHE_OVERFLOW. Instead, it MUST treat the option as Alias Type USE_VALUE. Since each endpoint's SETUP may be sent before the peer's SETUP is received, the sender MUST handle registration failures of this kind by purging any Token Aliases that failed to register based on the peer's MAX_AUTH_TOKEN_CACHE_SIZE option in SETUP (or the default value of 0).

MOQT IMPLEMENTATION The MOQT_IMPLEMENTATION option (Option Type 0x07) identifies the name and version of the sender's MOQT implementation. This SHOULD be a UTF-8 encoded string , though the message does not carry information, such as language tags, that would aid comprehension by any entity other than the one that created the text. An endpoint SHOULD send a MOQT_IMPLEMENTATION option unless specifically configured not to do so. This option helps identify the scope of interoperability problems and work around implementation-specific limitations. Senders SHOULD limit the value to the implementation name and version, avoiding advertising or other nonessential information. Implementations SHOULD NOT use the identifiers of other implementations to declare compatibility, as this undermines the usefulness of implementation identification for debugging.

MAX FILTER RANGES The MAX_FILTER_RANGES option (Type 0x06) limits the peer's total number of Ranges (Start/End pairs) allowed concurrently in all Range filter parameters for a given subscription or fetch. The default value is 0, so if not specified, the peer MUST NOT send any such filter parameters. If this limit is exceeded, an endpoint MUST reject this with REQUEST_ERROR with error code INVALID_FILTER.

MAX_REQUEST_UPDATES The MAX_REQUEST_UPDATES option (Option Type 0x08) communicates the maximum number of unacknowledged REQUEST_UPDATE messages per request stream that the endpoint is willing to receive. A REQUEST_UPDATE is considered outstanding from when it is sent until the sender receives the corresponding REQUEST_OK or REQUEST_ERROR response. The sender MUST NOT have more than MAX_REQUEST_UPDATES outstanding REQUEST_UPDATEs on any single request stream at a time. Each REQUEST_OK or REQUEST_ERROR response restores one credit on that stream. An implementation that processes and responds to a REQUEST_UPDATE immediately might not detect when a peer has pipelined messages exceeding its limit; coalescing REQUEST_UPDATE processing (see ) can be more effective at enforcing MAX_REQUEST_UPDATES. The value is encoded as a variable-length integer. A value of 0 means the endpoint does not limit REQUEST_UPDATE concurrency. If not present, the default value is 0. If an endpoint receives a REQUEST_UPDATE on a stream that already has MAX_REQUEST_UPDATES outstanding REQUEST_UPDATEs, it MUST close the session with TOO_MANY_REQUEST_UPDATES.

GOAWAY An endpoint sends a GOAWAY message on its control stream to inform the peer it intends to close the session soon. When sent by a server, it can initiate session migration () with an optional URI. A client MUST send a zero-length New Session URI in any GOAWAY, as clients cannot instruct servers to initiate connections. A GOAWAY MAY also be sent on a request stream to initiate migration of that individual request. Upon receiving a GOAWAY on a request stream, the endpoint SHOULD re-issue that specific request on a session at the specified URI (or the current session if no URI is provided), and close the old request stream using the appropriate mechanism (e.g. FIN, stream reset, or PUBLISH_DONE). This allows, for example, moving the publishers and subscribers of a common set of tracks to a common relay without draining their entire session. The GOAWAY message does not impact subscription state. A subscriber SHOULD individually unsubscribe from each existing subscription, while a publisher MAY reject new requests after sending a GOAWAY. Upon receiving a GOAWAY on the control stream, an endpoint SHOULD NOT initiate new requests to the peer including SUBSCRIBE, PUBLISH, FETCH, PUBLISH_NAMESPACE, SUBSCRIBE_NAMESPACE, SUBSCRIBE_TRACKS and TRACK_STATUS. Sending a GOAWAY does not prevent the sender from initiating new requests, though the sender SHOULD avoid initiating requests unless required by migration (see ( and ). An endpoint that receives a GOAWAY MAY reject new requests with an appropriate error code (e.g., REQUEST_ERROR with error code GOING_AWAY). The endpoint MUST close the session with a PROTOCOL_VIOLATION () if it receives more than one GOAWAY on the control stream or on a single request stream.

MOQT GOAWAY Message

New Session URI: When received by a client, indicates where the client can connect to continue this session or re-issue this request. The client MUST use this URI for the new session if provided. If the URI is zero bytes long, the current URI is reused instead. The new session URI SHOULD use the same scheme as the current URI to ensure compatibility. The maximum length of the New Session URI is 8,192 bytes. If an endpoint receives a length exceeding the maximum, it MUST close the session with a PROTOCOL_VIOLATION. If a server receives a GOAWAY with a non-zero New Session URI Length it MUST close the session with a PROTOCOL_VIOLATION.
Timeout: The time in milliseconds the sender will wait for graceful closure. When sent on the control stream, the sender closes the session with GOAWAY_TIMEOUT after the indicated timeout if there are still open requests. When sent on a request stream, the sender SHOULD reset the stream with GOING_AWAY after the indicated timeout. A value of 0 indicates the sender has no specific timeout, but the recipient SHOULD migrate as quickly as possible. This is a hint; the sender of the GOAWAY MAY close the session or reset the request stream before the indicated timeout has elapsed.

REQUEST_OK The REQUEST_OK message is sent in response to PUBLISH, REQUEST_UPDATE, TRACK_STATUS, SUBSCRIBE_NAMESPACE, SUBSCRIBE_TRACKS and PUBLISH_NAMESPACE requests. This document uses the shorthand PUBLISH_OK, REQUEST_UPDATE_OK, TRACK_STATUS_OK, SUBSCRIBE_NAMESPACE_OK, SUBSCRIBE_TRACKS_OK and PUBLISH_NAMESPACE_OK to refer to a REQUEST_OK sent in response to the corresponding request type.

MOQT REQUEST_OK Message

Parameters: The parameters are defined in .
Track Properties : A sequence of Properties. See . The length of Track Properties is the remaining length of the message after parsing all previous fields. Track Properties are populated in TRACK_STATUS_OK; they are empty in PUBLISH_OK, REQUEST_UPDATE_OK, SUBSCRIBE_NAMESPACE_OK and PUBLISH_NAMESPACE_OK. If an endpoint receives Track Properties in one of these messages it MUST close the session with a PROTOCOL_VIOLATION.

REQUEST_ERROR The REQUEST_ERROR message is sent in response to any request (SUBSCRIBE, FETCH, PUBLISH, SUBSCRIBE_NAMESPACE, SUBSCRIBE_TRACKS, PUBLISH_NAMESPACE, TRACK_STATUS, REQUEST_UPDATE).

Redirect Structure A Redirect provides a way for an endpoint to direct the peer to retry a request at a different URI and/or for a different Full Track Name.

Connect URI: The URI to connect to for the redirected request. If the length is zero, the requester SHOULD use the current session's URI. If a server receives a Redirect with a non-zero Connect URI Length it MUST close the session with a PROTOCOL_VIOLATION.
Track Namespace and Track Name: The Track Namespace and Track Name to use for the redirected request, together referred to as the Redirect target. Track Name is not meaningful for namespace-scoped requests (SUBSCRIBE_NAMESPACE, PUBLISH_NAMESPACE, SUBSCRIBE_TRACKS) and MUST be empty; an endpoint that receives a non-empty Track Name in a Redirect for a namespace-scoped request MUST close the session with a PROTOCOL_VIOLATION.

REQUEST_ERROR Message Format

MOQT REQUEST_ERROR Message

Error Code: Identifies an integer error code for request failure.
Retry Interval: The minimum time (in milliseconds) before the request SHOULD be sent again, plus one. If the value is 0, the request SHOULD NOT be retried.
Error Reason: Provides a text description of the request error. See .
Redirect: Present only when Error Code is REDIRECT. See .

If a request is retryable with the same parameters at a later time, the sender of REQUEST_ERROR includes a non-zero Retry Interval in the message. To minimize the risk of synchronized retry storms, the sender can apply randomization to each retry interval so that retries are spread out over time. A Retry Interval value of 1 indicates the request can be retried immediately. The error codes used in REQUEST_ERROR are defined in .

REQUEST_UPDATE The sender of a request (SUBSCRIBE, PUBLISH, FETCH, PUBLISH_NAMESPACE, SUBSCRIBE_NAMESPACE, SUBSCRIBE_TRACKS) can later send a REQUEST_UPDATE on the same bidi stream as the request to modify it. A subscriber can also send REQUEST_UPDATE to modify parameters of a subscription established with PUBLISH. An endpoint that receives a REQUEST_UPDATE other than in the two cases above MUST close the session with a PROTOCOL_VIOLATION. The receiver of a REQUEST_UPDATE MUST respond with exactly one REQUEST_OK or REQUEST_ERROR message indicating if the update was successful, unless it is coalescing failed updates to produce just one REQUEST_ERROR for multiple REQUEST_UPDATE messages. The number of outstanding REQUEST_UPDATEs on a single request stream is limited by the MAX_REQUEST_UPDATES Setup Option (). If a parameter previously set on the request is not present in REQUEST_UPDATE, its value remains unchanged. There is no mechanism to remove a parameter from a request. The format of REQUEST_UPDATE is as follows:

MOQT REQUEST_UPDATE Message

Request ID: See .
Parameters: The parameters are defined in .

Updating Subscriptions When a subscriber decreases the Start Location of the Location Filter (see ), the Start Location can be smaller than the Track's Largest Location, similar to a new Subscription. Including FILL_PARAMETERS (see ) in the REQUEST_UPDATE causes the publisher to deliver the new fill range by opening a new fill fetch stream (see ). FETCH can also be used to retrieve any necessary Objects smaller than the current Largest Location. When a subscriber increases the End Location, the Largest Object at the publisher might already be larger than the previous End Location. This will create a gap in the subscription. The REQUEST_UPDATE_OK will include the LARGEST_OBJECT parameter, and the subscriber can issue a FETCH to retrieve the omitted Objects, if any. When a subscriber narrows their subscription (increase the Start Location and/or decrease the End Group), it might still receive Objects outside the new range if the publisher sent them before the update was processed. When a REQUEST_UPDATE is unsuccessful, the publisher MUST also terminate the subscription by sending a PUBLISH_DONE with error code UPDATE_FAILED. When a REQUEST_UPDATE fails for a FETCH, the publisher MUST reset the FETCH data stream. When a REQUEST_UPDATE fails for a SUBSCRIBE_NAMESPACE, SUBSCRIBE_TRACKS or PUBLISH_NAMESPACE, the responder MUST close the bidi stream (see ). A receiver of multiple REQUEST_UPDATE messages on the same stream MAY coalesce their processing by applying only the cumulative result. Parameter values from later REQUEST_UPDATE messages override values from earlier ones. The receiver MUST still send a REQUEST_OK for each successful update, but it is not required to process intermediate states individually. If the coalesced REQUEST_UPDATE results in REQUEST_ERROR, only a single REQUEST_ERROR will be sent and the sender of the REQUEST_UPDATEs will not always be able to determine which caused an error.

Updating Namespace Subscriptions A subscriber can update the Track Namespace Prefix of an established SUBSCRIBE_NAMESPACE or SUBSCRIBE_TRACKS by including the TRACK_NAMESPACE_PREFIX parameter () in a REQUEST_UPDATE. The overlap restriction applies independently per type: the new prefix MUST NOT share a common prefix with any other active SUBSCRIBE_NAMESPACE (for a SUBSCRIBE_NAMESPACE update) or SUBSCRIBE_TRACKS (for a SUBSCRIBE_TRACKS update) in the same session. If the update is accepted, NAMESPACE and NAMESPACE_DONE messages following the REQUEST_OK will contain Track Namespace suffixes relative to the updated prefix. Updating the prefix of a SUBSCRIBE_TRACKS has no effect on existing subscriptions. If the subscriber is no longer interested it can cancel the corresponding bidirectional stream.

SUBSCRIBE SUBSCRIBE initiates a subscription to a track. The associated parameters determine the range and mechanism of object delivery; the Location Filter (see ) selects which Objects are sent, and a FILL_PARAMETERS parameter (see ) additionally retrieves the fill range on a fill fetch stream (see ). The format of SUBSCRIBE is as follows:

MOQT SUBSCRIBE Message

Request ID: See .
Track Namespace: Identifies the namespace of the track as defined in ().
Track Name: Identifies the track name as defined in ().
Parameters: The parameters are defined in .

On successful subscription, the publisher MUST reply with a SUBSCRIBE_OK, allowing the subscriber to determine the start group/object when not explicitly specified, and start sending objects.

SUBSCRIBE_OK A publisher sends a SUBSCRIBE_OK as the first response message on the bidi stream for successful subscriptions.

MOQT SUBSCRIBE_OK Message

Track Alias: The identifer used for this track in Subgroups or Datagrams (see ).
Parameters: The parameters are defined in .
Track Properties : A sequence of Properties. See .

PUBLISH The publisher sends PUBLISH as the first message on a new bidirectional stream to initiate a subscription for a Track. The receiver verifies the publisher is authorized to publish this track.

MOQT PUBLISH Message

Request ID: See .
Track Namespace: Identifies a track's namespace as defined in ()
Track Name: Identifies the track name as defined in ().
Track Alias: The identifer used for this track in Subgroups or Datagrams (see ).
Parameters: The parameters are defined in . Parameters such as FORWARD, GROUP_ORDER, SUBSCRIBER_PRIORITY, SUBGROUP_DELIVERY_TIMEOUT, OBJECT_DELIVERY_TIMEOUT, and LOCATION FILTER can appear in the Parameters of a PUBLISH to inform the Subscriber of the initial Subscription parameters. If the PUBLISH is the result of a SUBSCRIBE_TRACKS, the parameters are handled as described in , otherwise, they represent the publisher's initial settings for the subscription, which the subscriber can change.
Track Properties : A sequence of Properties. See .

A subscriber receiving a PUBLISH for a Track it does not wish to receive SHOULD send REQUEST_ERROR with error code UNINTERESTED, and abandon reading any publisher initiated streams associated with that subscription using a STOP_SENDING frame. A publisher that sends the FORWARD parameter () equal to 0 indicates that it will not transmit any objects until the subscriber sets the Forward State to 1. If the FORWARD parameter is omitted or equal to 1, the publisher will start transmitting objects immediately, possibly before PUBLISH_OK. Delivery starts at the Next Object relative to the Largest Object at the time the publisher begins sending.

PUBLISH_DONE A publisher sends a PUBLISH_DONE message as the final message before closing the subscription's bidi stream to indicate it is done publishing Objects for that subscription. The Status Code indicates why the subscription ended, and whether it was an error. Because PUBLISH_DONE is sent on a request stream, it is likely to arrive at the receiver before late-arriving objects, and often even late-opening streams. However, the receiver uses it as an indication that it should receive any late-opening streams in a relatively short time. Note that some objects in the subscribed track might never be delivered, because a stream was reset, or never opened in the first place, due to the delivery timeouts (see ). A sender MUST NOT send PUBLISH_DONE until it has closed all streams it will ever open, and has no further datagrams to send, for a subscription. After sending PUBLISH_DONE, the sender can immediately destroy subscription state, although stream state can persist until delivery completes. The sender might persist subscription state to enforce the subgroup delivery timeout. A sender MUST NOT destroy subscription state until it sends PUBLISH_DONE, though it can choose to stop sending objects (and thus send PUBLISH_DONE) for any reason. A subscriber that receives PUBLISH_DONE SHOULD set a timer of at least the larger of SUBGROUP_DELIVERY_TIMEOUT or OBJECT_DELIVERY_TIMEOUT in case some objects are still inbound due to prioritization or packet loss. The subscriber MAY dispense with a timer if it unsubscribed or is otherwise no longer interested in objects from the track. Once the timer has expired, the receiver destroys subscription state once all open streams for the subscription have closed. A subscriber MAY discard subscription state earlier, at the cost of potentially not delivering some late objects to the application. The subscriber SHOULD send STOP_SENDING on all streams related to the subscription when it deletes subscription state. The format of PUBLISH_DONE is as follows:

MOQT PUBLISH_DONE Message

Status Code: An integer status code indicating why the subscription ended.
Stream Count: An integer indicating the number of data streams the publisher opened for this subscription, including streams that contained no Objects (e.g., an empty Subgroup) and including any fill fetch streams (see ). This helps the subscriber know if it has received all of the data published in this subscription by comparing the number of streams received. The subscriber can immediately remove all subscription state once the same number of streams have been processed. If the publisher did not open any streams for this subscription, the publisher MUST set Stream Count to 0. If the publisher is unable to set Stream Count to the exact number of streams opened for the subscription, it MUST set Stream Count to 2^64 - 1. Subscribers SHOULD use a timeout or other mechanism to remove subscription state in case the publisher set an incorrect value, reset a stream before the SUBGROUP_HEADER, or set the maximum value. If a subscriber receives more streams for a subscription than specified in Stream Count, it MAY close the session with a PROTOCOL_VIOLATION.
Error Reason: Provides the reason for subscription error. See .

The status codes used in PUBLISH_DONE are defined in .

PUBLISH_STATE_NOTIFY A publisher sends PUBLISH_STATE_NOTIFY on a subscription's bidirectional stream to notify the subscriber that the state of the subscription has changed for a reason other than a subscriber sent REQUEST_UPDATE. Unlike REQUEST_UPDATE (), it is a unilateral notification: the receiver does not respond with REQUEST_OK or REQUEST_ERROR, and the message is not subject to the MAX_REQUEST_UPDATES limit (). PUBLISH_STATE_NOTIFY applies only to subscriptions, and is sent only by the publisher. An endpoint that receives a PUBLISH_STATE_NOTIFY for any other request type, or from the subscriber, MUST close the session with a PROTOCOL_VIOLATION. A PUBLISH_STATE_NOTIFY carries the parameters whose values have changed. If a parameter is not present, its value is unchanged. The semantics of each parameter, including whether it may appear in PUBLISH_STATE_NOTIFY, are defined by the parameter. A publisher MUST NOT use PUBLISH_STATE_NOTIFY to change the value of a subscriber controlled subscription parameter unless the subscriber requested the change. The publisher MUST include the LARGEST_OBJECT parameter (), if known, in PUBLISH_STATE_NOTIFY so the subscriber can determine the point in the Track at which the change took effect. This message is informative and no action is required by the recipient. The format of PUBLISH_STATE_NOTIFY is as follows:

MOQT PUBLISH_STATE_NOTIFY Message

Parameters: The parameters are defined in .

FETCH A subscriber sends FETCH as the first message on a new bidi stream to a publisher to request a range of already published objects within a track. The format of FETCH is as follows:

MOQT FETCH Message

Request ID: See .
Track Namespace: Identifies the namespace of the track as defined in ().
Track Name: Identifies the track name as defined in ().
Parameters: The parameters are defined in .

A publisher responds to a FETCH request with either a FETCH_OK or a REQUEST_ERROR message. The publisher creates a new unidirectional stream that is used to send the Objects. The FETCH_OK or REQUEST_ERROR can come at any time relative to object delivery. The publisher responding to a FETCH is responsible for delivering all available Objects in the requested range in the requested order (see ). The Objects in the response are delivered on a single unidirectional stream. Any gaps in the Group and Object IDs in the response stream indicate objects that do not exist unless filters were requested. For Ascending Group Order this includes ranges between the first requested object and the first object in the stream; between objects in the stream; and between the last object in the stream and the Largest Group/Object indicated in FETCH_OK, so long as the fetch stream is terminated by a FIN. If no Objects exist in the requested range, the publisher opens the unidirectional stream, sends the FETCH_HEADER (see ) and closes the stream with a FIN. A relay that has cached objects from the beginning of the range MAY start sending objects immediately in response to a FETCH. If it encounters an object in the requested range that is not cached and has unknown status, the relay MUST pause subsequent delivery until it has confirmed the object's status upstream. If the upstream FETCH fails, the relay sends a REQUEST_ERROR and can reset the unidirectional stream. It can choose to do so immediately or wait until the cached objects have been delivered before resetting the stream. The Object Forwarding Preference does not apply to fetches. Fetch can include a Location Filter parameter (see ) which specifies an inclusive range of Objects starting at Start Location and ending at End Location. Objects with Locations larger than the Largest Object at the time the request is processed will not be retrieved by a FETCH. If the requested End Location exceeds the Largest Object, the actual end of the FETCH response is indicated in the FETCH_OK End Location. If no Objects have been published for the track or Start Location is greater than the Largest Object () the publisher MUST return REQUEST_ERROR with error code INVALID_RANGE. A publisher MUST send fetched groups in the requested group order, either ascending or descending. Within each group, objects are sent in Object ID order; subgroup ID is not used for ordering. If a Publisher receives a FETCH with a range that includes one or more Objects with unknown status (e.g. a Relay has temporarily lost contact with the Original Publisher and does not have the Object in cache), it can choose to reset the FETCH data stream with UNKNOWN_OBJECT_STATUS (), or indicate the range of unknown Objects and continue serving other known Objects.

FETCH_OK A publisher sends a FETCH_OK as the first message on the bidi stream in response to a successful fetch. A publisher MAY send Objects in response to a FETCH before the FETCH_OK message is sent, but the FETCH_OK MUST NOT be sent until the End Location is known.

MOQT FETCH_OK Message

End Of Track: 1 if all Objects have been published on this Track, and the End Location is the final Object in the Track, 0 if not.
End Location: The end of the range covered by the FETCH response. This is the End Location from the FETCH request Location Filter parameter unless the requested range extends beyond Largest Object at the time the request was processed, or the last Object in the Track. If End Location is smaller than the Start Location in the corresponding FETCH the receiver MUST close the session with a PROTOCOL_VIOLATION.
Parameters: The parameters are defined in .
Track Properties : A sequence of Properties. See .

TRACK_STATUS A potential subscriber sends TRACK_STATUS as the first and only message on a new bidi stream to obtain information about the current status of a given track. The TRACK_STATUS message format is identical to the SUBSCRIBE message (), but subscriber parameters related to Track delivery (e.g. SUBSCRIBER_PRIORITY) are not included. The receiver of a TRACK_STATUS message treats it identically as if it had received a SUBSCRIBE message, except it does not create downstream subscription state or send any Objects. If successful, the publisher responds with a TRACK_STATUS_OK with the same parameters and Track Properties it would have set in a SUBSCRIBE_OK. Track Alias is not used. A publisher responds to a failed TRACK_STATUS with an appropriate REQUEST_ERROR message. The bidi stream is closed with a FIN after TRACK_STATUS_OK or REQUEST_ERROR are sent. Relays without an Established subscription MAY forward TRACK_STATUS to one or more publishers, or MAY initiate a subscription (subject to authorization) as described in to determine the response. The publisher does not send PUBLISH_DONE for this request, and the subscriber cannot send REQUEST_UPDATE.

PUBLISH_NAMESPACE The publisher sends the PUBLISH_NAMESPACE message as the first message on a new bidi stream to advertise that it has tracks available within a Track Namespace. The receiver verifies the publisher is authorized to publish tracks under this namespace.

MOQT PUBLISH_NAMESPACE Message

Request ID: See .
Track Namespace: Identifies a track's namespace as defined in .
Parameters: The parameters are defined in .

SUBSCRIBE_NAMESPACE The subscriber sends a SUBSCRIBE_NAMESPACE control message on a new bidirectional stream to a publisher to request the current set of matching published namespaces, as well as future updates to the set.

MOQT SUBSCRIBE_NAMESPACE Message

Request ID: See .
Track Namespace Prefix: A Track Namespace structure as described in with between 0 and 32 Track Namespace Fields. This prefix is matched against track namespaces known to the publisher. For example, using the serialized format from , if the publisher is a relay that has received PUBLISH_NAMESPACE messages for namespaces example.2ecom-123-100 and example.2ecom-123-200, a SUBSCRIBE_NAMESPACE for example.2ecom-123 would match both. If an endpoint receives a Track Namespace Prefix consisting of greater than 32 Track Namespace Fields, it MUST close the session with a PROTOCOL_VIOLATION.
Parameters: The parameters are defined in .

The publisher will respond with REQUEST_OK or REQUEST_ERROR on the response half of the stream. If the subscriber receives any message other than a REQUEST_OK or a REQUEST_ERROR as the first message on the response half of the stream, then it MUST close the session with a PROTOCOL_VIOLATION. If the SUBSCRIBE_NAMESPACE is successful, the publisher will send matching NAMESPACE messages on the response stream. If it is an error, the stream will be immediately closed via FIN. When there are changes to the namespaces being published and the subscriber is subscribed to them, the publisher sends the corresponding NAMESPACE or NAMESPACE_DONE messages. Within a session, if a publisher receives a SUBSCRIBE_NAMESPACE with a Track Namespace Prefix that shares a common prefix with an established SUBSCRIBE_NAMESPACE, it MUST respond with REQUEST_ERROR with error code PREFIX_OVERLAP. SUBSCRIBE_NAMESPACE and SUBSCRIBE_TRACKS have independent overlap spaces (see ). The publisher MUST ensure the subscriber is authorized to perform this namespace subscription. The publisher MUST NOT send NAMESPACE_DONE for a namespace suffix before the corresponding NAMESPACE. If a subscriber receives a NAMESPACE_DONE before the corresponding NAMESPACE, it MUST close the session with a 'PROTOCOL_VIOLATION'. If the publisher is unable to send NAMESPACE or NAMESPACE_DONE messages in a timely manner because the SUBSCRIBE_NAMESPACE response stream is blocked by flow control, the publisher MAY reset the SUBSCRIBE_NAMESPACE response stream. When a subscriber receives a stream reset or FIN on a SUBSCRIBE_NAMESPACE response stream, it SHOULD treat this as though each active namespace received a NAMESPACE_DONE. Subscriptions established via PUBLISH on separate bidi streams are not affected by closure of the SUBSCRIBE_NAMESPACE stream.

NAMESPACE The NAMESPACE message is similar to the PUBLISH_NAMESPACE message, except it is sent on the response stream of a SUBSCRIBE_NAMESPACE request. All NAMESPACE messages are in response to a SUBSCRIBE_NAMESPACE, so only the namespace tuples after the 'Track Namespace Prefix' are included in the 'Track Namespace Suffix'.

MOQT NAMESPACE Message

Track Namespace Suffix: Specifies the final portion of a track's namespace as defined in after removing namespace tuples included in 'Track Namespace Prefix' .

NAMESPACE_DONE The publisher sends the NAMESPACE_DONE control message to indicate its intent to stop serving new subscriptions for tracks within the provided Track Namespace. All NAMESPACE_DONE messages are in response to a SUBSCRIBE_NAMESPACE, so only the namespace tuples after the 'Track Namespace Prefix' are included in the 'Track Namespace Suffix'.

MOQT NAMESPACE_DONE Message

Track Namespace Suffix: Specifies the final portion of a track's namespace as defined in . The namespace begins with the 'Track Namespace Prefix' specified in .

SUBSCRIBE_TRACKS The subscriber sends a SUBSCRIBE_TRACKS control message on a new bidirectional stream to a publisher to request PUBLISH messages for all tracks within matching namespaces, as well as future track publications within those namespaces.

MOQT SUBSCRIBE_TRACKS Message

Request ID: See .
Track Namespace Prefix: A Track Namespace structure as described in with between 0 and 32 Track Namespace Fields. This prefix is matched against track namespaces known to the publisher. If an endpoint receives a Track Namespace Prefix consisting of greater than 32 Track Namespace Fields, it MUST close the session with a PROTOCOL_VIOLATION.
Parameters: The parameters are defined in , though they are handled differently from the same Parameters on Subscriptions, as outlined below.

Parameters on SUBSCRIBE_TRACKS Any Parameter that can be specified on a Subscription (ie: in SUBSCRIBE) is valid in SUBSCRIBE_TRACKS, unless otherwise specified. These parameters are used by the publisher as the initial Subscription parameters when a PUBLISH is sent as a result of SUBSCRIBE_TRACKS. These Parameters are explicitly communicated in PUBLISH. When omitted by the publisher in PUBLISH, the subscriber uses the default value for each. To join Tracks initiated via the resulting PUBLISHes, the subscriber can specify a Location Filter and optionally include FILL_PARAMETERS, as described in .

PUBLISH_SKIPPED The publisher sends the PUBLISH_SKIPPED control message to indicate it will not send a PUBLISH message to initiate a new Subscription for a Track in the SUBSCRIBE_TRACKS's Track Namespace. All PUBLISH_SKIPPED messages are in response to a SUBSCRIBE_TRACKS, so only the namespace tuples after the 'Track Namespace Prefix' are included in the 'Track Namespace Suffix'.

MOQT PUBLISH_SKIPPED Message

Track Namespace Suffix: Specifies the final portion of a track's namespace as defined in . The namespace begins with the 'Track Namespace Prefix' specified in .
Track Name: Identifies the track name as defined in ().

Control Message Parameters Some control messages include a field that encodes optional Message Parameters. Message Parameters are serialized as follows:

Message Parameter Type Delta: The difference between this Parameter Type and the previous Parameter Type in the message, or the Parameter Type itself for the first parameter. Parameters MUST be serialized in ascending order by Type. If the resulting Type would be greater than 2^64 - 1, the endpoint MUST close the session with a PROTOCOL_VIOLATION.

Value: The encoding is specified by each parameter definition. The encodings defined in this draft are:
- uint8: A single-byte unsigned integer (0-255)
- varint: A variable-length integer
- Location: Two consecutive varints (Group, Object)
- Length-prefixed: A varint length followed by that many bytes

Message Parameters are intended for the peer only and are not forwarded by Relays, though relays can consider received parameter values when making a request. All Message Parameters MUST be defined in the negotiated version of MOQT or negotiated via Setup Options. An endpoint that receives an unknown Message Parameter MUST close the session with PROTOCOL_VIOLATION. Because the receiver has to understand every Message Parameter, there is no need for a mechanism to skip unknown parameters. Because unknown parameters cannot be skipped, the block is bounded by a parameter count rather than a length. The Message Parameter types defined in this version of MOQT are defined in the following subsections. Senders MUST NOT repeat the same Parameter Type in a message unless the parameter definition explicitly allows multiple instances of that type to be sent in a single message. Receivers SHOULD check that there are no unexpected duplicate parameters and close the session with PROTOCOL_VIOLATION if found. The number of Message Parameters is not specifically limited, but the total length of a control message is limited to 2^16-1 bytes. Message Parameters in SUBSCRIBE and FETCH MUST NOT cause the publisher to alter the payload of the objects it sends, as that would violate the track uniqueness guarantee described in .

Parameter Scope Message Parameters are always intended for the peer endpoint only and are not forwarded by Relays, though relays can consider received parameter values when making a request. Track information not specific to the Message or Session is encoded in Track Properties. See . Each Message Parameter definition indicates the message types in which it can appear. If it appears in some other type of message, the receiving endpoint MUST close the connection with a PROTOCOL_VIOLATION. Note that since Setup Options use a separate namespace, it is impossible for Message Parameters to appear in Setup messages.

Allowed Parameters By Control Message

AUTHORIZATION TOKEN Parameter The AUTHORIZATION TOKEN parameter (Parameter Type 0x03) uses Length-prefixed encoding. It MAY appear in a PUBLISH, SUBSCRIBE, REQUEST_UPDATE, SUBSCRIBE_NAMESPACE, SUBSCRIBE_TRACKS, PUBLISH_NAMESPACE, TRACK_STATUS or FETCH message. This parameter conveys information to authorize the sender to perform the operation carrying the parameter. This Parameter MUST NOT be copied from a SUBSCRIBE_TRACKS to the resulting PUBLISH message Parameters. The parameter value is a Token structure, whose wire format and semantics are defined in .

SUBGROUP_DELIVERY_TIMEOUT Parameter The SUBGROUP_DELIVERY_TIMEOUT parameter (Parameter Type 0x06) is a varint. It MAY appear in a SUBSCRIBE, PUBLISH, or REQUEST_UPDATE message. Its semantics are defined in . This parameter is intended to be specific to a subscription, so it SHOULD NOT be forwarded upstream by a relay that intends to serve multiple subscriptions for the same track.

OBJECT_DELIVERY_TIMEOUT Parameter The OBJECT_DELIVERY_TIMEOUT parameter (Parameter Type 0x02) is a varint. It MAY appear in a SUBSCRIBE, PUBLISH, or REQUEST_UPDATE message. Its semantics are defined in . This parameter is intended to be specific to a subscription, so it SHOULD NOT be forwarded upstream by a relay that intends to serve multiple subscriptions for the same track.

FILL TIMEOUT Parameter The FILL_TIMEOUT parameter (Parameter Type 0x0A) MAY appear in a FETCH message, or inside a FILL_PARAMETERS parameter (see ) in a SUBSCRIBE or REQUEST_UPDATE (for a subscription), where it applies to the fill fetch stream. It is the maximum total duration in milliseconds a relay SHOULD spend waiting for upstream sources to provide Objects that are not immediately available before reporting them as Timed-Out gaps in the FETCH response. When a relay encounters Objects within the requested range that are not immediately available and have unknown status, it issues upstream FETCHes to retrieve them. The Fill Timeout represents a total budget for all such upstream FETCHes generated by this request. If the budget is exhausted, the relay reports any remaining unavailable Objects as Timed-Out gaps (End of Timed-Out Range, see ) and continues delivering available Objects in the range. A value of 0 indicates the subscriber only wants Objects that are immediately available; the relay MUST NOT wait for upstream delivery and MUST report any unavailable Objects as Timed-Out gaps. If the Fill Timeout parameter is absent, the relay waits for an implementation specific duration before reporting Timed-Out gaps. If the subscriber specifies a Fill Timeout larger than the relay is willing to wait, the relay MAY use a shorter timeout without informing the subscriber.

RENDEZVOUS TIMEOUT Parameter The RENDEZVOUS_TIMEOUT parameter (Parameter Type 0x04) MAY appear in a SUBSCRIBE message. It is the duration in milliseconds the subscriber is willing to wait for a publisher to become available. This applies when a relay receives a SUBSCRIBE for a Track that has no current publisher. If the RENDEZVOUS_TIMEOUT is present, the relay SHOULD hold the subscription and wait for a publisher to appear, up to the specified duration. The relay does not send SUBSCRIBE_OK until a publisher becomes available. If a publisher becomes available within this time, the relay proceeds with the subscription normally. If the timeout expires without a publisher, the relay SHOULD respond with REQUEST_ERROR with error code TIMEOUT. The relay MAY use a shorter timeout than requested by the subscriber. For example, a relay might limit the maximum rendezvous timeout to protect its resources. A value of 0 indicates the subscriber does not want to wait and expects an immediate response. The relay MUST immediately return REQUEST_ERROR with error code DOES_NOT_EXIST if no publisher is available If RENDEZVOUS_TIMEOUT is absent, the default is 0.

SUBSCRIBER PRIORITY Parameter The SUBSCRIBER_PRIORITY parameter (Parameter Type 0x20) is a uint8. It MAY appear in a SUBSCRIBE, PUBLISH, FETCH, or REQUEST_UPDATE (for a subscription or FETCH). It is an integer expressing the priority of a subscription relative to other subscriptions and fetch responses in the same session. Lower numbers get higher priority. See . If omitted from SUBSCRIBE or FETCH, the publisher uses the value 128.

GROUP ORDER Parameter The GROUP_ORDER parameter (Parameter Type 0x22) is a uint8. It MAY appear in a SUBSCRIBE, PUBLISH, SUBSCRIBE_TRACKS, or FETCH, or inside a FILL_PARAMETERS parameter (see ). Its value indicates how to prioritize Objects from different groups within the same subscription (see ), or how to order Groups in a Fetch response (see ). When it appears inside FILL_PARAMETERS, it governs the fill fetch stream and its ordering relative to subscription-delivered Objects (see ). The allowed values are Ascending (0x1) or Descending (0x2). If an endpoint receives a value outside this range, it MUST close the session with PROTOCOL_VIOLATION. If omitted from SUBSCRIBE or SUBSCRIBE_TRACKS, the publisher's preference from the Track is used. If omitted from FETCH, the receiver uses Ascending (0x1).

LOCATION FILTER Parameter The LOCATION_FILTER parameter (Parameter Type 0x21) MAY appear in a FETCH, SUBSCRIBE, PUBLISH, REQUEST_UPDATE (for a subscription) or PUBLISH_STATE_NOTIFY message. It is a Location Filter (see ). A Location filter parameter has the following length-prefixed structure: Length (in bytes) determines how many optional vi64 fields are present. A length of 0 indicates no filter, for example to remove the filter in REQUEST_UPDATE. * If only one field is present, it is StartGroup. * If only two fields are present, they are StartGroup and StartObject. * If only three fields are present, they are StartGroup, StartObject, and EndGroupDelta. If only StartGroup is present, it is a relative number of groups prior to the Next Group, hence the start Location is {Largest Object.Group + 1 - StartGroup, 0}. For example: * StartGroup=0 will start at the Next Group * StartGroup=1 will start at the current group * StartGroup=2 will start at 1 group prior to the current group * StartGroup=N will start at N-1 groups prior to the current group If only StartGroup and StartObject are present and both 0, the start Location is the Next Object (see ). An open-ended filter that starts at absolute Location {0, 0} is equivalent to unfiltered, so the subscriber need not include a Location filter. If a relative start group results in a computed absolute group less than 0, the computed value is set to 0; if greater than 2^64 - 1, it is set to 2^64 - 1. Otherwise, all fields are absolute. EndGroupDelta is delta encoded from StartGroup, but both the start and end groups are absolute, not relative to Largest Object. If StartGroup + EndGroupDelta exceeds 2^64 - 1, the endpoint MUST close the session with a PROTOCOL_VIOLATION. When EndGroupDelta and EndObject are omitted from a subscription filter, the subscription is open-ended. When they are omitted from a Fetch, the EndGroup and EndObject are Largest Object. When EndObject is omitted, the filter includes all objects in the End Group. If omitted from FETCH or SUBSCRIBE, the fetch or subscription is unfiltered. If omitted from REQUEST_UPDATE or PUBLISH_STATE_NOTIFY, the value is unchanged. When sent in PUBLISH_STATE_NOTIFY, it reports the Location Filter now in effect at the publisher.

SUBGROUP FILTER Parameter The SUBGROUP_FILTER parameter (Type 0x25) selects objects with specified Ranges of Subgroup ID. See and .

OBJECTID FILTER Parameter The OBJECTID_FILTER parameter (Type 0x26) selects objects with specified Ranges of Object ID. See and .

PRIORITY FILTER Parameter The PRIORITY_FILTER parameter (Type 0x27) selects objects with specified Ranges of Publisher Priority. See and . If a decoded value exceeds 255, the endpoint MUST reject this with REQUEST_ERROR with error code INVALID_FILTER since Publisher Priority is an 8-bit field.

OBJECT PROPERTY FILTER Parameter The OBJECT_PROPERTY_FILTER parameter (Type 0x28) selects objects with required Ranges of Property Value for a required Object Property Type which MUST be even, i.e. a single integer value (see ), otherwise the endpoint MUST reject this with REQUEST_ERROR with error code INVALID_FILTER. See and .

TRACK PROPERTY FILTER Parameter The TRACK_PROPERTY_FILTER parameter (Type 0x29) selects tracks with required Ranges of Property Value for a required Track Property Type which MUST be even, i.e. a single integer value (see ), otherwise the endpoint MUST reject this with REQUEST_ERROR with error code INVALID_FILTER. See and .

FILL PARAMETERS Parameter The FILL_PARAMETERS parameter (Parameter Type 0x23) uses length-prefixed encoding. It MAY appear in a SUBSCRIBE or REQUEST_UPDATE (for a subscription) message. Its value is a sequence of Parameters that apply to the fill fetch stream (see ), encoded as if they were Parameters for a separate message (see ). Its presence is what requests a fill fetch stream; a subscription with no FILL_PARAMETERS opens none. The following parameters MAY appear inside FILL_PARAMETERS:

Parameter Type	Parameter Name	Specification
0x0A	FILL_TIMEOUT
0x20	SUBSCRIBER_PRIORITY
0x21	LOCATION_FILTER
0x22	GROUP_ORDER
0x25	SUBGROUP_FILTER
0x26	OBJECTID_FILTER
0x27	PRIORITY_FILTER
0x28	OBJECT_PROPERTY_FILTER

The LOCATION_FILTER inside FILL_PARAMETERS selects the fill range and is evaluated using the rules for a Fetch (see ); it is independent of the subscription's own Location filter. A parameter that is omitted from FILL_PARAMETERS takes the value it has for the subscription; FILL_PARAMETERS therefore carries only the settings that differ. An endpoint that receives a parameter inside FILL_PARAMETERS that is not listed above MUST close the session with PROTOCOL_VIOLATION. The value of FILL_PARAMETERS is a separate parameter scope. Parameters inside it are not considered to appear in the enclosing message for the purposes of , so a Parameter Type MAY appear both in the message and inside FILL_PARAMETERS. FILL_PARAMETERS is not retained as subscription state. It applies only to the message that carries it, so the sticky-parameter rules in do not apply to it.

EXPIRES Parameter The EXPIRES parameter (Parameter Type 0x8) is a varint. It MAY appear in SUBSCRIBE_OK, PUBLISH, PUBLISH_OK, SUBSCRIBE_NAMESPACE_OK, SUBSCRIBE_TRACKS_OK, PUBLISH_NAMESPACE_OK, or REQUEST_UPDATE_OK. It encodes the time in milliseconds after which the sender of the parameter will terminate the subscription. The sender will terminate the subscription using PUBLISH_DONE or by cancelling the request (see ). This value is advisory and the sender can terminate the subscription prior to or after the expiry time. The receiver of the parameter can attempt to extend the subscription by sending a REQUEST_UPDATE with 0 or more updated parameters. If the receiver has one or more updated AUTHORIZATION_TOKENs, it SHOULD include those in the REQUEST_UPDATE. If the extension is granted, the sender includes a new EXPIRES value in REQUEST_UPDATE_OK. Relays that send this parameter and applications that receive it MAY introduce jitter to prevent many endpoints from updating simultaneously. If the EXPIRES parameter is 0 or is not present in a message, the subscription does not expire or expires at an unknown time.

LARGEST OBJECT Parameter The LARGEST_OBJECT parameter (Parameter Type 0x9) is a Location. It MAY appear in SUBSCRIBE_OK, PUBLISH, REQUEST_UPDATE_OK, TRACK_STATUS_OK, or PUBLISH_STATE_NOTIFY. It contains the largest Location (see ) in the Track observed by the sending endpoint (see ). If Objects have been published on this Track the Publisher MUST include this parameter. If omitted from a message, the sending endpoint has not published or received any Objects in the Track. A relay MUST set LARGEST_OBJECT to the largest of the following:

Any LARGEST_OBJECT value received from the upstream publisher in SUBSCRIBE_OK, PUBLISH, or REQUEST_UPDATE_OK
The largest Location of an Object received on an upstream subscription

FORWARD Parameter The FORWARD parameter (Parameter Type 0x10) is a uint8. It MAY appear in SUBSCRIBE, REQUEST_UPDATE (for a subscription or a SUBSCRIBE_TRACKS request), PUBLISH, SUBSCRIBE_TRACKS and PUBLISH_STATE_NOTIFY. It specifies the Forwarding State on affected subscriptions (see ). The allowed values are 0 (don't forward) or 1 (forward). If an endpoint receives a value outside this range, it MUST close the session with PROTOCOL_VIOLATION. In the case of a REQUEST_UPDATE for SUBSCRIBE_TRACKS, it specifies the Forwarding State on future subscriptions that match the prefix. Existing subscriptions are unaffected. If the parameter is omitted from REQUEST_UPDATE or PUBLISH_STATE_NOTIFY, the value for the subscription remains unchanged. If the parameter is omitted from any other message, the default value is 1. When sent in PUBLISH_STATE_NOTIFY, it reports the Forwarding State now in effect at the publisher.

NEW GROUP REQUEST Parameter The NEW_GROUP_REQUEST parameter (Parameter Type 0x32) is a varint. It MAY appear in SUBSCRIBE or REQUEST_UPDATE for a subscription. It represents the largest Group ID in the Track known by the subscriber, plus 1. A value of 0 indicates that the subscriber has no Group information for the Track. A subscriber MUST NOT send this parameter in REQUEST_UPDATE if the Track did not include the DYNAMIC_GROUPS Property with value 1. A subscriber MAY include this parameter in SUBSCRIBE without foreknowledge of support. If the original publisher does not support dynamic Groups, it ignores the parameter in that case. When an Original Publisher that supports dynamic Groups receives a NEW_GROUP_REQUEST with a value of 0 or a value larger than the current Group, it SHOULD end the current Group and begin a new Group as soon as practical. The Original Publisher MAY delay the NEW_GROUP_REQUEST subject to implementation specific concerns, for example, achieving a minimum duration for each Group. The Original Publisher chooses the next Group ID; there are no requirements that it be equal to the NEW_GROUP_REQUEST parameter value. Relay Handling: A relay that receives a NEW_GROUP_REQUEST for a Track without an Established subscription MUST include the NEW_GROUP_REQUEST when subscribing upstream. A relay that receives a NEW_GROUP_REQUEST for an Established subscription with a value of 0 or a value larger than the Largest Group MUST send a REQUEST_UPDATE including the NEW_GROUP_REQUEST to the publisher unless:

The Track does not support dynamic Groups
There is already an outstanding NEW_GROUP_REQUEST from this Relay with a greater or equal value

If a relay receives a NEW_GROUP_REQUEST with a non-zero value less than or equal to the Largest Group, it does not send a NEW_GROUP_REQUEST upstream. After sending a NEW_GROUP_REQUEST upstream, the request is considered outstanding until the Largest Group increases.

TRACK_NAMESPACE_PREFIX Parameter The TRACK_NAMESPACE_PREFIX parameter (Parameter Type 0x34) uses the Track Namespace encoding described in . It MAY appear in REQUEST_UPDATE for a SUBSCRIBE_NAMESPACE or SUBSCRIBE_TRACKS request. It updates the Track Namespace Prefix for that subscription. If the new prefix would share a common prefix with another active subscription of the same type in the same session, the receiver MUST respond with REQUEST_ERROR with error code PREFIX_OVERLAP.

INCLUDE_PROPERTIES Parameter The INCLUDE_PROPERTIES parameter (Parameter Type 0x35) is a uint8. It MAY appear in SUBSCRIBE, TRACK_STATUS, FETCH or SUBSCRIBE_TRACKS. It specifies whether the OK message sent in response includes Track Properties or whether the resulting PUBLISH messages include Track Properties in the case of SUBSCRIBE_TRACKS. If INCLUDE_PROPERTIES is 0, the Track Properties are still present in the message, but they SHOULD be empty. The allowed values are 0 (do not send Properties) or 1 (send Properties), and the default is 1. If an endpoint receives a value outside this range, it MUST close the session with PROTOCOL_VIOLATION.

MOQT Properties The following Properties are defined in MOQT. Each Property specifies whether it can be used with Tracks, Objects, or both. Property types in ranges reserved for application-specific use (0x78-0x7F, 0x3800-0x3FFF) are not defined by MOQT. See for usage guidance.

SUBGROUP_DELIVERY_TIMEOUT SUBGROUP_DELIVERY_TIMEOUT (Property Type 0x06) is a Track and Object Property. It is a variable-length integer. Its semantics are defined in . As an Object Property on the first object in a subgroup, it overrides the Track-level value for that subgroup; it is ignored on any other object in the subgroup.

OBJECT_DELIVERY_TIMEOUT OBJECT_DELIVERY_TIMEOUT (Property Type 0x02) is a Track and Object Property. It is a variable-length integer. Its semantics are defined in . As an Object Property on the first object in a subgroup, it overrides the Track-level value for that subgroup; it is ignored on any other object in the subgroup.

MAX CACHE DURATION MAX_CACHE_DURATION (Property Type 0x04) is a Track Property. It is an integer expressing the number of milliseconds an Object can be served from a cache. If present, the relay MUST NOT start forwarding any individual Object received through this subscription or fetch after the specified number of milliseconds has elapsed since the beginning of the Object was received. This means Objects earlier in a multi-object stream will expire earlier than Objects later in the stream. Once Objects have expired from cache, their state becomes unknown (see ). If MAX_CACHE_DURATION is not sent by the publisher, the Objects can be cached until implementation constraints cause them to be evicted.

DEFAULT PUBLISHER PRIORITY DEFAULT PUBLISHER PRIORITY (Property Type 0x0E) is a Track Property that specifies the priority of a subscription relative to other subscriptions in the same session. The value is from 0 to 255 and lower numbers get higher priority. See . Priorities above 255 are invalid. Subgroups and Datagrams for this subscription inherit this priority, unless they specifically override it. If omitted, the Default Publisher Priority is 128.

DEFAULT PUBLISHER GROUP ORDER DEFAULT_PUBLISHER_GROUP_ORDER (Property Type 0x22) is a Track Property. It is an enum indicating the publisher's preference for prioritizing Objects from different groups within the same subscription (see ). The allowed values are Ascending (0x1) or Descending (0x2). If an endpoint receives a value outside this range, it MUST close the session with PROTOCOL_VIOLATION. If omitted, the publisher's preference is Ascending (0x1).

DYNAMIC GROUPS DYNAMIC_GROUPS (Property Type 0x30) is a Track Property. The allowed values are 0 or 1. When the value is 1, it indicates that the subscriber can request the Original Publisher to start a new Group by including the NEW_GROUP_REQUEST parameter in REQUEST_UPDATE for this Track. If an endpoint receives a value larger than 1, it MUST close the session with PROTOCOL_VIOLATION. If omitted, the value is 0.

Immutable Properties Immutable Properties (Property Type 0xB) is a Track or Object Property that contains a sequence of Key-Value-Pairs (see ) that are themselves Track or Object Properties, respectively. This Property can be added by the Original Publisher, but MUST NOT be added by Relays. This Property MUST NOT be modified or removed and the serialization (e.g. variable-length integer encodings) of the Key-Value-Pairs MUST NOT change). Like other Properties, Relays MUST cache Immutable Properties if the Object or Track are cached and MUST forward it. Relays MAY decode and view the Properties in the Key-Value-Pairs. Unless specified by a particular Property specification, Properties MAY appear either in the mutable property list or inside Immutable Properties. When looking for the value of a property, processors MUST search both the mutable properties and the contents of Immutable Properties. If a Property allows multiple values, the same Property Type MAY appear in both the mutable list and inside Immutable Properties, unless prohibited by the Property specification. A Track is considered malformed (see ) if any of the following conditions are detected:

An Object contains an Immutable Properties property that contains another Immutable Properties key.
A Key-Value-Pair cannot be parsed.

The following figure shows an example Object structure with a combination of mutable and immutable properties and end to end encrypted metadata in the Object payload. <-------------------> +--------+-------+------------+-------+-----------+--------------------+ | Object | Ext 1 | Immutable | Ext N | [Payload] | Private Properties | | Fields | | Properties | | [Length] | App Payload | +--------+-------+------------+-------+-----------+--------------------+ xxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx yyyyyyyyyyyyyyyyyyyy x = e2e Authenticated Data y = e2e Encrypted Data EXT 1 and EXT N can be modified or removed by Relays ]]> An Object MUST NOT contain more than one instance of this property.

Prior Group ID Gap Prior Group ID Gap only applies to Objects, not Tracks. Prior Group ID Gap (Property Type 0x3C) is a variable-length integer containing the number of Groups prior to the current Group that do not, and will never, exist. For example, if the Original Publisher is publishing an Object in Group 7 and knows it will never publish any Objects in Group 8 or Group 9, it can include Prior Group ID Gap = 2 in any number of Objects in Group 10, as it sees fit. A Track is considered malformed (see ) if any of the following conditions are detected:

An Object contains more than one instance of Prior Group ID Gap.
A Group contains more than one Object with different values for Prior Group ID Gap.
An Object has a Prior Group ID Gap larger than the Group ID.
An endpoint receives an Object with a Prior Group ID Gap covering an Object it previously received.
An endpoint receives an Object with a Group ID within a previously communicated gap.

Use of this property is optional, as publishers might not know the prior gap size, or there may not be a gap. If Prior Group ID Gap is not present, the receiver cannot infer any information about the existence of prior groups (see ). This property can be added by the Original Publisher, but MUST NOT be added by relays. This property MAY be removed by a relay when the object in question is served via FETCH, and the gap that the property communicates is already communicated implicitly in the FETCH response; it MUST NOT be modified or removed otherwise. An Object MUST NOT contain more than one instance of this property.

Prior Object ID Gap Prior Object ID Gap only applies to Objects, not Tracks. Prior Object ID Gap (Property Type 0x3E) is a variable-length integer containing the number of Objects prior to the current Object that do not, and will never, exist. For example, if the Original Publisher is publishing Object 10 in Group 3 and knows it will never publish Objects 8 or 9 in this Group, it can include Prior Object ID Gap = 2. A Track is considered malformed (see ) if any of the following conditions are detected:

An Object contains more than one instance of Prior Object ID Gap.
An Object has a Prior Object ID Gap larger than the Object ID.
An endpoint receives an Object with a Prior Object ID Gap covering an Object it previously received.
An endpoint receives an Object with an Object ID within a previously communicated gap.

Use of this property is optional, as publishers might not know the prior gap size, or there might not be a gap. If Prior Object ID Gap is not present, the receiver cannot infer any information about the existence of prior objects (see ). This property can be added by the Original Publisher, but MUST NOT be added by relays. This property MAY be removed by a relay when the object in question is served via FETCH, and the gap that the property communicates is already communicated implicitly in the FETCH response; it MUST NOT be modified or removed otherwise. An Object MUST NOT contain more than one instance of this property.

Data Streams and Datagrams A publisher sends Objects matching a subscription on Data Streams or Datagrams and sends Objects matching a FETCH request on one Data Stream. Unidirectional stream types are defined in . Data streams use SUBGROUP_HEADER or FETCH_HEADER types. All MOQT datagrams start with a variable-length integer indicating the type of the datagram. See . An endpoint that receives an unknown datagram type MUST close the session. Every Object has a 'Object Forwarding Preference' and the Original Publisher MAY use both Subgroups and Datagrams within a Group or Track.

Objects An Object contains a range of contiguous bytes from the specified track, as well as associated metadata required to deliver, cache, and forward it. Objects are sent by publishers.

Object Header A canonical MOQT Object has the following fields:

Track Namespace and Track Name: The track this object belongs to.
Group ID: The identifier of the Object's Group (see ) within the Track.
Object ID: The order of the object within the group.
Publisher Priority: An 8 bit integer indicating the publisher's priority for the Object ().
Object Forwarding Preference: An enumeration indicating how a publisher sends an object. The preferences are Subgroup and Datagram. Object Forwarding Preference is a property of an individual Object and can vary among Objects in the same Track. In a subscription, an Object MUST be sent according to its Object Forwarding Preference.
Subgroup ID: The identifier of the Object's Subgroup (see ) within the Group. This field is omitted if the Object Forwarding Preference is Datagram.
Object Status: An enumeration used to indicate whether the Object is a normal Object or mark the end of a group or track. See below.
Object Properties : A sequence of Properties associated with the object. See .
Object Payload: An opaque payload intended for an End Subscriber and SHOULD NOT be processed by a relay. Only present when 'Object Status' is Normal (0x0).

Object Status The Object Status is a field that is only present in objects that are delivered via a SUBSCRIPTION, and is absent in Objects delivered via a FETCH. It allows the publisher to explicitly communicate that a specific range of objects does not exist. Status can have following values:

0x0 := Normal object. This status is implicit for any non-zero length object. Zero-length objects explicitly encode the Normal status.
0x3 := Indicates End of Group. Indicates that no objects with the specified Group ID and the Object ID that is greater than or equal to the one specified exist in the group identified by the Group ID.
0x4 := Indicates End of Track. Indicates that no objects with the location that is equal to or greater than the one specified exist.

All of those SHOULD be cached. There is no Object Status value indicating the end of a Subgroup. The end of a Subgroup is signaled by closing its stream with a FIN (see ). Any other value SHOULD be treated as a protocol error and the session SHOULD be closed with a PROTOCOL_VIOLATION (). An Object MUST have an empty payload unless its Object Status value is registered as permitting a payload in the Object Status registry (). Of the values defined in this document, only Normal (0x0) permits a payload.

Object Properties Any Object with status Normal can have properties (). If an endpoint receives properties on an Object with status that is not Normal, it MUST close the session with a PROTOCOL_VIOLATION. Object Properties are visible to relays and are intended to be relevant to MOQT Object distribution. Any Object metadata never intended to be accessed by the transport or Relays SHOULD be serialized as part of the Object payload and not as an Object Property. Object Properties set by the Original Publisher that are intended to be visible to relays, but not modified by them, SHOULD be placed in Immutable Properties (), which enables end-to-end authentication schemes. Object Properties are serialized as a length in bytes followed by Key-Value-Pairs (see ). Object Property types are registered in the IANA table 'MOQ Properties'. See .

Datagrams A single object can be conveyed in a datagram. The Track Alias field () indicates the track this Datagram belongs to. If an endpoint receives a datagram with an unknown Track Alias, it MAY drop the datagram or choose to buffer it for a brief period to handle reordering with the control message that establishes the Track Alias. An Object received in an OBJECT_DATAGRAM message has an Object Forwarding Preference = Datagram. To send an Object with Object Forwarding Preference = Datagram, determine the length of the header and payload and send the Object as datagram. When the total size is larger than the maximum datagram size for the session, the Object will be dropped without any explicit notification. Each session along the path between the Original Publisher and End Subscriber might have different maximum datagram sizes. Additionally, Object Properties () can be added to Objects as they pass through the MOQT network, increasing the size of the Object and the chances it will exceed the maximum datagram size of a downstream session and be dropped.

Object Datagram An OBJECT_DATAGRAM carries a single object in a datagram.

MOQT OBJECT_DATAGRAM The Type Flags field in the OBJECT_DATAGRAM is a variable-length integer that encodes a set of flags. All values defined in this specification fit in a single-byte encoding (values less than 128). If a received value has bit 4 set, or has a bit set whose meaning is not specified, the endpoint MUST close the session with a PROTOCOL_VIOLATION. The four low-order bits and bit 5 of the Type Flags field determine which fields are present in the datagram:

The PROPERTIES bit (0x01) indicates when the Properties field is present. When set to 1, the Object Properties structure defined in is present. When set to 0, the field is absent. If an endpoint receives a datagram with the PROPERTIES bit set and an Properties Length of 0, it MUST close the session with a PROTOCOL_VIOLATION.
The END_OF_GROUP bit (0x02) indicates End of Group. When set to 1, this indicates that no Object with the same Group ID and an Object ID greater than the Object ID in this datagram exists.
The ZERO_OBJECT_ID bit (0x04) indicates when the Object ID field is present. When set to 1, the Object ID field is omitted and the Object ID is 0. When set to 0, the Object ID field is present.
The DEFAULT_PRIORITY bit (0x08) indicates when the Priority field is present. When set to 1, the Priority field is omitted and this Object inherits the Publisher Priority specified in the control message that established the subscription. When set to 0, the Priority field is present.
The STATUS bit (0x20) indicates whether the datagram contains an Object Status or Object Payload. When set to 1, the Object Status field is present and there is no Object Payload. When set to 0, the Object Payload is present and the Object Status field is omitted. There is no explicit length field for the Object Payload; the entirety of the transport datagram following the Object header contains the payload.

The following Type Flags values are invalid. If an endpoint receives a datagram with any of these values, it MUST close the session with a PROTOCOL_VIOLATION:

Values with both the STATUS bit (0x20) and END_OF_GROUP bit (0x02) set.
Values with bit 4 (0x10) set. This bit is reserved and MUST be zero.
Values with a bit set whose meaning is not specified.

If an Object Datagram includes both the STATUS bit and PROPERTIES bit, and the Object Status is not Normal (0x0), the endpoint MUST close the session with a PROTOCOL_VIOLATION, because only Normal Objects can have Properties.

Subgroup Streams When Objects are sent on streams, the stream begins with a Subgroup or Fetch Header and is followed by one or more sets of serialized Object fields. If a stream ends gracefully (i.e., the stream terminates with a FIN) in the middle of a serialized Object, the session SHOULD be closed with a PROTOCOL_VIOLATION. A publisher SHOULD NOT open more than one stream at a time with the same Subgroup Header field values.

Subgroup Header All Objects on a Subgroup stream belong to the track identified by Track Alias (see ) and the Subgroup indicated by 'Group ID' and Subgroup ID indicated by the SUBGROUP_HEADER. If an endpoint receives a subgroup with an unknown Track Alias, it MAY abandon the stream, or choose to buffer it for a brief period to handle reordering with the control message that establishes the Track Alias. The endpoint MAY withhold stream flow control beyond the SUBGROUP_HEADER until the Track Alias has been established. To prevent deadlocks, endpoints MUST allocate connection flow control to the control streams before allocating it to any data streams. Otherwise, a receiver might wait for a control message containing a Track Alias to release flow control, while the sender waits for flow control to send the message.

MOQT SUBGROUP_HEADER All Objects received on a stream opened with SUBGROUP_HEADER have an Object Forwarding Preference = Subgroup. The Type Flags field in the SUBGROUP_HEADER is a variable-length integer that encodes a set of flags. All values defined in this specification fit in a single-byte encoding (values less than 128). Bit 4 is always set to 1. The four low-order bits and bits 5-6 determine which fields are present in the header:

The PROPERTIES bit (0x01) indicates when the Properties field is present in all Objects in this Subgroup. When set to 1, the Object Properties structure defined in is present in all Objects; Objects with no properties set Properties Length to 0. When set to 0, the field is never present.
The SUBGROUP_ID_MODE field (bits 1-2, mask 0x06) is a two-bit field that determines the encoding of the Subgroup ID. To extract this value, perform a bitwise AND with mask 0x06 and right-shift by 1 bit:
- 0b00: The Subgroup ID field is absent and the Subgroup ID is 0.
- 0b01: The Subgroup ID field is absent and the Subgroup ID is the Object ID of the first Object transmitted in this Subgroup.
- 0b10: The Subgroup ID field is present in the header.
- 0b11: Reserved for future use.
The END_OF_GROUP bit (0x08) indicates that this subgroup contains the largest Object in the Group. When set to 1, the subscriber can infer the final Object in the Group when the data stream is terminated by a FIN. In this case, Objects that have the same Group ID and an Object ID larger than the last Object received on the stream do not exist. This does not apply when the data stream is reset.
The DEFAULT_PRIORITY bit (0x20) indicates when the Priority field is present. When set to 1, the Priority field is omitted and this Subgroup inherits the Publisher Priority specified in the control message that established the subscription. When set to 0, the Priority field is present in the Subgroup header.
The FIRST_OBJECT bit (0x40) indicates that the first object in this subgroup stream is the first object published in the subgroup by the original publisher.

The following Type Flags values are invalid. If an endpoint receives a stream header with any of these values, it MUST close the session with a PROTOCOL_VIOLATION:

Values with SUBGROUP_ID_MODE set to 0b11. This mode is reserved for future use.
Values where bit 4 is not set. Bit 4 MUST be 1 for SUBGROUP_HEADER.
Values of 128 or greater (i.e., any value that requires more than a one-byte variable-length integer encoding).

To send an Object with Object Forwarding Preference = Subgroup, find the open stream that is associated with the subscription, Group ID and Subgroup ID, or open a new one and send the SUBGROUP_HEADER. Then serialize the following fields. The Object Status field is only sent if the Object Payload Length is zero. The Object ID Delta + 1 is added to the previous Object ID in the Subgroup stream if there was one. The Object ID is the Object ID Delta if it's the first Object in the Subgroup stream. If the resulting Object ID would be greater than 2^64 - 1, the endpoint MUST close the session with a PROTOCOL_VIOLATION. For example, a Subgroup of sequential Object IDs starting at 0 will have 0 for all Object ID Delta values. A consumer cannot infer information about the existence of Objects between the current and previous Object ID in the Subgroup (e.g. when Object ID Delta is non-zero) unless there is a Prior Object ID Gap property (see ).

MOQT Subgroup Object Fields

Closing Subgroup Streams Subscribers will often need to know if they have received all objects in a Subgroup, particularly if they serve as a relay or cache. QUIC and Webtransport streams provide signals that can be used for this purpose. Closing Subgroups promptly frees system resources and often unlocks flow control credit to open more streams. If a sender has delivered all objects in a Subgroup to the QUIC stream, except any Objects with Locations smaller than the subscription's Start Location, it MUST close the stream with a FIN. If a sender closes the stream before delivering all such objects to the QUIC stream, it MUST reset the stream. This includes, but is not limited to:

Either of the delivery timeouts defined in
Early termination of subscription due to request cancellation
A publisher's decision to end the subscription early
A REQUEST_UPDATE moving the subscription's End Group to a smaller Group or the Start Location to a larger Location
Omitting a Subgroup Object due to the subscriber's Forward State

When RESET_STREAM_AT is used, the reliable_size SHOULD include the stream header so the receiver can identify the corresponding subscription and accurately account for reset data streams when handling PUBLISH_DONE (see ). Publishers that reset data streams without using RESET_STREAM_AT with an appropriate reliable_size can cause subscribers to hold on to subscription state until a timeout expires. A sender might send all objects in a Subgroup and the FIN on a QUIC stream, and then reset the stream. In this case, the receiving application would receive the FIN if and only if all objects were received. If the application receives all data on the stream and the FIN, it can ignore any subsequent reset. If a sender will not deliver any objects from a Subgroup, it MAY send a SUBGROUP_HEADER on a new stream, with no objects, and then send RESET_STREAM_AT with a reliable_size equal to the length of the stream header. This explicitly tells the receiver there is an unsent Subgroup. A relay MUST NOT forward an Object on an existing Subgroup stream unless it is the next Object in that Subgroup. A relay determines that an Object is the next Object in the Subgroup if at least one of the following is true:

The Object ID is one greater than the previous Object sent on this Subgroup stream.
The Object was received on the same upstream Subgroup stream as the previously sent Object on the downstream Subgroup stream, with no other Objects in between, unless the intervening Objects did not pass the subscriber's filters.
It determined all Object IDs between the current and previous Object IDs on the Subgroup stream belong to different Subgroups or do not exist, or do not pass the subscriber's filters.

If the relay does not know if an Object is the next Object, it MUST reset the Subgroup stream and open a new one to forward it. Since SUBSCRIBEs always end on a group boundary, an ending subscription can always cleanly close all its subgroups. A sender that terminates a stream early for any other reason (e.g., to handoff to a different sender) MUST reset the stream. Senders SHOULD terminate a stream on Group boundaries to avoid doing so. An MOQT implementation that processes a stream FIN is assured it has received all objects in a subgroup from the start of the subscription. If a relay, it can forward stream FINs to its own subscribers once those objects have been sent. A relay MAY treat receipt of EndOfGroup or EndOfTrack objects as a signal to close corresponding streams even if the FIN has not arrived, as further objects on the stream would be a protocol violation. Similarly, an EndOfGroup message indicates the maximum Object ID in the Group, so if all Objects in the Group have been received, a FIN can be sent on any stream where the entire subgroup has been sent. This might be complex to implement. Processing a reset means that there might be other objects in the Subgroup beyond the last one received. A relay might immediately reset the corresponding downstream stream, or it might attempt to recover the missing Objects in an effort to send all the Objects in the subgroups and the FIN. It also might send RESET_STREAM_AT with reliable_size set to the last Object it has, so as to reliably deliver the Objects it has while signaling that other Objects might exist. A subscriber MAY send a QUIC STOP_SENDING frame for a subgroup stream if the Group or Subgroup is no longer of interest to it. The publisher SHOULD respond with a reset. If RESET_STREAM_AT is sent, note that the receiver has indicated no interest in the objects, so setting a reliable_size beyond the stream header is of questionable utility. Resets and STOP_SENDING on SUBSCRIBE data streams have no impact on other Subgroups in the Group or the subscription, although applications might cancel all Subgroups in a Group at once. A publisher that receives a STOP_SENDING on a Subgroup stream SHOULD NOT attempt to open a new stream to deliver additional Objects in that Subgroup. However, if the publisher subsequently receives a REQUEST_UPDATE that changes the Forward State from 0 to 1, it MAY open a new stream to deliver Objects in that Subgroup, as the update indicates the subscriber has renewed interest in forwarded Objects. The application SHOULD use a relevant error code when resetting a stream, as defined in .

Fetch Streams

Fetch Header When a stream begins with FETCH_HEADER, all objects on the stream belong to the track requested in the message identified by Request ID.

MOQT FETCH_HEADER Each Object sent on a FETCH stream after the FETCH_HEADER has the following format:

MOQT Fetch Object Fields The Serialization Flags field defines the serialization of the Object. It is a variable-length integer. When less than 128, the bits represent flags described below. The following additional values are defined:

Value	Meaning
0x8C	End of Non-Existent Range
0x10C	End of Unknown Range
0x20C	End of Timed-Out Range

Any other value is a PROTOCOL_VIOLATION.

Flags The two least significant bits (LSBs) of the Serialization Flags form a two-bit field that defines the encoding of the Subgroup. To extract this value, the Subscriber performs a bitwise AND operation with the mask 0x03.

Bitmask Result (Serialization Flags & 0x03)	Meaning
0x00	Subgroup ID is zero
0x01	Subgroup ID is the prior Object's Subgroup ID
0x02	Subgroup ID is the prior Object's Subgroup ID plus one
0x03	The Subgroup ID field is present

The following table defines additional flags within the Serialization Flags field. Each flag is an independent boolean value, where a set bit (1) indicates the corresponding condition is true.

Bitmask	Condition if set	Condition if not set (0)
0x04	Object ID Delta is present	Object ID is the prior Object's ID plus one
0x08	Group ID Delta is present	Group ID is the prior Object's Group ID
0x10	Priority field is present	Priority is the prior Object's Priority
0x20	Properties field is present	Properties field is not present
0x40	Datagram: ignore the two least significant bits	Decode the Subgroup ID as indicated by the two least significant bits

The first Object MUST include a Group ID Delta and Object ID Delta, and these values are the absolute Group ID and Object ID. If the first Object in the FETCH response uses a flag that references fields in the prior Object, the Subscriber MUST close the session with a PROTOCOL_VIOLATION. If the Group ID Delta field is present on an Object other than the first, the Group ID is computed from the Group ID Delta and the prior Object's Group ID. If the Group Order is Ascending, the Group ID is the prior Object's Group ID plus the Group ID Delta + 1. If the Group Order is Descending, the Group ID is the prior Object's Group ID minus the (Group ID Delta + 1). If the computed Group ID would be less than 0 or greater than 2^64-1, the Subscriber MUST close the Session with error 'PROTOCOL_VIOLATION'. When the Group ID Delta field is present, the Object ID is the value of Object ID Delta if present. When the Group ID Delta field is not present, the Object ID is the prior Object's ID plus the Object ID Delta if present. If Object ID Delta is not present, the Object ID is the prior Object's ID plus one, regardless of which group it belongs to. If the computed Object ID would be greater than 2^64-1, the Subscriber MUST close the Session with error 'PROTOCOL_VIOLATION'. The Object Properties structure is defined in . When encoding an Object with a Forwarding Preference of "Datagram" (see ), the object has no Subgroup ID. The publisher MUST SET bit 0x40 to '1'. When 0x40 is set, it SHOULD set the two least significant bits to zero and the subscriber MUST ignore the bits.

End of Range When Serialization Flags indicates an End of Range (e.g. values 0x8C, 0x10C, or 0x20C), the Group ID and Object ID fields are present. Subgroup ID, Priority and Properties are not present. All Objects with Locations between the last serialized Object, if any, and this Location, inclusive, either do not exist (when Serialization Flags is 0x8C), are unknown (0x10C), or timed out (0x20C). A publisher SHOULD NOT use End of Non-Existent Range in a FETCH response except to split a range of Objects that will not be serialized into those that are known not to exist and those with unknown or timed out status. When an Object follows an End of Range indicator and uses flags that reference the "prior Object", the prior Object fields are determined as follows:

Prior Group ID and prior Object ID: The values from the End of Range indicator.
Prior Subgroup ID: The Subgroup ID from the last actual Object before the End of Range indicator. If there was no prior Object, using a flag that references the prior Subgroup ID is a PROTOCOL_VIOLATION.
Prior Priority: The Priority from the last actual Object before the End of Range indicator. If there was no prior Object, using a flag that references the prior Priority is a PROTOCOL_VIOLATION.

Padding An endpoint MAY send padding on unidirectional streams or datagrams. Padding does not carry Objects or any other application data. An endpoint can use padding to probe for additional bandwidth while minimizing the impact on the delivery of application data. To avoid interfering with the delivery of Objects, senders SHOULD send padding streams at a lower priority than any control stream or Object data.

Padding Streams An endpoint MAY open a unidirectional stream with a stream type of 0x132B3E28 to send padding data. The stream begins with the stream type, followed by zero or more bytes that MUST all be set to zero.

MOQT Padding Stream The receiver MUST discard all data received on a padding stream to prevent exhausting flow control. Either the sender or the receiver MAY cancel a padding stream at any time without affecting any MOQT application state.

Padding Datagrams An endpoint MAY send a datagram with a type of 0x132B3E29 to send padding data. The datagram contains the type followed by zero or more bytes that MUST all be set to zero.

MOQT Padding Datagram The receiver MUST discard all data received in a padding datagram.

Error Handling

Malformed Tracks There are multiple ways a publisher can transmit a Track that does not conform to MOQT constraints. Such a Track is considered malformed. Some example conditions that constitute a malformed track when detected by a receiver include:

An Object with a particular Subgroup ID is received, but its Publisher Priority is different from that of the previous Object with the same Subgroup ID.
An Object is received whose Object ID is larger than the final Object in the Subgroup. The final Object in a Subgroup is the last Object received on a Subgroup stream before a FIN.
A Subgroup is received over multiple transport streams terminated by FIN with different final Objects.
An Object is received in a Group whose Object ID is larger than the final Object in the Group. The final Object in a Group is the Object with Status END_OF_GROUP, or the last Object before a FIN in a Subgroup which has the END_OF_GROUP bit set. If the end of a Group is implicitly determined via a gap in a FETCH response, the final Object in the Group remains unknown.
An Object is received whose Group and Object ID are larger than the final Object in the Track. The final Object in a Track is the Object with Status END_OF_TRACK or the last Object sent in a FETCH whose response indicated End of Track.
The same Object is received more than once with different Payload or other immutable properties.
An Object is received with a different Forwarding Preference than previously observed.

The above list of conditions is not considered exhaustive. When a subscriber detects a Malformed Track, it MUST cancel any corresponding subscription or fetches for that Track from that publisher (see ), and SHOULD deliver an error to the application. If a relay detects a Malformed Track, it MUST immediately terminate downstream subscriptions with PUBLISH_DONE and reset any fetch streams with Status Code MALFORMED_TRACK. Object(s) triggering Malformed Track status MUST NOT be cached.

Session Termination Codes When terminating the Session (), the application MAY use any error message and SHOULD use a relevant code, as defined below:

NO_ERROR (0x0):: The session is being terminated without an error.
INTERNAL_ERROR (0x1):: An implementation specific error occurred.
UNAUTHORIZED (0x2):: The client is not authorized to establish a session.
PROTOCOL_VIOLATION (0x3):: The remote endpoint performed an action that was disallowed by the specification.
INVALID_REQUEST_ID (0x4):: The endpoint received a Request ID with an incorrect least significant bit for the sender, or a duplicate Request ID. See .
DUPLICATE_TRACK_ALIAS (0x5):: The endpoint attempted to use a Track Alias that was already in use.
KEY_VALUE_FORMATTING_ERROR (0x6):: The key-value pair has a formatting error.
INVALID_PATH (0x8):: The PATH parameter was used by a server, on a WebTransport session, or the server does not support the path.
MALFORMED_PATH (0x9):: The PATH parameter does not conform to the rules in .
GOAWAY_TIMEOUT (0x10):: The session was closed because the peer took too long to close the session in response to a GOAWAY () message. See session migration ().
CONTROL_MESSAGE_TIMEOUT (0x11):: The session was closed because the peer took too long to respond to a control message.
DATA_STREAM_TIMEOUT (0x12):: The session was closed because the peer took too long to send data expected on an open Data Stream (see ). This includes fields of a stream header or an object header within a data stream. If an endpoint times out waiting for a new object header on an open subgroup stream, it MAY send a STOP_SENDING on that stream or terminate the subscription.
AUTH_TOKEN_CACHE_OVERFLOW (0x13):: The Session limit of the size of all registered Authorization tokens has been exceeded.
DUPLICATE_AUTH_TOKEN_ALIAS (0x14):: Authorization Token attempted to register an Alias that was in use (see ).
MALFORMED_AUTH_TOKEN (0x16):: Invalid Auth Token serialization during registration (see ).
UNKNOWN_AUTH_TOKEN_ALIAS (0x17):: No registered token found for the provided Alias (see ).
EXPIRED_AUTH_TOKEN (0x18):: Authorization token has expired ().
INVALID_AUTHORITY (0x19):: The specified AUTHORITY does not correspond to this server or cannot be used in this context.
MALFORMED_AUTHORITY (0x1A):: The AUTHORITY value is syntactically invalid.
TOO_MANY_REQUEST_UPDATES (0x1B):: The endpoint received a REQUEST_UPDATE that exceeded the per-stream limit communicated via the MAX_REQUEST_UPDATES Setup Option ().

Request Error Codes The application SHOULD use a relevant error code in REQUEST_ERROR (), as defined below and assigned in . Most codepoints have identical meanings for various request types, but some have request-specific meanings.

INTERNAL_ERROR:: An implementation specific or generic error occurred.
UNAUTHORIZED:: The subscriber is not authorized to perform the requested action on the given track. This might be retryable if the authorization token is not yet valid.
TIMEOUT:: The subscription could not be completed before an implementation specific timeout. For example, a relay could not establish an upstream subscription within the timeout.
NOT_SUPPORTED:: The endpoint does not support the type of request.
MALFORMED_AUTH_TOKEN:: Invalid Auth Token serialization during registration (see ).
EXPIRED_AUTH_TOKEN:: Authorization token has expired ().
GOING_AWAY:: The endpoint has received a GOAWAY and MAY reject new requests.
EXCESSIVE_LOAD:: The responder is overloaded and cannot process the request at this time. The sender SHOULD use the Retry Interval to indicate when the request can be retried.
UNSUPPORTED_EXTENSION:: The track contains a Mandatory Track Property (see ) that the endpoint does not understand.
REDIRECT:: The request cannot be fulfilled by this endpoint, but could succeed at the location specified in the Redirect structure. The requester SHOULD establish a new session to the provided URI (if present) and retry the request using the Redirect target. A Retry Interval of 0 indicates the original request SHOULD NOT be retried as sent; it does not prevent the requester from following a Redirect to a different URI or Redirect target. This error code can appear in response to SUBSCRIBE, FETCH, TRACK_STATUS, PUBLISH, PUBLISH_NAMESPACE, SUBSCRIBE_NAMESPACE, and SUBSCRIBE_TRACKS. Relays are not required to follow redirects from upstream and MAY forward a REDIRECT response to matching downstream requests. A relay MAY cache a REDIRECT response for up to Retry Interval milliseconds and use it to respond to subsequent matching requests without forwarding them upstream.

Below are errors for use by the publisher. They can appear in response to SUBSCRIBE, FETCH, TRACK_STATUS, SUBSCRIBE_NAMESPACE, and SUBSCRIBE_TRACKS, unless otherwise noted.

DOES_NOT_EXIST:: The track or namespace is not available at the publisher.
INVALID_RANGE:: In response to SUBSCRIBE or FETCH, specified Filter or range of Locations cannot be satisfied.
INVALID_FILTER:: A filter parameter is invalid.
MALFORMED_TRACK:: In response to a FETCH, a relay publisher detected the track was malformed (see ).

The following are errors for use by the subscriber. They can appear in response to PUBLISH or PUBLISH_NAMESPACE, unless otherwise noted.

UNINTERESTED:: The subscriber is not interested in the track or namespace.

Errors below can only be used in response to one message type.

PREFIX_OVERLAP:: In response to SUBSCRIBE_NAMESPACE or SUBSCRIBE_TRACKS, the namespace prefix shares a common prefix with another subscription of the same type in the same session. SUBSCRIBE_NAMESPACE and SUBSCRIBE_TRACKS have independent overlap spaces, so a SUBSCRIBE_NAMESPACE and a SUBSCRIBE_TRACKS may share the same prefix.
NAMESPACE_TOO_LARGE:: In response to SUBSCRIBE_NAMESPACE or SUBSCRIBE_TRACKS, the namespace prefix matches more publishers than the relay is willing to enumerate.
CONFLICTING_FILTERS:: In response to SUBSCRIBE_TRACKS, the filter parameters conflict among too many subscribers to aggregate the subscription upstream or otherwise efficiently service it.

Publish Done Codes The application SHOULD use a relevant status code in PUBLISH_DONE (), as defined below:

INTERNAL_ERROR (0x0):: An implementation specific or generic error occurred.
UNAUTHORIZED (0x1):: The subscriber is no longer authorized to subscribe to the given track.
TRACK_ENDED (0x2):: The track is no longer being published.
GOING_AWAY (0x4):: The subscriber or publisher issued a GOAWAY message.
TOO_FAR_BEHIND (0x5):: The publisher's queue of objects to be sent to the given subscriber exceeds its implementation defined limit.
EXPIRED (0x6):: The publisher reached the timeout specified in SUBSCRIBE_OK.
MALFORMED_TRACK (0x12):: A relay publisher detected that the track was malformed (see ).
UPDATE_FAILED (0x8):: REQUEST_UPDATE failed on this subscription (see ).
EXCESSIVE_LOAD (0x9):: The publisher is overloaded and is terminating the subscription.

Stream Reset Error Codes The application SHOULD use a relevant error code when resetting or sending STOP_SENDING on any stream.

INTERNAL_ERROR (0x0):: An implementation specific error.
CANCELLED (0x1):: The stream was cancelled by either endpoint. For Subscriptions, PUBLISH_DONE () may have a more detailed status code.
DELIVERY_TIMEOUT (0x2):: A delivery timeout () was exceeded for this stream.
SESSION_CLOSED (0x3):: The session is being closed.
GOING_AWAY (0x4):: The endpoint is rejecting this request because it has sent or received a GOAWAY.
TOO_FAR_BEHIND (0x5):: The corresponding subscription has exceeded the publisher's resource limits and is being terminated (see ).
UNKNOWN_OBJECT_STATUS (0x6):: In response to a FETCH, the publisher is unable to determine the status of the next Object in the requested range.
EXPIRED_AUTH_TOKEN (0x7):: The authorization token for the request has expired.
EXCESSIVE_LOAD (0x9):: The endpoint is overloaded and is resetting this stream.
MALFORMED_TRACK (0x12):: A relay publisher detected that the track was malformed (see ).

Grease To ensure that implementations correctly handle unknown values and do not fail when encountering protocol extensions they do not understand, this document reserves a range of values for the purpose of greasing; see . Grease values follow the pattern 0x7f * N + 0x9D for non-negative integer values of N (that is, 0x9D, 0x11C, ..., 0x3fffffffffffffde). The following registries include GREASE reservations:

Setup Options ()
Properties ()
Session Termination Error Codes ()
REQUEST_ERROR Codes ()
PUBLISH_DONE Codes ()
Stream Reset Error Codes ()
MOQT Auth Token Type

Because new values in these registries can be defined without negotiation, implementations MUST handle unknown values gracefully. Endpoints MUST NOT close the session solely because they received an unknown value. The following rules apply: Setup Options with reserved identifiers have no semantics and can carry arbitrary values. Endpoints MUST ignore unknown Setup Options as specified in . Unknown Properties MUST be handled as specified in . Receipt of an unknown error code in any error context (Session Termination, REQUEST_ERROR, PUBLISH_DONE, or Data Stream Reset) MUST be treated as equivalent to INTERNAL_ERROR for that context. An endpoint MUST NOT close the session because it received an unknown error code in a REQUEST_ERROR or PUBLISH_DONE.

Transport Considerations

Congestion Control Considerations MOQT does not specify a congestion controller, but there are important attributes to consider when selecting a congestion controller for use with an application built on top of MOQT.

Bufferbloat Traditional AIMD congestion controllers (ex. CUBIC and Reno ) are prone to Bufferbloat. Bufferbloat occurs when elements along the path build up a substantial queue of packets, commonly more than doubling the round trip time. These queued packets cause head-of-line blocking and latency, even when there is no packet loss.

Application-Limited The average bitrate for latency sensitive content needs to be less than the available bandwidth, otherwise data will be queued and/or dropped. As such, many MOQT applications will typically be limited by the available data to send, and not the congestion controller. Many congestion control algorithms only increase the congestion window or bandwidth estimate if fully utilized. This combination can lead to underestimating the available network bandwidth. As a result, applications might need to periodically ensure the congestion controller is not app-limited for at least a full round trip to ensure the available bandwidth can be measured. Some applications might have APIs to allow sending duplicate data or forward error correction to probe for more bandwidth while also limiting the impact of probing in case it causes packet loss. Subscribers wanting to switch to an alternate representation of a Track can subscribe to it at a lower priority, or subscribe to additional Tracks at the lowest (255) priority to fill the congestion window during probing intervals while minimizing the impact on higher priority media. Publishers can send padding () to probe for additional bandwidth without requiring additional subscriptions. Network-assisted bandwidth estimation mechanisms such as SCONE can provide receivers with sustainable bandwidth hints, which subscribers can use to inform track selection decisions and potentially avoid unnecessary probing.

Consistent Throughput Congestion control algorithms are commonly optimized for throughput, not consistency. For example, BBR's PROBE_RTT state halves the sending rate for more than a round trip in order to obtain an accurate minimum RTT. Similarly, Reno halves its congestion window upon detecting loss. In both cases, the large reduction in sending rate might cause issues with latency sensitive applications.

Security Considerations MOQT is a protocol used hop-by-hop between original publishers to relay, (possibly) relay to relay, and relay to end subscribers. Thus, the security considerations need to consider first what happens between two Endpoints, but also consider the impacts end to end over several hops of MOQT. MOQT uses a trust model where on each hop the Endpoints need to be securely identified, authorized to use resources of the peer, provide confidentiality and integrity to prevent third party attacks and limit monitoring and leakage of privacy sensitive information. The relays within the chain from original publisher to end subscribers will have access to Track names, Track Properties, Object Properties, as well as the object's content unless it is end-to-end encrypted . Publishers, including Relays, require authorization to prevent unauthorized subscriptions to content. Subscription requests can carry authorization tokens (see ) to prove the subscriber's right to access specific tracks or namespaces. Relays that aggregate subscriptions from multiple downstream subscribers MUST ensure each subscriber is independently authorized.

Subscription Amplification A malicious subscriber could attempt to overwhelm a publisher or relay by requesting subscriptions to many tracks simultaneously. Relays SHOULD implement rate limiting on subscription requests and MAY reject excessive subscriptions with REQUEST_ERROR using the EXCESSIVE_LOAD error code. Publishers SHOULD monitor the number of active subscriptions and enforce limits to prevent resource exhaustion from a single subscriber or session. TODO: Describe Cache Poisoning attacks

Communication Security MOQT depends on a secure transport to provide confidentiality, integrity and endpoint authentication between subscriber and publisher. Implementations use QUIC or WebTransport to fulfill the basic communication security requirements and these implementations SHOULD follow best practices for TLS 1.3 and QUIC. Relays MUST use authentication to prevent impersonation (). Note that the basic security protection offered by QUIC or TCP/TLS does not prevent traffic pattern analysis. Object sizes, sizes of request messages, etc can make it possible for a third party observer to identify media content, user patterns and media stream origin.

Authorization MOQT supports authorization via mutual TLS (mTLS) for endpoint identification and via token-based schemes for fine-grained, application-defined access control. The two mechanisms can be used together.

Mutual TLS In mutual TLS, both peers present an X.509 certificate during the TLS 1.3 handshake (), carried in the underlying transport. An endpoint that verifies a server certificate does so following . An application that authenticates clients via mTLS defines how a client certificate maps to identity. Once a peer is authenticated, an application MAY use attributes in the peer's certificate as an input to authorization decisions; the granularity and policy of such authorization is out of scope for this document. ### Authorization Tokens {#sec-tokens} MOQT has functionality to carry Authorization tokens as message parameters. These tokens can vary based on the application requirements. Two variants of authorization tokens have already been defined for MOQT, and more are expected in the future. The current tokens are Privacy Pass Authentication for Media over QUIC and Authentication scheme for MOQT using Common Access Tokens . Tokens are expected to contain information about which actions and which resources the endpoint providing the token is authorized to perform and access. Relays will verify the token to ensure that the request is authorized.

Replay Attacks Replay protection for authorization tokens is the responsibility of the specific token scheme used. Token schemes such as and include requirements for relays when processing tokens and requests.

Preventing Impersonation A relay MUST ensure that a client cannot publish to namespaces or tracks belonging to another identity. Impersonation occurs when a client publishes objects that appear to originate from a different publisher — for example, by targeting a namespace containing another user's identifier. To prevent impersonation, a relay MUST verify that the authenticated identity or token scope permits publishing to the specific namespace. The mapping from authenticated identity to permitted namespaces is determined by the authorization framework in use. When using bearer token-based authentication (e.g., ), a token that is bound to a client-held key via a confirmation claim prevents a stolen token from being replayed by a different party. When unlinkable access is used (e.g., ), the token's scope extensions determine which namespaces the bearer can publish to. Impersonation is still prevented because the token does not grant access beyond its defined scope. A relay that does not enforce these checks allows any connected client to inject content into arbitrary namespaces, breaking the integrity of content delivery.

Media Security MOQT uses secure transports that provide confidentiality and integrity protection. However, media objects are accessible to relays, and are subject to both intentional and accidental modification, unless they are additionally end-to-end protected. The media objects transported by MOQT in various tracks from various original publishers are subject to several considerations. The first is source authenticity, i.e. to know that the received media objects are what the original publisher actually published. In addition to the media objects, it can also be important to authenticate some Track and Object Properties. For example, timestamps are crucial to understand where on the timeline this media fragment belongs. The second aspect is content confidentiality. Beyond direct relay access to media objects, object sizes and traffic patterns enable analysis of content. Track namespace and track name can also be analyzed and correlated between end subscribers by relays. Consistent with the principle of confidential operation by default, publishers can apply end-to-end object encryption, for example using Secure Objects (), so that relays retain access only to the metadata required for forwarding. Such end-to-end security mechanisms are external to this specification and additionally provide source authenticity. MOQT's object model enables both the object data and Object Properties to be confidentiality and integrity protected, or integrity protected only. Secure key distribution for end-to-end encryption is specific to the encryption system and deployment, and outside the scope of this document.

Resource Exhaustion Live content requires significant bandwidth and resources. Failure to set limits will quickly cause resource exhaustion. MOQT uses stream limits and flow control to impose resource limits at the network layer. Endpoints SHOULD set flow control limits based on the anticipated bitrate. Endpoints MAY impose a MAX STREAM count limit which would restrict the number of concurrent streams which an application could have in flight. The publisher prioritizes and transmits streams out of order. Streams might be starved indefinitely during congestion. The publisher and subscriber MUST cancel a stream, preferably the one with the lowest priority, after reaching a resource limit.

Timeouts Implementations are advised to use timeouts to prevent resource exhaustion attacks by a peer that does not send expected data within an expected time. Each implementation is expected to set its own timeouts.

Idle Connection Handling The transport connection (e.g., QUIC) underlying a MOQT session can close due to idle timeout if no data is exchanged, either because there are no established subscriptions or the established subscriptions are not publishing Objects frequently. This includes publisher sessions that have issued a PUBLISH_NAMESPACE and are waiting for subscribers. Implementations that want to keep idle sessions open have several options:

Use transport-layer keep-alive mechanisms, such as QUIC PING frames, to prevent idle timeout closure.
Send periodic control messages, for example REQUEST_UPDATE with no modified Message Parameters.
Accept that idle connections can close and implement reconnection logic when needed.

The choice of mechanism is implementation-specific.

Relay security considerations

State maintenance A Relay SHOULD have mechanisms to prevent malicious endpoints from flooding it with PUBLISH_NAMESPACE, SUBSCRIBE_NAMESPACE, or SUBSCRIBE_TRACKS requests that could bloat data structures. It could use QUIC stream limits to limit the number of such requests, or could have application-specific policies that can reject incoming requests that cause the state maintenance for the session to be excessive.

SUBSCRIBE_NAMESPACE and SUBSCRIBE_TRACKS with short prefixes A Relay can use authorization rules in order to prevent subscriptions closer to the root of a large prefix tree. Otherwise, if an entity sends a relay a SUBSCRIBE_NAMESPACE or SUBSCRIBE_TRACKS message with a short prefix, it can cause the relay to send a large volume of NAMESPACE or PUBLISH messages. As changes occur in the tree of namespaces, the relay would have to send matching NAMESPACE/NAMESPACE_DONE messages or initiate new PUBLISH streams.

Implementation Identification Fingerprinting The MOQT_IMPLEMENTATION option () can reveal information that contributes to fingerprinting, a set of techniques for identifying a specific endpoint over time through its unique set of characteristics. Detailed implementation information, including specific version numbers, build identifiers, or platform details, can create a unique fingerprint that enables tracking endpoints across sessions without their awareness. When combined with other session characteristics, even minimal implementation identification can contribute to distinguishing one endpoint from another. To mitigate fingerprinting risks:

Implementations SHOULD send only the minimum information necessary for interoperability debugging. A short implementation name and major version number are typically sufficient.
Implementations SHOULD NOT include detailed system information, build numbers, or other attributes that could uniquely identify a specific instance or user.
Privacy-conscious deployments MAY omit the MOQT_IMPLEMENTATION option entirely or send a generic value.
Implementations MAY provide users with the ability to configure or disable the MOQT_IMPLEMENTATION option.

Operators are advised that detailed implementation identification facilitates the same privacy concerns as persistent identifiers, since it enables correlation of sessions across time.

Logging of Untrusted String Fields The Reason Phrase () and MOQT_IMPLEMENTATION option () carry sender-controlled text that is commonly written to logs. Even though these fields are UTF-8 encoded, an endpoint that logs or renders them SHOULD sanitize them first (for example, by escaping bytes outside the printable ASCII range), since unsanitized values can enable log injection or terminal escape sequence injection.

IANA Considerations TODO: fill out currently missing registries:

MOQT ALPN values
Message types
Session-Level Track Names

URI Scheme Registrations This document requests the registration of the following URI schemes in the "Uniform Resource Identifier (URI) Schemes" registry, per :

"moqt" URI Scheme Registration Scheme name: moqt Status: Permanent Applications/protocols that use this scheme name: Media over QUIC Transport (MOQT) over native QUIC or WebTransport, as defined in this document. Contact: IETF MoQ Working Group (moq@ietf.org) Change controller: IETF References: This document

Media Type Registration This document registers the following media type in the "Media Types" registry : Type name: application Subtype name: moqt Required parameters: N/A Optional parameters: N/A Encoding considerations: This media type is used to identify resources accessed via the moqt URI scheme. It is not used to label the content of MOQT objects, which are defined by separate media types in application-specific specifications. Security considerations: See the Security Considerations section of this document. Interoperability considerations: N/A Published specification: This document Applications that use this media type: Implementations of the Media over QUIC Transport (MOQT) protocol. Fragment identifier considerations: Fragment identifiers for application/moqt follow the syntax defined in . Additional information: N/A Contact: IETF MoQ Working Group (moq@ietf.org) Change controller: IETF

MOQT URI Fragment Types This document establishes the "MOQT URI Fragment Types" registry. This registry governs fragment type identifiers used in moqt URI fragments as defined in . New fragment type identifiers are registered using the Specification Required policy (). Each entry in the registry contains the following fields: | Fragment Type | Description | Specification | |:--------------|:------------|:--------------| This registry is initially empty.

Setup Options

Type	Name	Specification
0x01	PATH
0x03	AUTHORIZATION_TOKEN
0x04	MAX_AUTH_TOKEN_CACHE_SIZE
0x05	AUTHORITY
0x06	MAX_FILTER_RANGES
0x07	MOQT_IMPLEMENTATION
0x08	MAX_REQUEST_UPDATES
0x7f * N + 0x9D	Reserved for greasing

Endpoints MUST ignore unknown Setup Options as specified in . New Setup Option types are registered using the Specification Required policy (). Provisional registrations are permitted to allow experimentation and avoid codepoint collisions between independent implementations. There is no reserved range for private or application-specific use; implementations that need custom Setup Options SHOULD request a provisional registration.

Authorization Token Alias Type

Code	Name	Specification
0x0	DELETE
0x1	REGISTER
0x2	USE_ALIAS
0x3	USE_VALUE

MOQT Auth Token Type

Code	Name	Specification
0x0	Reserved
0x7f * N + 0x9D	Reserved for greasing

Message Parameters

Parameter Type	Parameter Name	Specification
0x02	OBJECT_DELIVERY_TIMEOUT
0x03	AUTHORIZATION_TOKEN
0x04	RENDEZVOUS_TIMEOUT
0x06	SUBGROUP_DELIVERY_TIMEOUT
0x08	EXPIRES
0x09	LARGEST_OBJECT
0x0A	FILL_TIMEOUT
0x10	FORWARD
0x20	SUBSCRIBER_PRIORITY
0x21	LOCATION_FILTER
0x22	GROUP_ORDER
0x23	FILL_PARAMETERS
0x25	SUBGROUP_FILTER
0x26	OBJECTID_FILTER
0x27	PRIORITY_FILTER
0x28	OBJECT_PROPERTY_FILTER
0x29	TRACK_PROPERTY_FILTER
0x32	NEW_GROUP_REQUEST
0x34	TRACK_NAMESPACE_PREFIX
0x35	INCLUDE_PROPERTIES

Message Parameters - List which params can be repeated in the table.

Properties

Type	Name	Scope
0x02	OBJECT_DELIVERY_TIMEOUT	Track, Object
0x04	MAX_CACHE_DURATION	Track
0x06	SUBGROUP_DELIVERY_TIMEOUT	Track, Object
0x0B	IMMUTABLE_PROPERTIES	Track, Object
0x0E	DEFAULT_PUBLISHER_PRIORITY	Track
0x22	DEFAULT_PUBLISHER_GROUP_ORDER	Track
0x30	DYNAMIC_GROUPS	Track
0x3C	PRIOR_GROUP_ID_GAP	Object
0x3E	PRIOR_OBJECT_ID_GAP	Object
0x7f * N + 0x9D	Reserved for greasing	Any

The following table contains provisional registrations for other active drafts in the moq wg. These entries share the same Property Type space as the table above.

Type	Name	Scope	Specification
0x10	TIMESTAMP	Object	draft-ietf-moq-loc
0x08	TIMESCALE	Track, Object	draft-ietf-moq-loc
0x09	VIDEO_FRAME_MARKING	Object	draft-ietf-moq-loc
0x0C	AUDIO_LEVEL	Object	draft-ietf-moq-loc
0x0D	VIDEO_CONFIG	Track, Object	draft-ietf-moq-loc
0x0F	AUDIO_CONFIG	Track, Object	draft-ietf-moq-loc
0x0A	ENCRYPTED_LIST	Object	draft-ietf-moq-secure-objects
0x32	PADDING	Object	draft-ietf-moq-secure-objects

Endpoints MUST ignore unknown Property types, skipping them according to the Key-Value-Pair encoding; odd types use their length field, even types are skipped by parsing a variable-length integer value.

MOQ Properties - we wish to define the following registration policies:
- 0x00 to 0x77: Standards Action or IESG Approval (1-byte encoding)
- 0x78 to 0x7F: Reserved for application-specific use (1-byte encoding, no registration permitted)
- 0x80 to 0x37FF: Specification Required (2-byte encoding)
- 0x3800 to 0x3FFF: Reserved for application-specific use (2-byte encoding, no registration permitted)
- 0x4000 to 0x7FFF: Reserved for Mandatory Track Properties (see ). Properties registered in this range MUST have Track scope; Object scope properties MUST NOT be registered in this range.
- 0x8000 and above: First Come First Served
Code points reserved for application-specific use will never be allocated by IANA. Applications using these values do not need to coordinate with IANA. Note that applications consuming tracks from uncoordinated sources may encounter different semantics for the same code points, creating potential collision risks.

Object Status This document establishes a registry for Object Status values (see ). The "Payload" column indicates whether an Object with that status is permitted to carry a non-empty payload.

Code	Name	Payload
0x0	Normal	Yes
0x3	End of Group	No
0x4	End of Track	No

New Object Status values are registered using the Specification Required policy (). Each registration MUST indicate whether the status permits a payload.

Session-Level Track Names This document establishes a registry for session-level track names under the .session namespace (see ). The registration policy is Specification Required (per ). Each registration must include:

Field	Description
Track Namespace	The track namespace under the `.session` namespace, can be empty
Track Name	The track name (bytes) within the full namespace
Description	Brief description of the track's purpose
Change Controller	Who may update the registration
Specification	Reference to the defining specification

This document does not define any initial entries.

Error Codes

Session Termination Error Codes

Name	Code	Specification
NO_ERROR	0x0
INTERNAL_ERROR	0x1
UNAUTHORIZED	0x2
PROTOCOL_VIOLATION	0x3
INVALID_REQUEST_ID	0x4
DUPLICATE_TRACK_ALIAS	0x5
KEY_VALUE_FORMATTING_ERROR	0x6
INVALID_PATH	0x8
MALFORMED_PATH	0x9
GOAWAY_TIMEOUT	0x10
CONTROL_MESSAGE_TIMEOUT	0x11
DATA_STREAM_TIMEOUT	0x12
AUTH_TOKEN_CACHE_OVERFLOW	0x13
DUPLICATE_AUTH_TOKEN_ALIAS	0x14
MALFORMED_AUTH_TOKEN	0x16
UNKNOWN_AUTH_TOKEN_ALIAS	0x17
EXPIRED_AUTH_TOKEN	0x18
INVALID_AUTHORITY	0x19
MALFORMED_AUTHORITY	0x1A
TOO_MANY_REQUEST_UPDATES	0x1B
Reserved for greasing	0x7f * N + 0x9D

REQUEST_ERROR Codes

Name	Code	Specification
INTERNAL_ERROR	0x0
UNAUTHORIZED	0x1
TIMEOUT	0x2
NOT_SUPPORTED	0x3
MALFORMED_AUTH_TOKEN	0x4
EXPIRED_AUTH_TOKEN	0x5
GOING_AWAY	0x6
EXCESSIVE_LOAD	0x9
DOES_NOT_EXIST	0x10
INVALID_RANGE	0x11
MALFORMED_TRACK	0x12
UNINTERESTED	0x20
PREFIX_OVERLAP	0x30
NAMESPACE_TOO_LARGE	0x31
UNSUPPORTED_EXTENSION	0x33
REDIRECT	0x34
CONFLICTING_FILTERS	0x35
INVALID_FILTER	0x36
Reserved for greasing	0x7f * N + 0x9D

PUBLISH_DONE Codes

Name	Code	Specification
INTERNAL_ERROR	0x0
UNAUTHORIZED	0x1
TRACK_ENDED	0x2
GOING_AWAY	0x4
TOO_FAR_BEHIND	0x5
EXPIRED	0x6
UPDATE_FAILED	0x8
EXCESSIVE_LOAD	0x9
MALFORMED_TRACK	0x12
Reserved for greasing	0x7f * N + 0x9D

Stream Reset Error Codes

Name	Code	Specification
INTERNAL_ERROR	0x0
CANCELLED	0x1
DELIVERY_TIMEOUT	0x2
SESSION_CLOSED	0x3
GOING_AWAY	0x4
TOO_FAR_BEHIND	0x5
UNKNOWN_OBJECT_STATUS	0x6
EXPIRED_AUTH_TOKEN	0x7
EXCESSIVE_LOAD	0x9
MALFORMED_TRACK	0x12
Reserved for greasing	0x7f * N + 0x9D

Contributors The original design behind this protocol was inspired by three independent proposals: WARP by Luke Curley, RUSH by Kirill Pugin, Nitin Garg, Alan Frindell, Jordi Cenzano and Jake Weissman, and QUICR by Cullen Jennings, Suhas Nandakumar and Christian Huitema. The authors of those documents merged their proposals to create the first draft of moq-transport. The IETF MoQ Working Group received an enormous amount of support from many people. The following people provided substantive contributions to this document:

Ali Begen
Charles Krasic
Christian Huitema
Cullen Jennings
James Hurley
Jordi Cenzano
Kirill Pugin
Luke Curley
Martin Duke
Mike English
Mo Zanaty
Will Law

Use of Generative AI Generative AI tools were used to assist with drafting and editing text for this document. All AI-generated content was reviewed and approved by the editors.

References Normative References QUIC: A UDP-Based Multiplexed and Secure Transport This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm. WebTransport over HTTP/3 Meta Apple Inc. Google WebTransport over HTTP/3 is a binding of the WebTransport protocol framework [OVERVIEW] to HTTP/3 [HTTP3]. It provides support for unidirectional streams, bidirectional streams, and datagrams, all multiplexed within the same HTTP/3 connection. WebTransport enables application clients constrained by the Web security model to communicate with a remote application server using a secure multiplexed transport. Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. QUIC Stream Resets with Partial Delivery Fastly QUIC defines a RESET_STREAM frame to abort sending on a stream. When a sender resets a stream, it also stops retransmitting STREAM frames for this stream in the event of packet loss. On the receiving side, there is no guarantee that any data sent on that stream is delivered. This document defines a new QUIC frame, the RESET_STREAM_AT frame, that allows resetting a stream, while guaranteeing delivery of stream data up to a certain byte offset. The WebTransport Protocol Framework Apple Inc. Google The WebTransport Protocol Framework enables clients constrained by the Web security model to communicate with a remote server using a secure multiplexed transport. It consists of a set of individual protocols that are safe to expose to untrusted applications, combined with an abstract model that allows them to be used interchangeably. This document defines the overall requirements on the protocols used in WebTransport, as well as the common features of the protocols, support for some of which is optional. Uniform Resource Identifier (URI): Generic Syntax A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK] Well-Known Uniform Resource Identifiers (URIs) This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes. In doing so, it obsoletes RFC 5785 and updates the URI schemes defined in RFC 7230 to reserve that space. It also updates RFC 7595 to track URI schemes that support well-known URIs in their registry. An Unreliable Datagram Extension to QUIC This document defines an extension to the QUIC transport protocol to add support for sending and receiving unreliable datagrams over a QUIC connection. Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension This document describes a Transport Layer Security (TLS) extension for application-layer protocol negotiation within the TLS handshake. For instances in which multiple application protocols are supported on the same TCP or UDP port, this extension allows the application layer to negotiate which protocol will be used within the TLS connection. UTF-8, a transformation format of ISO 10646 ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279. Guidelines and Registration Procedures for URI Schemes This document updates the guidelines and recommendations, as well as the IANA registration processes, for the definition of Uniform Resource Identifier (URI) schemes. It obsoletes RFC 4395. Media Type Specifications and Registration Procedures This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice. Guidelines for Writing an IANA Considerations Section in RFCs Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226. Informative References Authorization scheme for MOQT using Common Access Tokens Akamai Comcast Synamedia Cisco A token-based authorization scheme for use with Media Over QUIC Transport. Privacy Pass Authentication for Media over QUIC (MoQ) Cisco Cisco Cloudflare Inc. This document specifies the use of Privacy Pass architecture and issuance protocols for authorization in Media over QUIC (MoQ) transport protocol. It defines how Privacy Pass tokens can be integrated with MoQ's authorization framework to provide privacy- preserving authentication for subscriptions, fetches, publications, and relay operations while supporting fine-grained access control through prefix-based track namespace and track name matching rules. End-to-End Secure Objects for Media over QUIC Transport Cisco Cisco Cisco This document specifies an end-to-end authenticated encryption scheme for application objects transmitted via Media over QUIC (MoQ) Transport. The scheme enables original publishers that share a symmetric key with end subscribers, to ensuring that MoQ relays are unable to decrypt object contents. Additionally, subscribers can verify the integrity and authenticity of received objects, confirming that the content has not been modified in transit. Additionally it allows MoQ parameters to be protected so the publisher can select if they are readable and/or modifiable by relays. QUIC: A UDP-Based Multiplexed and Secure Transport This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm. OpenPGP This document specifies the message formats used in OpenPGP. OpenPGP provides encryption with public key or symmetric cryptographic algorithms, digital signatures, compression, and key management. This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not a step-by-step cookbook for writing an application. It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network. It does not deal with storage and implementation questions. It does, however, discuss implementation issues necessary to avoid security flaws. This document obsoletes RFCs 4880 ("OpenPGP Message Format"), 5581 ("The Camellia Cipher in OpenPGP"), and 6637 ("Elliptic Curve Cryptography (ECC) in OpenPGP"). Domain names - implementation and specification This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication. DNS Extensions to Support IP Version 6 This document defines the changes that need to be made to the Domain Name System (DNS) to support hosts running IP version 6 (IPv6). The changes include a resource record type to store an IPv6 address, a domain to support lookups based on an IPv6 address, and updated definitions of existing query types that return Internet addresses as part of additional section processing. The extensions are designed to be compatible with existing applications and, in particular, DNS implementations themselves. [STANDARDS-TRACK] Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records) This document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR) types to facilitate the lookup of information needed to make connections to network services, such as for HTTP origins. SVCB records allow a service to be provided from multiple alternative endpoints, each with associated parameters (such as transport protocol configuration), and are extensible to support future uses (such as keys for encrypting the TLS ClientHello). They also enable aliasing of apex domains, which is not possible with CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see RFC 9110, "HTTP Semantics"). By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy. The Transport Layer Security (TLS) Protocol Version 1.3 This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. Using Early Data in HTTP Using TLS early data creates an exposure to the possibility of a replay attack. This document defines mechanisms that allow clients to communicate with servers about HTTP requests that are sent in early data. Techniques are described that use these mechanisms to mitigate the risk of replay. Long-Term Viability of Protocol Extension Mechanisms The ability to change protocols depends on exercising the extension and version-negotiation mechanisms that support change. This document explores how regular use of new protocol features can ensure that it remains possible to deploy changes to a protocol. Examples are given where lack of use caused changes to be more difficult or costly. CUBIC for Fast and Long-Distance Networks CUBIC is a standard TCP congestion control algorithm that uses a cubic function instead of a linear congestion window increase function to improve scalability and stability over fast and long-distance networks. CUBIC has been adopted as the default TCP congestion control algorithm by the Linux, Windows, and Apple stacks. This document updates the specification of CUBIC to include algorithmic improvements based on these implementations and recent academic work. Based on the extensive deployment experience with CUBIC, this document also moves the specification to the Standards Track and obsoletes RFC 8312. This document also updates RFC 5681, to allow for CUBIC's occasionally more aggressive sending behavior. The NewReno Modification to TCP's Fast Recovery Algorithm RFC 5681 documents the following four intertwined TCP congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. RFC 5681 explicitly allows certain modifications of these algorithms, including modifications that use the TCP Selective Acknowledgment (SACK) option (RFC 2883), and modifications that respond to "partial acknowledgments" (ACKs that cover new data, but not all the data outstanding when loss was detected) in the absence of SACK. This document describes a specific algorithm for responding to partial acknowledgments, referred to as "NewReno". This response to partial acknowledgments was first proposed by Janey Hoe. This document obsoletes RFC 3782. [STANDARDS-TRACK] Standard Communication with Network Elements (SCONE) Protocol Mozilla Private Octopus Inc. Fastly Meta Ericsson This document describes a protocol where on-path network elements can communicate their perspective on the maximum sustainable throughput for QUIC flows to endpoints. This throughput advice suggests an upper bound on long-term average throughput, independent of and complementary to real-time congestion control signals. Service Identity in TLS Many application technologies enable secure communication between two entities by means of Transport Layer Security (TLS) with Internet Public Key Infrastructure using X.509 (PKIX) certificates. This document specifies procedures for representing and verifying the identity of application services in such interactions. This document obsoletes RFC 6125. Warp - Live Media Transport over QUIC Twitch Meta Cisco Google This document defines the core behavior for Warp, a live media transport protocol over QUIC. Media is split into objects based on the underlying media encoding and transmitted independently over QUIC streams. QUIC streams are prioritized based on the delivery order, allowing less important objects to be starved or dropped during congestion. RUSH - Reliable (unreliable) streaming protocol Meta Meta Meta Meta Meta RUSH is an application-level protocol for ingesting live video. This document describes the protocol and how it maps onto QUIC. Discussion Venues This note is to be removed before publishing as an RFC. Discussion of this document takes place on the mailing list (), which is archived at . Source for this draft and an issue tracker can be found at https://github.com/afrind/draft-rush. QuicR - Media Delivery Protocol over QUIC cisco Cisco Private Octopus Inc. Recently new use cases have emerged requiring higher scalability of media delivery for interactive realtime applications and much lower latency for streaming applications and a combination thereof. draft-jennings-moq-arch specifies architectural aspects of QuicR, a media delivery protocol based on publish/subscribe metaphor and Relay based delivery tree, that enables a wide range of realtime applications with different resiliency and latency needs. This specification defines the protocol aspects of the QuicR media delivery architecture.

Change Log RFC Editor's Note: Please remove this section prior to publication of a final version of this document. Issue and pull request numbers are listed with a leading octothorp.

Since draft-ietf-moq-transport-20 Notable Editorial Changes

Add a Document Structure section (#1903)
Move-only restructuring across the document (#1877)
Restructure and reorder Publishing and Receiving Tracks (#1885, #1893)
Move Error Handling and Grease ahead of the considerations sections (#1899)
Promote each Setup Option to its own section (#1896)
Collect Session Termination, Request Error, and Publish Done codes into Error Handling (#1879, #1880, #1881)
Extract common wire format sections: Authorization Token Compression, Track Namespace, Location Filter, and Range Filter (#1882, #1887, #1888, #1892)
Remove the Connection URL, Stream Cancellation, and Examples sections (#1878)
Restructuring pull requests that also made editorial clarifications are included as moves only; the clarifications are deferred (#1887, #1888, #1892)

Since draft-ietf-moq-transport-19 Session and Control Plane

Replace Joining FETCH with fill fetch streams (#1673)
- Add the FILL_PARAMETERS parameter, whose presence on a subscription requests a fill; it carries a sequence of Parameters (#1868)
- Remove the Joining variant of FETCH and the "standalone" moniker
Restructure the Location Filter to match the other filter parameters, and carry the FETCH range in LOCATION_FILTER instead of message fields (#1809)
Add PUBLISH_STATE_NOTIFY message (#1820)
Add INCLUDE_PROPERTIES parameter (#1813, #1847)
PUBLISH can carry Subscription Parameters, and AUTHORIZATION TOKEN is never copied from SUBSCRIBE_TRACKS (#1834)
Subscription parameters appear in REQUEST_UPDATE, not PUBLISH_OK (#1790)
Allow FORWARD on a REQUEST_UPDATE for SUBSCRIBE_TRACKS (#1812)
Remove PUBLISH_DONE status code SUBSCRIPTION_ENDED; a subscription does not end because Largest Object passes the end of the Location Filter (#1833)
Change the maximum Stream Count in PUBLISH_DONE to 2^64 - 1 (#1831)
Remove the requirement for a publisher to retain Largest Location (#1872)
Remove the VERSION_NEGOTIATION_FAILED session error (#1867)
A relay MUST send an upstream FETCH to at least one publisher (#1804)
Discuss the tradeoffs of aggregating downstream filters onto an upstream subscription (#1735)
Resolve REDIRECT ambiguity with empty Track Namespace and Track Name (#1824)
Clarify Retry Interval of 0 with REDIRECT (#1785)
Define host resolution for moqt URIs (#1817)
Exclude the URI query component from the MOQT scope (#1855)
SUBSCRIBE_TRACKS Parameters are the publisher's initial Subscription parameters and are explicitly communicated in the resulting PUBLISH (#1815, #1869)

Data Plane Wire Format and Handling

Describe OBJECT_DATAGRAM and SUBGROUP_HEADER types as Type Flags bitfields; a set bit with no specified meaning is a PROTOCOL_VIOLATION (#1774)
Add End of Timed-Out Range for Objects abandoned when Fill Timeout expires (#1822)
OBJECT_DELIVERY_TIMEOUT starts at the last header byte instead of the first payload byte (#1844)
Define scheduling between fill-delivered and subscription-delivered Objects (#1673)
Beware re-using a Track Alias for concurrent subscriptions (#1856)

Security Considerations

Add a Preventing Impersonation section (#1737, #1789)
Expand mutual TLS and authorization guidance (#1786)
Add moqt URI scheme security considerations (#1772)
Add a security consideration for logging untrusted string fields (#1823)
Recommend end-to-end object encryption for confidentiality from relays (#1755)

Notable Editorial Changes

Clarify the Range Filters section for readability (#1851)
Note that the recommended name encoding is not guaranteed filename-safe (#1863)
Fix LOC and Secure Objects entries in the provisional Property registry (#1807, #1818, #1848)

Since draft-ietf-moq-transport-18 Session and Control Plane

Add Range Filters that can filter Objects from Subscriptions and SUBSCRIBE_TRACKS (#1765)
Add MAX_REQUEST_UPDATES Setup Option and TOO_MANY_REQUEST_UPDATES error (#1613)
Allow multiple concurrent subscriptions per Track (#1775)
Move GROUP_ORDER from PUBLISH_OK to SUBSCRIBE_TRACKS (#1777)
Rename PUBLISH_BLOCKED to PUBLISH_SKIPPED (#1779)
Remove Request ID from GOAWAY (#1623)
Clarify session vs. per-request GOAWAY migration (#1787)
Define FIN vs. RST/STOP_SENDING semantics on request streams (#1698)
Unexpected REQUEST_UPDATE is a session error (#1784)
Update Forward State handling for relays (#1782)
Clarify authorization trust model for namespace subscriptions (#1656)
Clarify namespace discovery and NAMESPACE sending (#1710)

Data Plane Wire Format and Handling

Delivery timeouts are both Track and Object Properties (#1476)
Make the Object Status payload rule extensible via IANA registry (#1760)
Datagrams take precedence in cross-forwarding-preference scheduling ties (#1780)
Remove relay exception for reordering or dropping objects (#1762)
Specify relay processing rules for known Track Properties (#1771)
Recommend Immutable Properties for relay-visible, unmodifiable data (#1759)

Notable Editorial Changes

Rename control Message Payload field to Message Body (#1756)
Clarify Group and Subgroup terminology and object model (#1708)

Since draft-ietf-moq-transport-17 Session and Control Plane

Unified moqt:// URI scheme for QUIC and WebTransport (#1486)
Add fragment identifier support for moqt URIs (#1571)
Split SUBSCRIBE_NAMESPACE into SUBSCRIBE_NAMESPACE and SUBSCRIBE_TRACKS (#1542)
Remove Required Request ID (#1615)
Add REDIRECT for request errors and established subscriptions (#1534)
Allow GOAWAY on request streams to migrate individual requests (#1617)
Add Request ID to GOAWAY (#1559)
Remove PUBLISH_OK message type, make it a REQUEST_OK alias (#1611)
Generalize stream reset codes to all request streams, add new codes, align with PUBLISH_DONE (#1606)
Add Track Properties to REQUEST_OK (#1576)
Add support for mandatory-to-understand track extensions (#1509)
Exclude your own tracks from SUBSCRIBE_NAMESPACE (#1596)
Add Session-Level Tracks reserved namespace (#1562)
Allow coalescing REQUEST_UPDATE processing (#1540)
SUBSCRIBE takes precedence over SUBSCRIBE_NAMESPACE at relay (#1533)
Don't close the Session for unknown errors (#1561)
Clarify REQUEST_UPDATE failure behavior for all request types (#1539)
Clarify SUBSCRIBE_NAMESPACE stream closure semantics (#1541)
FETCH to a track with no objects returns INVALID_RANGE (#1537)
Clarify FETCH_OK End Location semantics (#1536)
Clarify definition of scope (#1629)
Clarify Joining Fetch behavior:
- Joining FETCH is unaffected by forward changing to 0 (#1620)
- Joining Fetch forward state mismatch is a request error (#1609)
- Clarify Joining Fetch ordering with Forward State transitions (#1577)

Data Plane Wire Format and Handling

Make Object ID and Group ID delta encoded in Fetch responses (#1586)
Add FIRST_OBJECT bit to SUBGROUP_HEADER type (#1618)
Split DELIVERY_TIMEOUT into two types of timeout (#1605)
FILL_TIMEOUT parameter (#1490)
Forbid relays from lying about LARGEST_OBJECT (#1621)
Allow publisher to reopen subgroup after REQUEST_UPDATE forward 0->1 (#1583)
Allow 7-byte varint and non-minimal encodings (#1595)
Padding streams and datagrams (#1475)
Close session when delta encoding wraps (#1560)

Notable Editorial Changes

Clarify Object existence and cross-source contradictions (#1566)
Clarify immutable track properties (#1535)
Improve Startup Latency and 0-RTT guidance (#1544)
Improve Security Considerations section (#1625)
Rewrite abstract and introduction (#1556)
Define textual aliases for REQUEST_OK by request type (#1610)
Add IANA registry for Setup Options (#1564)
Add provisional registry for LOC properties (#1624)
Update MOQ Properties registration policies (#1525)
Add stream type column to message type table (#1555)
Fix grease examples to match 0x7f multiplier (#1569)

Since draft-ietf-moq-transport-16 Session and Control Plane

Change control stream from bidi to a pair of uni streams (#1510)
Collapse CLIENT_SETUP and SERVER_SETUP into a single SETUP message (#1510)
Move requests to bidirectional streams; remove cancel messages (#1389)
Remove MAX_REQUEST_ID/REQUESTS_BLOCKED (#1471)
New variable-length integer encoding (#1016)
Encode Message Parameters as Type-Value pairs (#1462)
Add GREASE for Setup Options, Properties, and error code registries (#1460)
Add RENDEZVOUS_TIMEOUT parameter for SUBSCRIBE (#1447)
Add PUBLISH_BLOCKED message for SUBSCRIBE_NAMESPACE flow control (#1452)
Add Timeout field to GOAWAY message (#1497)
Add GOING_AWAY to REQUEST_ERROR codes (#1434)
Add EXCESSIVE_LOAD error code (#1479)
Add NAMESPACE_TOO_LARGE error and stream reset for large namespaces (#1496)
Add TOO_FAR_BEHIND stream reset code (#1445)
Add REQUEST_UPDATE to list of REQUEST_ERROR causes (#1466)
Enforce REQUEST_OK/ERROR as first message on the response stream (#1499)
Allow joining FETCH for PUBLISH and REQUEST_UPDATE with forward=1 (#1335)
Allow DELIVERY_TIMEOUT value of 0 to mean no timeout (#1450)
Allow zero-element namespaces (#1472)
Clarify EXPIRES parameter update mechanism (#1448)
Remove TRACK_STATUS from REQUEST_UPDATE (#1436)
Define how to use auth token cache safely with multiple streams (#1430)
Constrain encoding/parsing of track namespace and names (#1512)
Reserve Property type ranges for application-specific use (#1473)
Make EndGroup in Subscription Filters a delta (#1470)
Copy DELIVERY_TIMEOUT min requirement from parameter to property (#1427)

Data Plane Wire Format and Handling

Clarify prior Object semantics after End of Range indicators in FETCH (#1513)
Clarify datagram status and properties cases (#1444)
Clarify Stream Count includes empty subgroups (#1449)
Clarify language for malformed tracks in a subgroup with END_OF_GROUP (#1464)
Properties can appear in mutable list or inside Immutable Properties (#1442)
Clarify immutable property preservation requirements (#1441)
Clarification for Track Alias uniqueness (#1418)

Notable Editorial Changes

Rename Setup Parameters to Setup Options (#1461)
Rename Extension Headers to Properties (#1504)
Add security/privacy considerations for MOQT_IMPLEMENTATION (#1511)
Add editorial text on bandwidth probing techniques (#1477)
Explain idle connection handling (#1443)
Fix "SUBSCRIBE_NAMESPACE with short prefixes" (#1502)
Add generative AI disclosure per IRTF guidelines

Since draft-ietf-moq-transport-15 Setup and Control Plane

Delta encode Key-Value-Pairs for Parameters and Headers (#1315)
Use Request ID in PUBLISH_NAMESPACE_{DONE/CANCEL} (#1329)
Remove delivery related params from TRACK_STATUS for Subscribers (#1325)
PUBLISH does not imply PUBLISH_NAMESPACE (#1364)
Allow Start Location to decrease in SUBSCRIBE_UPDATE (#1323)
Change SUBSCRIBE_UPDATE to REQUEST_UPDATE and expand ability to update (#1332)
Put SUBSCRIBE_NAMESPACE on a stream, make Namespaces and PUBLISH independent (#1344)
Require NAMESPACE before NAMESPACE_DONE (#1392)
Allow the '*' or the empty namespace in SUBSCRIBE_NAMESPACE (#1393)
Relays match SUBSCRIBE to both Tracks and Namespaces (#1397)
Clarify sending requests after sending GOAWAY (#1398)
Add Retry Interval to REQUEST_ERROR (#1339)
Add Extension Headers to PUBLISH, SUBSCRIBE_OK, and FETCH_OK (#1374)
Move track properties to extensions, scope parameters (#1390)
Add LARGEST_OBJECT parameter to TRACK_STATUS (#1367)
Duplicate subscription processing (#1341)
Address Track Name/Namespace edge cases (#1399)

Data Plane Wire Format and Handling

Enable mixing datagrams with streams in one track (#1350)
Clarify datagrams and subgroups (#1382)
Redo the way we deal with missing Objects and Object Status (#1342)
Allow unknown ranges in a FETCH response (#1331)
Do not reopen subgroups after delivery timeout or STOP_SENDING (#1396)
Clarify handling of unknown extensions (#1395)
Clarify Delivery Timeout for datagrams (#1406)
Disallow DELIVERY_TIMEOUT=0 (#1330)
Malformed track due to multiple priorities for one subgroup (#1317)

Notable Editorial Changes

Subscribers can migrate networks too (#1410)
Rename Version Specific Parameters to Message Parameters (#1411)
Clarify valid joining fetch subscription states (#1363)
Formatting names for logs (#1355)
A Publisher might not use the congestion window (#1408)

Since draft-ietf-moq-transport-14 Setup and Control Plane

Always use ALPN for version negotiation (#499)
Consolidate all the Error Message types (#1159)
Change MOQT IMPLEMENTATION code point to 0x7 (#1191)
Add Forward to SUBSCRIBE_NAMESPACE (#1220)
Parameters for Group Order, Subscribe Priority and Subscription Filter (redo) (#1273)
REQUEST_OK message (#1274)
Subscribe Update Acknowledgements (#1275)
Disallow DELETE and USE_ALIAS in CLIENT_SETUP (#1277)
Remove Expires field from SUBSCRIBE_OK (#1282)
Make Forward a Parameter (#1283)
Allow SUBSCRIBE_UPDATE to increase the end location (#1288)
Add default port for raw QUIC (#1289)
Unsubscribe Namespace should be linked to Subscribe Namespace (#1292)

Data Plane Wire Format and Handling

Fetch Object serialization optimization (#949)
Make default PUBLISHER PRIORITY a parameter, optional in Subgroup/Datagram (#1056)
Allow datagram status with object ID=0 (#1197)
Disallow object extension headers in all non-Normal status objects (#1266)
Objects for malformed track must not be cached (#1290)
Remove NO_OBJECTS fetch error code (#1303)
Clarify what happens when max_cache_duration parameter is omitted (#1287)

Notable Editorial Changes

Rename Request ID field in MAX_REQUEST_ID (#1250)
Define and draw subscription state machine (#1296)
Omitting a subgroup object necessitates reset (#1295)
Define duplication rules for header extensions (#1293)
Clarify joining fetch end location (#1286)

Since draft-ietf-moq-transport-13 Setup and Control Plane

Add an AUTHORITY parameter (#1058)
Add a free-form SETUP parameter identifying the implementation (#1114)
Add a Request ID to SUBSCRIBE_UDPATE (#1106)
Indicate which params can appear PUBLISH* messages (#1071)
Add TRACK_STATUS to the list of request types affected by GOAWAY (#1105)

Data Plane Wire Format and Handling

Delta encode Object IDs within Subgroups (#1042)
Use a bit in Datagram Type to convey Object ID = 0 (#1055)
Corrected missed code point updates to Object Datagram Status (#1082)
Merge OBJECT_DATAGRAM and OBJECT_DATAGRAM_STATUS description (#1179)
Objects are not schedulable if flow-control blocked (#1054)
Clarify DELIVERY_TIMEOUT reordering computation (#1120)
Receiving unrequested Objects (#1112)
Clarify End of Track (#1111)
Malformed tracks apply to FETCH (#1083)
Remove early FIN from the definition of malformed tracks (#1096)
Prior Object ID Gap Extension header (#939)
Add Extension containing immutable extensions (#1025)

Relay Handling

Explain FETCH routing for relays (#1165)
MUST for multi-publisher relay handling (#1115)
Filters don't (usually) determine the end of subscription (#1113)
Allow self-subscriptions (#1110)
Explain Namespace Prefix Matching in more detail (#1116)

Explanatory

Explain Modularity of MOQT (#1107)
Explain how to resume publishing after losing state (#1087)

Major Editorial Changes

Rename ANNOUNCE to PUBLISH_NAMESPACE (#1104)
Rename SUBSCRIBE_DONE to PUBLISH_DONE (#1108)
Major FETCH Reorganization (#1173)
Reformat Error Codes (#1091)

Since draft-ietf-moq-transport-12

TRACK_STATUS_REQUEST and TRACK_STATUS have changed to directly mirror SUBSCRIBE/OK/ERROR (#1015)
SUBSCRIBE_ANNOUNCES was renamed back to SUBSCRIBE_NAMESPACE (#1049)

Since draft-ietf-moq-transport-11

Move Track Alias from SUBSCRIBE to SUBSCRIBE_OK (#977)
Expand cases FETCH_OK returns Invalid Range (#946) and clarify fields (#936)
Add an error code to FETCH_ERROR when an Object status is unknown (#825)
Rename Latest Object to Largest Object (#1024) and clarify what to do when it's incomplete (#937)
Explain Malformed Tracks and what to do with them (#938)
Allow End of Group to be indicated in a normal Object (#1011)
Relays MUST have an upstream subscription to send SUBSCRIBE_OK (#1017)
Allow AUTHORIZATION TOKEN in CLIENT_SETUP, SERVER_SETUP and other fixes (#1013)
Add PUBLISH for publisher initiated subscriptions (#995) and fix the PUBLISH codepoints (#1048, #1051)

Since draft-ietf-moq-transport-10

Added Common Structure definitions - Location, Key-Value-Pair and Reason Phrase
Limit lengths of all variable length fields, including Track Namespace and Name
Control Message length is now 16 bits instead of variable length
Subscribe ID became Request ID, and was added to most control messages. Request ID is used to correlate OK/ERROR responses for ANNOUNCE, SUBSCRIBE_NAMESPACE, and TRACK_STATUS. Like Subscribe ID, Request IDs are flow controlled.
Explain rules for caching in more detail
Changed the SETUP parameter format for even number parameters to match the Object Header Extension format
Rotated SETUP code points
Added Parameters to TRACK_STATUS and TRACK_STATUS_REQUEST
Clarified how subscribe filters work
Added Next Group Filter to SUBSCRIBE
Added Forward flag to SUBSCRIBE
Renamed FETCH_OK field to End and clarified how to set it
Added Absolute Joining Fetch
Clarified No Error vs Invalid Range FETCH_ERROR cases
Use bits in SUBGROUP_HEADER and DATAGRAM* types to compress subgroup ID and extensions
Coalesced END_OF_GROUP and END_OF_TRACK_AND_GROUP status
Objects that Do Not Exist cannot have extensions when sent on the wire
Specified error codes for resetting data streams
Defined an Object Header Extension for communicating a known Group ID gap
Replaced AUTHORIZATION_INFO with AUTHORIZATION_TOKEN, which has more structure, compression, and additional Auth related error codes (#760)