<?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/"
		>
<channel>
	<title>Comments on: office live communications server 2007 and public IM connectivity</title>
	<atom:link href="http://blog.loftninjas.org/2008/01/29/office-live-communications-server-2007-and-public-im-connectivity/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.loftninjas.org/2008/01/29/office-live-communications-server-2007-and-public-im-connectivity/</link>
	<description></description>
	<lastBuildDate>Sat, 21 Jan 2012 06:46:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ShadowMobo</title>
		<link>http://blog.loftninjas.org/2008/01/29/office-live-communications-server-2007-and-public-im-connectivity/comment-page-1/#comment-1341</link>
		<dc:creator>ShadowMobo</dc:creator>
		<pubDate>Thu, 12 Feb 2009 14:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.loftninjas.org/?p=130#comment-1341</guid>
		<description>What is great about the PIC feature in OCS is for companies like the one I run OCS for who are getting forced into keeping an archive of all IMs sent, but cannot take the Public IM services away from their customer. PIC lets us allow the customers in our network to chat with AOL, Yahoo, and MSN users while at the same time allowing the IT Divisin to keep a record of all chats to ensure compliancy in case someone wants to try and sue us.</description>
		<content:encoded><![CDATA[<p>What is great about the PIC feature in OCS is for companies like the one I run OCS for who are getting forced into keeping an archive of all IMs sent, but cannot take the Public IM services away from their customer. PIC lets us allow the customers in our network to chat with AOL, Yahoo, and MSN users while at the same time allowing the IT Divisin to keep a record of all chats to ensure compliancy in case someone wants to try and sue us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: btm</title>
		<link>http://blog.loftninjas.org/2008/01/29/office-live-communications-server-2007-and-public-im-connectivity/comment-page-1/#comment-156</link>
		<dc:creator>btm</dc:creator>
		<pubDate>Fri, 08 Feb 2008 16:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.loftninjas.org/?p=130#comment-156</guid>
		<description>Sure. I mean I get the super corporate point of view. So I run Communicator, Pidgin and an IRC client at work. I wouldn&#039;t run Communicator except that I do like it (except note #1). It&#039;d be sweet if communicator was more like pidgin. I&#039;m not just a nerd too, i&#039;d say the majority of my employees run at least one other IM client.&lt;br/&gt;&lt;br/&gt;note #1: I run communicator and communicator mobile. I&#039;d prefer that mobile always be &quot;away&quot;, but all this &quot;presence&quot; hackery makes it so my mobile status updates my desktop status and vice versa. Everytime I leave my desk I need to set myself as away, and everytime I  come back I have to set myself available.&lt;br/&gt;&lt;br/&gt;that&#039;s actually my biggest UI complaint, but again I get why it does it.</description>
		<content:encoded><![CDATA[<p>Sure. I mean I get the super corporate point of view. So I run Communicator, Pidgin and an IRC client at work. I wouldn&#8217;t run Communicator except that I do like it (except note #1). It&#8217;d be sweet if communicator was more like pidgin. I&#8217;m not just a nerd too, i&#8217;d say the majority of my employees run at least one other IM client.</p>
<p>note #1: I run communicator and communicator mobile. I&#8217;d prefer that mobile always be &#8220;away&#8221;, but all this &#8220;presence&#8221; hackery makes it so my mobile status updates my desktop status and vice versa. Everytime I leave my desk I need to set myself as away, and everytime I  come back I have to set myself available.</p>
<p>that&#8217;s actually my biggest UI complaint, but again I get why it does it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: conalw</title>
		<link>http://blog.loftninjas.org/2008/01/29/office-live-communications-server-2007-and-public-im-connectivity/comment-page-1/#comment-155</link>
		<dc:creator>conalw</dc:creator>
		<pubDate>Fri, 08 Feb 2008 05:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.loftninjas.org/?p=130#comment-155</guid>
		<description>Well, if you want your IM to be secure then it had better be running over TLS. Ditto for media. Alternatives such as E2E encryption schemes are difficult to orchestrate. Let&#039;s not make the same mistakes as email. Naturally, there is a limit to how much sensitive data you&#039;d pass into a giant provider network like AOL, but for federation with other companies it&#039;s a reasonably trustworthy mechanism. IMHO with PKI it comes down to how much you trust the public CAs to do their job properly.</description>
		<content:encoded><![CDATA[<p>Well, if you want your IM to be secure then it had better be running over TLS. Ditto for media. Alternatives such as E2E encryption schemes are difficult to orchestrate. Let&#8217;s not make the same mistakes as email. Naturally, there is a limit to how much sensitive data you&#8217;d pass into a giant provider network like AOL, but for federation with other companies it&#8217;s a reasonably trustworthy mechanism. IMHO with PKI it comes down to how much you trust the public CAs to do their job properly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: btm</title>
		<link>http://blog.loftninjas.org/2008/01/29/office-live-communications-server-2007-and-public-im-connectivity/comment-page-1/#comment-154</link>
		<dc:creator>btm</dc:creator>
		<pubDate>Thu, 07 Feb 2008 07:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.loftninjas.org/?p=130#comment-154</guid>
		<description>Sure, I get it. But normally most IM isn&#039;t over TLS anyways, so that&#039;s a poor selling point for having to buy in.&lt;br/&gt;&lt;br/&gt;At the very least, XMPP federation should be available and free, being open and everything.</description>
		<content:encoded><![CDATA[<p>Sure, I get it. But normally most IM isn&#8217;t over TLS anyways, so that&#8217;s a poor selling point for having to buy in.</p>
<p>At the very least, XMPP federation should be available and free, being open and everything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: conalw</title>
		<link>http://blog.loftninjas.org/2008/01/29/office-live-communications-server-2007-and-public-im-connectivity/comment-page-1/#comment-153</link>
		<dc:creator>conalw</dc:creator>
		<pubDate>Thu, 07 Feb 2008 04:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.loftninjas.org/?p=130#comment-153</guid>
		<description>OCS federates directly to the PIC providers so that the link is secured by TLS. Various providers have various kinds of servers on the other end, all of which somehow look like an OCS edge server. The provisioning process involves each PIC provider adding your organization&#039;s domain and edge server FQDN to their list of federated partners (they don&#039;t use DNS SRV to locate your edge server, though yours will use it to locate theirs). All this involves setup and maintenance costs, which is the primary reason why it isn&#039;t free.</description>
		<content:encoded><![CDATA[<p>OCS federates directly to the PIC providers so that the link is secured by TLS. Various providers have various kinds of servers on the other end, all of which somehow look like an OCS edge server. The provisioning process involves each PIC provider adding your organization&#8217;s domain and edge server FQDN to their list of federated partners (they don&#8217;t use DNS SRV to locate your edge server, though yours will use it to locate theirs). All this involves setup and maintenance costs, which is the primary reason why it isn&#8217;t free.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

