IETF MOQ WG: Knowing the start of a Subgroup
Alan Frindell posted to the MOQ working group mailing list on May 5, 2026. We've already been over this ground and I don't see any need to revisit the size of the subgroup ID field. It would be nice to have a specificat…
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: Alan Frindell
- Published: 2026-05-05T16:56:04.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 May 5, 2026. We've already been over this ground and I don't see any need to revisit the size of the subgroup ID field. It would be nice to have a specificat…
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
We've already been over this ground and I don't see any need to revisit the size of the subgroup ID field. It would be nice to have a specification for how to rationalize the priority of mixed subgroup and
Plain-Text Body
We've already been over this ground and I don't see any need to revisit the size of the subgroup ID field. It would be nice to have a specification for how to rationalize the priority of mixed subgroup and datagram groups that's not "implementation defined", but we're talking about the third tiebreaker, so I'm inclined to leave it alone.
Group IDs and Object IDs are varints and are also part of the priority scheme, so "we only have 1 byte for prioritization" is already the wrong place to start from. There's one byte controlled by the subscriber and that's fine.
Thanks
-Alan