Back to News
news

IETF MOQ WG: Subscription Flow Control Extension Draft

Alan Frindell posted to the MOQ working group mailing list on October 8, 2026. Hi, based on discussions of issue #869 <https://github.com/moq-wg/moq-transport/issues/869>, Ian and I have written an extension draft

Source: IETF Mailing ListView source →

Message Snapshot

  • List: moq@ietf.org
  • Thread subject: Subscription Flow Control Extension Draft
  • Message subject: [Moq] Subscription Flow Control Extension Draft
  • Author: Alan Frindell
  • Published: 2026-10-08T15:07:35.000Z
  • Source tag: ietf-mailing-list
  • Message URL: Open in IETF Mail Archive

Summary

Alan Frindell posted to the MOQ working group mailing list on October 8, 2026. Hi, based on discussions of issue #869 https://github.com/moq-wg/moq-transport/issues/869, Ian and I have written an extension draft

Why It Matters

This message came from the public MOQ working group archive and captures active discussion, meeting coordination, or implementation feedback around Media over QUIC.

Message Excerpt

Hi, based on discussions of issue #869 https://github.com/moq-wg/moq-transport/issues/869, Ian and I have written an extension draft

Plain-Text Body

Hi, based on discussions of issue #869 https://github.com/moq-wg/moq-transport/issues/869, Ian and I have written an extension draft https://datatracker.ietf.org/doc/draft-frindell-moq-subscription-flow-control/ that enables a receiver to limit the amount of data or streams a publisher can send on subscription without additional credit.

It's possible to combine this extension with the ability to subscribe in the past (not specified) in a way that prevents cached data from overwhelming the session.

The basic extension sketch is:

A SETUP option that negotiates the extension and sets the default initial limits. Parameters that can override the initial defaults in SUBSCRIBE, or SUBSCRIBE TRACKS A subscriber sent Message that can grant additional credit A reset Message sent by the publisher to ensure the receiver can account for streams/bytes that weren't delivered.

The reset message proved tricky, and required adding a per-subscription stream sequence number to the subgroup header, the use of RESET_STREAM_AT, and restrictions on Track Alias reuse.

Feedback welcome here on the list, or in the github repo https://github.com/afrind/draft-frindell-moq-subscription-flow-control as issues or PRs.

Thanks

-Alan and Ian

Stay ahead of MOQ

Get the latest IETF MOQ standards updates, protocol analysis, and ecosystem news delivered to your inbox.

Go deeper with MOQ Edge Pro

Weekly deep-dives, IETF standards tracking, and streaming tech trend reports — from $9/mo.

See plans →