|author||haoyuewang <email@example.com>||Thu Dec 09 07:58:25 2021 -0800|
|committer||Copybara-Service <firstname.lastname@example.org>||Thu Dec 09 07:59:12 2021 -0800|
Add knobs that enable QBONE to use IETF QUIC. Particularly, 1) --qbone_server_support_h3_loas defined in gfe_quic_dispatcher.cc enables QBONE server to support both gQUIC & IETF QUIC. 2) --qbone_client_use_h3_loas defined in bonnet_server.cc makes QBONE client to use IETF QUIC exclusively. These two flags are set up assuming: 1) --qbone_server_support_h3_loas can be enabled for all servers. 2) --qbone_client_support_h3_loas can then be enabled gradually for all clients. And the two flags should not be enabled until the following TODOs are done: 1) Add a special ProofSource that provides fake certificate. 2) Add code and test that handles messages/streams before LOAS2 authentication is done on the client side. 3) Set the idle timeout correctly in between TLS handshake done and LOAS2 handshake done. PiperOrigin-RevId: 415266155
QUICHE stands for QUIC, Http/2, 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.