1 / 58

Stop the Silos: The road to federated RTC

Stop the Silos: The road to federated RTC. Presented by Robin Raymond Chief Architect, Hookflash / OpenPeer.org. 2013-10-16. Agenda. When Alice met Bob. The World of RTC Today. Why is Federation Important?. Features Needed For Federation. Case Study: Open Peer ’ s Federation.

giorgio-lunney
Download Presentation

Stop the Silos: The road to federated RTC

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. Stop the Silos: The road to federated RTC Presented by Robin Raymond Chief Architect, Hookflash / OpenPeer.org 2013-10-16

  2. Agenda When Alice met Bob The World of RTC Today Why is Federation Important? Features Needed For Federation Case Study: Open Peer’s Federation Challenges ahead Stop the Silos: The road to federated RTC

  3. The World of RTC Today The World of RTC Today

  4. 100 Year Old Technology Still Works Best! (anyone can call anywhere on the planet at any time) The World of RTC Today

  5. Legacy / RTC Interactions (bridging often happens to the legacy network in an attempt at universal access) The World of RTC Today

  6. “Big Social” Can we play in your sandbox? The World of RTC Today

  7. Silo Apps (with varying degrees of interoperability but for the most part still islands of users) The World of RTC Today

  8. Protocols (promise a universal standard for RTC but isn’t solving federated access well) The World of RTC Today

  9. WebRTC – the future is now! The World of RTC Today

  10. When Alice met Bob… Who are Alice and Bob?

  11. Alice calls Bob This is how Alice and Bob are seen in RTC. But who are Alice and Bob anyway? Who are Alice and Bob?

  12. Alice isn’t just a character She’s a real person. She has a career, friends, interests, + she’s online. Who are Alice and Bob?

  13. Alice is known at work by… Who are Alice and Bob?

  14. Alice is in communication with friends… Who are Alice and Bob?

  15. Alice has interests… Who are Alice and Bob?

  16. And so does Bob… Who are Alice and Bob?

  17. Why is Federation Important? Why is Federation Important?

  18. Unless Alice and Bob are logged into a common website they can’t talk! ? Why is Federation Important?

  19. Alice and Bob Live in Communication Silos Why is Federation Important?

  20. While Alice and Bob use different websites… They are friends! So why can’t they talk? Why is Federation Important?

  21. Alice should be able to be one person behind the scenes… Why is Federation Important?

  22. Federation is important!(Your website is not a silo) Why can’t they talk together? foo.com bar.com Why is Federation Important?

  23. How does Alice contact Bob online? ? How does Alice contact Bob online?

  24. …when Alice and Bob have so many different online identities? How does Alice contact Bob online?

  25. WebRTC enable every website! … correct?!? How does Alice contact Bob online?

  26. Buzzzt! Nope. How does Alice contact Bob online?

  27. How does a user on one website talk to a user on another? ? (no magic solution) How does Alice contact Bob online?

  28. Welcome to browser tab hell… • Who’s going to put up with the inevitable: • Popups • Bouncing tabs • Tab per website identity • Background “ding” sounds with no clear indicator • Badly integrated communication interfaces How does Alice contact Bob online?

  29. Maintaining an active identity connected to each website is not practice on mobile Imagine switching apps constantly to talk between friends while draining your battery because of constant per site keep-alives. How does Alice contact Bob online?

  30. Is single sign-on the solution? • …not quite... • allows you to login to "generic” website with another site’s credentials • offers limited and non uniform control over other sites What is the solution?

  31. “Big Social” Solution? • This is where we are going today… • Top social websites and services fight for communication dominance • Unless you are in that group, this is bad for building your own community • Special interest social websites can’t play in this sandbox • Neglects online social migration that occurs over time What is the solution?

  32. Your Telco's Solution: Every website is reduced to a telephone number behind the scenes: 450-555-1212 What is the solution?

  33. Are Common Backend Protocols the Solution? • Part of the solution, but not the answer… • Where is the address book of friends from all the various websites? • How does a user coordinate a between websites? • How does Alice find Bob using the unknown backend protocol account? • Does Alice have to “friend” twice because of protocol demands? • Must Alice and Bob create a single “communication account” and register it with each website or does each site maintain its own “communication account”? What is the solution?

  34. What Features / Services are needed to support Federation? What Features / Services are needed to support Federation?

  35. A device or web app must be able to represent all identities across federated domains (thus no need for the user to maintain an open application per identity) What Features / Services are needed to support Federation?

  36. A single communication service provider may be used for all identities (thus no need for application to maintain an active session to a service provider per identity) What Features / Services are needed to support Federation?

  37. Login once, associate all other identities (to be able to associate all web facing identities behind the scenes to a single person) What Features / Services are needed to support Federation?

  38. Login into any identity on another device, represent all identities (do we really want to force a user to login to each identity again per device they own?) What Features / Services are needed to support Federation?

  39. Collect identity contact lists from various sources. Other sources (e.g. LDAP) Address Books Social Contacts (have up to date lists of all of your contacts) What Features / Services are needed to support Federation?

  40. Lookup Identity mapping to Communication Service Providers (thus never losing touch with all of your contacts even you or they migrate across services) What Features / Services are needed to support Federation?

  41. Connect Across Communication Service Providers (shouldn’t matter who is providing the backend service) What Features / Services are needed to support Federation?

  42. Case Study: How Federation works in Open Peer Case Study: How Federation works in Open Peer

  43. What is Open Peer? Open sourced protocol for federated secure peer-to-peer RTC Case Study: How Federation works in Open Peer

  44. Philosophy – Ever person owns their own private / public key pair AB4C59DEF385… 84FFE32AABC12… Contact ID Case Study: How Federation works in Open Peer

  45. Domain + Contact ID =Everything you need to contact a user in Open Peer peer://provider.com/AB4C59DEF385… Contact ID Case Study: How Federation works in Open Peer

  46. Server Philosophy – they are (dumb) facilitators Apps use servers like an army knife of tools but all communication is peer to peer. (they assist in finding identities and connecting peers and go then go away) Case Study: How Federation works in Open Peer

  47. Identity Service • Login / Authorization (web extension API supports OAuth, persona, 3rd party custom login, etc) • Registration – register public key, service provider and contact ID • Validation (signature proof of an identity belonging to communication account) Case Study: How Federation works in Open Peer

  48. Identity Lookup Service (resolves each identity public key, contact ID and service provider) Case Study: How Federation works in Open Peer

  49. Identity Lockbox Service Identity Lockbox remembers identity associations, stores keying material and/or other data (but encrypted in ways it cannot decrypt) Case Study: How Federation works in Open Peer

  50. Finder Service foo.com (service) bar.com (service) (find peer across federated domains) 84FFE32AABC12… AB4C59DEF385… Given a public key, contact ID and a domain, find + handshake peers to talk directly Case Study: How Federation works in Open Peer

More Related