John C Klensin wrote:
Having to configure multiple IM accounts, ...>
No question about it. I was thinking partially about Jabber,
Right. Which was why I said "proprietary". (Jabber, having been turned into
XMPP, nicely dodges that qualifier...)
with interoperability between implementations and hosts,
From some recent experiences, it is looking as if it still needs to go through
some implementation learning curve. I suspect it's not a protocol issue, but
I've seen some interoperability problems and would bet the issue was software
maturity.
and Skype with (at
least as I understand it) a fairly distributed architecture. As to the rest,
oh.
I think there is another interesting story in the fact that multiprotocol
clients seem more effective and useful, and much more widely used and
deployed, for IM than their equivalents were for email. Part of it is
Maybe. I'm seeing enough oddities with the popular, multi-protocol IM client
that I use to continue to believe that the combinatorials that are inherent with
multiple, competing protocols make long-term viability a real question.
Back when I wrote email gatewaying software -- and it's design was with a
canonical model that each service was mapped to/from -- I know that every time
I added a new email service, I had to go into the core and make tweaks. Or
sometimes deeper changes.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf