<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Rethinking out loud about infrastructure</title>
	<atom:link href="http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/</link>
	<description>Same old blog, brand new place</description>
	<lastBuildDate>Sat, 28 Nov 2009 21:14:31 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Doc Searls Weblog &#183; Stimulus Bill Qs</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-129892</link>
		<dc:creator>Doc Searls Weblog &#183; Stimulus Bill Qs</dc:creator>
		<pubDate>Thu, 12 Feb 2009 17:06:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-129892</guid>
		<description>[...] Bonus link. Comments included. [...]</description>
		<content:encoded><![CDATA[<p>[...] Bonus link. Comments included. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; Amsterdam blogging - Dec &#8216;08</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-112149</link>
		<dc:creator>Marc&#8217;s Voice &#187; Blog Archive &#187; Amsterdam blogging - Dec &#8216;08</dc:creator>
		<pubDate>Sat, 13 Dec 2008 03:24:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-112149</guid>
		<description>[...] Doc is rethinking out loud about infrastructure [...]</description>
		<content:encoded><![CDATA[<p>[...] Doc is rethinking out loud about infrastructure [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Warot</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-111475</link>
		<dc:creator>Mike Warot</dc:creator>
		<pubDate>Tue, 09 Dec 2008 17:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-111475</guid>
		<description>The nice thing about the InterNetwork is that you can always patch around a hole in the existing network. It would be nice if you didn&#039;t have to manually do it, though.</description>
		<content:encoded><![CDATA[<p>The nice thing about the InterNetwork is that you can always patch around a hole in the existing network. It would be nice if you didn&#8217;t have to manually do it, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc Searls</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-111468</link>
		<dc:creator>Doc Searls</dc:creator>
		<pubDate>Tue, 09 Dec 2008 16:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-111468</guid>
		<description>Quick question for the panel from the floor at LeWeb in Paris: would you call the Internet &quot;&lt;i&gt;inter&lt;/i&gt;structure&quot;?</description>
		<content:encoded><![CDATA[<p>Quick question for the panel from the floor at LeWeb in Paris: would you call the Internet &#8220;<i>inter</i>structure&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Bennett</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-111341</link>
		<dc:creator>Richard Bennett</dc:creator>
		<pubDate>Mon, 08 Dec 2008 21:35:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-111341</guid>
		<description>It&#039;s silly to build an infrastructure on the assumption that no traffic shaping is needed, and in fact everything we know about network design says that networks in which there is no delay ever need to constrain endpoint access speed to make that happen. This is how you build a telephone network, not how you build a computer network.</description>
		<content:encoded><![CDATA[<p>It&#8217;s silly to build an infrastructure on the assumption that no traffic shaping is needed, and in fact everything we know about network design says that networks in which there is no delay ever need to constrain endpoint access speed to make that happen. This is how you build a telephone network, not how you build a computer network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Warot</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-111315</link>
		<dc:creator>Mike Warot</dc:creator>
		<pubDate>Mon, 08 Dec 2008 16:54:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-111315</guid>
		<description>The basic problem with infrastructure is it&#039;s the last thing in the world you want to have to update rapidly, because of it&#039;s massive scope.

If we could put bundles of single mode fiber everywhere, and only worry about the ends of the fibers, that would greatly help.

Because we can&#039;t get a do-over ever 2 years, we should design the system with at least 2 pair to every home, business, apartment, etc.

The base system requirement should be 1 Gbps full duplex per pair.

We have to assume that the ends can take care of their own filtering, etc... and NOT try to bake it into the infrastructure.</description>
		<content:encoded><![CDATA[<p>The basic problem with infrastructure is it&#8217;s the last thing in the world you want to have to update rapidly, because of it&#8217;s massive scope.</p>
<p>If we could put bundles of single mode fiber everywhere, and only worry about the ends of the fibers, that would greatly help.</p>
<p>Because we can&#8217;t get a do-over ever 2 years, we should design the system with at least 2 pair to every home, business, apartment, etc.</p>
<p>The base system requirement should be 1 Gbps full duplex per pair.</p>
<p>We have to assume that the ends can take care of their own filtering, etc&#8230; and NOT try to bake it into the infrastructure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Marti</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-111298</link>
		<dc:creator>Don Marti</dc:creator>
		<pubDate>Mon, 08 Dec 2008 14:19:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-111298</guid>
		<description>One more fun one: Homes With Tails
http://www.newamerica.net/publications/policy/homes_tails</description>
		<content:encoded><![CDATA[<p>One more fun one: Homes With Tails<br />
<a href="http://www.newamerica.net/publications/policy/homes_tails" rel="nofollow">http://www.newamerica.net/publications/policy/homes_tails</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Bennett</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-111282</link>
		<dc:creator>Richard Bennett</dc:creator>
		<pubDate>Mon, 08 Dec 2008 11:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-111282</guid>
		<description>Time-travel a caveman into modern America and he&#039;ll be amazed at our transportation system. Send him back and he&#039;d tell his buddies something like: &quot;they have things called bus stations, train stations, and airports where you walk inside very clean cave and sit on this thing called a seat. You tie yourself down in this chair thing and it takes you far away. When you leave the cave you&#039;re in a totally different place. Dudes, it&#039;s magic.&quot; Many descriptions of the Internet infrastructure are like that. 

It&#039;s really a communications system, and unlike other communications systems it&#039;s made of diverse elements: fat things like Ethernets, SONETs, ATMs, and odd things like FiOSes, DOCSISes, DSLs, WiMaxes, and Wi-Fis. It doesn&#039;t seem like these things could all be part of a unified system, but they are. And unlike other communications systems that go to great lengths to ensure they provide predictable and invariant service, the Internet has a wierd attitude toward overuse and overload: it says &quot;bring it on, I can handle myself no matter what you do to me.&quot; 

This is what makes the economics of Internetting so brilliant. If we&#039;re willing to give up a little predictability, we can generally have great service for very little money. As more uses migrate off the old-style networks to the Internet, their communication needs come with them, so Internets of the future will be able to meet a wider range of needs without sacrificing economy. 

This infrastructure continuously improves itself, which is very cool, and very different from other infrastructures that really can&#039;t because they&#039;re stuck doing one thing in the same old way by law and regulation. 

That&#039;s the deal with Internet infrastructure. It&#039;s not magic, not free, and not above the laws of physics, but it&#039;s very flexible, very fast, very cheap, and getting more so. It&#039;s not magic, but it&#039;s very, very clever.</description>
		<content:encoded><![CDATA[<p>Time-travel a caveman into modern America and he&#8217;ll be amazed at our transportation system. Send him back and he&#8217;d tell his buddies something like: &#8220;they have things called bus stations, train stations, and airports where you walk inside very clean cave and sit on this thing called a seat. You tie yourself down in this chair thing and it takes you far away. When you leave the cave you&#8217;re in a totally different place. Dudes, it&#8217;s magic.&#8221; Many descriptions of the Internet infrastructure are like that. </p>
<p>It&#8217;s really a communications system, and unlike other communications systems it&#8217;s made of diverse elements: fat things like Ethernets, SONETs, ATMs, and odd things like FiOSes, DOCSISes, DSLs, WiMaxes, and Wi-Fis. It doesn&#8217;t seem like these things could all be part of a unified system, but they are. And unlike other communications systems that go to great lengths to ensure they provide predictable and invariant service, the Internet has a wierd attitude toward overuse and overload: it says &#8220;bring it on, I can handle myself no matter what you do to me.&#8221; </p>
<p>This is what makes the economics of Internetting so brilliant. If we&#8217;re willing to give up a little predictability, we can generally have great service for very little money. As more uses migrate off the old-style networks to the Internet, their communication needs come with them, so Internets of the future will be able to meet a wider range of needs without sacrificing economy. </p>
<p>This infrastructure continuously improves itself, which is very cool, and very different from other infrastructures that really can&#8217;t because they&#8217;re stuck doing one thing in the same old way by law and regulation. </p>
<p>That&#8217;s the deal with Internet infrastructure. It&#8217;s not magic, not free, and not above the laws of physics, but it&#8217;s very flexible, very fast, very cheap, and getting more so. It&#8217;s not magic, but it&#8217;s very, very clever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My Diigo Bookmarks 12/08/2008 &#124; AccMan</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-111238</link>
		<dc:creator>My Diigo Bookmarks 12/08/2008 &#124; AccMan</dc:creator>
		<pubDate>Mon, 08 Dec 2008 04:31:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-111238</guid>
		<description>[...] Doc Searls Weblog · Rethinking out loud about infrastructure [...]</description>
		<content:encoded><![CDATA[<p>[...] Doc Searls Weblog · Rethinking out loud about infrastructure [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russell Nelson</title>
		<link>http://blogs.law.harvard.edu/doc/2008/12/07/rethinking-out-loud-about-infrastructure/comment-page-1/#comment-111236</link>
		<dc:creator>Russell Nelson</dc:creator>
		<pubDate>Mon, 08 Dec 2008 04:13:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1161#comment-111236</guid>
		<description>I&#039;m too lazy to see if I&#039;ve yet pointed you to the idea of &quot;linear infrastructure&quot;.  Whenever you look at the history of linear infrastructure (pipes, roads, and wires), you see a common thread: it&#039;s hard to have a competitive market.  The first party into the space has the competitive advantage, which they can use to charge monopoly prices.  On the other hand, when government tries to run the service itself, it so do inefficiently and poorly.  An interesting model is the way heritage railroads in the UK are run: with many volunteers and a few paid staff to do the grunt-work.  Some of them run a handful of daily trains, approximating service prior to the Beeching Axe.</description>
		<content:encoded><![CDATA[<p>I&#8217;m too lazy to see if I&#8217;ve yet pointed you to the idea of &#8220;linear infrastructure&#8221;.  Whenever you look at the history of linear infrastructure (pipes, roads, and wires), you see a common thread: it&#8217;s hard to have a competitive market.  The first party into the space has the competitive advantage, which they can use to charge monopoly prices.  On the other hand, when government tries to run the service itself, it so do inefficiently and poorly.  An interesting model is the way heritage railroads in the UK are run: with many volunteers and a few paid staff to do the grunt-work.  Some of them run a handful of daily trains, approximating service prior to the Beeching Axe.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
