WebRTC Ingest Signaling over HTTPS (wish) Internet Drafts


      
 WebRTC-HTTP ingestion protocol (WHIP)
 
 draft-ietf-wish-whip-16.txt
 Date: 21/08/2024
 Authors: Sergio Murillo, Alex Gouaillard
 Working Group: WebRTC Ingest Signaling over HTTPS (wish)
This document describes a simple HTTP-based protocol that will allow WebRTC-based ingestion of content into streaming services and/or CDNs. This document updates RFC 8842 and RFC 8840.
 WebRTC-HTTP Egress Protocol (WHEP)
 
 draft-ietf-wish-whep-02.txt
 Date: 18/10/2024
 Authors: Sergio Murillo, Cheng Chen
 Working Group: WebRTC Ingest Signaling over HTTPS (wish)
This document describes a simple HTTP-based protocol that will allow WebRTC-based viewers to watch content from streaming services and/or Content Delivery Networks (CDNs) or WebRTC Transmission Network (WTNs).


data-group-menu-data-url="/group/groupmenu.json">

Skip to main content

WebRTC Ingest Signaling over HTTPS (wish)

WG Name WebRTC Ingest Signaling over HTTPS
Acronym wish
Area Web and Internet Transport (wit)
State Active
Charter charter-ietf-wish-02 Approved
Document dependencies
Additional resources Github
Zulip Stream
Personnel Chairs Nils Ohlmeier, Sean Turner
Area Director Francesca Palombini
Mailing list Address wish@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/wish
Archive https://mailarchive.ietf.org/arch/browse/wish/
Chat Room address https://zulip.ietf.org/#narrow/stream/wish

Charter for Working Group

The WISH working group is chartered to specify a simple, extensible, HTTPS-based set of signaling protocols to establish one-way WebRTC-based audiovisual sessions between broadcasting tools, media players and real-time media broadcast networks.

Background:

WebRTC defines a set of wire protocols for real-time media transmission, as well as a profile of the Session Description Protocol (SDP) for setting up and controlling the associated media streams. Because of its typical use cases, and to increase overall flexibility, WebRTC did not specify a wire protocol for exchanging SDP messages, leaving the creation of such protocols up to the applications that use WebRTC. This works well when WebRTC clients are vertically integrated with the servers they communicate with, as it allows for rapid iteration of new features.

At the same time, the use of WebRTC as a mechanism for large-scale media broadcast is gaining popularity, and unlike more vertically integrated uses of WebRTC, WebRTC-based media distribution networks would benefit immensely from being able to re-use the several broadcasting tools that have been developed over time.

To date, these media distribution networks have employed their own proprietary signaling protocols to establish the connection between broadcasting tools and the network, generally requiring either bespoke software or customized modifications to existing tools.

With the large number of available tools and the growing number of real-time media distribution networks, this ad-hoc approach to creating custom protocols for establishing sessions clearly does not scale. The real-time broadcasting ecosystem would benefit immensely from a set of common protocols to meet this goal.

Deliverables:

The product of this working group will be a specification for a simple, extensible, HTTPS-based signaling protocol set to establish one-way WebRTC-based audiovisual sessions between broadcasting tools and real-time media broadcast networks, and between those networks and the media players.

This working group will use existing HTTPS, WebRTC, and SDP mechanisms to the extent possible. While no extensions to those core protocols is expected, the working group may consider such extensions if they are necessary to meet the requirements of broadcasting tools and networks. Any such work will be coordinated with the HTTPBIS, MMUSIC, and/or MOPS working groups, as appropriate. Additionally, this working group will coordinate with HTTPBIS and HTTPAPI to assure that the HTTP protocol is being used according to current best practice.

While there may be other problems that the proposed mechanism may solve or nearly solve, such as general purpose bidirectional realtime communication (telephony, video conferencing etc), adding explicit protocol support for those use cases is not in scope for the WISH working group.

Milestones

Date Milestone Associated documents
Dec 2024 Submit WebRTC-HTTP egress protocol to IESG for publication draft-ietf-wish-whep