PITTSBURGH - The Internet Engineering Task Force has zeroed in on three technical proposals for creating an instant messaging standard, but the finalists do not include market leader AOL.
The three proposals - developed by Cisco, Microsoft, Fujitsu and other companies - were selected from a field of 10. AOL's last-minute submission was a general framework for instant messaging interoperability rather than a full-fledged protocol, so it was not chosen for further consideration.
IETF officials say all three of the selected protocols appear to interoperate with AOL's framework. AOL currently blocks instant messaging traffic from competitors such as AT&T and Microsoft.
"There are elements of our proposal in all three of the selected proposals," says Edwin Aoki, a principal engineer with AOL who is tracking the IETF effort. "We're not supporting any particular proposal. We will examine them all to see which will meet our needs."
The three protocol proposals selected for study by the IETF's Instant Messaging and Presence Protocol (IMPP) working group are:
- Instant Messaging and Presence using SIP, an approach that incorporates the Session Initiation Protocol (designed for telephone signaling applications) to handle instant messages and online presence perception. This proposal team includes representatives from Cisco and Microsoft.
- IMXP, a proposal that uses the Blocks Extensible Exchange Protocol, which itself supports XML-based messaging as its transport protocol. This proposal team is led by start-up Invisible Worlds.
- Simple Instant Messaging Protocol, which uses servers as socket-level forwarders to transport messages. This proposal team includes employees of Fujitsu and the Massachusetts Institute of Technology.
Fierce debate
The merits of the three proposals were fiercely debated at a two-hour meeting held here Aug. 1. By meeting's end, the group was deadlocked on whether to choose one of the protocols or develop all three. If multiple proposals are chosen, the group will develop a common data format and gateways between the protocols.
IETF leaders asked representatives of the three teams to prepare a report outlining the commonalties and differences between their approaches, and articulate whether they can converge their work into a single protocol. The report is due Aug. 21.
"It's very important that people don't see it as a failure if we end up with three protocols instead of one," says Patrik Faltstrom, who oversees the IMPP working group as director of the IETF applications area. "We had to develop gateways anyway because we have to interoperate between our protocol and the ones used by AOL and [its subsidiary] ICQ."
AOL's Aoki says it is premature for the company to comment on whether it will support multiple instant messaging standards if that's what the IETF develops.
"AOL will feel pressure to implement whatever standard the IETF develops," says Keith Moore, a former IETF applications area director. Moore adds that "there's so much more potential for instant messaging in the wireless world that AOL's installed base doesn't matter that much."
Formed more than two years ago, the IETF's IMPP working group has made little progress in its efforts to develop an instant messaging standard. The group will hold its next meeting in December in San Diego.
RELATED LINKS
Contact Senior Editor Carolyn Duffy Marsan
Other recent articles by Marsan
IETF's Instant Messaging and Presence Protocol working groupThe 10 instant messaging protocols submitted to the IETF
AOL's Instant Messaging interoperability framework
AOL out of instant messaging standard bake-off
Network World, 08/03/00.
The skinny on IMPP
Network World, 05/01/00.
Instant messaging protocol hits speed bump
InfoWorld, 05/26/00.
Housekeeping for traceroute and instant messaging
Network World, 08/09/99.

