{"id":1599,"date":"2003-07-09T03:29:59","date_gmt":"2003-07-09T10:29:59","guid":{"rendered":"http:\/\/mossback.org\/archives\/2003\/07\/misunderstanding-the-internet\/"},"modified":"2003-07-09T03:29:59","modified_gmt":"2003-07-09T10:29:59","slug":"misunderstanding-the-internet","status":"publish","type":"post","link":"https:\/\/bennett.com\/blog\/2003\/07\/09\/misunderstanding-the-internet\/","title":{"rendered":"Misunderstanding the Internet"},"content":{"rendered":"<p>\t\t\t\tThe mistaken idea that Internet architecture is &#8220;End-to-End&#8221; has cropped up again, this time on the <a href=\"http:\/\/doc.weblogs.com\/2003\/07\/07\">Doc Searls blog<\/a>, with a reference to some orders to the FCC from Larry Lessig, who&#8217;s not especially empowered to make them. <\/p>\n<p>While there are many problems with using the FCC to impose this view (like, um, the fact that they can&#8217;t), and with Searls&#8217; desire to make a political litmus test out of it, the most important is that it&#8217;s simply not true. While it may be argued that the Internet has an &#8220;end-<b>and<\/b>-end&#8221; architecture that concentrates as much intelligence as possible in the endpoints and has precious little in the middle, a truly &#8220;end-<b>to<\/b>-end&#8221; architecture would allow the ends to control the flow of messages through the middle, and the current architecture can&#8217;t do that. <\/p>\n<p>An end-to-end architecture, in other words, would allow a voice application to tell the network &#8220;I need a narrow stream of bandwidth connecting me to this other end, but I need that stream to be free of jitter. I don&#8217;t need retransmission of packets dropped to relieve congestion, but I do need to know I&#8217;m getting through, and I&#8217;m willing to pay 25 cents a minute for the that.&#8221; Or it would allow a caching media application to say &#8220;I need lots of bandwidth for a 4 gigabyte transfer, but I don&#8217;t want to pay a lot for it and you can work it around other applications that need small chunks because I don&#8217;t care about jitter.&#8221; Or it would allow an email application to say &#8220;Send this the cheapest way, period.&#8221;  And it would allow a teleconferencing application to say &#8220;send this to my group of these 14 end points without jitter and with moderately high bandwidth and we&#8217;ll pay you a reasonable fee.&#8221; <\/p>\n<p>The network would then deal with congestion by dropping the spam and the e-mail until conditions improve, and by delaying the honking media files, but it would endeavor to deliver as many of the voice and real-time media packets as possible. It therefore wouldn&#8217;t allow spam to step on VoIP, as it does now.  Most of us are able to see that this would be progress, but we see the Internet as a tool, and not as a socio-political metaphor. <\/p>\n<p>There are a number of kludges that have been adopted in TCP to approximate a truly end-to-end capability, but none of them really make it a reality because there&#8217;s not enough smarts in IP and its various kludgy cousins (ICMP, IGMP) to make this work. So freezing the architecture at this stage would be a serious mistake, which is why you never see network architects arguing for the things that Searls (a Public Relations  man), <a href=\"http:\/\/cyberlaw.stanford.edu\/lessig\/blog\/\">Lessig <\/a>(a law professor) or <a href=\"http:\/\/www.hyperorg.com\/blogger\/\">Dave Weinberger<\/a> (a philosophy professor) want.<\/p>\n<p>The story of how the Internet came by its odd architecture, which it doesn&#8217;t share with the much better-designed ARPANET, coherent architectures like SNA and DECNet, and extant PDNs, is a story of ambitious professors, government grants, and turf wars among contractors that&#8217;s not at all a tale of the best design winning out, but more on that later. This &#8220;end-to-end&#8221; fantasy is simply historical revisionism, and we need to nip it in the bud before it does any more damage.<\/p>\n<p>UPDATE: Weinberger <a href=\"http:\/\/snblog.pulver.com\/2003\/archives\/000032.html\">gets defensive<\/a> about his creds at the wanky Supernova conference:<\/p>\n<blockquote>\n<p>Up now, David Weinberger brings the Cluetrain ethos to the new areas of digital identity and DRM, professing his end-user ignorance as his unique qualification for speaking for normal users and articulating the rights they would want to protect.<\/p><\/blockquote>\n<p>Heh heh heh.\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The mistaken idea that Internet architecture is &#8220;End-to-End&#8221; has cropped up again, this time on the Doc Searls blog, with a reference to some orders to the FCC from Larry Lessig, who&#8217;s not especially empowered to make them. While there are many problems with using the FCC to impose this view (like, um, the fact &hellip; <a href=\"https:\/\/bennett.com\/blog\/2003\/07\/09\/misunderstanding-the-internet\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Misunderstanding the Internet&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[4,8],"tags":[],"class_list":["post-1599","post","type-post","status-publish","format-standard","hentry","category-comp","category-greatest"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pbifyw-pN","_links":{"self":[{"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/posts\/1599","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/comments?post=1599"}],"version-history":[{"count":0,"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/posts\/1599\/revisions"}],"wp:attachment":[{"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/media?parent=1599"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/categories?post=1599"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bennett.com\/blog\/wp-json\/wp\/v2\/tags?post=1599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}