What is WoQ?
Media Over QUIC (MoQ) is an emerging transport protocol (IETF Protocol) designed to efficiently deliver low-latency, interactive multimedia content over the internet, it utilizes QUIC (Quick UDP Internet Connections) transport protocol
- Its designed to ingest and distribution of live media efficiently
- MoQ takes advantage of QUIC’s features, such as
multiplexing,flow control, andcongestion control, to provide a reliable, efficient, and scalable way to deliver multimedia content.
MoQ is meant to unify how media is published and received, so the same protocol can support both contribution and distribution of live streams. The IETF working group describes it as a simple low-latency media delivery solution that can work in browser and non-browser endpoints. It is built around QUIC, which gives modern transport features and supports relays, caches, and replication points for scale.
Media Over QUIC (MoQ) is an IETF-standardized protocol designed to deliver ultra-low latency live streaming at scale
Key Features of MoQ
- Low-latency: MoQ is designed to minimize latency, making it suitable for real-time communication applications such as video conferencing, online gaming, and live streaming.
- Multiplexing: MoQ allows multiple media streams to be multiplexed over a single connection, reducing the overhead of establishing and maintaining multiple connections.
- Scalability: MoQ is designed to scale to meet the needs of large-scale media distribution, making it suitable for applications such as live event streaming and video-on-demand services.
- Congestion control: MoQ incorporates advanced congestion control mechanisms to ensure that media streams are delivered efficiently and reliably, even in the presence of network congestion.
Key attributes of MoQ include:
- Sub-Second Latency: Delivers WebRTC-like, real-time interactivity (under 1 second) directly within browsers without requiring the complex session management of WebRTC.
- Publish/Subscribe Architecture: Rather than using traditional HTTP request/response files, publishers announce named “tracks” (e.g., audio, video, metadata), and clients subscribe to them directly, pulling only the data they need.
- Built on QUIC: Leverages modern transport features—such as connection multiplexing, independent streams, and datagrams—to bypass the head-of-line blocking and handshake delays associated with older protocols like TCP.
- Scalable Distribution: Uses intelligent relay networks to “fan-out” content to large audiences while caching streams, allowing it to easily scale across generic Content Delivery Networks (CDNs) much like HLS or DASH.
- Hierarchical Object Model: Breaks media down into a structured hierarchy—Tracks, Groups (e.g., Video GoPs), and Objects (e.g., Video Frames)—giving applications precise control over what gets delivered and in what priority.
- Tunable Reliability: Supports partial reliability and prioritized delivery, ensuring that important packets take precedence while less critical packets are dropped rather than stalling playback during network congestion.
Use cases
- Live streaming: low-latency broadcast and interactive live events.
- Gaming: fast media delivery where timing is important.
- Media conferencing: browser and native conferencing systems.
- Contribution and ingest: getting live media from producers into a delivery network.
- Distribution at scale: pushing live media through relays or CDN-like infrastructure.
Trends Around MoQ
- Increased Adoption of QUIC: The adoption of QUIC as a transport protocol is increasing, with many major internet companies, such as Google, Facebook, and Microsoft, already using it in their products and services.
- Growing Demand for Low-Latency Video: The demand for low-latency video is growing, driven by applications such as live streaming, online gaming, and virtual reality.
- 5G and Edge Computing: The roll-out of 5G networks and the increasing adoption of edge computing are creating new opportunities for MoQ to deliver low-latency, high-quality video and audio streams.
- Cloud Gaming: MoQ can be used to deliver low-latency, high-quality video and audio streams for cloud gaming applications, such as Google Stadia and Microsoft xCloud.
- Standardization: There is a growing trend towards standardization of MoQ, with efforts underway to develop standardized protocols and APIs for MoQ.
Challenges and Limitations
- Complexity: MoQ requires a deep understanding of QUIC and multimedia transport protocols, which can be complex and challenging to implement.
- Interoperability: MoQ may require additional infrastructure and equipment to ensure interoperability with existing networks and devices.
- Security: MoQ requires robust security measures to protect against threats such as hacking and eavesdropping.
- Scalability: MoQ may face scalability challenges as the number of users and devices increases, requiring significant investments in infrastructure and resources.
Overall, MoQ has the potential to revolutionize the way multimedia content is delivered over the internet, enabling new use cases and applications that require low-latency, high-quality video and audio streams. However, there are also challenges and limitations that need to be addressed to ensure the widespread adoption of MoQ.
Properties
| Transport protocol | QUIC (Quick UDP Internet Connections) |
| QUIC is developed by | Google in 2012 |
| Now managed by | IETF - The Internet Engineering Task Force |
| MoQ is designed for | Low-latency, real-time media transmission |
| Supports | Video, audio, and other multimedia streams |
| Key features | Reduced latency, improved packet loss resilience, and enhanced security |
| Network requirements | UDP (User Datagram Protocol) support |
| Compared to | Traditional TCP-based media transmission protocols, such as TCP and HTTP |
| Specification | Defined in RFC 9227 (published in 2022) and other related IETF documents |
| Implementation status | Implemented in various media streaming platforms, including Google’s own services |
| Advantages over traditional protocols | Improved performance, reduced packet loss, and better support for real-time media transmission |

