QUIC-related PRs and Issues of Note

While we work on getting the WebRTC-QUIC repo hooked up to the ORTC CG mailing list, I'd like to point out some recent Issues and PRs that may be of interest to ORTC CG participants.


Issue 105:<https://github.com/w3c/webrtc-quic/issues/105> Pooled Connections.  As Peter Thatcher notes "I've recently heard interest in allowing the client/server QuicTransport to use the same QUIC connection(s) as the ones that are used for HTTP, perhaps even the one the page has used to load."  This issue brings up some fundamental questions about the design of HTTP/3, so it will be of interest to those who follow the development of the QUIC protocol.


Issue 110: <https://github.com/w3c/webrtc-quic/issues/110> Sub-protocols.  This Issue explores one of the problems brought up in Issue 105, which is how it could be possible for HTTP/3 to share use of an RTCQuicTransport with the QUIC Client/Server APIs.  The discussion in the Issue is by nature somewhat speculative.


PR 111<https://github.com/w3c/webrtc-quic/pull/111>:  WebTransport. This PR, submitted by Peter Thatcher, seeks to generalize the QUIC APIs so that they can apply to other transports, including WebSockets.   As Peter notes in the PR, "It's a big change, so lots of discussion to be had.  This PR can serve as a concrete thing to look at and discuss."