Interop, please

13
Phil Wolff, Skype Journal 10 March 2011 Interop, please

description

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.

Transcript of Interop, please

Page 1: Interop, please

Phil Wolff, Skype Journal 10 March 2011

Interop, please

Page 2: Interop, please

“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

Page 3: Interop, please

What if we start a standards/interoperability workshop for cloud conversation?

Page 4: Interop, please

What if we start a standards/interoperability workshop for cloud conversation?

Not just the cloud telephony part; the world needs interoperability across a much broader scope.

Page 5: Interop, please

• Consider Twilio, Voxeo, Skype, Telefónica/Jajah, Google Talk/Google Voice, Apple, Ribbit/BT, Yahoo!, TokBox, Microsoft/Nokia, Facebook, and Speek. • 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.• Together, they serve more than a

billion people.

Page 6: Interop, please

Their platforms are diverging on: • Models of a

conversation • Models of contacts,

relationship life cycles

• Models of groups of contacts

• Media and Modalities (IM, voice, video, 3D immersion/AR, subtitles, SMS)

• Dial Tone • Availability

Presence

• Activity messaging and streaming

• Intention Presence• Peering

Agreements • Call failure modes • Network failure

modes • Persistence • The new call detail

record (CDR) reporting

• User Interface widgets and experience design defaults

Page 7: Interop, please

Early divergence can be good, as an industry explores the possibilities.

Page 8: Interop, please

An industry with many platforms, however, benefits from some

types of convergence.

Page 9: Interop, please

1. The ability for applications to reach more people, working across systems.

2. The opportunity for apps to run in more places.

3. Network effects bigger than any one company.

4. Calls to include parties from more than one network

5. Product innovation within architectural layers, so changes in one technology don’t obsolete all the others.

6. Portability of customer data.

7. Freedom to move between and among accounts.

8. Independence from any one platform provider.

9. Convergence of the new call metadata useful for security, identity, billing, and peering.

Page 10: Interop, please

Interop can make this space into a more vital ecosystem and industry.

Page 11: Interop, please

Now would be a great time to start a conversation by and for

the people building the protocols

and the people using them.

Page 12: Interop, please

Starting Topics

In a world of mashups (that sounds so last decade), the cloud conversation products are new islands of isolation. • Are we ready to discuss interoperability?• Who should be invited to participate?• What will bring the right people together?• What will it take to make a safe space for

this conversation? • How open can we make this conversation?• What considerations affect timing?• Next steps?

Page 13: Interop, please

Phil Wolff@evanwolf

[email protected]

Skype:evanwolf+1-510-316-9773SkypeJournal.com

Let’s talk