IETF Interim: Media Over QUIC (MOQ) 2026-03-30 16:30
Why It Matters
Standardizing server‑side ABR and relay metadata in MOQ will enable lower‑latency, more reliable streaming services, directly impacting content providers and end‑users as QUIC becomes the backbone of next‑generation media delivery.
Key Takeaways
- •Server‑side ABR demo highlights latency and bitrate switching challenges.
- •Relay requires formal metadata exchange for track selection, not yet standardized.
- •Bandwidth estimation fluctuates with small objects; smoothing algorithms essential.
- •Seek operations force client‑side ABR, complicating server‑side implementation.
- •Upcoming IETF interims will address rewind, filters, DTS, and draft timelines.
Summary
The IETF Media over QUIC (MOQ) interim on March 30 convened to review progress on server‑side adaptive bitrate (ABR) implementations and to map the roadmap toward the next working‑group calls. After administrative introductions, the meeting featured a live demo of a server‑side ABR pipeline, showcasing video ingestion via FFmpeg, CMA‑to‑CMSF repackaging, and a custom H5JS player that reports real‑time buffer and ABR decisions. Key insights emerged around the need for a formal mechanism for relays to obtain precise track metadata—bitrate, availability, and other attributes—since the current workaround of passing raw catalogs is outside the standard. The demo revealed that bandwidth estimation based on per‑object download times can be volatile, especially for small objects, underscoring the importance of smoothing algorithms. Additionally, the team highlighted a latency penalty when switching down to a lower bitrate because the high‑bitrate data already in flight cannot be cancelled. During the demonstration, the buffer dropped sharply when the bandwidth limit was reduced from 15 Mbps to 5 Mbps, prompting a publish/okay handshake that took roughly one round‑trip to effect the switch. The presenters noted that the inability to abort ongoing object downloads prolongs rebuffering, and that seek operations currently force a fallback to client‑side ABR via fetch commands, adding complexity. They called on the working group to consider status‑exchange extensions, such as exposing player buffer length, to improve server‑side decisions. The session concluded with a roadmap outlining upcoming virtual and hybrid interims focused on rewind, filters, DTS, and draft finalization. The discussions signal that standardizing relay metadata exchange and refining server‑side ABR logic are critical steps toward achieving truly low‑latency, high‑quality streaming over QUIC.
Comments
Want to join the conversation?
Loading comments...