CONCEPT Cited by 1 source
Selectively reliable video transport¶
Definition¶
Selectively reliable video transport is the research direction of making QUIC's reliability model per-frame selective: not every video frame must be reliably delivered. Less-critical frames (B-frames, non-keyframes, frames in already-displayed GoP) could be dropped instead of retransmitted, preserving stream smoothness in the face of loss.
Zalando's 2024-06 post flags this as the next major research frontier for video streaming over HTTP/3 (Source: sources/2024-06-17-zalando-next-level-customer-experience-with-http3-traffic-engineering).
The problem QUIC creates¶
QUIC streams are reliable by default — a lost packet stalls the stream until retransmission succeeds. For file transfer and API traffic, this is the right behaviour. For real-time video, it's a stall:
"The real-time video streaming with QUIC over less than ideal network conditions faces an issue due to the reliable nature of the protocol. Retransmissions of lost packets in a video stream, inadvertently lead to stalls in the video stream. It also performs poorly when it encounters packet losses that are not due to congestion."
4K UHD as the canonical workload¶
Zalando names the bar:
- 4K UHD (3840×2160) at 60 fps with H.265 encoding.
- Bandwidth: 30–50 Mbps.
- Packet latency: 6–11 ms.
- Reliability target: 99.999 % packet delivery.
- HEVC-compressed video: ~5.6 MB / second.
Meeting these constraints is hard on 5G mid-bands (see RAN bottleneck); when loss occurs, reliable retransmit stalls the frame budget.
The proposed direction¶
Zalando frames it concretely:
"This is another improvement opportunity for QUIC to offer a selectively reliable transport wherein not all video frames are delivered reliably, we can optimise video streaming and improve end-user experiences. We believe this improvement impacts content consumption by supporting up to 4096 × 2160 at 60fps (True 4K)."
The architectural idea: let the application (the video encoder / streaming client) tell the transport which frames are skippable-on-loss vs must-deliver. The transport applies its reliability guarantee per-frame.
Prior art in adjacent protocols¶
- RTP / RTCP — classic real-time media transport over UDP is unreliable by default; applications handle reliability and jitter via FEC + playout buffer.
- UDP-without-retransmit — many video-conferencing systems (WebRTC, SRT) use UDP directly precisely to skip HTTP/HTTPS's reliability model.
- QUIC DATAGRAM extension (RFC 9221) — QUIC added unreliable datagrams as an extension; applications can send messages that are not retransmitted. Gives QUIC an unreliable-alongside-reliable mode, though not the per-frame selective-reliability Zalando frames as the ideal.
Wiki framing¶
Selectively reliable video transport sits at the intersection of three constraints:
- QUIC's reliability default — right for most traffic, wrong for real-time video.
- RAN bottleneck — 4K UHD is compute-and-bandwidth-bound at 5G mid-bands.
- 4K UHD as the demand driver — market pull for video quality puts pressure on the transport layer.
Zalando presents it as an aspirational research frontier, not a shipped Zalando feature; the post's closing axis.
Seen in¶
- sources/2024-06-17-zalando-next-level-customer-experience-with-http3-traffic-engineering — canonical wiki instance. Zalando's closing research direction alongside DRL CC.
Related¶
- concepts/quic-transport — the reliability model in question.
- concepts/http-3 — the application-layer carrier.
- concepts/radio-access-network-bottleneck — the constraint that makes selective reliability valuable.
- concepts/bbr-congestion-control — the CC algorithm that pairs with real-time video workloads.