Back to News
news

IETF MOQ WG: Joining FETCH Survey

Alan Frindell posted to the MOQ working group mailing list on May 15, 2026. Luke, I am translating you to: Question 1: 4 (Joining FETCH meets your use case functionally but is not performant)

Source: IETF Mailing ListView source →

Message Snapshot

  • List: moq@ietf.org
  • Thread subject: Joining FETCH Survey
  • Message subject: [Moq] Re: Joining FETCH Survey
  • Author: Alan Frindell
  • Published: 2026-05-15T17:47:37.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 15, 2026. Luke, I am translating you to: Question 1: 4 (Joining FETCH meets your use case functionally but is not performant)

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

Luke, I am translating you to: Question 1: 4 (Joining FETCH meets your use case functionally but is not performant)

Plain-Text Body

Luke, I am translating you to:

Question 1: 4 (Joining FETCH meets your use case functionally but is not performant)

Question 2: 3 (Require Unified control messages and data plane for current group)

Question 3: MAY remove joining FETCH

Question 4.1: Not answered (inferred because you aren't asking for SUBSCRIBE before current group) Question 4.2: No (You are saying use subscribe for CG and subscribe doesn't need flow control) Question 4.3: MUST (because you said CurrentGroupFill and that's how it works)

Question 5: Not answered (your tolerance for delaying the specification for this in particular is unknown)

Let me know if any of that is incorrect.

Thanks

-Alan

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 →