Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
Перейти к файлу
Nick Banks 35696722c6 Merge branch 'nibanks/kernel-platform-worker' of https://github.com/microsoft/msquic into nibanks/kernel-platform-worker 2024-11-13 18:20:33 -05:00
.azure Fix typo from #4576 (#4582) 2024-09-28 12:13:29 -07:00
.devcontainer
.docker
.github Bump github/codeql-action from 3.27.0 to 3.27.1 (#4649) 2024-11-09 20:59:35 +00:00
cmake
docs Improve version deployment documentation (#4646) 2024-11-06 09:45:25 +00:00
scripts Update MacOS version as macos-12 was deprecated. (#4645) 2024-11-05 08:29:36 +00:00
src Merge branch 'nibanks/kernel-platform-worker' of https://github.com/microsoft/msquic into nibanks/kernel-platform-worker 2024-11-13 18:20:33 -05:00
submodules export platform (#4574) 2024-11-07 14:52:39 +00:00
.CodeQL.yml
.dockerignore
.gitattributes
.gitignore
.gitmodules
.sscignore
CMakeLists.txt export platform (#4574) 2024-11-07 14:52:39 +00:00
CMakePresets.json
Cargo.toml
LICENSE
README.md
THIRD-PARTY-NOTICES
codecov.yml
msquic.kernel.sln
version.json

README.md

MsQuic logo

Documentation Perf Dashboard Build Status Test Status Stress Status codecov CodeQL CII Best Practices Discord crates.io nuget

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. MsQuic also has C++ API wrapper classes and exposes interop layers for both Rust and C#.

Protocol Features

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.

Library Features

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.

Documentation

Contributing

For information on contributing, please see our contribution guidelines. Feel free to take a look at our Good First Issues list if you're looking for somewhere to start. If you'd just like to talk, come chat with us on Discord.