MoQ Solicit Extension rev 00 lands on the IETF Datatracker
This document defines an extension for MoQ Transport [moqt] that lets an endpoint declare that advertisements to it must be solicited first. An endpoint that declares nothing receives unsolicited PUBLISH_NAMESPACE, which is what a peer unaware of this extension implicitly asks for. An endpoint that will instead ask for what it wants says so once during setup, and is spared the advertisements it would otherwise have to ignore. Because sending the option at all identifies an endpoint that implements this extension, the requirement is enforceable between two such endpoints rather than merely advisory.
Draft Snapshot
- Draft:
draft-lcurley-moq-solicit - Revision: 00
- Last updated: 2026-09-24
- Source: IETF Datatracker
Summary
This document defines an extension for MoQ Transport [moqt] that lets an endpoint declare that advertisements to it must be solicited first. An endpoint that declares nothing receives unsolicited PUBLISH_NAMESPACE, which is what a peer unaware of this extension implicitly asks for. An endpoint that will instead ask for what it wants says so once during setup, and is spared the advertisements it would otherwise have to ignore. Because sending the option at all identifies an endpoint that implements this extension, the requirement is enforceable between two such endpoints rather than merely advisory.
Analysis
This draft is directly relevant to the MOQ ecosystem and worth tracking because it reflects current protocol work or adjacent implementation guidance from the IETF process.
Abstract
This document defines an extension for MoQ Transport [moqt] that lets an endpoint declare that advertisements to it must be solicited first. An endpoint that declares nothing receives unsolicited PUBLISH_NAMESPACE, which is what a peer unaware of this extension implicitly asks for. An endpoint that will instead ask for what it wants says so once during setup, and is spared the advertisements it would otherwise have to ignore. Because sending the option at all identifies an endpoint that implements this extension, the requirement is enforceable between two such endpoints rather than merely advisory.