







This document provides a high-level overview of the Media over QUIC (MoQ) protocol suite. It describes the architecture, data model, transport protocol, streaming formats, and security mechanisms that together enable scalable low-latency media delivery over the Internet. The document explains how these components relate to each other and how they are composed to create interoperable media applications.
Media over QUIC Transport
This document defines Media over QUIC Transport (MOQT), a publish/ subscribe protocol that runs over QUIC and WebTransport. MOQT leverages the features of these transports, such as streams, datagrams, priorities, and partial reliability. MOQT operates both point-to-point and through intermediate relays, enabling scalable low-latency delivery. Despite its name, MOQT is media agnostic and can be used for a wide range of use cases.

Media over QUIC
Media over QUIC is a new live media protocol designed for simplicity and scale. It uses new browser technologies like WebTransport and WebCodecs to deliver media with latency that rivals WebRTC.
QUIC API for Peer-to-peer Connections
This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received from another browser or device implementing the QUIC protocol. The specification for multiplexing of QUIC with STUN/TURN/ZRTP/DTLS/RTP/RTCP [[RFC9443]] was developed within the IETF AVTCORE Working Group.
ATOM: AT Protocol Over MoQ Transport
This document specifies how the Authenticated Transfer (AT) Protocol can leverage Media over QUIC Transport (MOQT) for efficient data synchronization across decentralized social networks. The AT Protocol's firehose event stream and repository synchronization mechanisms map naturally to MOQT's publish/subscribe model, enabling scalable relay infrastructure, priority-based delivery, and improved resilience for large-scale social data distribution. This specification addresses the challenges of the current WebSocket- based transport and demonstrates how MOQT's relay architecture, group-based caching, and multiplexed streams provide significant benefits for AT Protocol deployments at scale.
Media PDS / Service
So recently there’s been some discussion about video on demand and how that may work for AT Protocol. I’ve been thinking a bit about this topic recently, since solving video and larger media files would unlock some interesting new classes AT Protocol applications. There’s a few different considerations here: Storing large media objects with in your PDS is likely not possible — the PDS implementation distributed by Bluesky PBC has a default 5mb blob size limit. Whilst that can be increased, it...

Going Peer to Peer with QUIC
Marten Seemann and I just published an entry on his blog, A p2p Vision for QUIC. This is a technical argument, explaining how a series of small improvements to the QUIC standards would suffice to make QUIC a great peer-to-peer (P2P) protocol. I personally love it, because the Internet suffers greatly from excessive centralization, with big platforms acting as gatekeepers. Currently, pretty much all user activities on the Internet are mediated by “services in the cloud”. Take for example something as simple as a security camera in your home. People want to check the camera images when they are outside the home. They cannot connect to the camera or even a home server directly, because the home network is “behind a NAT” – and very possibly behind multiple layers of NAT, given the scarcity of IPv4 addresses. The practical solution is to export the images from the camera to a “service in the cloud”, and to let user contact that service from their cellphone. It works, but it has obvious issues for privacy, security, or even continuity of service: if the cloud service stops, the camera gets bricked. The proposed QUIC architecture would provide a generic solution using the Masque standard for relaying QUIC, combine with QUIC NAT traversal extensions to migrate connections from “using the relay” to “directly P2P”, as shown in the following diagram. +------------------------------+ | Step 1: phone contacts | v the camera through +---|---+ +-----------+-+ the relay | Phone | | Masque ^ | +---|---+ | Relay | | | +-----------|-+ +-------------------------+ | | Step 2: phone and camera cooperate +-----|----|-+ and establish a "hole" in the NAT. | NAT | | | +-----|----|-+ Step 3: traffic flows directly | | between phone and camera without +-|----|-+ burdening the relay | Camera | +--------+ The standards to achieve that are almost ready. The relaying of incoming connections is described in the UDP Listen, already adopted in the Masque Working Group. A draft submitted to the IETF QUIC Working Group describes the Using QUIC to Traverse NAT, and another describes QUIC Address Discovery. I have already implemented the Address Discovery draft in picoquic, and intend to promptly implement the other two drafts. Using QUIC has many advantages. The communications are encrypted end to end, even when they are going through the relay, which has nice security and privacy benefits. The relay is uses standards and is not dependent on the application; if a relay goes out of business, just pick another one. In the weird cases where the NAT traversal fails, the application still works. There are of course many more applications of P2P possible, such as for example direct video calls between two homes, video games and more. The vision is clear: we can do all those applications using QUIC.
S2PA and MUXL: Bringing Video to Content-Addressed Systems - How Streamplace Works
S2PA and MUXL: Bringing Video to Content-Addressed Systems - How Streamplace Works
A p2p Vision for QUIC
Using QUIC to achieve everything needed for NAT traversal, from address discovery to proxying UDP
airsonic/airsonic
:satellite: :cloud: :notes:Airsonic, a Free and Open Source community driven media server (fork of Subsonic and Libresonic)
FOSDEM 2026 - iroh p2p connections
iroh is a library to establish direct connections between two peers, wherever they are on the internet. It takes care of using different transports and holepunching as needed, to reliably establish connectivity. To the application a normal QUIC connection is presented. The aim is to be a connection layer for p2p, providing greater user agency.

streama/README.md at master · streamaserver/streama
Self hosted streaming media server. https://docs.streama-project.com/ - streamaserver/streama


datum-cloud/app
A desktop app for safely exposing local services on the Internet via Iroh tunnels using QUIC. Built in rust.