<?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: Equinix &#8211; Proxy for the Internet</title>
	<atom:link href="http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/</link>
	<description>More Signal. Less Noise.</description>
	<lastBuildDate>Thu, 02 Apr 2009 12:29:57 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Charlie Brown</title>
		<link>http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1583</link>
		<dc:creator>Charlie Brown</dc:creator>
		<pubDate>Tue, 04 Dec 2007 08:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1583</guid>
		<description>So one thing that is not mentioned here, and rarely in discussions of large data centers is that of supplied power per customer.  20A per rack really doesn&#039;t cut it for big routers these days.  If I have to purchase large equipment such as Cisco CRS multi-chassis devices, I have to buy an inordinately large amount of space just to get the power to plug this &#039;single&#039; device into, and even then, large colo facilities don&#039;t like it.  As power consumption for high bandwidth backbone gear, whether housing SoNET/SDH or Ethernet interfaces grows, this problem will get bigger.  30MW sounds impressive, but if one customer can only get 2-4kW per cage, is that very efficient use of space and HVAC?</description>
		<content:encoded><![CDATA[<p>So one thing that is not mentioned here, and rarely in discussions of large data centers is that of supplied power per customer.  20A per rack really doesn&#8217;t cut it for big routers these days.  If I have to purchase large equipment such as Cisco CRS multi-chassis devices, I have to buy an inordinately large amount of space just to get the power to plug this &#8217;single&#8217; device into, and even then, large colo facilities don&#8217;t like it.  As power consumption for high bandwidth backbone gear, whether housing SoNET/SDH or Ethernet interfaces grows, this problem will get bigger.  30MW sounds impressive, but if one customer can only get 2-4kW per cage, is that very efficient use of space and HVAC?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Coluccio</title>
		<link>http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1579</link>
		<dc:creator>Frank Coluccio</dc:creator>
		<pubDate>Fri, 09 Nov 2007 21:37:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1579</guid>
		<description>I think if you look at research networks such as SURFnet6 of The Netherlands, two years ago, and a growing number of networks on NLR , along with the upsurge in MPLS and now Carrier Ethernet transport options (PBT, e.g.), and then look at how many large corporates are now outfitting their private (dark-fiber) networks at L2, you&#039;ll find that the trend in collapsing Layer 3 down to L1 wavelengths and L2 Ethernet is already well along. Why did we have, and why do we continue to maintain, so many hierarchical instances of routers where they are not really needed in the first place? I chalk this phenomenon up to an absolutely superb selling job by those who brought us &quot;The New World Network&quot; template (consisting of four layers of routing in every node building _and _ service provider location) about eight to ten years ago, as one reason. Also, a greater familiarity with IP, which accounted for the new kids on the block remaining comfortable with routers, and not just a touch of bellhead vs. nethead bigotry, too, I&#039;m sure.</description>
		<content:encoded><![CDATA[<p>I think if you look at research networks such as SURFnet6 of The Netherlands, two years ago, and a growing number of networks on NLR , along with the upsurge in MPLS and now Carrier Ethernet transport options (PBT, e.g.), and then look at how many large corporates are now outfitting their private (dark-fiber) networks at L2, you&#8217;ll find that the trend in collapsing Layer 3 down to L1 wavelengths and L2 Ethernet is already well along. Why did we have, and why do we continue to maintain, so many hierarchical instances of routers where they are not really needed in the first place? I chalk this phenomenon up to an absolutely superb selling job by those who brought us &#8220;The New World Network&#8221; template (consisting of four layers of routing in every node building _and _ service provider location) about eight to ten years ago, as one reason. Also, a greater familiarity with IP, which accounted for the new kids on the block remaining comfortable with routers, and not just a touch of bellhead vs. nethead bigotry, too, I&#8217;m sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why I didn&#8217;t like Transport Gear Markets before and like them less now &#171; Iain&#8217;s Chips &#38; Tech</title>
		<link>http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1580</link>
		<dc:creator>Why I didn&#8217;t like Transport Gear Markets before and like them less now &#171; Iain&#8217;s Chips &#38; Tech</dc:creator>
		<pubDate>Fri, 09 Nov 2007 19:25:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1580</guid>
		<description>[...] am I saying this today? As usual I was inspired by a recent Andrew@Nyquist post. Today it is was on Equinix and Datacenters. The discussion is on transport, but it reminded me that transport is a supporting function of a [...]</description>
		<content:encoded><![CDATA[<p>[...] am I saying this today? As usual I was inspired by a recent Andrew@Nyquist post. Today it is was on Equinix and Datacenters. The discussion is on transport, but it reminded me that transport is a supporting function of a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iain Verigin</title>
		<link>http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1581</link>
		<dc:creator>Iain Verigin</dc:creator>
		<pubDate>Fri, 09 Nov 2007 18:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1581</guid>
		<description>Interesting.  the inter-play between transport (L1), switching (L2), and routing (L3), and &quot;services&quot; (multiple layer) boxes is always confusing and the &quot;beauty is in the eye of beholder&quot; ( ie the network designer/user )

I&#039;ve always wondered why option 2 hasn&#039;t been used more often.  The L2/L3 switch industry has made very little in-roads on this this ( they are mainly deployed as L2 boxes ).  Big routers continue to sell well.  It&#039;s been happending for a while, too. Over 5 years ago I visited a major Canadian cable providers datacenter that was built like option 2.  It consisted of one GSR, lots of low-end Cisco switches, and a backbone consisting of Extreme black diamond Modular Switches.  It covered a huge geographic region -- all of Alberta and BC.  But not a big population.  One reason I believed they could get away with this was that they owned the whole network.

It seems like transport is only required to support the &quot;data-center&quot;.  The &quot;end-customers&quot; money comes from services and connections to routers.  Thus the good equipment business continues to be routers and services boxes.  The transport gear is not directly revenue generating ( which does not bode well for it ).

On the Cisco front.  I&#039;ve found it interesting that they dominate everything above L1.  There are notable chinks in the armour with F5, JNPR, etc.  But they still dominate the revenue generating &quot;functions&quot; and look to continue.</description>
		<content:encoded><![CDATA[<p>Interesting.  the inter-play between transport (L1), switching (L2), and routing (L3), and &#8220;services&#8221; (multiple layer) boxes is always confusing and the &#8220;beauty is in the eye of beholder&#8221; ( ie the network designer/user )</p>
<p>I&#8217;ve always wondered why option 2 hasn&#8217;t been used more often.  The L2/L3 switch industry has made very little in-roads on this this ( they are mainly deployed as L2 boxes ).  Big routers continue to sell well.  It&#8217;s been happending for a while, too. Over 5 years ago I visited a major Canadian cable providers datacenter that was built like option 2.  It consisted of one GSR, lots of low-end Cisco switches, and a backbone consisting of Extreme black diamond Modular Switches.  It covered a huge geographic region &#8212; all of Alberta and BC.  But not a big population.  One reason I believed they could get away with this was that they owned the whole network.</p>
<p>It seems like transport is only required to support the &#8220;data-center&#8221;.  The &#8220;end-customers&#8221; money comes from services and connections to routers.  Thus the good equipment business continues to be routers and services boxes.  The transport gear is not directly revenue generating ( which does not bode well for it ).</p>
<p>On the Cisco front.  I&#8217;ve found it interesting that they dominate everything above L1.  There are notable chinks in the armour with F5, JNPR, etc.  But they still dominate the revenue generating &#8220;functions&#8221; and look to continue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Baker</title>
		<link>http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1582</link>
		<dc:creator>Bill Baker</dc:creator>
		<pubDate>Thu, 08 Nov 2007 00:20:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.nyquistcapital.com/2007/11/06/equinix-proxy-for-the-internet/#comment-1582</guid>
		<description>Thanks for another insightful analysis. I always felt that Cisco’s vulnerability lies with solution #2. If I can switch at cheap L2 prices why do I need expensive routers. Off-loading is the way to go.</description>
		<content:encoded><![CDATA[<p>Thanks for another insightful analysis. I always felt that Cisco’s vulnerability lies with solution #2. If I can switch at cheap L2 prices why do I need expensive routers. Off-loading is the way to go.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
