MsQuic is a Microsoft implementation of the IETF QUIC protocol. It is cross-platform, written in C and designed to be a general purpose QUIC library.
RFC: 9000, 9001, 9002 Draft: Datagram, Version Negotiation, Load Balancing, ACK Frequency
QUIC has many benefits when compared to existing "TLS over TCP" scenarios:
- All packets are encrypted and handshake is authenticated with TLS 1.3.
- Parallel streams of (reliable and unreliable) application data.
- Exchange application data in the first round trip (0-RTT).
- Improved congestion control and loss recovery.
- Survives a change in the clients IP address or port.
- Stateless load balancing.
- Easily extendable for new features and extensions.
MsQuic has several features that differentiates it from other QUIC implementations:
- Optimized for client and server.
- Optimized for maximal throughput and minimal latency.
- Asynchronous IO.
- Receive side scaling (RSS) support.
- UDP send and receive coalescing support.
- For platform support details, see the Platforms docs.
- For release details, see the Release docs.
- For performance data, see the Performance dashboard.
- For building the MsQuic library, see the Build docs.
- For testing the MsQuic library, after the build step see the Run Tests.
- For using the MsQuic API, see the API docs or the Sample.
- For deploying with MsQuic, see the Deployment docs.
- For diagnosing MsQuic, see the Diagnostics docs and the Trouble Shooting Guide.
- For other frequently asked questions, see the FAQs.
For information on contributing, please see our contribution guidlines. Feel free to take a look at our Good First Issues list if you're looking for somewhere to start.