As interest in WebRTC based media streaming for non-conferencing scenarios such as broadcast is increasing, there is a need for standardizing some aspects of RTC session setup and signalling specifically for those scenarios. Since the mechanism to exchange SDP offers and answers during session setup is not part of the WebRTC standard there is no common way of interacting with media servers for ingesting and playing back WebRTC based media streams for broadcast scenarios.

On the stream ingestion side, there is ongoing work in defining a standard in {{!draft-ietf-wish-whip-02}}. This document focuses on the playback side, and proposes an HTTP based protocol for negotiating a playback client viewer session for consuming WebRTC based broadcast streams. This document also adds some constraints to how WebRTC is to be used in order to simplify operation.

webrtc-http-playback-protocol.md

• Sunny Stockholm: https://wrtc-edge.lab.sto.eyevinn.technology:8443/whpp/channel/sthlm

• @eyevinn/whpp-client: A Node / JS Library for WHPP.
• @eyevinn/webrtc-player: Media Server Independent WebRTC Player with WHPP support included. Demo available here.
• @eyevinn/wrtc-egress: Standardized WebRTC Egress Endpoint Library with WHPP support.
• Eyevinn Web Player: Open source HTML video player with support for HLS, MPEG-DASH and WHPP.

• eyevinntechnology/wrtc-whpp: WHPP Endpoint
• eyevinntechnology/wrtc-origin: WHIP Endpoint
• eyevinntechnology/wrtc-sfu: Symphony Media Bridge media server

• WebRTC HTTP Playback Protocol (WHPP)
• How to setup a lab environment for WebRTC broadcast streaming
• WebRTC based distribution with WHIP and WHPP running on AWS Fargate
• WHIP & WHPP for WebRTC based broadcast streaming