I'm currently doing MoQ over QMux* over WebSockets. I wish it wasn't the case, but a TCP fallback is a requirement for a production MoQ deployment, similar to TURN-TCP. I'd like to see QMux over TLS and/or WebSockets be this fallback.
The problem with using `moq-transport-16` as the TLS ALPN is that you can can't negotiate the QMux version. This is an unsolved issue with QMux in general; I filed an issue in the repo. On Mon, Mar 2, 2026, 6:22 AM Lucas Pardue <[email protected]> wrote: > Hi Suhas, > > Thanks for putting that draft together. As a minor note, the QMux draft > was recently formally adopted as draft-ietf-quic-qmux [1]. > > We have an open Qmux issue on the topic of ALPN usage [2] and your draft > speaks to that. If you'd like 5 mins on the QUIC WG agenda to present about > this aspect (not the media-related things) I think it could help. Please > let me know. > > Cheers, > Lucas > > [1] https://datatracker.ietf.org/doc/draft-ietf-quic-qmux/ > [2] https://github.com/quicwg/qmux/issues/25 > > On Mon, Mar 2, 2026, at 06:04, Suhas Nandakumar wrote: > > Hi Martin and Magnus, > > We would like to request 5-10 mins to talk about > https://datatracker.ietf.org/doc/draft-nandakumar-moq-qmux-moqt/ > > Thanks > Suhas > -- > Moq mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > -- > Moq mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
