CDNTechnical DevelopmentNovember 18, 2026

IETF 127 advances Media Over QUIC protocol with CMAF integration

IETF 127 advances Media Over QUIC protocol with CMAF integration

The IETF Media Over QUIC (MOQ) working group met at IETF 127 to discuss protocol refinements, including CMAF integration, fill-fetch mechanisms, and denial-of-service protections. The session focused on resolving outstanding issues to advance the draft toward a working group last call.

Key Takeaways

  • Working group replaced joining fetch with a new fill-fetch mechanism to handle stream catch-up and seeking more efficiently
  • MPEG Systems Group expressed concerns regarding potential divergence between IETF's Lock Media Over QUIC and standard CMAF file formats
  • New denial-of-service protections include rate-limiting request updates and managing 'gone' object states to prevent relay resource exhaustion
  • Google and Cisco engineers debated limiting subscriptions to a single concurrent fill-fetch to prevent rapid-reset style attacks

Why It Matters

The transition of Media Over QUIC from experimental drafts to a stable standard is critical for reducing latency in live streaming and interactive video. By refining how CMAF objects are transformed on the wire, the IETF is attempting to bridge the gap between traditional file-based delivery and real-time transport. This development forces a strategic choice for CDNs like Akamai and AWS between maintaining strict MPEG compatibility or adopting IETF-specific optimizations for performance. Watch for the upcoming February interim meeting in Europe to resolve the 'Lock Media Over QUIC' scope dispute and finalize the working group last call timeline.

In short

At IETF 127, the Media Over QUIC working group refined its protocol to improve low-latency streaming. Key updates include a new fill-fetch mechanism for stream catch-up and enhanced denial-of-service protections. These developments are vital for bridging the gap between traditional file-based delivery and real-time transport for interactive video applications.

FAQ

What is the purpose of the new fill-fetch mechanism?

The fill-fetch mechanism replaced the joining fetch to handle stream catch-up and seeking more efficiently within the Media Over QUIC protocol.

What concerns did the MPEG Systems Group raise?

The MPEG Systems Group expressed concerns regarding potential divergence between the IETF's Media Over QUIC and standard CMAF file formats.

What new denial-of-service protections were discussed?

New protections include rate-limiting request updates, managing 'gone' object states to prevent relay resource exhaustion, and limiting subscriptions to a single concurrent fill-fetch.

When is the next meeting to discuss the protocol?

An interim meeting is scheduled for February in Europe to resolve the 'Lock Media Over QUIC' scope dispute and finalize the working group last call timeline.


Read full article at youtube.com

Enjoy our coverage?

Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.

Add as preferred source

Related Articles

Get this in your inbox → Subscribe