Back to News
news

IETF MOQ WG: Knowing the start of a Subgroup

Ian Swett posted to the MOQ working group mailing list on May 4, 2026. I believe the concern with making Subgroup ID a single byte is if you wanted to do Object-per-Subgroup and couldn't or didn't want to use datagrams,…

Source: IETF Mailing ListView source →

Message Snapshot

  • List: moq@ietf.org
  • Thread subject: Knowing the start of a Subgroup
  • Message subject: [Moq] Re: Knowing the start of a Subgroup
  • Author: Ian Swett
  • Published: 2026-05-04T16:56:05.000Z
  • Source tag: ietf-mailing-list
  • Message URL: Open in IETF Mail Archive

Summary

Ian Swett posted to the MOQ working group mailing list on May 4, 2026. I believe the concern with making Subgroup ID a single byte is if you wanted to do Object-per-Subgroup and couldn't or didn't want to use datagrams,…

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

I believe the concern with making Subgroup ID a single byte is if you wanted to do Object-per-Subgroup and couldn't or didn't want to use datagrams, you'd be limited to 256 Objects per Group.

Plain-Text Body

I believe the concern with making Subgroup ID a single byte is if you wanted to do Object-per-Subgroup and couldn't or didn't want to use datagrams, you'd be limited to 256 Objects per Group.

Otherwise, making Subgroup ID a byte a very appealing change. Thinking along those lines is what caused me to file #1405 https://github.com/moq-wg/moq-transport/issues/1405 (Single Object Subgroups don't need a Subgroup ID)

Ian

On Mon, May 4, 2026 at 12:24 AM Mo Zanaty (mzanaty) <mzanaty= 40cisco.com@dmarc.ietf.org> wrote:

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 →