IETF MOQ WG: Consensus Call: DTS and SWITCH
Ali C. Begen posted to the MOQ working group mailing list on May 29, 2026. I could not attend the interim call due to a personal emergency, however, I watched the recording. My vote for both Switch and DTS is as follows:
Message Snapshot
- List:
moq@ietf.org - Thread subject: Consensus Call: DTS and SWITCH
- Message subject: [Moq] Re: Consensus Call: DTS and SWITCH
- Author: Ali C. Begen
- Published: 2026-05-29T10:02:29.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Ali C. Begen posted to the MOQ working group mailing list on May 29, 2026. I could not attend the interim call due to a personal emergency, however, I watched the recording. My vote for both Switch and DTS is as follows:
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
I could not attend the interim call due to a personal emergency, however, I watched the recording. My vote for both Switch and DTS is as follows:
Plain-Text Body
I could not attend the interim call due to a personal emergency, however, I watched the recording.
My vote for both Switch and DTS is as follows: (1) Should the Working Group adopt the contents of this work in some form? YES (2) If yes, should the contents of this work be incorporated into the MOQT draft (as opposed to an extension draft)? YES with a note below.
These are complementary; some will use Switch and others will use DTS, so both must be supported. This is clear from the charter. I prefer these as part of the main draft but I can live with them being a separate normative RFC and published together with the MOQT draft.
We have already implemented Switch and DTS in MOQtail, and we hope to present those results to the WG soon (either on the list or in London). It is important to note that Switch's main purpose is not just to cut down the number of messages needed but to reduce the excessive/redundant traffic in various edge cases. It must also be clear to the WG by now that track switching is not only for bandwidth issues. So, please don't limit the use cases just to that.
As Gwendal mentioned in this thread, not being interested in using either of these is not a roadblock for WG adoption.
-acbegen