draft-lcurley-moq-solicit-00 | Individual submission | submitted 2026-09-24 | Author: L. Curley | Datatracker
First look. This page records the draft’s own abstract and scope as published; the text has not been reviewed in depth here yet.
Abstract (as published)
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.
What it defines
A SOLICIT setup option. The semantics are deliberately backward-compatible by omission:
- Declare nothing → you keep receiving unsolicited
PUBLISH_NAMESPACE, which is exactly what a peer that has never heard of this extension is implicitly asking for. - Declare it once during setup → the peer withholds advertisements and answers only
SUBSCRIBE_NAMESPACE. You ask for what you want.
The motivation is a relay or client that would otherwise have to receive and discard a large advertisement stream. It sits directly adjacent to the namespace-discovery restructuring in flight on the core draft as #1946.
Context
Submitted in Luke Curley’s eight-document batch of 2026-09-24, at the IETF-127 (Seattle) submission cutoff — four brand-new drafts (moq-e2ee, moq-solicit, moq-flate, moq-mpegts) plus revisions of hang-03, lite-06, msfts-01 and cluster-01. Individual submission, not WG-adopted. See moq-dev, discussions-2026-09.
Related
- moq-transport — the extended protocol; see the namespace-discovery restructuring in #1946
- publish-subscribe —
PUBLISH_NAMESPACE/SUBSCRIBE_NAMESPACEflow - relays — the endpoints most likely to want this