What's next for WebRTC?
summary
Google outlines concrete changes: a new Alliance for Open Media and VP9 adoption (Chrome 47+; measured ~40% fewer bits at ~50% more CPU), Edge testing and iPhone moves away from HEVC, and a Chrome extension WebRTC Network Limiter that forces default-route candidates while Chrome will require HTTPS getUserMedia by December. DTLS moves to 1.2 and ECDSA certificates replace slow RSA (RSA generation ~500–1,000 ms on desktop, ~10 s on some Android; ECDSA is tens of ms). Screen share, DAEC and mobile hardware encoders ship now; AppRTC connects in ~300 ms.
AI-written summary · about
chapters (27)
- 0:00Intro
- 1:07Vital Signs: WebRTC Adoption
- 1:51Vital Signs: WebRTC API Usage
- 2:40News: An open alliance for media (2/2)
- 4:33News: Microsoft Edge
- 5:25PSA: IP Address 'Leakage'
- 7:22Network Limiter Extension
- 9:00Next Steps
- 10:46PSA: Mandatory HTTPS
- 13:22PSA: ECDSA
- 14:50PSA: DTLS 1.2
- 15:59PSA: Report it!
- 16:54Enhancements: Delay Agnostic - AEC
- 18:12Enhancements: AEC rollout troubles
- 20:01Enhancements: Screensharing
- 21:30Enhancements: Mobile performance
- 22:08Enhancements: Mobile power savings
- 22:55Enhancements: Mobile video
- 25:32Enhancements: Video smoothness
- 27:19Enhancements: Chrome on desktop
- 29:09Around the corner: iOS API revamp
- 30:29Around the corner: VP9
- 32:35Around the corner: H.264 in Chrome
- 34:17Around the corner: MediaStreamRecorder
- 35:19Around the corner: Misc
- 37:28WebRTC/ORTC (1/2)
- 39:17WebRTC/ORTC (2/2)
