 |
Federal Communications Commission (FCC) Chairman Julius Genachowski gave a speech in Washington recently in which he announced that the time has finally come for some net neutrality rules.
The speech was quite moderate overall, with concessions to the more nuanced network engineering requirements for managed services. Chairman Genachowski recognizes that the Internet is an evolving system that may need to supplement the traditional “best-effort” delivery system it inherited from early Ethernet with more sophisticated traffic management.
The Internet has changed a lot since it was first cobbled together to connect Arpanet with other networks, and we can expect that it will keep on changing as long as we use it for more things in more places.
The chairman made some interesting observations about the Internet’s history and architecture at the very beginning of the speech. However, his comments slightly missed the mark when he opined that the Internet’s historic openness means that it’s never been “biased in favor of any particular application.”
People who study network architectures and those who’ve followed the net neutrality debate in detail recognize this as more an aspiration than a statement of fact. In his 2003 paper, which introduced the term "network neutrality" into the debate on Internet regulation, Columbia law professor Tim Wu conceded that the Internet is biased by design in favor of certain applications:
Proponents of open access have generally overlooked the fact that, to the extent an open access rule inhibits vertical relationships, it can help maintain the Internet’s greatest deviation from network neutrality. That deviation is favoritism of data applications, as a class, over latency-sensitive applications involving voice or video.
A large part of the net neutrality debate revolves around this built-in bias. Given that we have a network that favors one kind of application over another, and the fact that increasing numbers of users want to employ voice and video applications, isn’t it necessary for the network to actively remedy its bias?
In the first phase of Internet design work, TCP and IP were conceived as a single, unified protocol, but the realization that this unified design would never work for voice led designers to split them in two and add a real-time enabler, UDP, to the mix. Separating the Siamese twins was a step in the right direction, although it didn’t solve the whole problem. The advent of extremely high volume P2P applications to the Internet aggravates the bias even more. Depending on how the rule-making comes out, we may look to “managed services” to deliver us from the content bias.
Chairman Genachowski’s remarks and the entry of net neutrality onto the final road to rule-making make research into the evolution of the Internet -- about which much remains not well known -- timely and necessary.
The net neutrality advocates tend to emphasize the end-to-end arguments as central to the Internet’s design, but in my research, I’ve found they’re more a means than an end.
The Internet Engineering Task Force (IETF) RFC 1958 on “Architectural Principles of the Internet” captures the question most clearly with this suggestion: "The principle of constant change is perhaps the only principle of the Internet that should survive indefinitely."
There’s some very compelling evidence that this sort of thinking is more productive than an insistence on adding all new features in the application space.
Network engineers have hard choices to make about how best to support the new applications, and it’s better to make these choices on the basis of engineering than on glib regulations. The current set of FCC commissioners are as good as any we’ve had for several years, so I’m confident they’re taking a serious look at their role in moving the Internet forward.
— Richard Bennett is an ITIF Research Fellow specializing in broadband networking and Internet policy.
IQ Crew
Saturday October 3, 2009 2:07:57 PM
Why would we ever be limited to a single Internet?
The advent of Cloud Computing brings us back to the days of dialing into various mainframes and minis.
Once a pipe is established to an end node, that end node can connect us to any number of proprietary or public networks.
Does everything have to be accessible via tcp/ip? It's a very limited design in many ways.
With my Clear Wimax connection, perhaps there could be any number of end points "in the air" that I can utilize, each with a unique design through many OSI layers.
Thinkernetter
Friday October 2, 2009 4:58:46 PM
NN regulations are frequently justified on the basis of "keeping" content from one source equal in access speed and price with content from all other sources, but this desire is reflected neither in the structure of the regulations nor in the way the Intenet delivers content today. Content producers who have the money to pay Akamail to host their content close to consumer enjoy a speed and quality advantage over those who host their content farther away; the Internet is not neutral in this sense. And those like Google/YouTube who can afford to build their own closed content delivery network buy an additional advantage for themselves. So the question about double-paying is whether small content producers can have the option of buying content caching services from the destination ISP or only from Akamai et. al.
When you enact a ban on ISPs offering CDN services, you don't create a level playing field for mom and pop, you reinforce the advantage that large players like Google/YouTube enjoy by having paid $20B for their closed, private network.
IQ Crew
Friday October 2, 2009 4:51:47 PM
There are so many issues tied into this. For one, not all net neutrality advocates are bullish on keeping all-you-can-eat plans. They are different issues that share a wide overlap of people, but I don't think they should be comingled.
Most of us NN folks are concerned not about different applications being treated differently (though there are many who are) but are most concerned about some content being treated differently than other content of the same application type because a carrier wants to charge some content producers twice for access to "the carrier's" subscribers. This is the heart of the NN debate, whether applications should be treated differently as a class is perhaps the stomach...
The question is whether I, as a subscriber, will have traffic treated the same if I visit Google video as if I go to Fox video or if my carrier can make deals with one or the other to favor that video content and thereby hurt the openness of the Internet and the meritocracy we have (though it remains imperfect even with NN magically guaranteed, I will agree).
Thinkernetter
Friday October 2, 2009 4:07:21 PM
Different people seem to be reading different subtexts into the Chairman's speech. His concessions about managing congestion and attacks were good and necessary, but leave all the questions open. A lot of the net neutrality debate is about pricing models: NN advocates would like to keep all-you-can-eat pricing, as would most consusmers, but now that there's so much diversity in resource consumption it's hard to see how it can survive without active management.
If network operators could lower the priority of P2P traffic, for example, it wouldn't be an impairment to people using video calling services like Skype. But there's not a well-accepted and uniform way to recognize P2P except DPI, and nobody likes that option (except the DPI vendors, of course.)
This tells me we have some more enigneering to do before the Internet is ready to meet the future.
Thinkernetter
Friday October 2, 2009 12:53:28 PM
The whole broadband initiative, at least on the government side, seems a wee bit out of touch with technological reality. It's high time we in the U.S. demanded that lawmakers get a grip on the technology they're legislating instead of thinking they get it and missing the nuances.
The FCC speech seems to indicate that there is some movement toward understanding that the Internet isn't a static resource that simply has to be extended further via the telecom infrastructure in order to please all parties.
The ThinkerNet does not reflect the views of TechWeb. The ThinkerNet is an informal means of communication to members and visitors of the Internet Evolution site. Individual authors are chosen by Internet Evolution to blog. Neither Internet Evolution nor TechWeb assume responsibility for comments, claims, or opinions made by authors and ThinkerNet bloggers. They are no substitute for your own research and should not be relied upon for trading or any other purpose. |
 |
|
 |
a moderated blogosphere of internet experts
A picture is worth a thousand words, or so the old saying goes. So understanding how to use images in e-newsletters effectively is quite important. Here are a few tips to ensure that your images in email newsletters work to your advantage.
Arms merchant or army? That's a fundamental question for vendors in the cloud computing space. Do they just sell their tooling to any and all comers, who then become the actual purveyors of hosted infrastructure, developer platforms, and software? Or do they offer their own cloud-based services, perhaps even keeping much of their technology in-house for competitive advantage?
With the value of toxic assets on the rise, large U.S. and European banks face many challenges on the road to recovery. Sharing key information may help these firms effectively track the way forward.
Most of us go through life knowing that we’re expected to learn from our mistakes and improve. Those who are more conscientious about learning and personal improvement usually reap greater rewards.
Marketers are known for exaggerated claims and stretching the truth just a wee bit. But most marketers I know truly believe in what they sell. Their aggressiveness is based on a confidence that what they are promoting truly benefits the customer.
IETV: the thinkerNet on film
an IBM information resource
sponsored content
big blue blog
While Google introduces its new Chrome OS (which I'm hearing will be widely available in one year? Did I mishear that?), IBM announced 10 new products today to help companies using IBM System z mainframe technology.
white papers & case studies
an IBM information resource
sponsored content
Smarter Collaboration: How to Thrive in a Challenging Business Environment
Market conditions are changing faster than ever, and organizations need to improve their agility and adaptability in order to provide better service and improve processes. The ability to work with customers, business partners, and employees as effectively as possible - while at the same time holding down costs - is a key to success.
READ THIS eBOOK
your weekly update of news, analysis, and
opinion from Internet Evolution - FREE!
REGISTER HERE
Wanted! Site Moderators
Internet Evolution is looking for a handful of readers to help moderate the message boards on our site as well as engaging in high-IQ conversation with the industry mavens on our thinkerNet blogosphere. The job comes with various perks, bags of kudos, and GIANT bragging rights. Interested?
Please email: moderators@internetevolution.com
|