<?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: Verizon shows off OpenFlow&#8217;s benefits for carriers</title>
	<atom:link href="http://gigaom.com/2012/04/17/verizon-shows-off-openflows-benefits-for-carriers/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/04/17/verizon-shows-off-openflows-benefits-for-carriers/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 16:50:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: perttik</title>
		<link>http://gigaom.com/2012/04/17/verizon-shows-off-openflows-benefits-for-carriers/#comment-833978</link>
		<dc:creator><![CDATA[perttik]]></dc:creator>
		<pubDate>Tue, 24 Apr 2012 00:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=511628#comment-833978</guid>
		<description><![CDATA[The way I understand this is that with OpenFlow you have one programming language/API that can talk to any number of routers from different manufacturers, rather than each router/manufacturer having its own API/Firmware.  Lingua Franca, if you will...  This way a whole bunch of routers can be managed from one place, which helps tremendously when dealing with changing network landscapes and infrastructures, VM&#039;s that spin up and down, traffic prioritization for certain events/time frames, etc.]]></description>
		<content:encoded><![CDATA[<p>The way I understand this is that with OpenFlow you have one programming language/API that can talk to any number of routers from different manufacturers, rather than each router/manufacturer having its own API/Firmware.  Lingua Franca, if you will&#8230;  This way a whole bunch of routers can be managed from one place, which helps tremendously when dealing with changing network landscapes and infrastructures, VM&#8217;s that spin up and down, traffic prioritization for certain events/time frames, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Mackey</title>
		<link>http://gigaom.com/2012/04/17/verizon-shows-off-openflows-benefits-for-carriers/#comment-831378</link>
		<dc:creator><![CDATA[Dave Mackey]]></dc:creator>
		<pubDate>Tue, 17 Apr 2012 21:56:37 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=511628#comment-831378</guid>
		<description><![CDATA[I&#039;m a bit embarrassed to admit it, but I&#039;m still not entirely understanding what OpenFlow is all about...sure, sure, I&#039;ve heard the buzz words, but how exactly is it going to simplify things?]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m a bit embarrassed to admit it, but I&#8217;m still not entirely understanding what OpenFlow is all about&#8230;sure, sure, I&#8217;ve heard the buzz words, but how exactly is it going to simplify things?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
