--- Andre-John Mas <[EMAIL PROTECTED]> wrote:
> The only thing, is I am not sure I can imagine how they would deal > with MSN, > which allows for accounts with domain names which aren't in the > msn.com or > hotmail.com realm. Maybe this could be a fallback method if > everything > This is not an issue just with MSN - AOL allows vanity domains as well for their AIM services. It does not appear that any of the older consumer IM networks announce any IM-related SRV records for these domains. (Google Apps does) Further, it is possible for just a subset of users in a domain to pick [EMAIL PROTECTED] id's on the AIM network while other users on that domain or the entire company may use, say XMPP or SIP on their enterprise IM servers. All of this fragmentation can break (eventual) seamless Federation - for now you are required to ask your correspondent which consumer IM network/transport serves their [EMAIL PROTECTED] ID, specify that while adding it your roster, and work around it by using selective routing on the local IM servers. Any idea how Sametime and/or LCS handle these issues in their federation implementations as they both have built-in federated connectivity to AOL, MSN and Yahoo
