Clear Standards for Reasonable Network Management

This is the second in a series of posts by Chris Riley, Free Press Policy Counsel, to summarize the primary policy recommendations made in recent comments submitted to the Federal Communications Commission in its open Internet proceeding. Today’s topic: reasonable network management.

In my last post, I discussed Free Press’ position on nondiscrimination, and why a clear and comprehensive rule without loopholes is essential to protect consumers, competition and innovation. But are there times when discrimination is beneficial and should be allowed? Although the ISPs’ network problems are exaggerated, the answer is yes – in the right contexts, when done in the right way. We support the FCC’s general idea of allowing for “reasonable network management,” but as we discuss in our filing for the agency’s NPRM on open Internet rules, we remain highly critical of the vagueness of the definition proposed.

The discussion of network controls centers on the issue of congestion, which is often discussed but less often understood. Congestion occurs as a result of very heavy network use, when many users are simultaneously sharing a network resource that has been designed for use by only a few. When congestion occurs, not all of the data passing through a pipe can fit. Congestion sometimes lasts for only a fraction of a second, but sometimes it lasts much longer. Although the Internet was designed to handle congestion without the network faltering, poorly engineered Internet applications or applications that depend on high performance can be temporarily disrupted. The higher the utilization gets within a network, the more frequent and severe the congestion and impact on Internet use.

Previously, network operators dealt with high utilization by increasing network capacity. If too many people used the network at the same time, then it was expanded to accommodate the high demand. This system worked well for the history of the Internet, and it’s still working well today.

Delusional data usage

A big talking point of network gatekeepers in the FCC’s proceeding on open Internet rules is the idea that Internet use is getting out of hand, leading to unprecedented levels of use and severe congestion. Allegedly, network gatekeepers need to impose similarly unprecedented additional controls to deal with this congestion. This idea is commonly known as the “exaflood,” and it’s a delusion. Data usage has been growing steadily for years; network engineers have always been able to accommodate the rapid pace of growth; and there is no evidence to support any change to this pattern. Talk about a solution in search of a problem!

That said: Even a properly engineered network will experience sporadic, mild periods of high utilization and congestion. So appropriate network controls to deal with periods of congestion can be reasonable. Similarly, network controls that deal with spam or viruses or denial of service attacks can certainly be reasonable. And the FCC should ensure that network operators’ ability to impose “reasonable” network controls can coexist with consumer protections in this proceeding.

Clear guidance from the FCC

So, where does that leave us? The FCC needs to offer clear guidance as to what “reasonable” means, so that network operators can better understand what actions might get them in trouble, and consumers can be assured that this “reasonable” framework won’t just rubber stamp anything the network operator wants. But rather than be clear, the FCC’s suggestion was circular: “Reasonable network management consists of practices which are reasonable.”

Admittedly, this isn’t an easy question. The FCC has two conflicting goals: Be clear, but allow for good behavior. But the right solution isn’t that hard. It’s similar to frameworks that have been adopted either voluntarily or by regulation in Japan and Canada. To be considered reasonable, network controls must have a good reason for their existence, and they must not harm anybody unnecessarily. Put in other terms, this is a two-part test for “purpose” and “means.”

Public interest purpose

The first part of the test is: What is the purpose of the practice, and why should we consider it valuable? In our comments, we propose that the purpose be a “public interest purpose” – something which on balance serves the public interest, not merely short-term parochial interests. The purpose should also be real, not hypothetical. For example, congestion management can be a public interest purpose, but only if the network operator can demonstrate that congestion is occurring or at least likely because of high utilization. Going back to my first post: Any discrimination is inherently harmful to some Internet traffic. Thus, if the purpose isn’t real, the discrimination at issue is unwarranted and unreasonable. Practices should not be approved absent data showing that the intended purpose is not merely hypothetical.

Time, geography and proportion

If the purpose is real and valuable, the next question is, what means are used to achieve that purpose? We break this question down into three parts: time, geography and proportion, and I will use congestion management as my hypothetical purpose. “Geography” says that if you demonstrate high utilization in a service area somewhere in downtown San Francisco, you should not be using a congestion management practice in Boston. “Time” says that if you demonstrate that your network experiences high utilization between 7 and 9 p.m. in a local area, you should not be using a congestion management practice at noon. And “proportion” says that you can’t block all uses of one application even if some of those uses are contributing to congestion. You can’t discriminate just because it’s the easy answer if you have a more appropriate remedy available.

With a good two-part purpose and means test in place, the FCC can evaluate network controls that violate the open Internet rules on a case-by-case process, to separate the bad actors from the good. Clear standards for what counts as “reasonable” will limit the FCC’s arbitrary discretion, and give the reviewing courts (and the public and Congress) something to evaluate. But a definition that says “reasonable is that which is reasonable” is nothing but Swiss cheese.

Free Press is a national, nonpartisan organization working to reform the media. Free Press does not support or oppose any candidate for public office. Through education, organizing and advocacy, we promote diverse and independent media ownership, strong public media and universal access to communications.

Chris Riley

Policy Counsel M. Chris Riley advises Free Press on legal matters related to our policy, research and campaign work, and represents Free Press on our issues before the FCC and Congress. Prior to joining Free Press, Chris worked as an Honors Program Attorney at the FCC, as a summer associate at Ropes & Gray, LLP, and as a legal intern at the Electronic Frontier Foundation. Read Chris's full bio »

Comments

Paul Daigle's picture

Clear Standards for Reasonable Network Management

By Paul Daigle (not verified) on January 20, 2010

This is an incredibly frustrating post in that it implies that finding fair and reasonable methods for dealing with network congestion is both difficult and elementary. But you offer nothing in the way of specific solutions that you believe represent a fair and reasonable approach. I'm not seeing any primary policy recommendation here. Like most Net Neutrality advocates, you are alluding to a fuzzy ideal that providers should be held to. You assert that engineers have always been able to address capacity issues to make the "solution in search of a problem" argument. But this argument ignores the fact that in the near future broadband will provide more and more of our media diet, and that the media we will consume will get heavier and heavier, and that these two trends will likely make congestion management a more pressing problem. Let's take this opportunity to hammer out reasonable standards that ensure transparency. If we as Net Neutrality advocates can't define fair and reasonable, the Broadband industry will be all too glad to do so on our behalf, and they'll use their proximity to the system to legitimize their position. The Net Neutrality movement is being too vague in what it's fighting for. If we can't hammer out specific recommendations for congestion management based on industry facts and consumer perception than our overall position will appear idealistic and naive in the face of Broadband industries PR machine.

annonymous_man's picture

Paul Daigle has a point: Net Neutrality must be specific

By annonymous_man (not verified) on January 20, 2010

Paul is right about one thing we need to ensure the policy ideas described in this article -- he writes aren't specific enough -- he says he's "not finding any primary policy recommendations here" in response to the article -- so I suggest a policy approach be taken and specific policy ideas be shared in future. I'm all for Net Neutrality to keep the Internet open, democratic, nondiscriminatory and most importantly neutral but we have to ensure there are specifics in future for how to achieve this. Otherwise it will be frustrating not having access to the specifics. If we do not help the FCC set the specifications for its Net Neutrality rule and don't encourage Congress to participate with the FCC on crafting pro Net Neutrality legislation the monopolistic ISPs will set the future course of the debate, the tone of Net Neutrality and its definition for us.

Don Smith's picture

What do net neutrality people want?

By Don Smith (not verified) on January 21, 2010

I'm wondering whether it's ever reasonable for ISPs to squelch (slow down) downloads for people using file-sharing apps. Some people constantly download (illegal) movies and software or operate such file-sharing services. There's nothing illegal per se in downloading files. But illegal material is illegal. The issue of illegality is different but related to the issue of network management.

Do net neutrality people think it's OK for ISPs to charge more money for more usage? So, they can charge for usage per bit? Or for bits per second?

Certainly, we don't want ISPs discriminating against political or competitors' content. But nor do we want to encourage illegal downloading.

But what, if any, reasonable steps can ISPs take to discourage illegal usage? And should ISPs be able to squelch people who download huge amounts of data?

Perhaps some people in the Net Neutrality movement think all content should be free. Such thinking may lead to the disaster: no high quality content, including news.

bowtrol's picture

I visit this blog three times

By bowtrol (not verified) on January 30, 2010

I visit this blog three times a week and its always good to read all the good stuff in here

Acnezine's picture

This blog is a great one

By Acnezine (not verified) on February 01, 2010

This blog is a great one considering all the information

mary's picture

Get enhanced network

By mary (not verified) on February 03, 2010

Get enhanced network monitoring and server monitoring software only at
http://zyrion.com/download/

Free Press is a national, nonpartisan, nonprofit organization working to reform the media. Through education, organizing and advocacy, we promote diverse and independent media ownership, strong public media, quality journalism, and universal access to communications.

Learn More »

close [x]

The Free Press Action Fund is member-supported. We don't take money from government, political parties or businesses. Member contributions fuel our work lobbying Congress and the FCC, filing lawsuits and legal complaints, and aggressively advocating for real changes in media policymaking that benefit the public.

Donate To the Free Press Action Fund »

close [x]