the #QUIC RFC was published four years ago:
daniel.haxx.se/blog/2021/05/27…
The official publication date of the relevant QUIC specifications is: May 27, 2021. I've done many presentations about HTTP and related technologies over the years.daniel.haxx.se
Technical Advisory – Hash Denial-of-Service Attack in Multiple #QUIC Implementations
github.com/ncc-pbottine/QUIC-H…
Contribute to ncc-pbottine/QUIC-Hash-Dos-Advisory development by creating an account on GitHub.GitHub
Let me explain the #OpenSSL #QUIC API move and what it might mean. For #curl and for others.
daniel.haxx.se/blog/2025/02/16…
But will it satisfy the world? I have blogged several times in the past about how OpenSSL decided to not ship the API for QUIC a long time ago, even though the entire HTTP world was hoping for it - or even expecting it.daniel.haxx.se
I asked the #OpenSSL team about their new #QUIC API:
Out of curiosity: since you decided to provide a quite different API than what was once offered to you and what several QUIC stacks are already using. How did you come up with this API?
github.com/openssl/openssl/pul…
We provide some callbacks for third party QUIC stacks to use in order to be able to reuse the OpenSSL TLS implementation in that stack. This is essentially a thin wrapper around the same API that O...GitHub
We provide some callbacks for third party QUIC stacks to use in order to be able to reuse the OpenSSL TLS implementation in that stack. This is essentially a thin wrapper around the same API that O...GitHub
It is now *six* years ago since I first blogged about how the #QUIC API situation was going to slow down QUIC (and HTTP/3) deployment. Unfortunately I was entirely correct.
daniel.haxx.se/blog/2019/01/21…
The follow-up post a few years later on OpenSSL's decision to be a laggard:
daniel.haxx.se/blog/2021/10/25…
I trust you've heard by now that HTTP/3 is coming. It is the next destined HTTP version, targeted to get published as an RFC in July 2019. Not very far off. HTTP/3 will not be done over TCP.daniel.haxx.se
Three years ago I blogged about #OpenSSL's decision to deliberately block #QUIC progress in the world: daniel.haxx.se/blog/2021/10/25…
Which is timely with the OpenSSL 3.4.0 release announced just days ago: that still does not offer a working (and performant) QUIC API. (yes, there is an attempt there but it's not production grade)
It's almost like the writing was on the wall already a long time ago.
In a world that is now gradually adopting HTTP/3 (which, as you know, is implemented over QUIC), the problem with the missing API for QUIC is still a key problem.daniel.haxx.se
Since #openssl does not seem to fix any of the remaining #QUIC API problems in their upcoming 3.4 release, it will keep lagging behind.
openssl-library.org/post/2024-…
The freeze date for OpenSSL 3.4 Alpha is rapidly approaching. Alpha freeze approaching The freeze date for OpenSSL 3.4 Alpha is rapidly approaching. Planned features are viewable on our 3.4 Planning page.Library
I just learned there is a #QUIC in the #Linux kernel effort: github.com/lxin/quic
... as a draft PR making curl use it was filed: github.com/curl/curl/pull/1431…
Hi, this is still very early as the quic kernel module is still under discussion on the LKML. This is unfinished and needs a lot more modification. I would appreciate some initial feedback now befo...GitHub
According to @bagder the stubborn way the #OpenSSL project is handling #QUIC implementation is directly responsible for delaying HTTP/3 adoption (1), and I tend to agree. When the project rejected the community QUIC patches and decided to go with their own design, it wasn't difficult to predict problems. This was proven right by the massive feature gaps (2) and performance issues (3) discovered by @icing when trying to marry OpenSSL QUIC to #curl. Even with API fixes released in version 3.3 the implementation is still inferior, and there is no good solution in sight.
1) lwn.net/Articles/983380/
2) github.com/openssl/openssl/dis…
3) github.com/icing/blog/blob/mai…
Contribute to icing/blog development by creating an account on GitHub.GitHub
Protocol geeks might like the new proposals on how to do #QUIC over TCP/TLS: datatracker.ietf.org/doc/html/… (called Streams) and then how to do #http3 over Streams: datatracker.ietf.org/doc/html/…
Discussed on the #HTTPbis mailing list.
This document specifies how to use HTTP/3 on top of bi-directional, byte-oriented streams such as TLS over TCP. Discussion Venues This note is to be removed before publishing as an RFC.IETF Datatracker
Building #curl using #OpenSSL 3.2 #QUIC?
github.com/curl/curl/discussio…
Hello, are there any plans to build libcurl with OpenSSL v3.2's new QUIC API? OpenSSL v3.2 was officially released 11/23 (which supports QUIC client capabilities). In this way, libcurl doesn't need...GitHub
"The #OpenSSL project really seems to be in a dead end for me, it's incompatible with #QUIC and unfixable performance-wise" / Willy Tarreau
mailarchive.ietf.org/arch/msg/…
Search IETF mail list archivesmailarchive.ietf.org
Join us to hear from QUIC expert Stefan Eissing, and cURL founder and lead developer Daniel Stenberg and learn about all things QUIC.Zoom
XMPP End of the Year Talk 2022!
Let's have a good time with the #XMPP Community folks!
Short talks:
- On #ActivityPub, #Movim, #Prosody development, XMPP + #QUIC
When: 6th Dec 2022, 19:00 CET (tomorrow!)
Join via this instance: bbb.sfconservancy.org/b/ste-fd…
(technical issues as always)
You have been invited to join Home Room using BigBlueButton. To join, click the link above and enter your name.bbb.sfconservancy.org
