On Sat, Oct 1, 2022 at 2:53 AM Willy Tarreau <[email protected]> wrote: > On Fri, Sep 30, 2022 at 02:34:11PM -0400, Phillip Hallam-Baker wrote: > > The crux of the matter is that the high level model of QUIC is that it > > provides a collection of streams between two points. While that is what > > people are used to using in WebServices, this model is really only suited > > to Web Services that are inherently data retrieval. > > Why ? I mean, there was a considerable effort so split gQUIC into QUIC+H3, > and QUIC does provide independent, full-duplex streams that have nothing > to do with H3.
Streams of octets. Not structured streams directed at identified well-known services. I don't think the changes I am going to need are very extensive and there is a good chance they can be back ported into QUIC when I understand what they are. But it will be QUIC+X and the X will need to have visibility into the QUIC part. Going back to the original point, dropping confidentiality for Web Browsing in QUIC+H3 is going to be unacceptable to many, myself included. Dropping confidentiality in QUIC+X might be possible but I would not count on it and it is not clear that QUIC+X is possible because of the 'why would you want to do that' tendency. We charter WGs with a narrow scope because that is the only way to get the work done. That sometimes means the end product is more constrained than it need be.
