[Members] [news] Anyone can build a Windows Messenger client—with open standards access via XMPP

Ralph Meijer jabberfoundation at ralphm.ik.nu
Wed Dec 21 11:06:03 UTC 2011


On 2011-12-15 03:39 , jehan at zemarmot.net wrote:
> Hi,
>
> On Wed, 14 Dec 2011 14:40:16 -0700, Peter Saint-Andre
> <stpeter at stpeter.im>  wrote:
>> http://windowsteamblog.com/windows_live/b/windowslive/archive/2011/12/14/anyone-can-build-a-windows-live-messenger-client-with-open-standards-access-via-xmpp.aspx
>
> I'll note that they indeed have DNS SRV records for both client and
> server, though that gives back an alias (which — I think —is wrong,
> though the RFC does not give this precise case. It says only one should
> not return a target which is itself on alias; anyway we lose port,
> priority, weight, etc. information):
>
> jehan at marmot-balladeuse:~$ ring -t SRV _xmpp-server._tcp.live.com
> _xmpp-server._tcp.live.com. is an alias for rds.live.com.nsatc.net.
> jehan at marmot-balladeuse:~$ ring -t SRV _xmpp-client._tcp.live.com
> _xmpp-client._tcp.live.com. is an alias for rds.live.com.nsatc.net.

Well, they basically have a wildcard CNAME record for *.live.com 
pointing to rds.live.com.nsatc.net. No SRV records there. However, the 
domain for their messenger service is 'messenger.live.com' which does 
have a SRV record for clients:

> _xmpp-client._tcp.messenger.live.com. 3600 IN SRV 10 0 5222 beta.xmpp.messenger.live.com.

As expected, there is no SRV record for s2s traffic. In the comments of 
the article, Dare Obasanjo points to 
<http://windowsteamblog.com/windows_live/b/windowslive/archive/2011/09/08/betting-on-connect-100x-the-im-engagement-and-no-need-to-re-spam-your-friends-with-more-invites.aspx>. 
Reading that, it seems to me that they consider *not* providing 
federation to be a feature. Or at least for now. Instead they do this 
'connect' thing, which I believe is similar to server-side gateways in 
our universe.

-- 
ralphm


More information about the Members mailing list