Add section: MoQ/WARP — Media over QUIC (Draft-17, 2026)

[alexbj75]

Summary

Media over QUIC (MoQ) is the most significant emerging streaming protocol of the coming 2–3 years and is completely absent from this repo. Anyone entering the streaming field in 2026 needs to know what it is and where it is heading.

What MoQ is

MoQ (Media over QUIC) / WARP is a new transport protocol being standardized by the IETF MoQ Working Group. It aims to combine:

• WebRTC-level latency
• HLS/DASH-level scalability
• A unified protocol for both interactive and broadcast streaming

Current status (March 2026):

• draft-ietf-moq-transport-17 published March 2026
• Cloudflare running production relay network in 330+ cities
• Not yet production-ready for broad deployment (Safari lacks WebTransport support)
• Expected to become a primary streaming transport protocol within 2–3 years

Why include it now

Every streaming engineer working over the next few years will encounter MoQ. An onboarding resource that doesn't mention it leaves newcomers unprepared for where the field is heading. The key is to frame it correctly: strategic awareness, not production deployment.

Eyevinn OSS implementations

Eyevinn has two MoQ repos worth referencing:

• warp-player — https://github.com/Eyevinn/warp-player — MoQ WARP player implementation
• moqlivemock — https://github.com/Eyevinn/moqlivemock — MoQ live streaming mock server

Suggested content

A section under emerging protocols covering:

• What problem MoQ solves (latency + scale, the tradeoff that currently requires choosing between WebRTC and HLS)
• Current status vs. production readiness
• IETF working group and spec references
• Eyevinn's OSS implementations as hands-on exploration tools

References

• IETF MoQ WG: https://datatracker.ietf.org/group/moq/about/
• draft-ietf-moq-transport: https://datatracker.ietf.org/doc/draft-ietf-moq-transport/
• Cloudflare MoQ: https://blog.cloudflare.com/moq/