NNSquad - Network Neutrality Squad
[ NNSquad ] Re: Google response to WSJ 12/15/08"Fast Track on the Web" story
single mode fiber capacity is on the order of 38 THz of analog bandwidth
On Dec 15, 2008, at 6:05 PM, Waclawsky John-A52165 wrote:I'm not so sure ....the core network has a lot of capacity via opticswith the equipment at the end points supporting nearly 1 trillion bpstoday on a single "light pipe" (88 x 10 Gbps color) - this was unheardof just a few years ago. The electronics at the end of the fiber link isthe limiting factor - Moores law does effect that. I asked the questionat GlobeComm (two weeks ago): what was the theoretical capacity of afiber link? I was told there was none (at least today) and everyone wasshaking their head yes (100% consensus). I am always suspicious aboutclaims of scarcity and never under estimate human ingenuity (in searchof a buck) ability to solve the problem which I see as a loose corollaryof Moore's law, IMHO :-) My 2 cents..-----Original Message-----From: nnsquad-bounces+jgw=motorola.com@nnsquad.org[mailto:nnsquad-bounces+jgw=motorola.com@nnsquad.org] On Behalf OfGeorge OuSent: Monday, December 15, 2008 3:24 PMTo: 'John Bartas'; 'Lauren Weinstein'Subject: [ NNSquad ] Re: Google response to WSJ 12/15/08"Fast Track onthe Web" storyJohn, content caching will always be the solution for large scale videodistribution. Networks will get 10s, 100s, 1000s of times faster butthe same relative bottlenecks will be there and we'll run in to the sameproblems as the bitrates of the video increases proportionally withcapacity. Distributed caching solves the unicast problem whichreplicates transmissions millions of times over the same infrastructureand that's just silly. Caching will never become "obsolete" no matterhow fast the network gets because it's a 10,000-fold performancemultiplier. In fact, if network prioritization is the "fast lane", thencontent caching is the "warp lane"which exceeds the speed of light since you don't even have to botherre-transmitting the content.No, network prioritization is not a content accelerator because itdoesn't prevent you from having to send the same content millions oftimes."I spent most of 2007 working on a VoIP analysis device (Packet Island)and the vast majority of VoIP jitter problems we saw were caused bycrappy local ISP networks"That's what I said in my network management report, jitter mostlyhappens where there is the largest bottleneck which will always bebroadband. All Net Neutrality legislation proposed so far specificallytargets broadband and prevents jitter-mitigation and legitimatebandwidth management techniques.Broadband by definition will always be the bottleneck because ifbroadband speeds up 10-fold, the core and distribution part of theInternet will also have to speed up 10-fold to keep up. So your theorythat we can simply grow out of these bottlenecks with "Moore's law"(which talks about transistor count BTW) is simply wrong.George Ou-----Original Message-----From: nnsquad-bounces+george_ou=lanarchitect.net@nnsquad.org[mailto:nnsquad-bounces+george_ou=lanarchitect.net@nnsquad.org] OnBehalf Of John BartasSent: Monday, December 15, 2008 2:53 AMTo: 'Lauren Weinstein'Subject: [ NNSquad ] Re: Google response to WSJ 12/15/08 "Fast Track onthe Web" storyThere's some careless assertions in Georges post. First, content cachingis not the ultimate anything; just a stopgap. Moore's law willaccelerate the backbone with faster routers and media, whereascompany-specific co-located servers will always have an overhead. Evenif the co-lo server storage was free, the cost of a Chennai staff tomanage the extra data copy is pretty well fixed, and eventually a fasterbackbone would make it uneconomical. Like all forms of caching, progresswill either obsolete it or commoditize it. This day will come a lotfaster if U.S. providers realize they are not going to make a killingholding people's content hostage with QoS schemes.Also "Network prioritization is designed for a totally different purposebut people confuse it for a content delivery mechanism when it isn't."is misleading. Network prioritization has a lot of flavors, and some canbe a great content delivery accelerator. The duopoly shows every signthat they will use it this way as soon as they can get away with it.And jumping ahead, I see someone's still floating the argument that NNis bad for Jitter. I spent most of 2007 working on a VoIP analysisdevice (Packet Island) and the vast majority of VoIP jitter problems wesaw were caused by crappy local ISP networks - too many hops and routeflap between the phone and the backbone. The biggest ISPs are the worst.The backbone itself is fine. NN won't hurt jitter.Despite this, I'm inclined to agree with George that minor legislationis not the answer - Congress is clueless and the Duopoly PR machine istoo good at muddying the water for a serious policy debate. Ultimatelyit will have to be a tightly regulated public utility; with a strict capon profits. Only by stripping off the profit motive can the net stayfree.-JB-George Ou wrote:Now you know why every Net Neutrality bill ever proposed allspecifically target broadband and they don't apply to the type ofnon-neutraladvantagesthat large dotcom companies can buy.Content caching [usually in the form of Content Delivery Networks(CDN)]isultimate fast track mechanism for content distribution. Contentcachingisthe only model that supports on-demand high quality video, not P2P ornetwork prioritization. Content caching shows why the Internet neverhas and never will be equal. The Internet is only equal to those whocan buy the same infrastructure but it's never been equal to everyoneat anyprice.Richard Bennett also debunks this myth that everything has to be equalhereNetwork prioritization is designed for a totally different purpose butpeople confuse it for a content delivery mechanism when it isn't.Network prioritization ensures that a network can support multipleapplications as well as possible. That means bandwidth should beintelligentlyprioritizedin favor of interactive applications with low duty cycles overbackground applications with non-stop usage. That means backgroundapplicationsaren'taffected in terms of average bandwidth but the interactive applicationimproves substantially. This does not conflict with the purpose ofprotocolagnostic network management which is designed to ensure equitabledistribution of bandwidth between customers of the same broadbandservice tier. This system relies on a priority budget system toprevent users and application developers from abusing the system bylabeling every packet as top priority.The other purpose of network prioritization is to mitigate jitter(large spikes in packet delay) which can even occur at very lownetworkutilizationlevels. To fix this, we have to deliver the packets out-of-order suchthatthe network toggles between packets of different applications at ahigher rate which prevents real-time applications from timing out.Some will consider this "cutting in line" but it isn't because someapplicationspackthe line with 10 to 100 times more packets and a smart network willquicklyalternate between the different applications to prevent starvation.I cover this in my new report on network management released lastThursday.The problem with Net Neutrality legislation is that they either try toban network prioritization outright (Wyden bill in 2006) or they trytoprohibitdifferentiated pricing and give everyone priority regardless of source(Snowe/Dorgan and Markey in 2006). The anti-tiering legislationeffectivelybreaks prioritization because if every packet is prioritized, then nooneisprioritized. If we can't look at the source of the packets, we can'tdetermine whether people have exceeded their budgets and it'simpossibletoenforce a fair prioritization scheme. If we can't have differentiatedpricing, then there's no effective way we can give people a prioritybudgetwhich means there's no way to enforce a fair and meaningfulprioritization scheme. The end result is that all the Net Neutralityproposals make it impossible to have a network prioritization systemwhich makes broadband a less useful network that multitasks poorly.George Ou-----Original Message-----From: nnsquad-bounces+george_ou=lanarchitect.net@nnsquad.orgBehalfOfLauren WeinsteinSent: Sunday, December 14, 2008 9:52 PMSubject: [ NNSquad ] Google response to WSJ 12/15/08 "Fast Track ontheWeb"storyGoogle response to WSJ 12/15/08 "Fast Track on the Web" storyts-of-caching.html--Lauren--NNSquad Moderator