Media Over QUIC can scale real-time streaming and carry the world's vids

The low latency of WebRTC, the scalability of DASH, and perhaps no need for CDNs Bruce Davie Bruce Davie Published wed // UTC SYSTEMS APPROACH A few weeks ago, Larry and I independently received the same advice from two different sources: take a look at Media Over QUIC (MoQ) for your next edition. I’ve been following the standardization of QUIC for several years (and wrote about it) but MoQ had not yet come onto my radar. A quick look at some IETF drafts gave me some of the main concepts, but it can be frustratingly hard to pick out the important high-level ideas from the masses of protocol-specific detail that goes into an Internet draft. And there are enough moving parts to MoQ for it to present another case of the blind men and the elephant. I’m going to explain what I think is important about MoQ in this post. For one thing, the name doesn’t get across what is interesting to me about MoQ. Yes, it can be used to transmit media (e. g., video and audio) using QUIC as the underlying transport protocol. But you can do that today just by watching a video on the web if the server happens to support HTTP3 over QUIC. There is something else going on with MoQ. In my view, MoQ occupies a middle ground between WebRTC (which is used for lots of video conferencing applications like Google Meet) and DASH (Dynamic Adaptive Streaming over HTTP) which powers most entertainment video streaming on the web. If I take some of the proponents of MoQ at face value it could replace both those technologies, but more realistically I can see it filling a gap when neither DASH nor WebRTC is the ideal choice. So let me first explain the two bookends that MoQ sits between. There are two handy blogs positioning MoQ against WebRTC and DASH that helped me form the views below, so you may want to go back to the source. WebRTC is a collection of protocols and APIs (backed ) that enable a real-time media stream to be established between a pair of web browsers. There are quite a few problems that need to be solved, such as getting access to the camera and audio devices, and building an end-to-end connection between two hosts that might both be sitting behind NATs and firewalls. The media is sent using RTP over UDP (usually).