Victor Pascual Avila is a technology, innovation, and strategy consultant focused on helping make WebRTC happen. He is involved in WebRTC standardization, development, and first industry deployments. He provides an update on recent WebRTC standards including supported audio/video codecs, signaling protocols, and new efforts relating to a common browser API and interworking with legacy IMS networks. He discusses various industry groups and alliances working on WebRTC interoperability and the relationship between WebRTC, VoLTE, and RCS standards.

1. WebRTC Standards update (April 2015)
Victor
Pascual
Avila
Victor.Pascual@quobis.com
@victorpascual

2. 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
- WebRTCHacks.com co-founder and blogger
- Independent Expert at European Commission
- Adjunct Professor at Universitat Pompeu Fabra
About Me

3. (Media)
(Signaling)
(Signaling)
“Set or RTC APIs
for Web Browsers”
“New protocol
profile”
WebRTC standards

4. - Audio codecs – G.711, Opus
- Video codecs – H.264, VP8 (oh, well…)
- 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)

6. Some discussion on the topic: http://webrtchacks.com/cisco-openh264/
The Video Codec Battle

7. 7

8. Photo
taken
by
Dan
York
8

9. Consensus!
9

10. But…
10

11. Consensus!
11

12. VP9
vs.
H.265
12

13. 19
Nov
2014
13

14. 14

15. 15

16. 16

17. 17

18. 18

19. 19

25. Source:
hJp://iswebrtcreadyyet.com/

26. 26

30. 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
1.1
2.0
?

31. http://status.modern.ie/
Browser API

32. 32

33. Plug-­‐in free or free plug-­‐in?
33

34. 34

35. 35

36. 36

37. http://webrtchacks.com/ims-approach-webrtc/
WebRTC Access to IMS (r12)

38. Adding New Wheels to IMS
with WebRTC

39. 3GPP TS 23.228 V12.5.0
(2014-06)

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

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

42. Alliance for Telecom Solutions

43. 43

44. WebRTC Interop Activity Group

45. RESTful Network API for WebRTC Signaling v.1.0 (Feb 2014)
OMA
This
slide
might
be
outdated

46. How does WebRTC relate to VoLTE
and RCS?
GSMA

47. This
slide
might
be
outdated
47

48. This
slide
might
be
outdated
48

49. 49

50. Thank You!
Victor
Pascual
Avila
Victor.Pascual@quobis.com
@victorpascual