A live Q&A session about WebRTC in general and an update about Apple's work on WebRTC. Session included internal information from a meeting between Apple engineers and the people behind the WebRTC-in-WebKit initiative. Session by Alex Gouailard, Dan Burnett and Amir Zmora

1. WebRTC Standards &
Implementation Q&A
Amir Zmora
TheNewDialTone
Dan Burnett
StandardsPlay
Alex Gouaillard
WebRTC by Dr Alex / Citrix

2. View video recording of this session
http://ccst.io/e/webrtcstandards4

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

5. WebRTCStandards.info
Sponsored by

6. About Us
• Amir Zmora • Dan Burnett • Alex Gouaillard

7. Save The Date: June 6
Register/View: ccst.io/e/webrtcstandards5
Next Session

9. Many Questions To Be Asked
• When will it be available?
• Will it interoperate with other browsers?
• What codecs will it support? Opus? H.264? VP8/9
• What’s the plan for ORTC?
• Will it be accessible by iOS applications via WebView?

10. WebRTC in Webkit : who does what
• Project initiated by Ericsson R&D and Dr Alex G.
• Goal was to reduce the technology debt in WebKit to speed up WebRTC
adoption
• Long shot: Apple Safari ports and iOS WebView framework
• Validation of the non-opposition by Apple with an initial meeting in oct 2013
(W3C TPAC)
• Main engineering work done by Ericsson R&D, Adam B. until mid 2015
• Several companies joined the effort
• Either on the engineering side (centricular, igalia)
• Or on the funding side: Citrix

11. WebRTC in Webkit and Apple: what relationship?
• No contract, no commitment, no comment 
• Discussions are possible around:
• Standards, Design, Implementation
• Open source parts of WebKit,
• Through “weak consensus” (lots of double negatives)
• Validation of the non-opposition by Apple with an initial meeting in oct 2013 (W3C TPAC)
=> start of the webrtc-in-webkit
• Follow-up meeting in June 2015 before an intern started working on it at Apple
• WebRTC APIs and implementation available in nightly builds
• Follow-up meeting early 2016 at Apple around testing
• Possible follow up at W3C TPAC in September 2016 at Lisbon.

12. Webrtc and Apple: what do we know?
• Apple reviewers fast tracking WebRTC patches from webrtc-in-webkit
since the beginning (oct 2014)
• Apple putting dev resources on mac only portions of the code since June
2015.
• Full latest JS API already implemented (JS layer)
• Full Media Device API fully implemented (including Capturers)
• Media Device API available in nightly and dev builds
• WebRTC API not available in nightly and dev builds yet
• Security prompt missing, preventing usage except in test suite
• Work ongoing on a daily basis (commits).

13. Webrtc and Apple: What we don’t know.
• When will the security prompt be available to start using GUM?
• Possible answer: Q2 2016. In any case, very soon.
• When will the WebRTC API be available?
• Already available in the Linux browser, the safari and WebView version
should use a different implementation, more “native” and might not leverage
openWebRTC. ETA unknown, and no visible activity on Apple side. It is
possible that this activity is not done publicly though (i.e. no public activity
does not mean no activity).
• That means that details about WebRTC APIs (codecs) are unknown today.
The Linux port supports everything that openWebRTC supports today.

15. Save The Date: June 6
Register Now: ccst.io/e/webrtcstandards5
Next Session

16. 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

17. Thank You
Amir Zmora
TheNewDialTone
Dan Burnett
StandardsPlay
Alex Gouaillard
WebRTC by Dr Alex