Interop, please

1,175 views
1,129 views

Published on

The new landscape of realtime conversation is here. Skype, Google, Facebook, Microsoft, Yahoo!, TokBox, Voxeo, Twilio and many others have divergent models. This talk lists some of the opportunities for convergence and interop, the benefits to operators, and questions about preconditions for this dialog.

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

  • Be the first to like this

No Downloads
Views
Total views
1,175
On SlideShare
0
From Embeds
0
Number of Embeds
55
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Interop, please

  1. 1. Interop, please<br />Phil Wolff, Skype Journal 10 March 2011<br />
  2. 2. “Bruegel's paintings seem to attribute the ultimate failure of the Tower to engineering difficulties rather than to sudden, divinely-caused linguistic differences.” ̶ The Tower of Babel, Wikipedia<br />
  3. 3. What if we start a standards/interoperability workshop for cloud conversation?<br />
  4. 4. What if we start a standards/interoperability workshop for cloud conversation?<br />Not just the cloud telephony part; the world needs interoperability across a much broader scope.<br />
  5. 5. Consider Twilio, Voxeo, Skype, Telefónica/Jajah, Google Talk/Google Voice, Apple, Ribbit/BT, Yahoo!, TokBox, Microsoft/Nokia, Facebook, and Speek. <br />All operate a public cloud communications platform, operate a private one for their own purposes, or are very likely to in the next 18 to 24 months. The list is growing.<br />Together, they serve more than a billion people.<br />
  6. 6. Their platforms are diverging on: <br />Models of a conversation <br />Models of contacts, relationship life cycles <br />Models of groups of contacts <br />Media and Modalities (IM, voice, video, 3D immersion/AR, subtitles, SMS) <br />Dial Tone <br />Availability Presence<br />Activity messaging and streaming <br />Intention Presence<br />Peering Agreements <br />Call failure modes <br />Network failure modes <br />Persistence <br />The new call detail record (CDR) reporting <br />User Interface widgets and experience design defaults <br />
  7. 7. Early divergence can be good, as an industry explores the possibilities. <br />
  8. 8. An industry with many platforms, however, benefits from some types of convergence. <br />
  9. 9. The ability for applications to reach more people, working across systems. <br />The opportunity for apps to run in more places. <br />Network effects bigger than any one company. <br />Calls to include parties from more than one network <br />Product innovation within architectural layers, so changes in one technology don’t obsolete all the others. <br />Portability of customer data. <br />Freedom to move between and among accounts. <br />Independence from any one platform provider. <br />Convergence of the new call metadata useful for security, identity, billing, and peering. <br />
  10. 10. Interopcan make this space into a more vital ecosystem and industry.<br />
  11. 11. Now would be a great time to start a conversation by and for<br />the people building the protocols<br />and <br />the people usingthem. <br />
  12. 12. Starting Topics<br />In a world of mashups (that sounds so last decade), the cloud conversation products are new islands of isolation. <br />Are we ready to discuss interoperability?<br />Who should be invited to participate?<br />What will bring the right people together?<br />What will it take to make a safe space for this conversation? <br />How open can we make this conversation?<br />What considerations affect timing?<br />Next steps?<br />
  13. 13. Let’s talk<br />Phil Wolff<br />@evanwolf<br />pwolff@SkypeJournal.com<br />Skype:evanwolf<br />+1-510-316-9773<br />SkypeJournal.com<br />

×