Hi folks, At the 125 session, Kazuho presented several QMux open issues with associated PRs. This email serves to summarize the outcome of the discussion and confirm the feeling in the room on the list.
Since there has seemed to be strong emerging consensus on GitHub and in the room, the authors would like to promptly follow up on the outcomes. If you disagree with them, please let that be known ASAP and before 2026-03-26, ideally on the issue or PR itself. As noted in the session, we'd like to schedule a virtual interim for QMux before IETF 126, targetting an EMEA friendly timeslot. Look out for a follow up email on that topic, in the meantime you can express your interest directly to the chairs. • Two-layer encoding • Issues: https://github.com/quicwg/qmux/issues/21 and https://github.com/quicwg/qmux/issues/24 • PR: https://github.com/quicwg/qmux/pull/26 • Outcome: merge the PR to close the issues • Deadlock and flow control • Issue: https://github.com/quicwg/qmux/issues/9 • PR: https://github.com/quicwg/qmux/pull/27 • Outcome: merge the PR to close the issue • TLS Profile - negotiating application protocol when using TLS • Issues: https://github.com/quicwg/qmux/issues/12 and https://github.com/quicwg/qmux/issues/25 • PR: https://github.com/quicwg/qmux/pull/33 • Outcome: merge the PR to close the issue • TLS Profile - QMux transport params (TPs) in TLS handshake • Issue: https://github.com/quicwg/qmux/issues/18 • PR: https://github.com/quicwg/qmux/pull/28 • Outcome: merge the PR and close the issue (the PR adds improved text but we will keep TPs in QMux frames • Implicit acks & ping • Issue: https://github.com/quicwg/qmux/issues/22 • PR: https://github.com/quicwg/qmux/pull/23 • Outcome: merge the PR to close the issue • Multipath TCP • Issue: https://github.com/quicwg/qmux/issues/5 • PR: https://github.com/quicwg/qmux/pull/29 • Outcome: do not merge the PR, close with no action Cheers, Lucas & Matt QUIC WG Chairs
