IETF MOQ WG: New Agenda for London

Message Snapshot

• List: moq@ietf.org
• Thread subject: New Agenda for London
• Message subject: [Moq] Re: New Agenda for London
• Author: Cullen Fluffy Jennings
• Published: 2026-06-09T21:49:18.000Z
• Source tag: ietf-mailing-list
• Message URL: Open in IETF Mail Archive

Summary

Cullen Fluffy Jennings posted to the MOQ working group mailing list on June 9, 2026. Few comments on new agenda … We have three hours on "Other MOQT Issues”. It makes sense to use time on our open issues but it is reall…

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

Few comments on new agenda … We have three hours on "Other MOQT Issues”. It makes sense to use time on our open issues but it is really hard to come prepared or read ahead with that vague an agenda. Could we group these into specific topics that actually need face to face time and allocate time and speakers for specif…

Plain-Text Body

Few comments on new agenda …

We have three hours on "Other MOQT Issues”. It makes sense to use time on our open issues but it is really hard to come prepared or read ahead with that vague an agenda. Could we group these into specific topics that actually need face to face time and allocate time and speakers for specific topics ?

On the "Joining FETCH” … most people can live with it as it is now. I would much rather see us push this down the road a bit and get the other stuff that is critical done first then come back to this. I don’t think is should be the priority use of face to fact time. Like peeps, bidir, this is something that might be atheistically pleasing but does not really improve the uses cases we can solve with MoQT. I do think we should come back to this but we have more important stuff to resolve first.

Is "request blocking" time going to be for talking about request ID we had before and got removed or proposing a new switch variant ?

I don’t think we should spend time at this meting on "SWITCH/DTS implementation lessons”. If there are problems, put in issues. If there is perf data, send to list. If there is demos, send a video to list. We are just so tight on time that without specific things we are trying to accomplish with this time, I think we could use it better other ways.

All of the topics on after lunch on the 2nd day seem like things that could be done at a virtual interim phone calls if we could use that time to nail down the key issue Top N, DTS, object filters, client side ABR, and security including DDoS.