Back to News
news

IETF MOQ WG: Consensus call on way forward on REWIND

Luke Curley posted to the MOQ working group mailing list on April 28, 2026. Absolutely, Gwendal. We should merge one of the CurrentGroup proposals first. Ian is looking ahead; potential paths include:

Source: IETF Mailing ListView source →

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: Luke Curley
  • Published: 2026-04-28T15:43:23.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 April 28, 2026. Absolutely, Gwendal. We should merge one of the CurrentGroup proposals first. Ian is looking ahead; potential paths include:

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

Absolutely, Gwendal. We should merge one of the CurrentGroup proposals first. Ian is looking ahead; potential paths include:

Plain-Text Body

Absolutely, Gwendal.

We should merge one of the CurrentGroup proposals first. Ian is looking ahead; potential paths include:

  1. Maintain the status-quo with JOINING FETCH (if you want >1 group)
  2. Replace JOINING FETCH with REWIND, or a modified SUBSCRIBE that behaves like REWIND (ie. add Start_Group).
  3. Remove JOINING FETCH. Subscribers would block on SUBSCRIBE_OK then FETCH groups older than the latest.

I would personally prefer option 2, but I'm also fine with anything. I think Ian would prefer anything but option 1 to simplify the draft.

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 →