On Mon, 16 Sep 2019, Antoni Villalonga wrote:
HTTP/3 support in curl is marked *EXPERIMENTAL* for several reasons.
- The project reserves itself the right in changing how it works in ways that
may change behavior and ABI/API in ways that otherwise curl would never do.
- The HTTP/3 protocol is still only in draft and not final. It is a moving
target, and so are the HTTP/3 and QUIC libraries as well as the few
available HTTP/3 servers. Enabling draft-22 support now will soon be old
as we transition into a draft-23 world. And maybe soon draft-24?
Dependencies
Whether to go with the quiche or the ngtcp2 backend when finally packaging for
Debian is a decision to take once lots of other pieces have fallen into place.
Including, but not limited to, the TLS library situation and what QUIC APIs
that are made available and which of those libraries the QUIC libraries can be
made to use.
So, to sum up, we need this to happen (possibly even in this order):
- TLS libraries packaged in Debian that offer the necessary QUIC APIs
- QUIC + HTTP/3 libraries packaged in Debian - that can use said TLS
libraries
- The HTTP/3 and QUIC specifications to stop moving
- HTTP/3 support in curl to leave the experimental state
- (We *probably* also want curl's alt-svc support enabled, which also is
marked EXPERIMENTAL for the moment.)
--
/ daniel.haxx.se
