§3.

Publishing and Receiving Tracks

Sections

§3.1. Subscriptions §3.2. Fetch §3.3. Filtering Tracks and Objects §3.4. Fill Semantics §3.5. Joining an Ongoing Track §3.6. Subscribing to Tracks by Prefix §3.7. Mandatory to Understand Track Properties

A subscription is a stateful ongoing relationship in which the Publisher delivers newly-published Objects from a single Track to the Subscriber. It can be established by either endpoint, via either SUBSCRIBE or PUBLISH. A subscription is active until either endpoint terminates it, and its parameters can be updated via REQUEST_UPDATE.

A fetch is a request for a bounded set of pre-existing Objects from a single Track. It is delivered on a single stream, and ends automatically when all of the objects are delivered.

This is one section of the MoQT specification, rendered per-section for quick reference and citation. The authoritative text is draft-ietf-moq-transport-22 at the IETF.

All draft-22 sections What is MoQT? Debug MoQT with moqtap