<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: IM Interoperability: It&#8217;s Not a Technology Issue</title>
	<atom:link href="http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/</link>
	<description></description>
	<lastBuildDate>Wed, 16 Dec 2009 16:39:22 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brad</title>
		<link>http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/#comment-23968</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Thu, 16 Apr 2009 18:39:55 +0000</pubDate>
		<guid isPermaLink="false">http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/#comment-23968</guid>
		<description>Mar, 

I don&#039;t presume to be an expert in IM, but I&#039;ve published your post in the hope that somebody closer to the day-to-day action in that space might be able to assist you. Best of luck. 

Brad</description>
		<content:encoded><![CDATA[<p>Mar, </p>
<p>I don&#8217;t presume to be an expert in IM, but I&#8217;ve published your post in the hope that somebody closer to the day-to-day action in that space might be able to assist you. Best of luck. </p>
<p>Brad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mar</title>
		<link>http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/#comment-23965</link>
		<dc:creator>mar</dc:creator>
		<pubDate>Thu, 16 Apr 2009 09:20:24 +0000</pubDate>
		<guid isPermaLink="false">http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/#comment-23965</guid>
		<description>hello,
Im master sudent and Im doing research in this area and Im looking for experts in this area to know experts opinion. could you please assist me.</description>
		<content:encoded><![CDATA[<p>hello,<br />
Im master sudent and Im doing research in this area and Im looking for experts in this area to know experts opinion. could you please assist me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/#comment-8</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Sat, 15 Jul 2006 14:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/#comment-8</guid>
		<description>Jean-Louis,

Thanks for the comment. 

Upon further investigation, Microsoft apparently continues to use its proprietary MSNP as the IM/presence protocol that resides on its Windows Live Messenger client. Yahoo, too, is staying with its proprietary Yahoo Messenger Protocol.

The text in my post has been modified to reflect those facts. Rather than implementing standards protocols on their IM clients for the mass market, which would suggest true openness, Microsoft and Yahoo are hedging their bets (and defending their turf) by continuing to use proprietary IM/presence protocols while using SIP/SIMPLE gateway servers to facilitate interoperability between services. 

It&#039;s far from ideal, and a it&#039;s still a dual IM universe that&#039;s effectively walled off from everybody else. What&#039;s interesting, of course, is that Microsoft has adopted SIP/SIMPLE as its core protocols for Windows Messenger and its Live Communications Server client, albeit with some extensions that Microsoft justifies on technical grounds. LCS, as you know, allows communication interoperability between itself and correspondents on the MSN, AOL and Yahoo IM networks.</description>
		<content:encoded><![CDATA[<p>Jean-Louis,</p>
<p>Thanks for the comment. </p>
<p>Upon further investigation, Microsoft apparently continues to use its proprietary MSNP as the IM/presence protocol that resides on its Windows Live Messenger client. Yahoo, too, is staying with its proprietary Yahoo Messenger Protocol.</p>
<p>The text in my post has been modified to reflect those facts. Rather than implementing standards protocols on their IM clients for the mass market, which would suggest true openness, Microsoft and Yahoo are hedging their bets (and defending their turf) by continuing to use proprietary IM/presence protocols while using SIP/SIMPLE gateway servers to facilitate interoperability between services. </p>
<p>It&#8217;s far from ideal, and a it&#8217;s still a dual IM universe that&#8217;s effectively walled off from everybody else. What&#8217;s interesting, of course, is that Microsoft has adopted SIP/SIMPLE as its core protocols for Windows Messenger and its Live Communications Server client, albeit with some extensions that Microsoft justifies on technical grounds. LCS, as you know, allows communication interoperability between itself and correspondents on the MSN, AOL and Yahoo IM networks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Louis Seguineau</title>
		<link>http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/#comment-7</link>
		<dc:creator>Jean-Louis Seguineau</dc:creator>
		<pubDate>Sat, 15 Jul 2006 09:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://nerdtwilight.wordpress.com/2006/07/14/im-interoperability-its-not-a-technology-issue/#comment-7</guid>
		<description>The latest versions of Microsoft’s and Yahoo’s clients use the IETF’s SIP-based SIMPLE (SIP Instant Messaging and Presence Leveraging Extensions) protocol.

Hi Brad, you are making a very realistic tour of the context... unfortunately very true.

You are stating Yahoo! and Microsoft are deploying SIMPLE based clients, but I cannot find anything in their latest or previous announcements describing precisely their technology options. Do you have any technology pointers you could share.

Thanks

Jean-Louis</description>
		<content:encoded><![CDATA[<p>The latest versions of Microsoft’s and Yahoo’s clients use the IETF’s SIP-based SIMPLE (SIP Instant Messaging and Presence Leveraging Extensions) protocol.</p>
<p>Hi Brad, you are making a very realistic tour of the context&#8230; unfortunately very true.</p>
<p>You are stating Yahoo! and Microsoft are deploying SIMPLE based clients, but I cannot find anything in their latest or previous announcements describing precisely their technology options. Do you have any technology pointers you could share.</p>
<p>Thanks</p>
<p>Jean-Louis</p>
]]></content:encoded>
	</item>
</channel>
</rss>
