MOQT Message formats from draft-02.

Also totally refactored the API for sending Objects. Now that the spec clarifies the stream mapping, applications simply indicate the forwarding preference, and MoqtSession does all the stream management (except that the application indicates when the stream is done.)

Not in production.

PiperOrigin-RevId: 603743999
25 files changed
tree: 44da2bcb0f12af1ee45f4bce2aed46a72675124d
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. .bazelversion
  6. BUILD.bazel
  11. WORKSPACE.bazel


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

QUICHE is only supported on little-endian platforms.