Will the rest of Windows also go open source?
At this time there is no plan to open source the rest of Windows.
When is this shipping with Windows?
The kernel mode version, msquic.sys, will ship in future Windows releases. For more details see our support and release documentation.
Why isn’t there an HTTP/3 implementation along with MsQuic?
MsQuic is designed as a generic QUIC transport for any application protocol. Several HTTP/3 stacks that use MsQuic exist, both internal to Windows and external (.NET Core).
Do you plan to support other platforms?
MsQuic currently supports Windows and Linux (in preview). In the future support for other platforms may be added.
Why aren't you allowing community contributions?
We are currently stabilizing our build and integration processes. External contributions will be allowed at a later time.
Isn’t QUIC a Google product?
QUIC was started by Google, but then was picked up by the IETF to be standardized (see here). MsQuic is an implementation of that upcoming standard.
When is the standard going to be finalized?
The final date depends on the IETF process but the Internet-Drafts have already started to stabilize. We are already experimenting with using MsQuic in our internal services and we will continue updating MsQuic as the standard evolves.
Do you have any performance data?
We don't have any performance numbers to share at this time.
Does this mean Microsoft will stop investing in TCP?
TCP will continue to be used widely for a long time and we will continue to improve it as necessary.
Why is MsQuic written in C?
Windows Kernel mode is one of the supported platforms, and while it supports some C++ features, it does not support all of them. So, it was decided to use just pure C to reduce complexity.