WHIP WHEP... What?

WHIP and WHEP are new IETF standards that define standardized HTTP signaling for WebRTC PeerConnections. The WISH working group https://datatracker.ietf.org/wg/wish/about/ in particular calls out this as a technology for 'broadcasting tools and real-time media broadcast networks'.

As I have spent more time with technology I have found that its impact is so much greater then that. WHIP/WHEP is already seeing uptake in Server<->Server integrations and other tools.

This talk covers the benefits I have seen so far and where I am seeing it used.

Transcript

1. WHIP/WHEP/WebRTC… What?
2. WHAT IS WEBRTC?
3. 1 The Basics - E2E Secure Connection between two Peers - Multiple Audio/Video Tracks - Variable Latency (200ms and up!) - Binary Data - Browser, Mobile, Embedded
4. 2 Things you appreciate later - W3C/IETF Standard - Multiple Implementations - Primitive supports P2P or Server - Lots of knobs/dials to build your idea
5. Session Establishment
6. 3 It was DIY
7. 4 Everyone did it a bit di ff erently - REST or WebSocket - JSON or protobuf - Session Description Protocol or ORTC - Di ff erent SDK for each platform
8. 5 WHIP to the rescue!
9. 6 Custom Behaviors
10. 7 Available Now
11. 8 Coming Soon
12. What does it change?
13. 9 n < 400ms is magical
14. 10 Codecs, even your own! - AV1 - H265 - Opus - Or whatever you want! No hardcoded IDs
15. 11 Simulcast
16. 12 Adverse Networks and Mobility - Clients can roam (ICE Restart) - Forward Error Correction - User Con fi gurable Bu ff er (Userspace networking) - Receiver Feedback (RTCP)
17. 13 Easier Integrations - SRT -> WebRTC - Server <-> Server communication
18. 14 WebRTC E2E - One fl eet of servers - No more transcoding or transmuxing - All experiences supported (200ms or 5s)
19. 15 Serverless Broadcasting?
20. 16 webrtcforthecurious.com github.com/pion pion.ly/slack twitter.com/_pion sean@pion.ly https://www.linkedin.com/in/sean-dubois/