Support QUIC TLS API
Description of the feature:
QUIC decided to use TLS 1.3 as the foundation for the crypto and security layer to avoid inventing something new and instead lean on a trustworthy and existing protocol. However, A QUIC implementation needs to extract traffic secrets from the TLS connection and it needs to be able to read/write TLS messages directly – not using the TLS record layer. So it should only use "TLS messages" and not "TLS records" for the protocol.
Applications that this feature may be relevant to:
Currently any implementation of HTTP/3
Is this feature implemented in other libraries (and which)
There are tweaked versions OpenSSL that currently has the crypto API for QUIC TLS. Similar to this, there is an ongoing boringSSL patch as well. There is QUIC TLS APIs in PicoTLS as well.
Edited by Aniketh Girish