IETF MOQ WG: Consensus Call: DTS and SWITCH
Gwendal Simon posted to the MOQ working group mailing list on June 5, 2026. Suhas, The requirements have been on the table for 15 months. Slide 2 of the SWITCH presentation at the February 2025 interim (https://datatrac…
Message Snapshot
- List:
moq@ietf.org - Thread subject: Consensus Call: DTS and SWITCH
- Message subject: [Moq] Re: Consensus Call: DTS and SWITCH
- Author: Gwendal Simon
- Published: 2026-06-05T07:10:53.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Gwendal Simon posted to the MOQ working group mailing list on June 5, 2026. Suhas, The requirements have been on the table for 15 months. Slide 2 of the SWITCH presentation at the February 2025 interim (https://datatrac…
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
Suhas, The requirements have been on the table for 15 months. Slide 2 of the SWITCH presentation at the February 2025 interim (https://datatracker.ietf.org/meeting/interim-2025-moq-03/materials/slides-interim-2025-moq-03-sessa-update-to-switch-slides-00) lists them explicitly: - Switch from track A to track B while ma…
Plain-Text Body
Suhas,
The requirements have been on the table for 15 months. Slide 2 of the SWITCH presentation at the February 2025 interim (https://datatracker.ietf.org/meeting/interim-2025-moq-03/materials/slides-interim-2025-moq-03-sessa-update-to-switch-slides-00) lists them explicitly:
- Switch from track A to track B while maintaining agreed subscription settings
- Minimize switch delay, ideally at the next group boundary
- Even when subscriber and/or relay lag several groups behind live due to accumulated congestion
- No throughput increase, no duplicate objects, no concurrent subscriptions
- Robust under high RTT and short group durations
Since then, two additional requirements raised by WG participants were incorporated:
- replacing already-buffered objects when switching up
- immediate group termination for catastrophic downswitch
Calling for requirements work at the point of a consensus call, without introducing any new requirement that has not already been addressed, is not moving the discussion forward.
Gwendal
From: Suhas Nandakumar suhasietf@gmail.com Sent: Friday, June 5, 2026 6:15 AM To: Law, Will wilaw=40akamai.com@dmarc.ietf.org Cc: Martin Duke martin.h.duke@gmail.com; MOQ Mailing List moq@ietf.org Subject: [Moq] Re: Consensus Call: DTS and SWITCH
I support adoption of DTS work and also as part of core transport work as this is an important and useful feature with proven application support.
On Client side ABR, the WG should spend some time to work on addressing the requirements regardless of the approach we decide to solve it
Thanks Suhas