IETF MOQ WG: 2026-09-02 Virtual Interop Hackathon on Draft 18
Mike English posted to the MOQ working group mailing list on August 21, 2026. Hi all, As discussed in Vienna at IETF 126, we're doing another round of interop hacking on draft-ietf-moq-transport-18 before draft-20 is cu…
Message Snapshot
- List:
moq@ietf.org - Thread subject: 2026-09-02 Virtual Interop Hackathon on Draft 18
- Message subject: [Moq] 2026-09-02 Virtual Interop Hackathon on Draft 18
- Author: Mike English
- Published: 2026-08-21T17:54:01.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Mike English posted to the MOQ working group mailing list on August 21, 2026. Hi all, As discussed in Vienna at IETF 126, we're doing another round of interop hacking on draft-ietf-moq-transport-18 before draft-20 is cu…
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
Hi all, As discussed in Vienna at IETF 126, we're doing another round of interop hacking on draft-ietf-moq-transport-18 before draft-20 is cut as the
Plain-Text Body
Hi all,
As discussed in Vienna at IETF 126, we're doing another round of interop hacking on draft-ietf-moq-transport-18 before draft-20 is cut as the interop target for the Seattle hybrid interim (October 12-15). We've selected Wednesday, September 2 as the date. The goal is to solidify draft-18 interop now so that we go into October in good shape.
The event will run all day - participants are welcome to join and drop off as their schedule allows. Interop hacking before and after the event is also welcome; the shared date is mainly to increase the chances of synchronous time with other implementors. I'll follow up here with a Google Meet link closer to the date.
Our primary focus will be draft-ietf-moq-transport-18. If you have implementations ready for other drafts and would like to test and report interop, feel free to add those as well.
For automated test results, please make sure your implementation is registered in the interop runner[1] and that your Docker image or public relay endpoint is up to date - the runner pairs implementations against each other and produces a matrix of which test cases pass for specific builds of specific implementations. We're also hoping to use some time that day to work on the runner itself: expanding the test suite to cover more data plane scenarios, and possibly revamping the results presentation based on the per-draft matrix work in progress ( https://github.com/englishm/moq-interop-runner/pull/95). If you're interested in helping with that, come find us on the Meet.
For higher-level, ad hoc testing that doesn't fit neatly into the runner (application-level flows, observations about draft ambiguities, notes on how you set up your tests), please capture those in the ad hoc interop reports section of the wiki, where I've already stubbed out a section for this event:
Notes on struggles, ambiguities, or divergences in draft understanding are particularly valuable - they help us make better use of the data we generate during these events to inform improvements of the specification going forward.
If you plan to participate, consider replying to this thread with when you expect to be online so others can plan accordingly.
Thanks! -Mike