IETF MOQ WG: MoQ + Compression
Luke Curley posted to the MOQ working group mailing list on June 26, 2026. Sorry hit the send button to early. But you can imagine the headache if both of these files were large I meant tracks.
Message Snapshot
- List:
moq@ietf.org - Thread subject: MoQ + Compression
- Message subject: [Moq] Re: MoQ + Compression
- Author: Luke Curley
- Published: 2026-06-26T18:45:09.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Luke Curley posted to the MOQ working group mailing list on June 26, 2026. Sorry hit the send button to early. But you can imagine the headache if both of these files were large I meant tracks.
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
Sorry hit the send button to early. But you can imagine the headache if both of these files were large I meant tracks.
Plain-Text Body
Sorry hit the send button to early.
But you can imagine the headache if both of these files were large
I meant tracks.
Some companies use my libraries to publish sensor data or controls over Starlink. We don't want a scenario where one outdated subscriber that doesn't support compression causes 9x the data transfer from the publisher to the relay.
Making DEFLATE mandatory to implement in moq-transport would fix a lot.