<?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: AireSpace in Stratosphere</title>
	<atom:link href="http://gigaom.com/2005/01/05/airespace-in-stratosphere/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2005/01/05/airespace-in-stratosphere/</link>
	<description>Trusted Insights and Conversations on the Next Wave of Technology</description>
	<lastBuildDate>Thu, 26 Nov 2009 03:26:30 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wi-Fi Networking News</title>
		<link>http://gigaom.com/2005/01/05/airespace-in-stratosphere/#comment-5317</link>
		<dc:creator>Wi-Fi Networking News</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/01/05/airespace-in-stratosphere/#comment-5317</guid>
		<description>&lt;p&gt;&lt;strong&gt;Cisco May Buy Airespace&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt; I&#8217;ve been saying it for months and months: It&#8217;s been crystal clear to me that Cisco did not have an internal WLAN switch strategy, and has its biggest problems in dealing with issues that switches can solve, which is policy-based VLAN assignment for&#8230; &lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>Cisco May Buy Airespace</strong></p>

<p> I&#8217;ve been saying it for months and months: It&#8217;s been crystal clear to me that Cisco did not have an internal WLAN switch strategy, and has its biggest problems in dealing with issues that switches can solve, which is policy-based VLAN assignment for&#8230; </p>]]></content:encoded>
	</item>
</channel>
</rss>
