<?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: Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Before It Started</title>
	<atom:link href="http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/feed/" rel="self" type="application/rss+xml" />
	<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/</link>
	<description>Resources for Network / IT Business Decision Makers</description>
	<lastBuildDate>Tue, 22 May 2012 00:38:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Tristan Mundy</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-456765</link>
		<dc:creator>Tristan Mundy</dc:creator>
		<pubDate>Tue, 20 Mar 2012 05:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-456765</guid>
		<description>This is one awesome blog.Really getting excited about read more. Really Great.</description>
		<content:encoded><![CDATA[<p>This is one awesome blog.Really getting excited about read more. Really Great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aimee Ahmad</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-455311</link>
		<dc:creator>Aimee Ahmad</dc:creator>
		<pubDate>Sat, 17 Mar 2012 09:39:35 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-455311</guid>
		<description>Great post.Thanks Again. Much obliged.</description>
		<content:encoded><![CDATA[<p>Great post.Thanks Again. Much obliged.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lai Debray</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-252898</link>
		<dc:creator>Lai Debray</dc:creator>
		<pubDate>Mon, 17 Jan 2011 21:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-252898</guid>
		<description>The article is in reality the excellent on this worthy topic. I slot in collectively together with your conclusions and looking forward to your coming updates. Just saying many thanks is not going to simply be enough, for that implausible clarity inside your writing. I&#039;ve grabbed your rss feed to stay informed of any updates. Gratifying job and quite a bit success in your organization dealings!</description>
		<content:encoded><![CDATA[<p>The article is in reality the excellent on this worthy topic. I slot in collectively together with your conclusions and looking forward to your coming updates. Just saying many thanks is not going to simply be enough, for that implausible clarity inside your writing. I&#8217;ve grabbed your rss feed to stay informed of any updates. Gratifying job and quite a bit success in your organization dealings!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Lippis</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-206558</link>
		<dc:creator>Nick Lippis</dc:creator>
		<pubDate>Mon, 26 Jul 2010 19:34:57 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-206558</guid>
		<description>Jeffery and Marty,

Thank you for your comments and thoughts.  We are in agreement on the need for interoperability in the UC market.  In fact, I believe that the UC address market will expand when the type of UC interoperability that Marty discusses in his post is realized.  Were we differ is on how the industry delivers it.  Without Cisco, Avaya, ShoreTel, Mitel, NEC et in the UCIF it will have marginal impact.  The trade show Interop provided a great gathering place and demonstration of TCP/IP interoperability.  The UC industry needs such an interoperability platform.

Nick</description>
		<content:encoded><![CDATA[<p>Jeffery and Marty,</p>
<p>Thank you for your comments and thoughts.  We are in agreement on the need for interoperability in the UC market.  In fact, I believe that the UC address market will expand when the type of UC interoperability that Marty discusses in his post is realized.  Were we differ is on how the industry delivers it.  Without Cisco, Avaya, ShoreTel, Mitel, NEC et in the UCIF it will have marginal impact.  The trade show Interop provided a great gathering place and demonstration of TCP/IP interoperability.  The UC industry needs such an interoperability platform.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sagemcom</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-205766</link>
		<dc:creator>Sagemcom</dc:creator>
		<pubDate>Tue, 20 Jul 2010 15:05:57 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-205766</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;RT @Nicklippis: Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Before It Started http://bit.ly/9fnyiB&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @Nicklippis: Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Before It Started <a href="http://bit.ly/9fnyiB" rel="nofollow">http://bit.ly/9fnyiB</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Lippis</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-205732</link>
		<dc:creator>Nick Lippis</dc:creator>
		<pubDate>Tue, 20 Jul 2010 07:56:18 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-205732</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Before It Started http://bit.ly/9fnyiB&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Before It Started <a href="http://bit.ly/9fnyiB" rel="nofollow">http://bit.ly/9fnyiB</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marty Parker</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-204958</link>
		<dc:creator>Marty Parker</dc:creator>
		<pubDate>Wed, 14 Jul 2010 20:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-204958</guid>
		<description>Thanks, for the perspective, Nick, but what we need in the Unified Communications industry is interoperatbility at more basic levels, starting with inter-system federation for presence, IM and peer-to-peer text and voice communcations.  

For example, if a company with Microsoft Office Communications Server to support their desktops and mobile devices has a partner or client using, say, Avaya one-X to support their desktops and mobile devices, they want to be able to communicate across organization boundaries effectively and economically.  

If some media translation has to happen at the edges, that&#039;s each vendor&#039;s accountability; and if some vendor&#039;s translations are too costly, that vendor will be pressured to conform, or lower the price.   

As to video interoperation, Jeffrey Rodman (CTO of Polycom) pretty well says it in his post.  But with the bandwidth loads of video, most businesses will prefer to solve problems at the IM, text (e-mail) and voice bandwidth levels if they can.  

In any case, those who choose not to join every possible interoperability forum are missing out on opportunities to serve a broader market than just their existing customer base.</description>
		<content:encoded><![CDATA[<p>Thanks, for the perspective, Nick, but what we need in the Unified Communications industry is interoperatbility at more basic levels, starting with inter-system federation for presence, IM and peer-to-peer text and voice communcations.  </p>
<p>For example, if a company with Microsoft Office Communications Server to support their desktops and mobile devices has a partner or client using, say, Avaya one-X to support their desktops and mobile devices, they want to be able to communicate across organization boundaries effectively and economically.  </p>
<p>If some media translation has to happen at the edges, that&#8217;s each vendor&#8217;s accountability; and if some vendor&#8217;s translations are too costly, that vendor will be pressured to conform, or lower the price.   </p>
<p>As to video interoperation, Jeffrey Rodman (CTO of Polycom) pretty well says it in his post.  But with the bandwidth loads of video, most businesses will prefer to solve problems at the IM, text (e-mail) and voice bandwidth levels if they can.  </p>
<p>In any case, those who choose not to join every possible interoperability forum are missing out on opportunities to serve a broader market than just their existing customer base.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeffreyrodman</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-204931</link>
		<dc:creator>jeffreyrodman</dc:creator>
		<pubDate>Wed, 14 Jul 2010 15:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-204931</guid>
		<description>The assertion that &quot;UCIF is controlled by Microsoft&quot; is apparently flavored by some past history having nothing to do with UCIF, but actually has no factual basis.  UCIF was founded by five companies, not one (HP, Juniper, Lifesize/Logitech, my own, Polycom, and Microsoft); each has only one vote on the Board of Directors, and there are currently over twenty active members, growing rapidly.  The purpose of UCIF is to achieve precisely the goals described in this article - interoperability, establishment of connection among platforms and across networks.  Given that the UCIF is fundamentally open and democratic, welcomes all UC vendors whether hardware, software, services, carrier or network, and already has a strong and broad membership, the best path forward for the industry is not to &quot;dissolve&quot; this existing, viable and vibrant collaboration, but to encourage non-members to transform their ongoing discussions (of which there are many) into active membership, and make their voices, and influences, felt.  We welcome, and need, their participation.</description>
		<content:encoded><![CDATA[<p>The assertion that &#8220;UCIF is controlled by Microsoft&#8221; is apparently flavored by some past history having nothing to do with UCIF, but actually has no factual basis.  UCIF was founded by five companies, not one (HP, Juniper, Lifesize/Logitech, my own, Polycom, and Microsoft); each has only one vote on the Board of Directors, and there are currently over twenty active members, growing rapidly.  The purpose of UCIF is to achieve precisely the goals described in this article &#8211; interoperability, establishment of connection among platforms and across networks.  Given that the UCIF is fundamentally open and democratic, welcomes all UC vendors whether hardware, software, services, carrier or network, and already has a strong and broad membership, the best path forward for the industry is not to &#8220;dissolve&#8221; this existing, viable and vibrant collaboration, but to encourage non-members to transform their ongoing discussions (of which there are many) into active membership, and make their voices, and influences, felt.  We welcome, and need, their participation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denis Du Bois</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-204922</link>
		<dc:creator>Denis Du Bois</dc:creator>
		<pubDate>Wed, 14 Jul 2010 14:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-204922</guid>
		<description>@P5Group RT @nicklippis: How Microsoft Killed The Unified Communications Interoperability Forum Before It Started http://bit.ly/9ByqJj</description>
		<content:encoded><![CDATA[<p>@P5Group RT @nicklippis: How Microsoft Killed The Unified Communications Interoperability Forum Before It Started <a href="http://bit.ly/9ByqJj" rel="nofollow">http://bit.ly/9ByqJj</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silje Ingvoldstad</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-204883</link>
		<dc:creator>Silje Ingvoldstad</dc:creator>
		<pubDate>Wed, 14 Jul 2010 07:36:16 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-204883</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;RT @nicklippis: Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Before It http://is.gd/dqYJE&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @nicklippis: Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Before It <a href="http://is.gd/dqYJE" rel="nofollow">http://is.gd/dqYJE</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Network Gang</title>
		<link>http://lippisreport.com/2010/07/lippis-report-152-how-microsoft-killed-the-unified-communications-interoperability-forum-before-it-started/comment-page-1/#comment-204871</link>
		<dc:creator>The Network Gang</dc:creator>
		<pubDate>Wed, 14 Jul 2010 04:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3247#comment-204871</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;#Networks Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Be.. http://bit.ly/9ByqJj&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">#Networks Lippis Report 152: How Microsoft Killed The Unified Communications Interoperability Forum Be.. <a href="http://bit.ly/9ByqJj" rel="nofollow">http://bit.ly/9ByqJj</a></span></span></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

