Hi, since QUIC-on-Streams[1] was introduced in Brisbane last year, at least 3 implementations have emerged, and I’ve engaged with people from a range of organizations that are very interested in this work moving forward. Though the initial use case described an HTTP/2 replacement, there's interest in using this for protocols other than HTTP (eg: MoQ), as well as in internal environments.
I know there was some mixed feedback during the presentation, but given implementer interest, can we add time to the agenda to discuss how to move this draft forward? I would like to discuss the possible path to adoption by this working group, including any minor charter revisions that may be necessary to do so. I apologize for the late request and understand if you are unable to accommodate. If I may toss in a bikeshed, I think QUIC on Streams is a confusing name, because QUIC means many things to many people. I humbly offer something along the lines of “QUIC Multiplexing using any stream” (QMux). Thanks -Alan [1] https://datatracker.ietf.org/doc/html/draft-kazuho-quic-quic-on-streams
