About MOQ Edge — Your Reference for Media over QUIC
MOQ Edge is an automated intelligence feed for the Media over QUIC (MOQ) protocol and its surrounding ecosystem. We surface IETF draft updates, open-source implementation releases, and CDN adoption news so that streaming engineers and protocol researchers always have the full picture.
What is Media over QUIC (MOQ)?
Media over QUIC is a new application-layer protocol being standardized by the IETF MOQ working group. It defines a publish/subscribe model for media delivery where a publisher emits named objects (compressed frames, audio samples, timed metadata) organized into tracks and groups; relay nodes accept those objects over a QUIC transport connection and forward them to every active subscriber. Because each object travels on its own independent QUIC stream, a single lost UDP packet can stall at most one video frame — not the entire broadcast. The result is low-latency streaming with the fan-out economics of a traditional CDN.
The core specification, draft-ietf-moq-transport, is produced by the IETF MOQT working group. Chartered in 2023, the group has met biweekly to refine the protocol's object model, relay forwarding rules, subscription management, and congestion-response primitives. Companion drafts define the catalog format (how subscribers discover available tracks), media mapping (how H.264/H.265/AV1 frames map to MOQ objects), and low-overhead variants for constrained edge devices. Every revision is publicly visible on the IETF Datatracker, and MOQ Edge ingests each new draft the day it is posted.
The MOQ protocol matters because the two dominant live-streaming approaches today each carry a fundamental tradeoff that QUIC transport can dissolve. HTTP segmented delivery (HLS, DASH, LL-HLS) reuses existing CDN infrastructure at the cost of 3–30 seconds of buffering latency — unacceptable for live sports betting, real-time auctions, or interactive broadcast. WebRTC achieves sub-second latency but imposes a peer-to-peer session model that scales poorly beyond a few hundred concurrent viewers without expensive Selective Forwarding Unit (SFU) servers. MOQ sits in the empty quadrant: sub-second glass-to-glass latency and relay-tree scalability to millions of subscribers, both unlocked by QUIC's multiplexed stream design and 0-RTT connection resumption.
| Protocol | Latency | Scale | Transport | Status |
|---|---|---|---|---|
| HLS / DASH | 3 – 30 s | CDN-scale | HTTP/TCP | Production |
| LL-HLS / LL-DASH | 2 – 5 s | CDN-scale | HTTP/TCP | Production |
| WebRTC | < 500 ms | SFU-limited | UDP/DTLS | Production |
| MOQ protocol | < 500 ms | CDN-scale | QUIC / WebTransport | IETF Draft |
What We Cover
MOQ Edge aggregates signal across the full MOQ ecosystem — protocol specifications, code, and industry adoption — so you get a complete picture in one place.
IETF MOQ Working Group Drafts
We automatically ingest every new revision of draft-ietf-moq-transport, draft-ietf-moq-catalogformat, and companion drafts the day they are published to the IETF Datatracker.
Open-Source Implementations
Releases, tags, and notable commits from moq-rs, moq-go, quic-go, MoQ.js, and the growing ecosystem of MOQ protocol libraries on GitHub.
CDN & Infrastructure Adoption
Engineering blog posts, conference talks, and product announcements from Akamai, Cloudflare, Fastly, Meta, and other CDN operators experimenting with the MOQ protocol.
WebTransport Integration
Browser support timelines, spec changes, and implementation notes for WebTransport — the HTTP/3 API that delivers MOQ to web clients without native QUIC sockets.
WebCodecs & Media Pipeline
How WebCodecs pairs with MOQ to encode and decode media frames in the browser, enabling low-latency streaming without Flash- or plugin-era hacks.
IETF Mailing List Threads
Active design discussions from the moq@ietf.org mailing list, surfaced in plain English so you stay current without reading raw RFC-style email threads.
Why MOQ Edge
Our mission is to be the most reliable single source for engineers and researchers who need to track the MOQ protocol without subscribing to multiple IETF mailing lists, monitoring dozens of GitHub repositories, and combing through CDN engineering blogs by hand. The MOQ space moves fast — new draft revisions, implementation releases, and design decisions arrive weekly — and staying current is a real time cost.
Our pipeline is fully automated. A daily cron job polls the IETF Datatracker for new draft-ietf-moq-* revisions, the GitHub API for releases and significant commits from tracked MOQ implementation repositories, and the IETF mailing list archive for notable Working Group threads. Each item is summarized, categorized, and published to the news feed with a source-traceable link back to the original. Summaries are generated programmatically so you can decide in seconds whether a given update warrants deeper reading.
Our audience includes streaming engineers evaluating whether to prototype on MOQ before the RFC is finalized, CDN platform teams scoping relay infrastructure investments, protocol researchers following the IETF standardization process, and open-source developers building MOQ client and server libraries. If you work anywhere in the real-time media delivery stack, the MOQ protocol transition will affect you — and MOQ Edge is designed to make sure you see it coming.
Frequently Asked Questions
Common questions about the Media over QUIC protocol, the IETF standardization process, and how MOQ compares to existing streaming technologies.
What is MOQ (Media over QUIC)?
How does the MOQ protocol differ from HLS and DASH?
How does MOQ compare to WebRTC?
What is the IETF MOQ working group?
When will MOQ be production-ready?
What is QUIC transport and why does MOQ use it?
Does MOQ replace WebRTC entirely?
Explore the MOQ Protocol Coverage
Stay current on the MOQ protocol
Get the weekly MOQ digest — IETF draft updates, new implementations, and ecosystem news delivered to your inbox.
No spam. Unsubscribe anytime.