Is MPEG-2 still used over h264 for things that would justify this RFC in 2026?

MPEG-2 TS is a container. H.264 is a coding specification. They are totally different things.

One can find MPEG-2 TS in surprising places (see: DOCSIS encapsulating Ethernet frames into TS packets).

If I had to guess why MPEG-2 TS, it'd probably be the for the fact it's a well-supported streaming format in both hardware and software. If you tried using QuickTime or MPEG-4 containers, you'd have to rely on hacks like ensuring the moov atom preceeds mdat.

Matroska may be worth considering (especially the subset used by WebM to make it stream-friendly and quicker to seek), but no idea how widespread hardware support is for (de)muxing that.

	▲	dylan604 2 hours ago \| parent [-]
		Before ProRes, we captured HD content at 100Mbps MPEG2 video with PCM audio wrapped in a 302m stream that were muxed together as an MP2TS wrapper. The 302m made it even more difficult as not all MP2TS tools could do it correctly, and some would not allow for custom Program stream IDs and needed to be remuxed by other tools allow for custom PIDs as a post process. But seeing how many uses people came up with for using MP2TS just shows it's flexibility and resilience.

▲

2 hours ago | parent | prev | next [-]

[deleted]

▲

conradev 2 hours ago | parent | prev [-]

MPEG-TS is used to contain h264 chunks for HLS. MPEG-DASH and the new CMAF standard use fMP4 containers instead. My personal take is that Media over QUIC (MoQ) should support both.