Fewer than 2% of IETF RFCs reach formal Internet Standard status

For streaming engineers, this underscores that technical ubiquity is not tied to formal standardization status. Most modern media protocols, including emerging frameworks like Media over QUIC (MoQ), are likely to see multi-year production use while remaining technically 'Proposed Standards.' The high bar for STD status—requiring multiple independent implementations and extensive operational stability—means that the formal catalog remains a lagging indicator of technological health. Decision-makers should prioritize interoperability and community consensus over formal STD numbers when evaluating protocol stability. Watch for the eventual RFC publication of MoQ in 2027-2028 as the next major indicator of transport-layer maturity for low-latency video.

The trend of practical adoption outpacing formal IETF elevation is increasingly visible in the streaming media sector, where the industry-wide move toward QUIC-based delivery illustrates the lag. Although QUIC was standardized as RFC 9000 in May 2021, the surrounding ecosystem for media—specifically Media over QUIC (MoQ)—remains in a prolonged developmental phase. Per IETF records from July 2026, the MoQ working group is still actively refining transport and media format drafts, with formal RFC publication for core transport currently targeted for late 2027 or early 2028.

Despite the lack of finished RFCs, production deployments are already operational. Per Digital Samba and ForaSoft reports from May 2026, vendors including Cloudflare, nanocosmos, and WINK Streaming have launched MoQ-based relay networks to achieve sub-300ms latency at global scale. Cloudflare alone operates a production MoQ relay network across 330+ cities. These early movers are utilizing draft versions (such as draft-18) to bypass the latency floors of LL-HLS and the unfavorable economics of WebRTC SFUs, proving that B2B streaming infrastructure often scales effectively on specifications that the IETF still classifies as active 'work in progress.'

This operational reality has prompted internal IETF debates regarding the utility of STD numbers in a modern context. Per an IETF Internet-Draft from March 2026, experts like J.C. Klensin have proposed modifying the standards track to assign stable reference numbers earlier in the process. Proponents argue that the current system, where few documents advance beyond Proposed Standard, reduces the utility of formal numbering for developers who require stable references for interoperability in a fast-moving market. As of the IETF 126 meeting in Vienna in July 2026, the organization continues to weigh these changes against the traditional 'rough consensus and running code' philosophy.