1. The document summarizes the benefits of ORTC (Object Real-Time Communications), which enables mobile endpoints and web browsers to communicate in real-time via native and simple JavaScript APIs. 2. Some key benefits of ORTC mentioned include direct programmer control over media pipelines, signalling flexibility without requiring repeated offer/answer exchanges, support for media forking and asymmetric audio/video streams. ORTC also supports capabilities like simulcasting/scalable video coding and is optimized for mobile networks. 3. The document discusses the relationship between ORTC and WebRTC, noting that WebRTC 1.1 aims to incorporate a new set of APIs for direct control based on ORTC, while integrating with existing WebRTC 1

1. 1
the future of ORTC with WebRTC
KRANKYGEEK WEBRTC SHOW
San Francisco California
September 11 2015
Trent Johnsen
trent@hookflash.com
@hookflash

2. 2
• Founder, Chair and Editor of ORTC Community Group
and ORTC Library
• Distributed VirtualTeam: currently US, Canada, and Serbia
• Technology focus includes:
• ORTC
• WebRTC signalling, security and identity protocol - Open Peer
• Work with large enterprise customers, technology service providers and
carriers on digital transformation with real-time communications

3. What is ORTC?
“ORTC (Object Real-Time Communications) is a free, open project that
enables mobile endpoints to talk to servers and web browsers with Real-Time
Communications capabilities via native and simple JavascriptAPIs.”
http://ortc.org/

4. 4
ORTC
BENEFITS

5. 5
ORTC benefits
• developer control
• time to market
• reduced complexity
• network efficient
• advanced video
quality
10. direct programmer control
over media pipeline
Provides direct control over codecs, codec properties, media flow
direction, media forking to N parties, asymmetric media scenarios.
Alternative to SDP (Session Description Protocol) for offer/answer.
9. signalling flexibility
ORTC does not require offer/answer exchange to be repeated
every time media is changed (e.g. new audio stream, codec change,
etc). Media can be sent or updated without any round trip exchanges
and no offer/answer is mandated. SDP is largely tied to SIP signalling,
many companies are dropping SIP in favour of custom protocols for
OTT (over-the-top) solutions
8. media forking
Each time one device adds communication with another device in
WebRTC, a new set of network ports must be opened and an
independent offer/answer exchange must happen. ORTC can reuse
same set of ports without exhausting network for one to many
7. asymmetric audio/video
WebRTC assumes same number of audio/video streams required in
both directions between two devices. Audio and video streams in
ORTC can be sent unidirectionally on demand without requiring
the device to send back the same number of audio/video streams in
the reverse direction.
6. simulcasting / SVC
ORTC supports simulcast/SVC [Scalable video coding] natively.
This is proving exceptionally challenging in WebRTC, especially
given symmetric video assumptions.

6. 6
ORTC benefits
• optimized for mobile
• iOS, Android, WinRT
• reduced requirement
for relay
• future of RTC
• connection stability
for mobile
5. capabilities exchange
(alternative to negotiation)
ORTC allows scenarios like "remote side can send anything
within these listed capabilities”. Easier to add or change audio/
video if programmers only need to update their capabilities to a
remote party rather than requiring full negotiated "agreement" with
remote side for what they mutually support for audio/video.
4. SDES/SRTP transport*
Not all corporate infrastructure devices support DTLS handshakes.
SDES/SRTP allows direct communication to those devices without a
network proxy providing for easier integration with legacy devices.
3. IPv6 and mobile networks
3G/4G/LTE networks with IPv4 use firewalls that often cause a
requirement for network relay (due to overuse of IPv4 addresses
across many mobile devices). Mobile carriers promote IPv6 as an
alternative and IPv6 removes the need for mobile clients to
require network relays to operate. (supported in Chrome)
2. optimized for mobile*
ORTC SDK’s for iOS, Android and WinRT, optimized to run on
mobile platforms (e.g. backgrounding, mobile network conditions)
1. mobile network handoff *
Enhanced connection stability for mobile, the majority use case for
WebRTC. WebRTC assumes a "steady state" for network conditions,
not designed to handle mid-usage changes of network adapters (e.g.
changing from WiFi to 3G/4G). ORTC-lib has has a technology called
"continuous nomination" which allows network changes to be
adapted and changed while media is happening.
* benefits specific to ORTC - lib

7. 7
do I have to choose between WebRTC and ORTC?

8. webRTC | ORTC roadmap is getting clearer
8

9. 9
““WebRTC 1.1 is our proposal for how we can accomplish both of
these things
1) a new set ofAPIs for direct control, based on ORTC
2) integration with the existing WebRTC 1.0API set.
As an evolution of the existingAPI, we consider this WebRTC 1.1””
Justin Uberti, Google Tech Lead, WebRTC

10. 10
“As our proposed new charter sets the
path for convergence with the work
started in the ORTC Community Group,
we expect Erik's experience in
leading that group will prove a great
asset in finalizing the 1.0
version of the WebRTCAPI and in
progressing on the
path of convergence.”

11. 11
BernardAboba
PrincipalArchitect
Microsoft Lync

12. 12

14. 14
our work here is done
thank you !