The meeting focused on reviewing a technical report regarding the current landscape and classification of contribution protocols for streaming.
Document Progress
Yuriy presented an updated technical report that aims to tabulate existing solutions for contribution protocols, ranging from legacy RTMP to emerging QUIC-based approaches. The report categorizes protocols based on technical aspects such as buffer usage, FEC, retransmissions, and feedback mechanisms.
- Current Scope: The report covers RTMP, enhanced RTMP, SRT, RIST, Zixi, TS over UDP/RTP, DASH-IF ingest, and QUIC.
- Methodology: The evaluation relies on public specifications, documentation, and existing industry benchmarks rather than new performance studies.
- Milestones: The goal is to have a complete document ready for group analysis by the October 7–8 meeting in Ran, following the IBC event in September.
Protocol Analysis
Yuriy and the participants discussed the functional differences between various transport types, including TCP, UDP, HTTP chunk-based, and QUIC.
- Comparison Dimensions: Key metrics include recovery delay, graceful degradation, and suitability for different network conditions like high RTT or cellular environments.
- Technical Insights: Dmitriy noted that SRT natively supports bandwidth distribution across multiple interfaces (bonding), which is useful for reliability and capacity.
- Emerging Tech: There was significant discussion regarding DASH-IF ingest over HTTP/3. Alex suggested that using HTTP/3 could allow for sophisticated multiplexing, such as prioritizing audio and video tracks through interleaving.
Future Directions
The group identified several areas where the report or the industry needs further clarification or coordination.
- Vendor Neutrality: Alex cautioned that while the report evaluates protocols like Zixi, it must avoid recommending specific vendors to maintain professional standards.
- Industry Coordination: A potential joint activity was discussed between this group and the DASH-IF working group to formalize the use of HTTP/3 and QUIC for ingest.
- Open Questions:
- How can the report better serve expert users who require deeper technical data?
- What are the optimal implementation strategies for using QUIC to maximize efficiency in low-latency applications?
- Which vendors can provide more insight into bonded connectivity for high-bitrate contribution?
- Create a DASH-IF ingest working group GitHub issue to formally propose adding HTTP/3 support and related recommendations (such as interleaving and prioritization of tracks) to the DASH-IF ingest specification.
- Revise the deployment scenarios and protocol recommendation sections of the contribution protocols technical report so that FEC-based transport recommendations do not directly attribute performance or suitability to the Zixi vendor, while preserving the underlying technical guidance.
- Upload the latest, more complete local version of the contribution protocols technical report (including updated RTMP/SRT/RIST/Zixi/Ts-over-RTP sections) to replace the current document.
- Identify and approach vendors who already implement bonded connectivity across multiple network links (for example, SRT-based bonding) to gather information and potential use cases for inclusion in the contribution protocols survey.
- Antitrust Statement and WG Discussion
Meeting Introduction
- The group discussed upcoming industry events, including IBC 2026 in September and a face-to-face member meeting in Rennes, France in October.
- Alex Giladi noted that the October meeting will include an AI hackathon and an AI workshop.
- The primary goal of the session was to review the status of the technical report on contribution protocols for streaming.
Technical Report Overview
- Yuriy Reznik explained that the document aims to tabulate existing solutions for the complex streaming contribution ecosystem.
- The report covers a spectrum of protocols ranging from legacy RTMP and enhanced RTMP to SRT, RIST, Zixi, and DASH-IF ingest.
- Evaluation dimensions include buffer usage, FEC, retransmissions, feedback for encoder adaptation, and support for additional features like analytics.
- The methodology relies on public data, specifications, and existing benchmarks rather than new rigorous performance studies.
Protocol Survey and Analysis
- The updated document provides detailed discussions on SRT, RIST, Zixi, and TS over RTP.
- Yuriy Reznik highlighted that RIST offers advanced redundancy and switchover capabilities used by entities like Amazon Media.
- Zixi is noted for its unique integration of an analytics management cloud alongside its protocol.
- The team discussed how different protocols handle delay models, specifically focusing on recovery delay as a key controllable parameter.
DASH-IF and QUIC Integration
- Alex Giladi pointed out that DASH version 6 allows for explicit HTTP/3 usage, which is critical for low latency.
- A discussion occurred regarding the feasibility of using DASH-IF ingest over HTTP/3 to leverage QUIC's benefits.
- Alex Giladi took an action item to add an issue regarding HTTP/3 in DASH-IF ingest, specifically mentioning interleaving and priorities.
- The group identified potential future joint activities between their group and DASH-IF to formalize these emerging technologies.
Functional Comparison and Performance
- The report compares protocols based on transport type (TCP, UDP, HTTP chunk, or QUIC) and functional aspects like FEC and buffering.
- Yuriy Reznik noted that while RTMP buffers can grow uncontrollably on bad networks, SRT and Rist allow for explicit configuration.
- The comparison includes performance under different network conditions such as cellular, Wi-Fi, high RTT satellite links, and cloud interconnects.
- Dzmitriy mentioned that SRT natively supports bandwidth distribution across multiple interfaces for bonding.
Deployment Scenarios and Recommendations
- The document categorizes deployment scenarios into broadcast, pure OTT, user-generated content (UGC), and security surveillance.
- Yuriy Reznik suggested that while RTMP is dominant in UGC, it is suboptimal for professional broadcast compared to SRT or RIST.
- Alex Giladi advised the team to avoid direct vendor recommendations, suggesting they describe technology classes instead of praising specific brands like Zixi.
- Final recommendations are based on requirements such as broad compatibility, poor connection resilience, or deterministic timing needs.
Â
Next Meeting: Â Wednesday, August 26, 2026 9am PDT