WebRTC Standards -- The 10 Minutes guide
1 like1,011 views
This document provides an overview of WebRTC standardization efforts in 3 sentences or less: WebRTC standardization is being addressed by the W3C for browser APIs, the IETF for protocols, and other groups like the SIP Forum and 3GPP. There are still open issues around browser support, signaling, interworking with SIP, video codecs, and security. The document concludes by introducing the speaker, Victor Pascual, as a technology consultant who can be contacted for further discussion on WebRTC standardization topics.
WebRTC Standards -- The 10 Minutes guide
- 1. WebRTC Standards The 10 Minutes guide London, UK 16 Sept 2013 Victor Pascual Technology, Innovation & Strategy Consultant Email: victor.pascual.avila@gmail.com Twitter: @victorpascual
- 2. We've a packed agenda Goal for today: introduce what's going on re WebRTC standardization (in 10 min) We'll go deeper into details in future sessions Offline discussions/follow-ups: you can contact me at victor.pascual.avila@gmail.com
- 3. WebRTC standardization WebRTC can be seen from two angles W3C WebRTC set of RTC APIs for Web-browsers IETF RTCWEB new ‘protocol profile’ -- it's about media (can be used in non-Web endpoints) Other activities SIP Forum WebRTC Task Group 3GPP “WebRTC access to IMS (IMS-WEBRTC)” IMTC WebRTC Interoperability Activity Group Recommended reading A Hitchhiker’s Guide to WebRTC standardization (July 2013)
- 4. Watch List WebRTC moving really fast, lots of early implementations, customer trials... BUT still a number of open issues and items to include into the watch list (non- exhaustive): Browser support and industry commitment Signaling options for WebRTC WebRTC-SIP interworking Impact on Signaling and media planes incl. RCS and VoLTE strategy Strict firewall and HTTP-middlebox traversal Video Codec discussion (i.e. VP8 vs H.264) Current plan (as per Friday 13 Sept) is to make a decision by Nov 2013 Media codecs (support beyond G.711 and Opus?) SDP Offer/Answer discussion and competing API proposals WebRTC 1.0 vs WebRTC 2.0 Security aspects (e.g. media encryption DTLS-SRTP vs SDES -- re-encryption, EKT?) Mobile and non-Web endpoints (apps, set-top-boxes, Smart TV, etc.) Federation, Identity management, credentials and user authentication Regulation, charging, QoS, etc. Source: iswebrtcreadyyet.com
- 5. About me Technology, Innovation & Strategy Consultant Main focus: Help to make WebRTC happen – involved in WebRTC standardization, development and first industry deployments (ongoing RFx's, PoC's and field trials). Current activities IETF contributor (SIP, Diameter and WebRTC) and STRAW Working Group co-chair SIP Forum WebRTC Task Group co-chair WebRTCHacks.com co-founder and blogger Independent expert at European Commission Speaker and Advisory board member for several industry conferences Chief Strategy Officer (CSO) at Quobis Consulting services (e.g. product/service/strategy definition, fair advise on vendor/technology selection, in-house training, etc.) Software development services (e.g. vendor agnostic WebRTC client + management server, etc.) Integration services (e.g. commercial third party or open-source WebRTC-to-SIP gateways, etc.) Previous background Acme Packet (led OTT and WebRTC strategy in EMEA and CALA) Tekelec (extended open-source SIP Express Router/OpenSER/Kamailio for 3GPP IMS and NGN) Universitat Pompeu Fabra (Researcher and associate Professor) Voztelecom (first SIP-based Service Provider in Europe)
- 6. Thank you! Offline discussions/follow-ups: you can contact me at victor.pascual.avila@gmail.com