Thrilled to Be Joining the WHEP Spec as an Editor
— WHEP, WebRTC, IETF, specification, editor, protocol, HTTP egress, Server Sent Offers, IETF 123, Madrid — 1 min read
I've recently stepped up as an editor of the WHEP (WebRTC HTTP Egress Protocol) specification. It's my first proper involvement with the IETF, beyond reading specs and occasionally commenting from the sidelines, so I'm looking forward to contributing more directly.
WHEP is about setting up WebRTC media sessions using HTTP – which makes things a lot simpler for developers and deployers who don't want to deal with full-on signalling stacks just to receive media. It's an important piece of the puzzle for making WebRTC more accessible and easier to integrate into existing platforms.
One of the big motivations for getting more involved was to help get the Server Sent Offers proposal into the spec. It's something that came out of real-world experience and has had strong community backing. The working group agreed it should be part of v1, not deferred or turned into an extension, so I'm keen to help make that happen in a clean, usable way.
This week is IETF 123 in Madrid — the first meeting since I became an editor. I'll be joining remotely, but I'm looking forward to the discussions and to helping move things forward.
More soon as we continue working towards a v1 of WHEP. If you've got thoughts or use cases you want to see supported, let me know.
Links
- WHEP on GitHub: https://github.com/wish-wg/webrtc-http-egress-protocol
- IETF 123 agenda: https://www.ietf.org/meeting/123/