Support draft-07 version of WebTransport.

See <https://www.ietf.org/archive/id/draft-ietf-webtrans-http3-07.html#name-changes-between-draft-versi> for the draft version changelog.

This CL makes QUICHE capable of negotiating draft-07, and enforces the parameter constraints related to draft-07; specifically, the requirement to explicitly support extended CONNECT and HTTP datagrams (it also de-supports pre-RFC datagrams SETTINGS codepoint for the new version only).

Of non-backwards-compatible changes, our code is still missing WEBTRANSPORT_STREAMS position enforcement, and MAX_SESSIONS support.

PiperOrigin-RevId: 542260756
12 files changed
tree: 15e3e168483011b0ea76c776344ca300b1f2dd5a
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. BUILD.bazel
  6. CONTRIBUTING.md
  7. LICENSE
  8. README.md
  9. WHITESPACE
  10. WORKSPACE.bazel
README.md

QUICHE

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.