An #ngtcp2 lead developer told me they have no current plans to adapt to the new #OpenSSL #QUIC API because of its lack of 0RTT support and the "pull model".
Of course someone else can go ahead and write it and ideally someone from #OpenSSL does it, for dogfooding purposes.
I have no heard of any other QUIC stack either having adapted to it yet.
@rsalz "We did get some feedback from other QUIC stacks" they said to me. But few QUIC stacks support several different TLS library QUIC APIS, and with this being very different they need to if they don't at the same drop the support for the other TLS libs - which seems unlikely.
"plan to support it" might not mean much, plus we don't know what those authors knew about the API when they said so.
Clearly one of those four was not ngtcp2, which in my eyes is the most important one...
daniel:// stenberg://
rsalz
Stefan Eissing