Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

WebRTC Status Update - 2017Q2

381 views

Published on

Update on WebRTC standard and Implementation Status. Presented at Sydney's webrtc meet-up on may 25 2017. Find the companion blog post at webrtcbydralex.com

Published in: Technology
  • Be the first to comment

WebRTC Status Update - 2017Q2

  1. 1. Dr Alex Gouaillard CEO, CoSMo Software, Singapore W3C, IETF, IMTC, ... Blogger webrtcbydralex.com Twitter: @agouaillard
  2. 2. “Standards to Make it easy!”
  3. 3. Signaling Server Web Server Bob (Device) Alice (Browser) Up to You: Transport Protocol Up to you: Signaling Protocol Up to you Handshake Algorithm Defined in IETF Specs (JSEP) • SDP • O/A Defined in IETF Specs (ALL) Defined in W3C Specs (BROWSER) • GUM • PC • DC Server / Back-end / Infrastructure Client Media Minimum webrtc Solution: What is provided, what is up to you
  4. 4. “Google statement of what is left to be done”
  5. 5. This effort will be fourfold: 1. Complete the WebRTC 1.0 specifications in both the W3C and IETF As one of the key contributors to these specifications, we aim to resolve the remaining gaps so that these documents can be published. 2. Resolve remaining major spec incompatibilities in Chrome’s implementation We will address the key areas where our implementation does not conform to the WebRTC 1.0 specifications. In particular, this will include: i. Adding support for RTCRtpTransceiver, RTCRtpSender, and RTCRtpReceiver ii. Transitioning from Plan B to Unified Plan SDP iii. Improving conformance for getStats identifiers 3. Ensure interoperability across all browsers With browser vendors increasingly relying on Web Platform Tests for compliance, we are developing a WPT test suite for the WebRTC specification. In addition, we aim to release a system for testing cross-browser interoperability at the API and protocol level, including complex interworking scenarios. 4. Resolve remaining reliability pain points Improvement of Webrtc Code (non-api) WebRTC powers thousands of apps with hundreds of millions of users, but we are always working on making the platform more robust. As part of this initiative, we plan to complete several significant infrastructure improvements that will reduce audio echo and glitches, and provide improved resiliency against camera or microphone issues caused by the device or OS. Specs Draft Status Implementation Status Compliance Testing & Interop Testing
  6. 6. “W3C Standard Process and Draft Status”
  7. 7. “(W3C) Compliance Tests”
  8. 8. Signaling Server Web Server Bob (Device) Alice (Browser) Up to You: Transport Protocol Up to you: Signaling Protocol Up to you Handshake Algorithm Defined in IETF Specs (JSEP) • SDP • O/A Defined in IETF Specs (ALL) Defined in W3C Specs (BROWSER) • GUM • PC • DC Server / Back-end / Infrastructure Client Media Minimum webrtc Solution: What is provided, what is up to you
  9. 9. Web Platform Test
  10. 10. Web Platform Test - Reloaded - Automatic Upstream from Browsers Vendors forks - SauceLab Support - Commit Testing Bot - WPT runner & Dashboard - Webdriver extension for permission prompts And of course - More tests / better coverage
  11. 11. Web Platform Test - Reloaded - Automatic Upstream from Browsers Vendors forks - SauceLab Support - Commit Testing Bot - WPT runner & Dashboard (https://wptdashboard.appspot.com/t/webrtc) - Webdriver extension for permission prompts And of course - More tests / better coverage
  12. 12. Web Platform Test - Reloaded Ok, now I know if my JS API is implemented in my favorite browser, and if it is compliant to the spec … but it still does not connect or show any video ….
  13. 13. “(IETF/P2P/E2E) Interop. Tests”
  14. 14. Signaling Server Web Server Bob (Device) Alice (Browser) Up to You: Transport Protocol Up to you: Signaling Protocol Up to you Handshake Algorithm Defined in IETF Specs (JSEP) • SDP • O/A Defined in IETF Specs (ALL) Defined in W3C Specs (BROWSER) • GUM • PC • DC Server / Back-end / Infrastructure Client Media Minimum webrtc Solution: What is provided, what is up to you
  15. 15. “Implementation Status”

×