Earlier this week, Google’s Chief Internet Evangelist Vint Cerf said something that brightened my day.
…the real question for today’s broadband networks is not whether they need to be managed, but rather how.
We couldn’t agree more, since I’ve expressed that same sentiment once or twice or thrice. Network managers know that networks need to be managed. Cerf even explained why:
Network capacity (bits per second or data rate) is a limiting factor in all communications networks. Users cannot send traffic faster than the amount of network capacity available to them. But when users’ aggregate demand exceeds the available capacity of the network, network operators naturally seek to manage the traffic loads… The end result is the potential for traffic congestion, leading to service delays and even outages for consumers.
Cerf then goes on to discuss various methods, such as transmission rate caps, low latency prioritization and bandwidth constraints, but they’re all based on that phrase: “…not whether [networks] need to be managed, but rather how.” [Emphasis added.] I take great interest in these remarks, because I’ve been following his arguments over the last couple years.
For example, back on June 13 of 2006, he appeared on Public Radio’s The Kojo Nnamdi Show. You can find that episode online; if you skip ahead to about 23 minutes in, you can hear Cerf speak of net neutrality for a few minutes. At that time, he argued that innovation will be stifled and users will not be able to freely access content unless the Internet is kept “open and neutral.” He said that the government may need to provide protection. Two years later, it’s unclear what innovation was stifled.
By October of 2007, Cerf was speaking of other concerns, such as at his address at the WebbyConnect conference, which I attended. He said in his speech that “net neutrality” as a phrase has been distorted and that he would clarify what Google was asking for.
- It’s okay to charge for higher capacity.
- It’s okay to address denial of service attacks, viruses and so on.
- It’s okay to provide low latency services.
- As long as all of these practices are done in a non-discriminatory fashion.
Even at this point, Cerf was arguing that network management was necessary, but he had his opinion about what methods ought to be used. That approach is much better than comments (like this one) that argue that the “management” argument is a scare tactic. There are those who would claim we should just build a bigger pipe. But then you read this quote from a Singapore ISP executive: “Even buying more bandwidth will not work since stuff like BitTorrent is designed to gobble whatever extra bandwidth we buy.”
Cerf specifically mentions that conversations with Comcast engineers have led him to a better understanding of the underlying motivation and rationale for that company’s network management decisions. As we often see, when people examine the capacity constraints we face and the unique challenges of running cable systems, it can contribute to the conversation.
Now that Cerf has confirmed that network management is a fact and a necessity, we can begin to have the broader dialogue about the network management that needs to take place. Cerf argues the “how” of network management is the important piece of the puzzle, but I would suggest the “who” is even more critical – as in, “Who decides what network management practices are reasonable?”
Cerf argues that government should. I think that is the wrong approach. I think it makes more sense for engineers and companies to make those decisions, not government bureaucrats. Those decisions should be based on what methods of network management might be most efficient and which ones would provide the best experience for the largest number of their customers. They should not be based on the dreams and schemes of politicians.
I recently heard one of these people describe network congestion as akin to a mail truck being full. This kind of talk makes my head hurt.
I shudder to think of the regulations that would be dreamed up by the US Department of Network Management.
