For contributors: Experimenting on QUIC and HTTP/3 in ASP.NET Core

[analogrelay]

The ASP.NET Core team is investigating adding HTTP/3 and QUIC support across the .NET stack. It's still very early in the process, but we're checking in some initial experiments and want to make our current plans clear. This is a long-lead effort that will take time, but we want to get this work in public as soon as possible so our community can be involved.

Initial Experiments

Over the next few weeks, we will be starting to merge in some early experiments in supporting HTTP/3. We'll also continue to improve these experiments as we explore HTTP/3 and QUIC and learn how best to integrate it into our stack.

The prototype uses "msquic", a cross-platform QUIC implementation developed at Microsoft. This library is not available for public consumption at this time, so external contributors cannot run our experimental HTTP/3 work. This only affects contributors who are specifically working in our prototype HTTP/3 components, other contributors will not be affected (all the necessary builds, samples, tests, etc. will be disabled by default). Unless you are trying to make changes to the HTTP/3 components, you should not be affected by this change.

This is a temporary situation and we will keep you posted via this announcements repo.

Timelines

We aren't making any commitments on a timeline for HTTP/3 support. Right now, these are experiments as we learn what we need to do to deliver HTTP/3 support.

See dotnet/aspnetcore#15271 for more details on the upcoming work.