1 / 16

The Phone Meets the Web.

The Phone Meets the Web. IETF and W3C Standards for Real Time Communications in Browsers. RTCWEB / WEBRTC Andrew Hutton – Head of Standardization at Siemens Enterprise Communications. www.siemens-enterprise.com/uk. Contents. Standardization - IETF & W3C RTCWEB / WEBRTC. Why, Who, What.

caron
Download Presentation

The Phone Meets the Web.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The PhoneMeets the Web. IETF and W3C Standards for Real Time Communications in Browsers. RTCWEB / WEBRTC Andrew Hutton – Head of Standardization at Siemens Enterprise Communications. www.siemens-enterprise.com/uk

  2. Contents • Standardization - IETF & W3C • RTCWEB / WEBRTC. • Why, Who, What. • Disruptive? • Use Cases and Requirements. • Solution Overview. • Architecture • Security • Identity, Consent, Firewalls. • Implementation Status. .

  3. Standardization – Internet Engineering Task Force (IETF) • The mission of the IETF is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet. • An Open Standards organisations based on consensus and openness. • One of the "founding beliefs" is embodied in a quote from David Clark: "We reject kings, presidents and voting. We believe in rough consensus and running code". • Another quote that has become a commonly-held belief in the IETF comes from Jon Postel: "Be conservative in what you send and liberal in what you accept". – Its all about interoperability. • 115 Active Working Groups – Probably something you are interested in? • RFC / Protocol Factory • HTTP – RFC 2616 • TCP – RFC 675 • SIP – RFC 3261 IETF Video - http://youtu.be/tqc8vd_jPpg.

  4. Standardization – World Wide Web Consortium (W3C) • The World Wide Web Consortium (W3C) is an international community that develops open standards to ensure the long-term growth of the Web. An Open Standards organisations based on consensus and openness. • Principles. • Web for All (Accessibility, Internationalization etc.) • Web on Everything (Mobile Web Etc.) • Web of Rich Interaction (Communications, Social Networking Etc.) • Web of Data and Services (Semantic Web Etc.) • Web of Trust (Security and Privacy). • HTML5, CSS, XML, Web Services, • Browser API’s, Device API’s.

  5. IETF / W3C Participation. • Anyone can participate in Open Standards Development. • All IETF work is done in public using public mailing lists and meetings. • Most W3C work uses public mailing lists but not all. • However be careful. • Both IETF and W3C have strict IPR Policies and your employer might not be happy if you give away your company IPR. • You need to understand IPR issues before you make any contribution (Even an E-Mail to the working group mailing list).

  6. RTCWEB / WEBRTC Who, What and Why. Interactive Voice, Video and Data in a Browser. • Initiated by Google in late 2010 who organised meeting of IETF & W3C members. • Proposed to initiate standardization project with the aim of enabling real-time media transport (Voice, Video and Data) between browsers. • Real-Time Communication was previously only possibly in Web Applications using Plug-ins which have many issues. • Agreed to split the work between IETF & W3C (There is a large overlap in people and companies anyway). • Now probably largest working group in IETF and many participants / contributors.

  7. WEBRTC – Disruptive ? • Makes every browser in to a potential VoIP Soft client. • No Plugin’s, no downloads. • GUI is web based. • Security controls are built-in to the browser. • Audio/Video codec’s built-in to the browser and royalty-free (Hopefully). • Standard API for the millions of web application and games developers to work with. • Does not require any real-time VoIP knowledge it just works.

  8. RTCWEB / WEBRTC Standards • IETF RTCWEB (Real-Time Communications For WEB Browsers) • Defines requirements, architecture, security model, and protocols, for peer to peer communication (Audio, Video, Data) between browsers. • Has to be standardized to enable interoperability between browser vendors. • Too many internet drafts to mention 78 at last count but only a few will become RFC’s. http://tools.ietf.org/id/rtcweb. • W3C WEBRTC (Web Real-Time Communications). • Specifies browser API’s. • Has to be standardized so that application developers have a common API to work with. • Three specifications (PeerConnection, getUserMedia, mediaStreamCapture).

  9. WEBRTC – Use Cases and Requirements. • Basic Voice / Video Communications. • Multiparty Voice/Video. • FedEx calling – PSTN/Legacy Interworking requirements. • Enterprise NAT/FW Scenarios. • Multiparty on-line gaming. • Data channel requirements. • Security Considerations. • There are lots – Consent (Receive Media, Device/Camera Access etc.) http://tools.ietf.org/html/draft-ietf-rtcweb-use-cases-and-requirements-10

  10. RTCWEB Architecture - Trapezoid & Identity Inter-domain Communication Servers example.com Servers example.net Out of Scope* Signaling over HTTPS/WebSockets(JSEP/ROAP, SIP*) Signaling over HTTPS/WebSockets (JSEP/ROAP, SIP*) JavaScript/HTML/CSS JavaScript/HTML/CSS Connectivity (STUN/ICE) Browser Browser Media DTLS-SRTP Verify Assertion Verify Assertion Get Assertion Get Assertion Identity Provider Identity Provider * Browser to Web Server and Inter-domain signalling is out of scope but has strong influence on browser API.

  11. Identity – How do you know who you are talking to? WEBRTC WEBSITE Alice log’s on to her identity provider. Before calling Bob Alice’s Browser gets identity token assertion from the provider. Identity assertion is passed to Bob’s browser during call establishment. Bob’s browser asks the identity provider to verify the assertion. The identity assertion and the DTLS fingerprint are checked and the user is given the green light to indicate that the remote party is trusted (by the identity provider) and there is no man in the middle. Alice Bob Secure Media over DTLS/SRTP Identity Provider

  12. Consent – How do we prevent media hammer attacks. Target HTML5 / JavaScript Alice Alice Audio, Video, Data Audio, Video, Data Bob

  13. Consent – How do we prevent media hammer attacks. ICE Credentials passed via the service provider. HTML5 / JavaScript HTML5 / JavaScript Bob Alice Audio, Video, Data ICE/STUN – Ok to talk? ICE/STUN – Yes ok to talk ICE/STUN – Still Ok to talk? ICE/STUN – Yes ok to talk http://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-06

  14. NAT’s and Firewall – Connectivity Problems. ICE – RFC 5245 – Is the answer. ICE – Interactive Connectivity Establishment Provides a means of finding the best path between Alice and Bob. Provides means to create NAT binding and obtain server reflexive address (STUN). Provides a means to insert relays if necessary (TURN) – Symmetric NAT’s. Alice gathers all possible address candidates and asks remote party to connectivity check them until best candidates are chosen. Also provides means for consent. Bob Alice STUN Server TURN Server TURN Server

  15. Browser Implementation Status – Not Finished Yet. • Google - Chrome • The leaders and following the standards as close as possible. • Available in Chrome stable and Chrome canary. • http://www.webrtc.org/home. - Some confusion regarding Google project name. • Mozilla – Firefox • Available in Firefox nightly build. • Recently demonstrated interoperability with Chrome. • Apple – Safari • Who knows? • Microsoft – Internet Explorer. • Implemented getUserMedia API, • Active contributor to standards bodies (Microsoft/Skype). • However has an alternative API proposal (CU-RTC-WEB) • Others with implementations. • Opera, Ericsson Browser (Mobile).

  16. Thank you for your attention! Andrew Hutton Siemens Enterprise Communications Ltd. E-mail: andrew.hutton@siemens-enterprise.com Twitter: @huttonandy

More Related