-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HTTP/3] Developers can build libraries for HTTP/3 to meet their client/server needs #43546
Comments
@scalablecory @geoffkizer @karelz as a P0 story, we need to get a t-shirt cost for this by 11/13. I am assuming that includes the first two of the list above. @Pilchie who will cost the third one -- the work on the Kestrel side? |
I expect @jkotalik is the best person on our side. |
I marked this as XL (it's XL even for just the Kestrel work). |
Is there some reasonable way to break this into child items, @jkotalik ? (For example, one item per entry in the list above, or more) |
We are tracking this in the aspnetcore repo as well: dotnet/aspnetcore#15271. I'd put it on the runtime folks to determine if/how the want to split it up. |
I'd cost adding HTTP/3 to Kestrel at ~20 weeks for everything (including perf/stress tests, implementation, abstractions, etc.) |
Alright, I parented that under this. It's labeled Epic, but fine. |
I think 12 weeks is enough for QUIC (MsQuic implementation) and client-side H3. @geoffkizer how do you feel about that? |
That seems a bit short to me. I also think we should break out the MsQuic work vs the H3 work. |
@scalablecory (or @geoffkizer ) could you please open (or link) appropriate user stori(es) for our work, similar to how the Kestrel one is linked above? Just tag with "User Story". Then we have a place for our own cost. |
@geoffkizer - Can we flush this out to sub issues? |
Tagging subscribers to this area: @dotnet/ncl Issue DetailsHTTP3 is the next major version of HTTP and the successor to HTTP2. It is in the final stages of standardization in the IETF. Some browsers (notably Chrome) already support draft versions of HTTP3. HTTP3 runs over QUIC, which replaces TCP as the underlying transport. QUIC is also in the final stages of standardization in the IETF. It provides secure, multiplexed streams over UDP. QUIC is a general-purpose, extensible transport protocol and we expect it to be used by other application protocols aside from HTTP3. Work Items
We have already made some progress on this in .NET 5.0 and are delivering HTTP3 support in a “preview”, unsupported capacity. There is no public API for QUIC in .NET 5.0. We intend to share as much HTTP3 code as is reasonably possible between the client and server implementation.
|
HTTP3 is the next major version of HTTP and the successor to HTTP2. It is in the final stages of standardization in the IETF. Some browsers (notably Chrome) already support draft versions of HTTP3. HTTP3 runs over QUIC, which replaces TCP as the underlying transport. QUIC is also in the final stages of standardization in the IETF. It provides secure, multiplexed streams over UDP. QUIC is a general-purpose, extensible transport protocol and we expect it to be used by other application protocols aside from HTTP3.
Work Items
P0
P1
P2
We have already made some progress on this in .NET 5.0 and are delivering HTTP3 support in a “preview”, unsupported capacity. There is no public API for QUIC in .NET 5.0.
We intend to share as much HTTP3 code as is reasonably possible between the client and server implementation.
The text was updated successfully, but these errors were encountered: