<?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: Cisco Debuts &#8216;EnergyWise&#8217; Power Management Tool</title>
	<atom:link href="http://www.environmentalleader.com/2009/01/29/cisco-debuts-energywise-power-management-tool/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.environmentalleader.com/2009/01/29/cisco-debuts-energywise-power-management-tool/</link>
	<description>The Executive's Daily Green Briefing</description>
	<lastBuildDate>Sat, 21 Nov 2009 02:27:50 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tony Rybczynski Nortel</title>
		<link>http://www.environmentalleader.com/2009/01/29/cisco-debuts-energywise-power-management-tool/comment-page-1/#comment-105989</link>
		<dc:creator>Tony Rybczynski Nortel</dc:creator>
		<pubDate>Fri, 30 Jan 2009 12:53:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.environmentalleader.com/2009/01/29/cisco-debuts-energywise-power-management-tool/#comment-105989</guid>
		<description>Three problems with EnergyWise: 1. security exposures; 2. an application bottleneck; 3. doesn’t eliminate the Cisco Energy Tax. See
http://blog.tmcnet.com/the-hyperconnected-enterprise/green-it/energywise-doesnt-make-cisco-switches-any-greener.asp</description>
		<content:encoded><![CDATA[<p>Three problems with EnergyWise: 1. security exposures; 2. an application bottleneck; 3. doesn’t eliminate the Cisco Energy Tax. See<br />
<a href="http://blog.tmcnet.com/the-hyperconnected-enterprise/green-it/energywise-doesnt-make-cisco-switches-any-greener.asp" rel="nofollow">http://blog.tmcnet.com/the-hyperconnected-enterprise/green-it/energywise-doesnt-make-cisco-switches-any-greener.asp</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
