<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>QUIC on The Coders Blog</title><link>https://thecodersblog.com/tag/quic/</link><description>Recent content in QUIC on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 16:55:56 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/quic/index.xml" rel="self" type="application/rss+xml"/><item><title>Optimizing Media Streaming: MPEG-2 &amp; QUIC Integration</title><link>https://thecodersblog.com/mpeg-2-transport-stream-packaging-for-media-over-quic-2026/</link><pubDate>Thu, 07 May 2026 16:55:56 +0000</pubDate><guid>https://thecodersblog.com/mpeg-2-transport-stream-packaging-for-media-over-quic-2026/</guid><description>&lt;h3 id="the-pragmatic-bridge-injecting-mpeg-2-ts-into-the-moqt-stream-canvas"&gt;The Pragmatic Bridge: Injecting MPEG-2 TS into the MOQT Stream Canvas&lt;/h3&gt;
&lt;p&gt;The convergence of legacy broadcast infrastructure with cutting-edge transport protocols is a fascinating, albeit often complex, technical challenge. The recent registration of &lt;code&gt;&amp;quot;m2ts&amp;quot;&lt;/code&gt; for MPEG-2 Transport Streams (TS) within the Media Over QUIC Transport (MOQT) framework signifies a pragmatic step towards integrating established content into the low-latency, highly scalable world of QUIC-based streaming. This isn&amp;rsquo;t about reinventing the wheel, but rather about carefully packaging existing wheels (MPEG-2 TS) to fit onto a much faster, more agile chassis (MOQT).&lt;/p&gt;</description></item></channel></rss>