USA India
Home Articles UserTV Press Releases Dictionary Books Education Careers B-Channels Resources Forums Blogs Classifieds
Saturday 19 Jul, 2008 eNewsletter Register Login
Archives
Articles By Date
Articles By Category
 
 
 Archives >> Details
Putting the Net in Neutral
Part 1 of a look at a growing controversy.
Posted by : Nelson King
I have the feeling that most of the world--not to mention the computer industry--has been following the Net neutrality issue in the United States. No wonder; seldom do we see an issue so fundamentally difficult to grasp and so clouded with confusing rhetoric. It may not seem like this to the fierce partisans (paid and unpaid), such as those marching the halls of Congress on behalf of one interest group or another. Nor may it seem confusing to those whose knees jerk in synchronicity with calls for Internet fairness or the unfettered free market. However, though confused as any, I did suspect that under the raveled and sometimes intentionally twisted Net neutrality arguments there are things worth thinking about. Foolishly treading where angels fear, I'll try to do some unraveling in this column and the next.

I'd start with an acceptable description of the Net neutrality issue, but unfortunately such descriptions have so often been embedded in ways to cast, frame, or bias the issue (take your pick) that almost any approach will be seen as falling into one camp or another. But what the heck, I'll identify the Net neutrality issue with three things: A principle that guides the Internet, the technical reality of the Internet, and making money.

Principle Interest

It's generally agreed that one of the reasons the Internet has been so successful is that it was founded on a set of goals and principles that guided and enabled its growth. One such principle is the idea that the network itself is "dumb." In other words, it knows not and cares not what is contained in the packets of data that whiz across the network. Packets should be moved, by whatever route, as rapidly as possible, from whatever source to whatever destination. In short, the Internet is a packet-data transport mechanism that is content-neutral, which these days is what most people recognize as Net neutrality.

Current use of the Internet is dominated by an enormous volume of relatively small transmissions (a small number of packets)--Web pages, e-mail, search requests, and so forth. The original content is broken up into packets, the packets travel by the best available route to the destination, and at the end point the packets are reassembled into the original content. With small transmissions, the Internet does this quite efficiently.

However, we are at the beginning of using the Internet for streaming data--movies, radio, television, voice (phone). By definition, streaming involves a massive number of packets that must be delivered in a timely manner. Here latency of the Internet comes into play. The more packets in a transmission and the farther they have to go, the more likely some packets get lost. The system has to request replacement of lost packets and they are retransmitted. Of course this takes time and holds up the assembly of a transmission at the destination--creating a lag (latency in the system). Lags may not be a problem for e-mail, which sits around anyway, but for movies, TV, or telephone conversations, latency degrades the quality of what you see or hear, sometimes a lot.

There are many ways latency can be addressed, but the two most mentioned at the moment are faster transmission--usually by installing fiber-optical transmission lines--and preferred transmission, which means that some packets move through the system faster than others.

Who Pays, Who Profits

Much of the U.S. Internet, especially the fiber-optic, nation-spanning backbone transmission lines, was built with government subsidy (about $280 billion worth). The current performance upgrade to the system is installation of fiber-optic lines on the "last mile" to homes and businesses. While it was understood that backbone lines would be used by everybody and controlled by nobody, there is no such understanding for last mile lines. Those who spend the money to put in the last mile lines, typically the cable or telephone carriers such as Verizon, AT&T, or Time-Warner want control of those lines and profit from their investment. There is some dispute about this, but it fits within the current practice of carriers owning the cable and telephone lines and charging both users and providers for access to the Internet. We've also generally accepted paying more money for more bandwidth.

What is relatively new (and the source of the fiercest debate) is the notion of stepping up the speed of transmission by giving some packets priority. New router technology makes it possible for Internet carriers to differentiate packet by source, content, and destination and treat some preferentially. These routers turn the Internet into a "smart" network capable of analyzing and acting on the packets. Network carriers are suggesting that like Internet access bandwidth, content providers, particularly those with streaming data, should pay for preferential treatment of their packets. The carriers say this will pay for redressing the inherent bias of the Internet against streaming data.

Packet Priority

It is on the issue of paying for prioritizing packets that the rhetoric becomes thunderous and the confusion endemic. Content providers such as Google, Yahoo, and Microsoft, naturally, hate the idea--it complicates their business model. Obviously, analyzing and handling packets based on their origin, content, or destination is not what the principle of net neutrality is about, so this is where the defenders of net neutrality join the battle. They and the content providers want Congress to ban or regulate the ability of Internet carriers to charge for packet prioritization. The carriers and their supporters countercharge that a Congressional mandate for net neutrality is unnecessary government intervention, and that in a number of ways will lead to no good.

I'll plunge into some specific arguments in the next column, but I'll note here that there are big problems with the debate: Almost everyone is arguing on the basis of speculation about the extreme cases: what might happen if net neutrality is totally abandoned, or if a government ban on packet prioritization is applied. Also, when the subject is complicated and assertions are difficult or impossible to prove, then there is a counter-argument to almost everything. For example: "Internet carriers will have too much power over what content will be provided," countered by "Competition will give people ways around the control." Finally, as important to the future of the Internet as this issue probably is, it has become quite politicized, which has kicked what is almost a technical debate into deep philosophical waters.

Under the circumstances, is there any way to cut through some of the clutter and confusion? I think so, and I'll spell out how next time.

Nelson King writes Pursuits bimonthly for ComputerUser.

 
 
Archives by Date
 
 
 
 
 
Copyright © 2001-2008 ComputerUser, Inc., All Rights Reserved
About us | Terms of use | Privacy Policy | Legal | Trademark/Copyright | Awards | Advertise | Writer guidelines | Sitemap | Contact | FAQ's | Feedback  | Link to us

Here are the topics we cover computer certification computer careers computer training computer games consulting data recovery data security digital entertainment emerging technology gadget reviews handheld computers hardware reviews home automation home networks home office how-to advice internet linux local companies local news local profiles macintosh mp3 players network security online music online security open-source small-business technology soho software reviews technology books technology dictionary vpn web site reviews wi-fi windows wireless technology tech articles tech news press releases tech dictionary education resources career solutions create your personal blog upload your videos become a writer usergroups special interest group SIG 3com cipts adobe adobe certified expert apc ncpi apple achds acpt acsa actc avaya bea 8.1 certified administrator 8.1 certified architect 8.1 certified developer 9 certified administrator bicsi rcdd checkpoint ccmse ccsa ccsa ngx ccse ccse ng plus with ai ccse ngx cisco access routing and lan switching ccda ccdp ccie ccip ccna ccnp ccnp old ccsp ccvp crmam ip communications optical proctored exams for validating knowledge sales specialist storage networking vpn and security wireless lan citrix cca 3.0 cca 4.0 cca 4.5 cca xp ccea 3.0 ccea 4.0 ccea xp ccia ciw ciw associate ciw certified instructor master ciw admin master ciw designer master ciw enterprise developer security analyst comptia a+ network+ security+ server+ computer associates ca cusa cuse cwna cwna cwsp dell eccouncil cea cep certified ethical hacker chfi e-commerce architect emc emc specialist implemenation technology foundations enterasys ese eta exam express exin exin itil extreme networks ena ens filemaker f7cd f8cd fortinet fortigate foundry cne fujitsu fujitsu guidance software ence hdi css hda hdm hdsa hitachi hitachi certified professional hp ais apc app aps ase certified systems developer csa cse master ase huawei hcne hyperion hcp ibm advanced deployment professional advanced technical expert application developer business process analyst certified administrator certified advanced system administrator certified advanced technical expert certified associate developer certified enterprise developer certified solution designer certified specialist certified systems expert database administrator db2 deployment professional enterprise developer eserver certified specialist ibm on demand business solution advisor solution designer solutions developer solutions expert storage administrator system administator iisfa cifi intel isaca cisa isc cissp sscp iseb itil ism cpm juniper jncia jncis legato lcaa lcea lotus clp lpi lpic level 1 lpic level 2 lpic level 3 macromedia mcafee mcdata csnd microsoft crm mbs mcad .net mcdba mcdst mcitp mcp mcpd mcsa longhorn mcsa 2003 mcsa 2008 mcsd .net mcse mcse 2000 security mcse 2000 to mcse 2003 upgrade mcse 2003 mcse 2003 messaging mcse 2003 security mcse 2008 mcts microsoft business solutions microsoft partner competency mile2 cnsa network appliance nac-na nac-nie naca nace nacp network general sniffer certified professional nokia nokia security administrator nortel ncde ncds ncse ncss ncts novell5 cna 5 cne 6 cna 6 cne 6.5 cne cne upgrade omg ocup oracle 10g dba 10g oca 11i 8i dba 9i dba 9i internet application developer oca ocp8 to ocp8i dba upgrade exam pmi project management professional polycom pcve redhat rhce rhct sair sas institute sas scp saas scp snia snia certified architect snia certified professional snia certified systems engineer snia storage networking certification program administrator professional associate symantec scse scsp scta scts teradata tca v2r5 tcad v2r5 tcda v2r5 tcis v2r5 tcm v2r5 tcp v2r5 tia ccnt ctp tibco tcp trusecure ticsa veritas infraguard chamber of commerce vcp vmware certified professional webex linkedin facebook myspace Professional page layout, image editing, vector illustration, and print production Website design, development, prototyping, and blogging Creation of rich interactive content Industry-standard visual effects and motion graphics Video capture, editing, and production; DVD titling; and digital audio, Adobe Photoshop CS3 extended, Adobe illustrator CS3,Adobe indesign CS3,Adobe Acrobat 8 Professional, Adobe Flash CS3 Professional, Adobe Dreamweaver CS3,Adobe Contribute CS3,Adobe Fireworks CS3,Adobe After Effects CS3 Professional, Adobe Premiere Pro CS3,Adobe Soundbooth CS3,Adobe Encore CS3,Adobe OnLocation,Adobe Bridge CS3,Adobe Version Cue CS3,Adobe Device Central CS3,Adobe Stock Photos, Intel Pentium 4 (1.4GHz processor for DV; 3.4GHz processor for HDV), Intel Centrino, Intel Xeon, (dual 2.8GHz processors for HD), or Intel Core, Duo (or compatible) processor; SSE2-enabled processor required for AMD systems Microsoft Windows XP with Service Pack 2 or Microsoft Windows Vista Home Premium, Business, Ultimate, or Enterprise (certified for 32-bit editions) 1GB of RAM for DV; 2GB of RAM for HDV and HD; more RAM recommended when running multiple components 10GB of available hard-disk space (additional free space required during installation) Dedicated 7,200 RPM hard drive for DV and HDV editing; striped disk array storage (RAID 0) for HD; SCSI disk subsystem preferred Microsoft DirectX compatible sound card (multichannel ASIO-compatible sound card recommended),1,280x1,024 monitor resolution with 32-bit color adapter Blu-ray burner required for Blu-ray Disc creation OHCI compatible IEEE 1394 port for DV and HDV capture, export to tape, and transmit to DV device QuickTime 7.1.2 software required to use QuickTime features Broadband Internet connection required for Adobe Stock Photos* and other services