Dnscrypt-proxy: Feature request: HTTP/3 support

[KrasnayaPloshchad]

With this feature any communication with remote DNSCrypt or DoH server would be passed through HTTPS/3 proctol.

[jedisct1]

HTTP/3 does not exist yet.

And you can get the same performance as DNS-over-HTTP-over-QUIC today, with better privacy, by using DNSCrypt instead.

[uBlock-user]

@jedisct1

https://www.zdnet.com/article/http-over-quic-to-be-renamed-http3/
https://quicwg.org/base-drafts/draft-ietf-quic-http.html

[Mikaela]

I guess it's in the same state as https://github.com/jedisct1/dnscrypt-proxy/issues/656, not finalized and deployed yet.

[uBlock-user]

same state as #656

Not exactly, it's not even in fully developed yet, on the other hand QUIC soon to be known as HTTP/3 is already used in stable builds of Chromium/Chrome since 2012 and is in deployed on all google sites including youtube.

[publicarray]

@uBlock-user I just want to point out that HTTP/3 is in a draft stage, meaning more changes to the protocol are expected until it is finalised. Interestingly there are Google QUIC Transport and IETF QUIC Transport Implementations with different draft revisions.

HTTP-over-QUIC != QUIC

---

Some reading material:

Book by curl developer Daniel Stenberg: https://http3-explained.haxx.se/en/ - Github

Recent Changes:
https://github.com/quicwg/base-drafts/commits/master/draft-ietf-quic-http.md

https://mailarchive.ietf.org/arch/msg/quic/RLRs4nB1lwFCZ_7k0iuz0ZBa35s

[publicarray]

From the book:

As of November 2018, there still has not been any larger interoperability tests with HTTP/3 - only with the existing two implementations and none of them are done by a browser or a popular open server software.
[..]
None of the larger browser vendors have yet shipped any version, at any state, that can run the IETF version of QUIC or HTTP/3.

Google Chrome has shipped with a working implementation of Google's own QUIC version since many years, but that does not interoperate with the official QUIC protocol and its HTTP implementation is different than HTTP/3.

[jedisct1]

Good read on QUIC and HTTP/3: https://calendar.perfplanet.com/2018/quic-and-http-3-too-big-to-fail/