Red5 discusses the state of ad insertion for Media over QUIC (MOQ), focusing on how SCTE-35 signaling can be carried as structured events to enable server-guided ad insertion (SGAI) and regional blackout workflows while keeping ad and primary media streams separately distributed. The article references presentations at an IETF MOQ interim meeting (Feb 2026, Google Boulder) describing an architecture using an Event Timeline track for real-time switching between program and ad tracks. Red5 also states it is developing MOQ ad workflow integrations with partners and plans to showcase MOQ/TrueTime and collect beta testers for a Red5 Cloud + CacheFly MOQ delivery network at NAB 2026.
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred sourceMOQ’s adoption won’t be decided by latency charts—it’ll be decided by whether ad ops and rights workflows survive the protocol shift. The Event Timeline approach effectively turns SCTE-35 into a first-class control plane for MOQ: ads and blackout replacements can be triggered precisely without forcing monolithic server-side stitching, and without coupling scale of signaling to scale of video delivery. If this pattern holds, the “next-gen transport” meme becomes: separate the media plane from the monetization plane. NAB demos and early betas will reveal whether vendors can make that interoperability real across CDNs, ad decisioning, and players.
