IETF MOQ WG: Consensus call on way forward on REWIND

Message Snapshot

• List: moq@ietf.org
• Thread subject: Consensus call on way forward on REWIND
• Message subject: [Moq] Re: Consensus call on way forward on REWIND
• Author: Ian Swett
• Published: 2026-04-28T00:12:21.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 April 28, 2026. Regarding the consensus call, I think we should make changes to the core draft (some variant of option 3). As Luke said, I think CurrentGroupFill…

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

Regarding the consensus call, I think we should make changes to the core draft (some variant of option 3). As Luke said, I think CurrentGroupFill (Alan's PR

Plain-Text Body

Regarding the consensus call, I think we should make changes to the core draft (some variant of option 3).

As Luke said, I think CurrentGroupFill (Alan's PR https://github.com/afrind/moq-transport/pull/15) is a strict improvement on the current draft and fixes the worst of the "Joining Fetch Dissent" issues.

I'm open to some variant of REWIND, but not very optimistic that we'll get consensus on anything more complex than CurrentGroupFill. The motivation to tackle something slightly more complex like REWIND is if it would enable us to remove Joining Fetch, because Joining FETCH adds complexity in several ways. Personally, I'd be happy to remove Joining Fetch if we had CurrentGroupFill, but I'm not sure others would?

Ian