keynote: the state of WebRTC

Transcription

1 keynote: the state of WebRTC Erik Lagerway Co-founder Hookflash Co-chair WebRTC Working Group Chair ORTC Community Group Trent Johnsen CEO and co-founder Hookflash

2 W3C WebRTC & ORTC Standards Update March 7, 2016 Erik Lagerway, Co-founder Hookflash Founder & Chair - W3C ORTC Community Group Co-chair, W3C WebRTC Working Group

3 what is the state of WebRTC today? Media Capture, last call for comments Reference Permissions API Few other issues No outstanding PRs Peer Connection & Data Channel, making progress 12 +/- open PRs 33 +/- open issues

4 WebRTC re-charters July 2015 "The Working Group will take the work done by the ORTC Community Group as a source of input, and when contemplating similar APIs in the Working Group, make efforts to align with the ORTC CG on API methodologies and nomenclature. This may include scheduled design meetings with relevant WG and CG stakeholders to foster convergence of the APIs." Source:

5 excerpt from: WebRTC Charter Agreement As the name indicates, WebRTC 1.0: Real-time Communication Between Browsers is a first version of APIs for real-time communication, sometimes referred to as the PeerConnection API. The activities in the ORTC (Object Real-time Communications) Community Group indicate that there is interest in additional APIs to provide more direct control over WebRTC than what the PeerConnection API offers. In recognition of this interest, the Working Group will, once WebRTC 1.0: Real-time Communication Between Browsers reaches Candidate Recommendation, start work on a new set of object-oriented APIs for real-time communication. In developing these new APIs, the Working Group will adhere to the following principles: Direct control: The new APIs are intended to provide direct control over the details of real-time communication, where the application can directly specify how information should be transmitted, without any built-in negotiation semantics. Standalone operation: The new APIs will be complete enough to allow applications to write solely to the new APIs to complete common tasks. Backwards-compatibility: The new APIs will extend the WebRTC 1.0 APIs, rather than replace them. Applications that use the PeerConnection API will continue to function, unless there is a clear and compelling reason to deprecate specific 1.0 functionality. Feature independence: Features may be introduced in the new APIs that are not available when using the PeerConnection API. The Working Group will take the work done by the ORTC Community Group as a source of input, and when contemplating similar APIs in the Working Group, make efforts to align with the ORTC CG on API methodologies and nomenclature. This may include scheduled design meetings with relevant WG and CG stakeholders to foster convergence of the APIs.

6 new Chairs/Editors W3C WebRTC Working Group Erik Lagerway (Hookflash) is added as a WebRTC Working Group Cochair (June 2015) Bernard Aboba (Microsoft) is added as a WebRTC Working Group Editor (Sept 2015)

7 WebRTC two years ago Application PeerConnection MediaStream getusermedia (GUM) ICE DTLS SCTP RTP MediaStream MediaStream Track MediaStream Track Track Visible only through stats Only indirect control

8 2015 WebRTC spec additions PeerConnection.getSenders().getReceivers() // Name TBD.addTransceiver(kind).sctp... RtpSender.track.transport.getCapabilities().getParameters().setParameters(params).replaceTrack(track)... RtpReceiver.track.transport.getCapabilities().getContributingSources()... DtlsTransport.transport.state.getRemoteCertificates().onstatechange... IceTransport.state.getLocalParameters(),.getRemoteParameters(),.getLocalCandidates().getRemoteCandidates().getSelectedCandidatePair().onstatechange... SctpTransport.transport DataChannel.transport RtpParameters.codecs.encodings... RtpCodecParameters (read only).mimetype.payloadtype... RtpEncodingParameters.active.maxBandwidth (read only).ssrc... IceParameters (read only).usernamefragment.password DtlsParameters... Source: Has read-only getcapabilities, parameters, codecs, header extensions, SSRCs Has multiple encodings

9 what you can do with WebRTC 1.0 objects "Warm up" media path while getting a track and ringing Change the send codec (without SDP munging) Change the camera source instantly (front to back) Enable/disable sending of media instantly (without signalling) Set a maximum bitrate or maximum frame rate Obtain detailed status of individual ICE and DTLS transports Send simulcast

10 WebRTC now ORTC Application Application PeerConnection ICE DTLS SCTP RTP ICE DTLS SCTP RTP Objects all read-only Indirectly controlled via PeerConnection Some direct control Same objects as WebRTC Full direct control PeerConnection optional (via JS lib)

11 ORTC in more detail

12 what will you be able to do with ORTC but not WebRTC? Configure the objects without SDP and related complexities Scalable Video Coding (Temporal & Spatial Scalability) Call forking RTP unhandled events Interoperate with other ORTC endpoints, without the need for a shim (eg. Edge ORTC & ORTC Lib applications)

13

14 how does WebRTC NV differ from ORTC? NV (Next Version) Mandates support for WebRTC 1.0 interoperability SDP or Objects When will it ship? ORTC Object-centric interface SDP handled outside of the spec (eg. JS shim)

15 ORTC is shipping now: Microsoft Edge (Sept 2015) Build ORTC web apps on top of ORTC in Edge eg. Skype for Web (timing?) ORTC Library (Q3 2016) Open Source Build ORTC apps everywhere else via ORTC Library, Alpha release WebRTC supported via JS shim Samples: PeerCC + ORTC, DataChannel (April 2016)

16 what is ORTC Lib? Open Source (MIT) real world usable ORTC reference implementation C++ API implementation Focus is on mobile (Material work on ICE stack) Wrapped in Objective-C, CX (WinRT), Java Support for WinRT (Win 10), ios, Mac, Android Applications can be written in C++, Obj-C, C#, Java Uses lower level WebRTC media components in core Main API implementation done by Hookflash

17 what is in ORTC Lib? Sending Application Receiving Application C# application WinJS application* ios application Mac application Android application Native C++ application WinRT CX API wrapper Objective-C API wrapper Java API wrapper Track Track RtpSender RtpSender Sdes Transport Sdes Transport RtpReceiver Track DtlsTransport IceTransport IceTransport DtlsTransport Internet Data Data Channel Sctp Sctp Transport RtpListener IceGatherer IceGatherer Sctp Sctp Transport Data Data Channel IceTransportC ontroller IceTransportC ontroller * not officially supported

18 does ORTC make WebRTC NV somewhat irrelevant? Both will have objects in stand-alone model Both will have support for SDP (with ORTC via application) One is shipping today At the end of the day, the market will decide

19 summary WebRTC WG and ORTC CG converging (charter, chairs, editors) WebRTC and ORTC specs converging (objects) WebRTC 1.0 (with objects!): ORTC: ICE (Feb 25, nd Virtual Interim) ORTC available in Edge ORTC Library, Alpha release (soon) PeerConnection implementation in JS already working (adapter.js pull request) Google has started implementing WebRTC/ORTC Basic RtpSender/RtpReceiver already available for mobile apps at webrtc.org More to come in Will be available in Chrome, Android, and ios

20 ORTC links ORTC portal W3C ORTC CG - W3C Community Group - Specification issues ORTC Library repo

21 WebRTC links W3C WebRTC links Specification: Working Group: Charter: Related sites - Google SDK / Library - specification issues

22 Thank you! Erik Lagerway Thanks to: Bernard Aboba, Microsoft Peter Thatcher, Google Robin Raymond, Hookflash

23 WebRTC moves communications from infrastructure to software Source: We are Software People Jeff Lawson - Twilio 2012

24 millions of developers will deliver integrated real-time communications solutions

25 software is eating the world World s largest taxi company owns no taxis (Uber) Largest accommodation provider owns no real estate (Airbnb) Largest phone companies own no telco infrastructure (Skype, WeChat) World s most valuable retailer has no inventory (Alibaba) Most popular media owner creates no content (Facebook) World s largest movie provider owns no theatres (Netflix) Largest software vendors don t write the Apps ( Apple and Google)

26 how will your enterprise use RTC? business process / API consumption W3C Specification Software Libraries Applications SDKs and APIs Services: Skype for Web (built on ORTC)

27 applications examples (hint: ORTC best use case is NOT video calling in a browser)

28 There is a huge and growing interest in blending communications apps/services with other software capabilities. We are moving from a world of standalone voice, video and messaging to a range of contextualised, work-stream-based and embedded alternatives. DEAN BUBLEY DISRUPTIVE ANALYSIS NOVEMBER 2015

29 state of WebRTC > what are leading companies doing today?

30 state of WebRTC > what are leading companies doing today?

31 WebRTC differentiators & benefits (as compared to a phone call) Authenticated logged into the app Secure encrypted peer to peer session, no server to attack Contextual data, geolocation & screen sharing can be integrated with call Better call quality wideband audio Less expensive voice minute rate is about 100,000 times lower (over-the-top) than typical voice rates * Source OECD: The Internet Economy: Generating Innovation and Growth, October 2012.

32 WebRTC requirements by market Enterprise IT Needs Performance Security Stability Predictability System integration Scaling down costs of mobile development and maintenance Consumer App Needs Advertising Virtual good purchases Virality Direct Monetization High Engagement Enterprise Mobile Tools Needs User analytics App performance analytics Crash reporting Integration with existing business logic (connectors with Microsoft, Oracle, SAP, IBM, Salesforce) Identity management Data security Own app store distribution

33 state of WebRTC > what are leading companies doing today?

34 "Oops, I mentioned #WebRTC still just another year away from being important"

35 World s Most Admired Companies working with WebRTC / ORTC today - March 2016 (that we know of)

36 learn more... Trent Johnsen CEO

37 keynote: the state of WebRTC Erik Lagerway Co-founder Hookflash Co-chair WebRTC Working Group Chair ORTC Community Group Trent Johnsen CEO and co-founder Hookflash