Ignore key_update_not_yet_support transport parameter

When we first introduced IETF QUIC key update, we were communicating with older versions of our implementation that didn't support this feature. If we updated keys when communicating with that older software, the connection would fail. To avoid that, we had added a temporary key_update_not_yet_support transport parameter that would disable key updates. We stopped sending that transport parameter when we added support for key updates in Chrome m88. That version is no longer in any experiments, and also that version did not yet have IETF QUIC default-enabled, so we are guaranteed to not be communicating using IETF QUIC with this old software any more. It's therefore safe to remove this transport parameter as it no longer provides value. Once we deprecate the flag, we'll remove transport parameter entirely.

Protected by FLAGS_quic_reloadable_flag_quic_ignore_key_update_not_yet_supported.

PiperOrigin-RevId: 402628993
4 files changed
tree: 72486cc3758fd37a819a368dcf1b40b31e8d3bea
  3. README.md
  4. common/
  5. epoll_server/
  6. http2/
  7. quic/
  8. spdy/


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.