HTTP/3 Support

[uvd]

Current status

HTTP/3 support is on the roadmap. There is a working h3 crate, and reqwest has unstable HTTP/3 support.

Much work is still needed, and volunteers are welcome.

Besides the issue tracker (which should store durable decisions and their context), there's this h3 Discord channel to coordinate work.

Here's some of the main steps:

• Harden the h3 crate itself, such as fixing any straggling interop issues,
  and filling out the spec conformance tags we use for accountability.
• Proposal for (initially unstable) hyper::rt::quic integration, allowing
  people to bring their own QUIC.
• Write the hyper::proto::http3 glue that translates hyper's connection
  patterns with the h3 crate.

[shenshouer]

Any plan for this?

[quentusrex]

Since I followed the rabbit hole from Tokio and Tonic to here, the latest work appears to be over here currently:
quinn-rs/quinn#734

Any best ways to support the latest efforts on http/3 support?

[djc]

I have a branch going on here: https://github.com/djc/hyper/tree/quinn-h3. This adds (completely untested) support for HTTP/3 to the hyper server, but doesn't yet add any API to set it up. I have some ideas on how to do that. That branch also more or less depends on #2182 and #2188 (which are currently included in that branch) and on further tweaks to quinn-rs/quinn#734 that I'll have to rebase on the final version of that PR once it's ready.

[quentusrex]

@djc Looks like all of the tickets but #2182 were merged. Does this mean that https://github.com/djc/hyper/tree/quinn-h3 is getting close?

[djc]

I've been discussing it with @seanmonstar, as far as I can tell he's still figuring out how he wants to go about it.

[seanmonstar]

We've put together a proposal here: hyperium/h3#1

[quentusrex]

With the proposal merged, what is the best way to see current status towards first MVP of the functionality? and with status, ways to support the effort?

[djc]

To the best of my knowledge, work is ongoing in the h3 repo. There is a h3 channel in the Tokio Discord which you might join, as well.

(If by support the effort you mean financially, I might be available to accelerate the efforts on a consulting basis. If that is of interest, shoot me an email.)

[seanmonstar]

Good point, I'll see about setting up a milestone with all the issues needed to get the design working. If by support the effort you mean to contribute code, as mentioned, there's an h3 Discord channel to discuss next features, and I'll get a milestone going. There is the general issue tracker, which already has some work split up.