| commit | b159ab09b25b9049577899cd69f70f3b04a486c2 | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Mon Jan 30 10:58:46 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 30 10:59:32 2023 -0800 |
| tree | ed779f259c0d24f5db3f8de0f221197637f13171 | |
| parent | 1fdac9bdbf85d27537e8ce47ca4f1eaa034f1ff5 [diff] |
Implement QUIC server preferred address (SPA) on server side. Basically advertising SPA and handling clients migrating to using SPA. Current implementation is a half-way SPA which advertises SPA in transport parameters and accepts packets received on SPA, but the server doesn't validate the migration nor does it switch to use SPA to send packets(go/quic_server_migration). The behavior is behind config knobs QuicConfig::SetIPv(4|6)AlternateServerAddressToSend(). PiperOrigin-RevId: 505741961
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.