WebRTC standards update (July 2014)
Victor	
  Pascual	
  Avila	
  
Victor.pascual@quobis.com	
  
	
  	
  	
  	
  	
  	
  	...
Upperside WebRTC
Conference, Dec 16-18
7/15/14	
   2	
  
New WebRTC Blog
7/15/14	
   3	
  
New WebRTC Blog
7/15/14	
   4	
  
blog.uppersideconferences.com
Technology, Innovation & Strategy Consultant
Main focus: help make WebRTC happen – involved in WebRTC
standardization, dev...
WebRTC is…..?
OeAng	
  
WebRTC is…..?
OeAng	
  
WebRTC is…..?
•  A	
  media	
  engine	
  in	
  the	
  browser	
  with	
  JavaScript	
  APIs	
  
•  Open	
  Sourc...
周小逸 Ian	
  
- Audio codecs – G.711, Opus
- Video codecs – H.264 vs. VP8
- Media codecs are negotiated with SDP (for now at least)
- Re...
RTCWeb WG
Don’t panic, it’s not a bad thing!
WebRTC Doesn’t Define
Signaling
Some discussion on the topic: http://webrtchacks.com/signalling-options-for-webrtc-
applications/
Signaling Plane
•  WebRT...
each deployment/vendor is implementing
its own proprietary signaling mechanism
(1/3)
Interworking Towards Legacy?
•  A browser-embedded media engine
•  Best-of-breed echo canceler
•  Video jitter buffer, ima...
WebRTC signaling and media is NOT
compatible with existing VoIP/IMS
deployments – gateways are required to
bridge the two ...
Some discussion on the topic: http://webrtchacks.com/cisco-openh264/
The Video Codec Battle
Poll Question
Room participants: 30/50 in favor of H.264
Remote participants (minority): 75/25 in favor of VP8
→ No clear consensus
No d...
“The mission of the W3C WebRTC WG is to define client-side APIs to enable Real-Time Communications in
Web-browsers. These ...
iswebrtcreadyyet.com
Browser Support
Poll Question
Some discussion on the topic: http://
webrtchacks.com/why-the-webrtc-api-has-it-
wrong-interview-with-webrtc-object-api-or...
http://status.modern.ie/
Browser API
http://status.modern.ie/
Browser API
Browser API
Plug-­‐in  free  or  free  plug-­‐in?
7/15/14	
   29	
  
the WebRTC API can have different flavors
(3/3)
http://webrtchacks.com/ims-approach-webrtc/
WebRTC Access to IMS (r12)
Adding New Wheels to IMS
with WebRTC
3GPP TS 23.228 V12.5.0
(2014-06)
P
C
E
F
N
A
T
I
P
-
C
A
N
WWSF
W1
W2
UE
WIC
I/S-CSCF
eIMS-AGW
Iq
MweP-CSCF
H/V-PCRF
Gx
Rx
W3
IMS-ALG
WAFW4
W5
Reference Ar...
codec1
SRTP
IP IP
UDP
IP
UDP UDP UDP
IP
UE eIMS-AGW peer
SRTP RTP
codec1 codec2
RTP
codec2
BFCP
SCTP
DTLS
IP
SCTP
DTLS
IP
...
“the initial focus of the Task Group is to determine what
the needs are for successful interoperability of
WebRTC-to-SIP d...
Alliance for Telecom Solutions
“focuses on interoperability issues relating to the use of WebRTC”
“the group is focused on enterprise WebRTC , interworki...
How does WebRTC relate to VoLTE
and RCS?
GSMA
l  each deployment/vendor is implementing its own
proprietary signaling mechanism
l  WebRTC signaling and media is incom...
Thank You!
Victor	
  Pascual	
  Avila	
  
Victor.pascual@quobis.com	
  
	
  	
  	
  	
  	
  	
  	
  @victorpascual	
  
	
 ...
WebRTC standards update (Jul 2014)
WebRTC standards update (Jul 2014)
Upcoming SlideShare
Loading in...5
×

WebRTC standards update (Jul 2014)

2,454

Published on

WebRTC standards update (Jul 2014)

Published in: Internet
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,454
On Slideshare
0
From Embeds
0
Number of Embeds
19
Actions
Shares
0
Downloads
55
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

WebRTC standards update (Jul 2014)

  1. 1. WebRTC standards update (July 2014) Victor  Pascual  Avila   Victor.pascual@quobis.com                @victorpascual     Amir  Zmora   amzmora@gmail.com                  @AmirZmora    
  2. 2. Upperside WebRTC Conference, Dec 16-18 7/15/14   2  
  3. 3. New WebRTC Blog 7/15/14   3  
  4. 4. New WebRTC Blog 7/15/14   4   blog.uppersideconferences.com
  5. 5. Technology, Innovation & Strategy Consultant Main focus: help make WebRTC happen – involved in WebRTC standardization, development and first industry deployments (on-going RFX's, PoC's and field trials) Other activities: - Chief Strategy Officer (CSO) - IETF contributor (SIP, Diameter and WebRTC areas) - IETF STRAW WG co-chair - SIP Forum WebRTC Task Group co-chair - WebRTCHacks.com co-founder and blogger - Independent Expert at European Commission About Me
  6. 6. WebRTC is…..?
  7. 7. OeAng   WebRTC is…..?
  8. 8. OeAng   WebRTC is…..? •  A  media  engine  in  the  browser  with  JavaScript  APIs   •  Open  Source,  no  royalKes,  license  fees   •  Real-­‐Kme  voice,  video  &  data   •  No  plug-­‐in   •  Secured   •  Standard  interfaces  
  9. 9. 周小逸 Ian  
  10. 10. - Audio codecs – G.711, Opus - Video codecs – H.264 vs. VP8 - Media codecs are negotiated with SDP (for now at least) - Requires Secure RTP (SRTP) – DTLS-SRTP (SDES is prohibited) - Requires Peer-2-peer NAT traversal tools (STUN, TURN, ICE) – trickle ICE - Multiplexing: RTPs & RTP+RTCP - Tools for firewall traversal - DataChannel - Etc. NEW PROTOCOL PROFILE FOR MEDIA RTCWeb WG (and other)
  11. 11. RTCWeb WG
  12. 12. Don’t panic, it’s not a bad thing! WebRTC Doesn’t Define Signaling
  13. 13. Some discussion on the topic: http://webrtchacks.com/signalling-options-for-webrtc- applications/ Signaling Plane •  WebRTC has no defined signaling method. JavaScript app downloaded from web server. Popular choices are: •  SIP over Websockets -  Standard mechanism (RFC7118) -  Extend SIP directly into the browser by embedding a SIP stack directly into the webpage – typically based on JavaScript -  WebSocket create a full-duplex channel right from the web browser -  Popular examples are jsSIP, sip-js, QoffeeSIP, or sipML5 •  Call Control API -  proprietary signaling scheme based on more traditional web tools and techniques -  “standard” APIs enhanced to include WebRTC support •  Other alternatives based on XMPP, JSON or foobar
  14. 14. each deployment/vendor is implementing its own proprietary signaling mechanism (1/3)
  15. 15. Interworking Towards Legacy? •  A browser-embedded media engine •  Best-of-breed echo canceler •  Video jitter buffer, image enhancer •  Audio codecs – G.711, Opus are MTI •  Video codecs – H.264 vs. VP8 (MTI TBD - IPR discussion) •  Media codecs are negotiated with SDP (for now at least) •  Requires Secure RTP (SRTP) – DTLS •  Requires Peer-2-peer NAT traversal tools (STUN, TURN, ICE) – trickle ICE •  Multiplexing: RTPs & RTP+RTCP •  Yes, your favorite SIP client implementation is compatible with most of this. But, the vast majority of deployments •  Use plain RTP (and SDES if encrypted at all) •  Do not support STUN/TURN/ICE •  Do not support multiplexing (ok, not really an issue) •  Use different codecs that might not be supported on the WebRTC side
  16. 16. WebRTC signaling and media is NOT compatible with existing VoIP/IMS deployments – gateways are required to bridge the two worlds (2/3)
  17. 17. Some discussion on the topic: http://webrtchacks.com/cisco-openh264/ The Video Codec Battle
  18. 18. Poll Question
  19. 19. Room participants: 30/50 in favor of H.264 Remote participants (minority): 75/25 in favor of VP8 → No clear consensus No decisionSome discussion on the topic: http://webrtchacks.com/ietf-finally-made-decision- mandatory-implement-mti-video-codec-webrtc/ Result of The Discussion?
  20. 20. “The mission of the W3C WebRTC WG is to define client-side APIs to enable Real-Time Communications in Web-browsers. These APIs should enable building applications that can be run inside a browser, requiring no extra downloads or plugins, that allow communication between parties using audio, video and supplementary real-time communication, without having to use intervening servers (unless needed for firewall traversal).” Discussion: provides the current API in its form (e.g. based on SDP O/A) the flexibility Web developers need? Answer: well, not really but it's good enough for most of the use cases we have today Alternative proposals: Microsoft's CU- RTC-WEB (Aug'12), WebRTC Object API (ORTC) (Aug'13) Next step: “Done is better than perfect”, Let's finish WebRTC 1.0, Let the industry adopt it Future work: “fix/improve things in WebRTC 2.0”, Backward interoperability? Obtain local media Setup Peer Connection Attach media or Data Close Connection ← getUserMedia(), etc. ← RTCPeerConnection(), etc. ← addStream(), createOffer(), etc. WebRTC WG
  21. 21. iswebrtcreadyyet.com Browser Support
  22. 22. Poll Question
  23. 23. Some discussion on the topic: http:// webrtchacks.com/why-the-webrtc-api-has-it- wrong-interview-with-webrtc-object-api-ortc-co- author-inaki-baz-3-2/ Browser API
  24. 24. http://status.modern.ie/ Browser API
  25. 25. http://status.modern.ie/ Browser API
  26. 26. Browser API
  27. 27. Plug-­‐in  free  or  free  plug-­‐in? 7/15/14   29  
  28. 28. the WebRTC API can have different flavors (3/3)
  29. 29. http://webrtchacks.com/ims-approach-webrtc/ WebRTC Access to IMS (r12)
  30. 30. Adding New Wheels to IMS with WebRTC
  31. 31. 3GPP TS 23.228 V12.5.0 (2014-06)
  32. 32. P C E F N A T I P - C A N WWSF W1 W2 UE WIC I/S-CSCF eIMS-AGW Iq MweP-CSCF H/V-PCRF Gx Rx W3 IMS-ALG WAFW4 W5 Reference Architecture
  33. 33. codec1 SRTP IP IP UDP IP UDP UDP UDP IP UE eIMS-AGW peer SRTP RTP codec1 codec2 RTP codec2 BFCP SCTP DTLS IP SCTP DTLS IP TCP IP UDP UDP BFCP TCP IP UE eIMS-AGW peer MSRP SCTP DTLS IP MSRP SCTP DTLS IP MSRP TCP IP UDP UDP MSRP TCP IP UE eIMS-AGW peer Interworking Towards Legacy IMS
  34. 34. “the initial focus of the Task Group is to determine what the needs are for successful interoperability of WebRTC-to-SIP deployments” covering both Enterprises and Service Providers “recommendations, Reference Architecture Documents, Certifications, and/or White Papers” SIP Forum WebRTC Task Group
  35. 35. Alliance for Telecom Solutions
  36. 36. “focuses on interoperability issues relating to the use of WebRTC” “the group is focused on enterprise WebRTC , interworking of WebRTC and other carrier technologies, and other existing videoconferencing systems” “develop an interoperability test framework and prepare for IOT events” WebRTC Interop Activity Group
  37. 37. How does WebRTC relate to VoLTE and RCS? GSMA
  38. 38. l  each deployment/vendor is implementing its own proprietary signaling mechanism l  WebRTC signaling and media is incompatible with existing VoIP deployments – gateways are required to bridge the two worlds l  the WebRTC API can have different flavors Summary
  39. 39. Thank You! Victor  Pascual  Avila   Victor.pascual@quobis.com                @victorpascual     Amir  Zmora   amzmora@gmail.com                  @AmirZmora    
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×