IETF MOQ WG: MoQ + Compression
Alan Frindell posted to the MOQ working group mailing list on June 26, 2026. Cool work Luke. MOQT's model is clearly "the objects can't change for the same track name" - therefore the only way we have to signal compress…
Message Snapshot
- List:
moq@ietf.org - Thread subject: MoQ + Compression
- Message subject: [Moq] Re: MoQ + Compression
- Author: Alan Frindell
- Published: 2026-06-26T18:07:49.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 June 26, 2026. Cool work Luke. MOQT's model is clearly "the objects can't change for the same track name" - therefore the only way we have to signal compress…
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
Cool work Luke. MOQT's model is clearly "the objects can't change for the same track name" - therefore the only way we have to signal compression support now is it
Plain-Text Body
Cool work Luke.
MOQT's model is clearly "the objects can't change for the same track name"
- therefore the only way we have to signal compression support now is it bake it into the Full Track Name (eg: SUBSCRIBE namespace--name.deflate or something). Otherwise, aren't you wandering into HTTP content negotiation, Vary header, etc territory?
-Alan