Hi Ilya, On Thu, Mar 06, 2025 at 01:54:25PM +0100, ???? ??????? wrote: > Hello, > > > likely you already heard the news > > QUIC server post-rebase nits · openssl/openssl@b48145c > <https://github.com/openssl/openssl/commit/b48145cd189734de287afae79a0723361a05ddca>
Well, we'll see if anyone ends up making any use of it, 4 years after QUIC stacks have all been developed and are still improving. Having a transport layer implemented in a crypto library is completely upside- down and unlikely to integrate well in many projects... And finally we're well placed to know that you can't declare "Tada, now we have a working QUIC stack". QUIC was designed for continuous experimentation and improvements, not for being tied deeply into a lib that will not evolve in the field for several years due to security constraints. Given that even the minimal part that was asked for 5 or 6 years now by many (the so-called "boringssl API") was done differently, we can easily imagine that the rest of the API is not used like others would possibly expect (or maybe it's just another NIH reason to justify having waited so long). Daniel Stenberg covered some of these points there recently: https://daniel.haxx.se/blog/2025/02/16/openssl-does-a-quic-api/ Cheers, Willy
