WebRTC Standards & Implementation Q&A - WebRTC Standards Feature Complete Now What?
0 likes126 views
This document summarizes a discussion on WebRTC standards and implementation. It outlines that WebRTC is now a candidate recommendation, meaning feature completion and testing can begin. It discusses remaining fixes and tests needed by browser implementations. New proposed work areas are simplified ICE APIs, WebAssembly for pluggable codecs, and integrating QUIC features like QUIC data channels and sending audio/video over QUIC. The session was sponsored by WebRTC.ventures and used CrowdCast for the video conference platform.
WebRTC Standards & Implementation Q&A - WebRTC Standards Feature Complete Now What?
- 2. Watch video recording of this session http://ccst.io/e/webrtcstandards21
- 3. Session sponsored by WebRTC.ventures is a custom design and development shop dedicated to building WebRTC based applications for web and mobile. We have built end-to-end broadcast solutions for events and entertainment clients, telehealth solutions for multiple clients, live support tools, as well as communication tools for a variety of other applications. WebRTC.ventures is a recognized development partner of TokBox and has also built native WebRTC solutions
- 4. We use CrowdCast….It’s WebRTC
- 6. About Us • Amir Zmora • Dan Burnett
- 7. WebRTC Standards Feature Complete Now What?
- 8. WebRTC-PC is a Candidate Recommendation • See https://www.crowdcast.io/e/webrtcstandards15/ • Candidate Recommendation means • Feature complete • Testing should begin • In the case of WebRTC, it means we can begin working on NV – 'Beyond 1.0'
- 9. Finishing involves . . . • Implementation • FF – now with Transceivers! Also see https://www.crowdcast.io/e/webrtcstandards16 • Chrome – now with AddTrack/RemoveTrack, Senders! See https://groups.google.com/forum/?pli=1#!topic/discuss-webrtc/fIWg5n67xHo • Fixes • 99 Issues and 5 PRs as of yesterday (https://github.com/w3c/webrtc-pc/issues) • Testing • Web Platform Tests – only tests within-browser capabilities • See https://github.com/w3c/web-platform-tests/tree/master/webrtc • KITE – tests communication between/among browsers (https://github.com/webrtc/KITE) • See http://www.allthingsrtc.org/2017/10/25/dr-alex-gouaillard-founder-kite/ • And http://www.rtc-conference.com/2017/wp-content/uploads/gravity_forms/2- 2f7a537445fa703985ab4d2372ac42ca/2017/10/kite-iit-rtc-AGOUAILLARD.ppt
- 10. Proposed new work • See https://www.w3.org/2011/04/webrtc/wiki/images/8/8a/WebRTCWG-2017-TPAC.pdf (beginning on slide 82) • About 'NV' • Simulcast-like SVC controls – TPAC notes p. 55-59 • Preference for reducing spatial vs. temporal layer • Preference for how resolution should change • Content hints - TPAC notes p 122-123 • For video, maybe 'detailed' and 'motion' • For audio, maybe 'music'
- 11. Proposed new work (cont.) • Simpler ICE API ("Scary ICE", "Project Snowflake") – TPAC notes p. 121 • ICE state machine is complex. So let the app build only what it needs. • Provide new API that can • Gather candidates • Send STUN requests • Notify of STUN requests • Everything else done by app in JavaScript • WebASM for pluggable encoders/encryption • To address long-standing request for pluggable codecs
- 12. QUIC-based features • QUIC • New UDP-based alternative to TLS, inspired by WebRTC work • Provides encrypted, fast streams optimized to do HTTP2 transport • See http://www.allthingsrtc.org/2017/11/08/quic-and-webrtc/ • QUIC data channels • Audio/video over QUIC
- 13. QUIC data channels • TPAC slides pp. 86-104 • New QuicTransport + QuicStream • QUICTransport • would need ICETransport and ICEGatherer • ICETransport - new constructor to be added to WebRTC 1.0 • ICEGatherer – likely separate spec to handle candidate gathering • QuicStream • Basically just QUIC streams • QUIC streams by default are reliable and ordered • Since inexpensive to create, could use one for each data packet if ordering not important
- 14. Audio/Video over QUIC • Why only data? Why not send media this way as well? • TPAC slides starting p. 112, option A preferred • Given videoEncodeFrame() and videoDecodeFrame() and a serializer/deserializer that does encryption, the rest is just JavaScript • Ditto for audio
- 15. ?
- 17. WebRTC Standards & Implementation Q&A Amir Zmora TheNewDialTone Dan Burnett StandardsPlay