Visit [Github](/source) or join [Discord](https://discord.gg/FCYF3p99mr)
We are designing a protocol that is simple and yet flexible enough to support the wide range of use-cases: -from ultra-low latency to ultra-high quality, 1 viewer to 1 million viewers, and everything in -between. It's possible by evaluating the entire ecosystem and breaking the problem into layers: +from ultra-low latency to ultra-high quality, 1 viewer to 1 million viewers, contribution and distribution, and everything in +between. It's possible by carefully breaking the protocol into layers: - **QUIC**: Provides the networking: independent streams and datagrams. -- **WebTransport**: Provides web support for QUIC. -- **MoqTransport**: Designed specifically for CDNs with built-in caching and fanout. -- **Catalog**: Describes the available media tracks: the codec, container, resolution, etc. -- **Container**: [quic.video](https://quic.video) uses CMAF and is backwards compatible with HLS/DASH, but it's not required. +- **WebTransport**: (optional) Provides web support for QUIC. +- **MoqTransport**: Designed specifically for CDNs and mass fanout. +- **Catalog**: Describes the available tracks: the codec, container, resolution, etc. +- **Container**: Describes the encoding of each track. + +This website uses CMAF for backwards compatibility with HLS/DASH but it's not required. +You can use whatever encoding the encoder/decoder agree to support, including for non-media purposes like chat, input, metadata, etc. MoQ is still very early in development and many features are missing. Everything is liable to change, especially if you get involved! -Check out the current [Issues](/issues) and **Roadmap**
+If you want to help, check out the [major issues](/issues)
The protocol is being developed by the [IETF MoQ working group](https://datatracker.ietf.org/group/moq/about/). The