IM Interoperability: It's the Business Model, StupidBy Matthew Hicks | Print
Re-Imagining Linux Platforms to Meet the Needs of Cloud Service Providers
Microsoft's recent deal with the three major IM services demonstrates that business dealings, not competing technology protocols, are driving the big battle for interoperability.The tension between technology and business models is intensifying in the instant messaging market as the largest IM providers test new approaches for working together.
So far, business is winning.
Last month marked a turning point in the ability for users to communicate across the largest IM networks. Microsoft Inc., Yahoo Inc. and America Online Inc. forged an agreement for letting messages and presence information move between Microsoft's forthcoming Office Live Communications Server 2005 and the three big networksMSN Messenger, Yahoo Messenger and AOL Instant Messenger
"Everybody wants interoperability, but everybody wants it around a business model that works for them," said Royal Farros, chairman and CEO of messaging vendor MessageCast Inc., in Redwood City, Calif. "What the big three are trying to do is to find a way where if they open up to interoperability, they all can get paid."
Farros likened the emerging IM approach to the way telecommunication companies charge one another for calls as they transverse various network boundaries. The enterprise space is a fertile testing ground because, unlike the free consumer IM client, there is revenue from IM server licenses, Farros said.
Analysts have predicted that Microsoft's move with its public IM rivals will lead the top networks to forge more deals with other enterprise IM players, such as IBM's Lotus division. Lotus already links with AOL in its Instant Messaging product.
But if the leading IM providers focus on specific business arrangements for interconnections, where will that leave the technological efforts toward a common protocol?
In the short term, analysts say, adoption of a common protocol will be secondary to the still-developing business models, and users and vendors will be left with multiple protocols.
AOL, MSN and Yahoo each run their services on their own proprietary protocols.
In the server space, the vendors have split into various camps. Microsoft and IBM support different implementations of a protocol based on Session Initiation Protocol (SIP), called SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE). Meanwhile the Extensible Messaging and Presence Protocol (XMPP) became a standard through the Internet Engineering Task Force, and it is largely backed in the open-source community and through enterprise IM vendor Jabber Inc.
For its part, Denver-based Jabber has acknowledged that XMPP is far from a single, widely adopted standard. Jabber, which competes with Microsoft and Lotus for enterprise customers, last month responded swiftly to Microsoft's deal by announcing plans for a gateway between its Jabber XCP product, based on XMPP, and IBM's version of SIMPLE used in Lotus Instant Messaging.
"XMPP, SIP and SIMPLE needed to cooperate and work together, and at the end of the day, we want to allow our customers not to make a specific protocol decision but an application decision," said Rick Emery, vice president of business development at Jabber.
Jabber expects to release the gateway in the fourth quarter of this year and to release additional interoperability between XMPP and SIP implementations.
Next Page: Living in a multiprotocol world.
"It's an acknowledgement that we live in a multiprotocol world," Boyd said. "And Jabber Inc., as opposed to the open-source group, can't win by continuously proclaiming that XMPP is better because most people don't care a hoot about protocols, but they care about whether IM helps them do what they want to do."
In many ways, the IM industry is in a position similar to e-mail before wide adoption of standard protocols, analysts and vendors said. The closed networks such as MCI Mail and CompuServe gave way to gateways among networks before the exchange of messages opened up completely through standards.
"If you look historically at how e-mail evolved, you had individual deals and then at some point that was not satisfying people," said Sara Radicati, president and CEO of The Radicati Group Inc., a research firm in Palo Alto, Calif.
Radicati said she considers Microsoft's move a short-term approach to gain early interconnections among IM networks, but she said a widely adopted standard will be necessary in the longer term.
The federation between LCS 2005 and the three IM networks will focus on one-to-one messaging and presence information but won't allow more advanced features such as multiparty chat sessions, which a common protocol could enable, Radicati said.
"People will start to want full, protocol-level interoperability," she said.
At the same time, the number of major enterprise IM platform vendors is narrowing after Yahoo and AOL conceded the space to software companies, Boyd said. In June, Yahoo stopped offering its separate enterprise IM service, called Yahoo Business Messenger, while AOL dropped its AIM Enterprise Gateway product.
Both companies instead have been touting their partnerships with IM gateway server vendors such as IMlogic Inc., FaceTime Communications Inc. and Akonix Systems Inc., which add monitoring and management tools to the public networks.
Their decision to leave the enterprise market signaled a shift in focus for the large IM networks and helped set up a scenario for greater cooperation with enterprise software companies such as Microsoft, Boyd said.
"The business issue was formally strategic, and that was because they wanted control of their brand and their market in enterprise space," Boyd said. "But now they've rethought it. Now, they're thinking tactically."