How ORTC adds Power to WebRTC - London April 1, 2014

Hookflash Inc. All Rights Reserved 2014

Object Real-Time Communications - ORTC Giving WebRTC New Power

Trent Johnsen | CEO | Hookflash

WebRTC Global Summit, London April 2014

http://hookflash.com

[email protected]

@hookflash @trentjohnsen

1/28


Calgary, Canada

2/28


COMMUNICATIONS are MOVING COMPLETELY from TELEPHONY to the INTERNET

3/28


TRADITIONAL TELECOM WILL SIMPLY BE LEFT BEHIND

4/28


JAVASCRIPT & HTML5 DEVELOPERS DO IN MINUTES WHAT TAKES TELECOM WEEKS, MONTHS & YEARS

5/28


“Voice is just another JavaScript Application”

Henning SchulzrinneChief Technology Officer (CTO) U.S. Federal Communications Commission

Co-Designer of SIP, RTP & RTSP2013 Internet Hall of Fame Inductee

6/28


“WebRTC is a new front in the long war

for an open and unencumbered web”

Brendan EichInventor of JavaScript & Mozilla CEO

MARCH 24, 2014

7/28


So with all this talk of voice being a JavaScript app & supporting the Open Web . . .

when Hookflash Chief Architect Robin Raymond noticed a telecom protocol from 1998 called “SDP” proposed for the

WebRTC 1.0 Spec . . .

he was somewhat taken aback

8/28


“For the love of all that is human, why is SDP part of WebRTC efforts at all?”

Robin Raymond

Author of Open Peer | Chief Architect at Hookflash | Chair ORTC CG

9/28


Robin published his concerns in a

blog post at WebRTC.is

10/28


other software developers spoke up

“SDP is not appropriate for use in a Web API”

11/28


W3C ORTC Community Group

Mission: “to define Object-Centric API’s to enable Real-Time Communications in Web browsers, Mobile endpoints and Servers.

A Community group was formed . . .

12/28


ORTC -“Object Real-Time Communications”

13/28


SDP - “Session Description Protocol”

a set of rules that defines how real-time communications sessions can be setup to allow all endpoints to effectively participate in the session.

- essentially prescribes how offer/answer is handled in WebRTC

14/28


Unnecessary - Too High level an API

SDP Concerns:

15/28


Arcane Format - legacy, problematic

16/28


specifies offer/answer

17/28


incompatibilities

18/28


doesn’t truly solve goal of compatibility to legacy systems

19/28


Proposed WebRTC Protocol does not define stack signaling protocol and limit

developers to SIP or XMPP/Jingle.

Why define & limit media signaling to SDP?

20/28


Solution:

Give Developers the Power with an Object enabled API

ORTC -“Object Real-Time Communications”

Simple Examples of what ORTC will enable Developers to do:

❏ Layered Video Coding

❏ Codec Settings per TrackKeep in mind that WebRTC will be about a lot more than video calling

21/28


ORTC W3C Community Group: Currently 30+ members | March 2014

ORTC Community group today . . .

Finland

Australia

22/28


Hookflash & Open Peer

23/28

Proprietary and Confidential Hookflash Inc. All Rights Reserved 2014

TEAM

Erik Lagerway Co-Founder - COO Founder of Xten (now CounterPath Corporation) where he designed CounterPath’s award-winning softphone technology that powers voice & video calling, messaging, and presence offerings of customers such as Alcatel -Lucent, AT&T, Verizon, BT, Rogers, Avaya, & Cisco

Trent Johnsen CEO - Co founderInternet, Mobile, Cloud and IP telecom sectors. President & CEO Canada’s 1st ,largest national provider of hosted Business VoIP working with global tech leaders including Acme Packet, Mitel and Broadsoft.

ADVISORS *

Robin Raymond - Chief ArchitectExpert software architect, technical leader and developer. Specialist in scalable network asynchronous software architecture, and peer-to-peer communications. Chair and Author of W3C Object Real-Time Communications (ORTC) API and community group.

Alan Duric PhD Former Chair Cullen Jennings PhD Evan Kirstel

24/28


HOOKFLASH OPEN PEER: IETF 80 - Prague - April 2011

Original New Peer-to-Peer signalling Protocol with these main objectives: ➔ Open ➔ Peer communications, Social, Legacy & Private Directories➔ Identity Federation➔ Strong Security/Privacy➔ Scalability➔ WebRTC/ORTC enabling Protocol

◆ WebRTC/ORTC embeds a real-time communication stack into browsers BUT DOES NOT INCLUDE SIGNALLING. Open Peer is original design, purpose built new signalling protocol enabling developers to communicate and federate across domain infrastructure (eliminates silos where desired)

❏

25/28


Hookflash: “SOFTWARE ENABLED COMMUNICATIONS”OPEN PEER SOFTWARE DEVELOPMENT KITS (SDK’S) FOR MAJOR MOBILE AND WEB PLATFORMS

● Real-time Communications can be integrated into anything

WebRTC/ORTC

26/28


Hookflash API* enables Open Peer SDK’s

API delivers complex, scalable services for Developers, Partners and Customers

● IDENTITY (Social, 3rd Party)● SECURITY (Auth, Signaling, Media)● ANALYTICS

○ (Reg, A/V Calls, Messaging, Geo)

● CONTINUOUS DEPLOYMENT● NAT TRAVERSAL (Relay)

MEDIA FLOW & SIGNALING all Peer-to-Peer (P2P) using Hookflash “Open Peer” - PRIVATE, HIGH QUALITY, LOW COST

* API “Application Programming Interface”

27/28


Recent Press:


thank you!http://hookflash.com

[email protected]

@hookflash

1.855.hookflash

Q&A

28/28

Join the ORTC Community Group at:http://www.w3.org/community/ortc/


● Updated ORTC Specification Fills in Missing Pieces to Drive Real-time Communications

● MS Open Tech delivers updated ORTC API prototype, reflecting recent progress within the W3C ORTC Community Group

Recent ORTC Updates: