Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
Перейти к файлу
Nick Banks 22805951c1
Fix Mirror AZP Stage (#147)
2020-02-17 10:34:16 -08:00
.azure Fix Mirror AZP Stage (#147) 2020-02-17 10:34:16 -08:00
.github Add GitHub Issue Templates (#142) 2020-02-14 11:33:46 -08:00
docs Readme and Build Doc Improvements (#143) 2020-02-14 14:41:25 -08:00
scripts Move PowerShell Scripts out of Root (#132) 2020-02-12 15:27:44 -08:00
src Add missing #define causing KArray to fail to build on debug (#133) 2020-02-12 15:59:48 -08:00
submodules Update OpenSSL submodule to the latest commit. (#113) 2020-02-07 18:41:04 -08:00
.gitignore Initial Commit of MsQuic Code (#1) 2019-10-30 14:51:06 -07:00
.gitmodules Update submodules (#34) 2020-01-11 18:35:25 -08:00
CMakeLists.txt Clean up build warnings and errors (#91) 2020-02-11 18:02:19 -08:00
LICENSE Initial Commit of MsQuic Code (#1) 2019-10-30 14:51:06 -07:00
README.md Readme and Build Doc Improvements (#143) 2020-02-14 14:41:25 -08:00

README.md

MsQuic

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.

Important The MsQuic library, as well as the protocol itself, is still a work in progress. Version 1 is not yet finalized and may continue to experience breaking changes until it is finalized.

Build Status

Protocol Features

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.
  • Exchange application data in the first round trip (0-RTT).
  • Survives a change in the clients IP address or port.
  • Easily extendable for new features (such as unreliable delivery).

Important Several QUIC protocol features are not yet fully implemented:

  • 0-RTT with Schannel and OpenSSL
  • Client Migration
  • Server Preferred Address
  • Path MTU Discovery

Library Features

  • Cross-platform support.
  • Optimized for client and server.
  • Optimized for maximal throughput and minimal latency.
  • Asynchronous IO.
  • Receive side scaling (RSS).
  • UDP send and receive coalescing support.

Documentation

Contributing

For the time being, external code contributions will not be accepted. We are still working on setting up internal repository sycnhronization, continuous integration, and generally ironing out our processes.

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 opencode@microsoft.com with any additional questions or comments.