IETF MOQ WG: 26 May Agenda
Martin Duke posted to the MOQ working group mailing list on May 21, 2026. Please read carefully: After a few minutes of administrivia, almost the entire balance of Tuesday's meeting will be given to Gwendal and Will to…
Message Snapshot
- List:
moq@ietf.org - Thread subject: 26 May Agenda
- Message subject: [Moq] 26 May Agenda
- Author: Martin Duke
- Published: 2026-05-21T17:17:46.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Martin Duke posted to the MOQ working group mailing list on May 21, 2026. Please read carefully: After a few minutes of administrivia, almost the entire balance of Tuesday's meeting will be given to Gwendal and Will to…
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
Please read carefully: After a few minutes of administrivia, almost the entire balance of Tuesday's meeting will be given to Gwendal and Will to discuss SWITCH and
Plain-Text Body
Please read carefully:
After a few minutes of administrivia, almost the entire balance of Tuesday's meeting will be given to Gwendal and Will to discuss SWITCH and DTS: https://github.com/moq-wg/moq-transport/pull/1378 https://github.com/wilaw/dts4moq
The chairs expect them to work together to use the time constructively. The chairs would also like to point out that there are two SWITCH demos available, one by Ali and one by Yu, that apparently include experimental results. Watching a bunch of video over Meetecho is probably not constructive, but if there are any results or takeaways from the work that Gwendal and Will feel are informative for the discussion, they are welcome to incorporate that. This decision is entirely up to Gwendal and Will.
The chairs will also take the last 15 minutes for a series of Show of Hands to supplement a consensus call that will go on the list shortly. The outcome of this meeting will be a decision to either (1) incorporate this work directly into MoQT, (2) adopt as an extension, or (3) send to /dev/null.
If, by some miracle, this ends early, we will give the balance of time to the MOQT editors to discuss various issues.
Martin