<?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: Introducing VXLAN</title>
	<atom:link href="http://blogs.cisco.com/datacenter/introducing-vxlan/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.cisco.com/datacenter/introducing-vxlan/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 07:30:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Container shipping and virtualisation - a potent analogy &#124; www.vExperienced.co.uk</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-370495</link>
		<dc:creator>Container shipping and virtualisation - a potent analogy &#124; www.vExperienced.co.uk</dc:creator>
		<pubDate>Mon, 31 Oct 2011 16:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-370495</guid>
		<description><![CDATA[[...] for example). Despite ongoing innovation in the network space (new models such as Openflow , VXLAN/NVGRE, and innovative vendors such as Xsigo, Arista etc) it&#8217;s largely the economics of [...]]]></description>
		<content:encoded><![CDATA[<p>[...] for example). Despite ongoing innovation in the network space (new models such as Openflow , VXLAN/NVGRE, and innovative vendors such as Xsigo, Arista etc) it&#8217;s largely the economics of [...]
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',370495)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-370495">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vmDK &#187; ProfessionalVMware.com Brownbag recap, week of October 31st, 2011</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-370346</link>
		<dc:creator>vmDK &#187; ProfessionalVMware.com Brownbag recap, week of October 31st, 2011</dc:creator>
		<pubDate>Mon, 31 Oct 2011 14:19:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-370346</guid>
		<description><![CDATA[[...] submitted a joint proposal to the IETF to have the VXLAN technology standardized. &#8211; &#8220;Introducing VXLAN&#8220;, Omar Sultan, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] submitted a joint proposal to the IETF to have the VXLAN technology standardized. &#8211; &#8220;Introducing VXLAN&#8220;, Omar Sultan, [...]
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',370346)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-370346">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Earl</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-250282</link>
		<dc:creator>Earl</dc:creator>
		<pubDate>Fri, 23 Sep 2011 14:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-250282</guid>
		<description><![CDATA[Omar
Interesting piece. How does another protocol hack fix the virtualization issue.  Don&#039;t we already have GRE Tunnels?
Why not just go with OpenFlow?]]></description>
		<content:encoded><![CDATA[<p>Omar<br />
Interesting piece. How does another protocol hack fix the virtualization issue.  Don&#8217;t we already have GRE Tunnels?<br />
Why not just go with OpenFlow?
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',250282)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-250282">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Show notes: Episode 41, VMworld Roundup &#171; APAC Virtualization Podcast</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-229239</link>
		<dc:creator>Show notes: Episode 41, VMworld Roundup &#171; APAC Virtualization Podcast</dc:creator>
		<pubDate>Wed, 14 Sep 2011 12:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-229239</guid>
		<description><![CDATA[[...] information from Cisco Citrix and [...]]]></description>
		<content:encoded><![CDATA[<p>[...] information from Cisco Citrix and [...]
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',229239)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-229239">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-211987</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Tue, 06 Sep 2011 19:05:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-211987</guid>
		<description><![CDATA[How does adding in a 24-bit header via software impact the server&#039;s CPU &amp; memory utilization?  Nexus 1000V already consumes 15-25% of available resources just for switching, so how does adding in the network ID impact these resources?]]></description>
		<content:encoded><![CDATA[<p>How does adding in a 24-bit header via software impact the server&#8217;s CPU &amp; memory utilization?  Nexus 1000V already consumes 15-25% of available resources just for switching, so how does adding in the network ID impact these resources?
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',211987)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-211987">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Huynh</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-209776</link>
		<dc:creator>Rick Huynh</dc:creator>
		<pubDate>Mon, 05 Sep 2011 06:05:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-209776</guid>
		<description><![CDATA[I am glad to see that the demands of virtualization and cloud computing are pushing the boundaries of legacy networks and companies like Cisco and VMware continue to innovate and evolve the network.]]></description>
		<content:encoded><![CDATA[<p>I am glad to see that the demands of virtualization and cloud computing are pushing the boundaries of legacy networks and companies like Cisco and VMware continue to innovate and evolve the network.
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',209776)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-209776">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cam</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-205306</link>
		<dc:creator>Cam</dc:creator>
		<pubDate>Fri, 02 Sep 2011 20:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-205306</guid>
		<description><![CDATA[Hi Omar,

Interesting technology.  Maybe you can answer a couple of quick question that have been bugging me since I read the white paper:

1.  What is the benefit of VxLAN over the older MAC in MAC tunneling that Vmware already has? (presumably, I can use OTV to extend that over the WAN, so what does this buy me?)

2.  It appears that the MAC encapsulation/de-encapsulation happens in the 1000V.  Are there other switches or devices that will also perform the encapsulation or de-encapsulation....such as the Nexus 5000/7000....or is this just a VM to VM protocol (like the MAC in MAC stuff)

3.  If this is truly an open standard intended for multi-vendor solutions, is the Vswitch API that Cisco gets from Vmware open to everyone?  Last I heard it was not, in which case this is specifically a Vmware/Cisco proprietary solution for the foreseable future.

4.  Does Cisco have products that will support me tunneling to bare metal servers or other hypervisors such as HyperV, Xen, or KVM?  If so, when will we see those?

Thanks a ton for clearly articulating why traditional networking equipment and approaches are no longer valid for Virtualized Datacenter. We at Xsigo have been saying that for a long time.

Looking forward to your answers.

Regards]]></description>
		<content:encoded><![CDATA[<p>Hi Omar,</p>
<p>Interesting technology.  Maybe you can answer a couple of quick question that have been bugging me since I read the white paper:</p>
<p>1.  What is the benefit of VxLAN over the older MAC in MAC tunneling that Vmware already has? (presumably, I can use OTV to extend that over the WAN, so what does this buy me?)</p>
<p>2.  It appears that the MAC encapsulation/de-encapsulation happens in the 1000V.  Are there other switches or devices that will also perform the encapsulation or de-encapsulation&#8230;.such as the Nexus 5000/7000&#8230;.or is this just a VM to VM protocol (like the MAC in MAC stuff)</p>
<p>3.  If this is truly an open standard intended for multi-vendor solutions, is the Vswitch API that Cisco gets from Vmware open to everyone?  Last I heard it was not, in which case this is specifically a Vmware/Cisco proprietary solution for the foreseable future.</p>
<p>4.  Does Cisco have products that will support me tunneling to bare metal servers or other hypervisors such as HyperV, Xen, or KVM?  If so, when will we see those?</p>
<p>Thanks a ton for clearly articulating why traditional networking equipment and approaches are no longer valid for Virtualized Datacenter. We at Xsigo have been saying that for a long time.</p>
<p>Looking forward to your answers.</p>
<p>Regards
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',205306)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-205306">2</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Jagger (@StefanJagger)</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-203227</link>
		<dc:creator>Stefan Jagger (@StefanJagger)</dc:creator>
		<pubDate>Wed, 31 Aug 2011 18:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-203227</guid>
		<description><![CDATA[This is from: http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-685115.html

VXLAN is intended for creating more logical networks in a cloud environment. Overlay Transport Virtualization (OTV) while using similar frame format as VXLAN, is a data center interconnect technology extending Layer 2 domains to different data centers over Layer-3. Unlike VXLAN, OTV has simpler deployment requirements since it does not mandate multicast-enabled transport network. Locator ID Separation Protocol (LISP) goes a step further by providing IP address mobility between data centers with dynamic routing updates. While VXLAN, OTV, and LISP may share similar frame format, they serve very different networking purposes and are hence complimentary to each other.]]></description>
		<content:encoded><![CDATA[<p>This is from: <a href="http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-685115.html" rel="nofollow">http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-685115.html</a></p>
<p>VXLAN is intended for creating more logical networks in a cloud environment. Overlay Transport Virtualization (OTV) while using similar frame format as VXLAN, is a data center interconnect technology extending Layer 2 domains to different data centers over Layer-3. Unlike VXLAN, OTV has simpler deployment requirements since it does not mandate multicast-enabled transport network. Locator ID Separation Protocol (LISP) goes a step further by providing IP address mobility between data centers with dynamic routing updates. While VXLAN, OTV, and LISP may share similar frame format, they serve very different networking purposes and are hence complimentary to each other.
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',203227)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-203227">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank D'Agostino</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-202723</link>
		<dc:creator>Frank D'Agostino</dc:creator>
		<pubDate>Wed, 31 Aug 2011 00:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-202723</guid>
		<description><![CDATA[Omar, great article.  It is fantastic to see the industry acknowledge that legacy network model for data centers no longer meet the requirements for enterprises and providers.  This will improve opportunities for everyone in the industry.]]></description>
		<content:encoded><![CDATA[<p>Omar, great article.  It is fantastic to see the industry acknowledge that legacy network model for data centers no longer meet the requirements for enterprises and providers.  This will improve opportunities for everyone in the industry.
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',202723)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-202723">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VLAN limit and the VXLAN proposal. &#171; Reggle</title>
		<link>http://blogs.cisco.com/datacenter/introducing-vxlan/#comment-202515</link>
		<dc:creator>VLAN limit and the VXLAN proposal. &#171; Reggle</dc:creator>
		<pubDate>Tue, 30 Aug 2011 20:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=41087#comment-202515</guid>
		<description><![CDATA[[...] proposes a new kind of network topology in data centers (thanks to Omar Sultan for the link on his blog). It&#8217;s four days old (at the time of writing) and is proposed by some mayor players in the [...]]]></description>
		<content:encoded><![CDATA[<p>[...] proposes a new kind of network topology in data centers (thanks to Omar Sultan for the link on his blog). It&#8217;s four days old (at the time of writing) and is proposed by some mayor players in the [...]
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',202515)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-202515">0</span> likes</p>
]]></content:encoded>
	</item>
</channel>
</rss>
