| commit | fe093fd39a9a4aa6f41b1b9247f3f4693ceec6fa | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Tue Jun 17 11:32:09 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jun 17 11:33:05 2025 -0700 |
| tree | 4b95e435cc53d44cf835322c190c2ae693fa12b5 | |
| parent | b541621d2faf9f610feb77f64c462acba96b16cc [diff] |
This PR adds the support to probe alternative path on RTO instead of receiving a new connection ID. If RTO triggers while the client is not actively validating a path, it will probe for the multipath on RTO. ``` - The PR adds the connection option "MPR1". - Probe for alternative path on RTO. - Add kMPR1 option to enable probing on RTO. - Add unit test and e2e test. ``` Protected by QUIC connection option for multiport. PiperOrigin-RevId: 772554253
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.