<?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 178: Nearly 2 Years after HP Buys 3Com for $2.7B, It Has Very Little to Show for IT: Can HP Make It in Networking?</title>
	<atom:link href="http://lippisreport.com/2011/09/lippis-report-178-nearly-2-years-after-hp-buys-3com-for-2-7b-it-has-very-little-to-show-for-it-can-hp-make-it-in-networking/feed/" rel="self" type="application/rss+xml" />
	<link>http://lippisreport.com/2011/09/lippis-report-178-nearly-2-years-after-hp-buys-3com-for-2-7b-it-has-very-little-to-show-for-it-can-hp-make-it-in-networking/</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: Chris</title>
		<link>http://lippisreport.com/2011/09/lippis-report-178-nearly-2-years-after-hp-buys-3com-for-2-7b-it-has-very-little-to-show-for-it-can-hp-make-it-in-networking/comment-page-1/#comment-398860</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 16 Dec 2011 21:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=5216#comment-398860</guid>
		<description>Sorry guys, but H3C is not just a fellower on networking market. Netgear, Avaya, Foundry, Extreme, Enterasys, those are real fellowers.

Have you ever looked at H3C´s data sheets? Look at the functionality, look at the supported networking protocols. And then you will see, that it is not H3C that has to fear about Cisco...</description>
		<content:encoded><![CDATA[<p>Sorry guys, but H3C is not just a fellower on networking market. Netgear, Avaya, Foundry, Extreme, Enterasys, those are real fellowers.</p>
<p>Have you ever looked at H3C´s data sheets? Look at the functionality, look at the supported networking protocols. And then you will see, that it is not H3C that has to fear about Cisco&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

