QUIC draft

The new Media over QUIC draft follows live video from camera to audience

Two people can open the same livestream at the same moment and see different parts of it. One hears the host finish a sentence while the other is still waiting for the question. In an online live casino, that gap can leave the dealer on screen collecting cards from one hand while the interface has already opened the next. The timing depends on what happens to the video between the camera and each viewer.

On November 2, the Internet Engineering Task Force’s working group published revision 23 of its Media over QUIC transport draft. The proposal gives services a common way to send live media directly or through relays. Instagram Live has already put part of that approach into production, giving the latest draft a real deployment to read alongside it.

The camera sends the first leg

The first part of a broadcast starts on the host’s phone or camera and ends at the service receiving the signal. Engineers call it ingest. A presenter walking through a crowded venue can see an uninterrupted preview on their own screen while the phone’s connection to the service deteriorates. Viewers may then see the picture freeze even though the presenter keeps talking.

The service must also get the feed out to everyone watching. That second leg can involve several distribution points and thousands of connections under different conditions. A platform can change how it receives video without changing how an audience receives it.

What Instagram Live changed first

In October, Meta described in its Instagram Live engineering report how it was using Media over QUIC for ingest on iOS and Android. Its engineering team reported that the new path matched the previous one on the streaming quality and reliability measures used for the rollout. That result concerns the path from the person broadcasting to the service. End-to-end delivery using the protocol is a separate step in Meta’s plans.

The rollout illustrates why a platform might tackle one stage at a time. If it replaces the first leg while keeping the rest in place, it can observe how the change behaves without rebuilding the entire delivery chain. A creator can start a broadcast the usual way while the engineering team compares performance behind the scenes. Meta also describes keeping a way to fall back to another transport on networks that block or limit the traffic QUIC needs. That fallback matters when broadcasters connect from unfamiliar networks.

What a relay can pass along

The IETF draft describes a system in which a publisher offers media and subscribers ask for the tracks they need. A relay can receive material upstream and pass it downstream to subscribers. Picture a broadcast with audio and video traveling separately. A service can make decisions about how to forward each track instead of treating the whole feed as a single undifferentiated file.

Priorities also give the service a way to handle time-sensitive material. In a live conversation, for instance, sound that arrives too late may have already lost much of its value. A recording assembled after the event can place more weight on receiving every part. The same source material can therefore serve audiences with different timing needs.

How a stream can recover without drifting further behind

Every live player has to decide how much material to hold in reserve. Keeping more video ready can smooth out a burst of uneven delivery. It also adds time between when something happens and when the viewer sees it. With a smaller buffer, the screen stays closer to the camera, while the player has less time to recover a late frame.

A short disruption can also leave viewers behind even after their connection improves. A service then needs a way to return them closer to the live point. Depending on the implementation, it might move past video that is already too old to be useful. The protocol gives engineers tools for those decisions. The service still has to choose how much delay its audience can tolerate.

The test that matters to an audience

A broadcaster can measure the time from the camera to the viewer by putting a clock in the shot and comparing it with the clock beside the receiving screen. Repeating that check after a viewer changes networks or after the stream briefly stalls shows how quickly playback returns to its normal delay. For a session with audience participation, the team can measure separately how long it takes to acknowledge a response.

The IETF document is still an Internet-Draft. The Instagram deployment offers evidence about the start of the route at a large service. The next useful result would come from measuring the whole route under the conditions viewers actually encounter, including the moment the broadcast falls behind and how it catches up.