MsQuic is an implementation of the IETF QUIC protocol by Microsoft. It is a cross platform, general purpose QUIC library written in C.
QUIC has many benefits when compared to existing TLS over TCP scenarios:
- Handshake authenticated with TLS 1.3
- All packets are encrypted
- Parallel streams of application data.
- Improved (compared to TCP) congestion control and loss recovery.
- 0-RTT (support depends on TLS library)
Note - Several QUIC protocol features are still unimplemented:
- NAT Rebinding
- Client Migration
- Server Preferred Address
- Full Path MTU Discovery
- Optimized for throughput performance and minimal latency.
- Asychronous IO.
- Receive side scaling (RSS).
- UDP send and receive coalescing.
The source is divided into several directories:
bin- Packages up all static libraries into the platform specific binaries.core- The platform independent code that implements the QUIC protocol.inc- Header files used by all the other directories.platform- Platform specific code for OS types, sockets and TLS.test- Test code for the MsQuic API / protocol.tools- Several tools for exercising MsQuic.
You can find detailed instructions here.
For the near future, external contributions will not be accepted. We are still working on setting up internal repository sycnhronization and continuous integration, and until that happens, this repository will be a simple copy of the Microsoft internal one.
Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.