Obviously all the “interoperability” solutions that exists today are just Band-Aids. True interoperability would mean that users could log into whatever IM product they choose to use (and JUST that IM program) and communicate with users on any other IM program. As it stands right now, you have to login from one client to multiple networks.

Once again, it depends how you define interoperability. Any Sametime user that wants you to be able to IM them from AIM is accessible from AIM. You just need to know their AIM ScreenName. So I would say YES you can chat with Sametime users.

Why doesn’t this qualify? Exchange Messenger and MSN Messenger use completely different protocols, connect to different servers and do not share user information between them.

Actually, I’m pretty sure this is the case because AOL would have to open up their network to competitors if they linked AOL & ICQ together. As I recall this was one of the issues that was discussed as part of the FCC ruling with AOL & TimeWarner merging last year.

While there is certainly an argument to be made that AOL in particular isn’t interested in promoting interoperability in the IM space at this time for consumers, not all of the “big 3” feel that way. Look at what MSN did recently informing Trillian of a change they were making to their servers that would cut off Trillian access. That’s a positive sign that at least Microsoft is not opposed to the concept of interoperability. Actions speak louder than words.

AOL’s behavior on the other hand definitely has an air anti-interoperability, despite what they say in the press. Personally, I don’t consider it an “open” system if you have to pay AOL money in order to gain interop, or your users have to register for AIM accounts in order to message users on the service.

Businesses are clamoring for enterprise solutions that address interoperability specifically because the consumer products don’t meet their technical requirements, but that a large amount of business communication is done with people outside of the organization. Products like Bantu, Sametime and Exchange Messenger (to a lesser extent) are attempting to meet the business requirements for interoperability.

://B

Some software companies in the education space are starting to integrate IM into their existing product offerings.

Blackboard, for example, has a number of IM “building blocks” that allow the integration of consumer or enterprise IM (Bantu) products into their platform. This allows students and professors to send real-time messages in the context of their classes.

A lot of colleges and university IT departments are starting to realize that they want to offer their own IM solution, in a way similar to offering e-mail for students and staff.

The lack of any true interoperability standards makes this a decision between proprietary technologies (at least for the moment.)

B://