Net Neutrality: Regulation Makes Evil Empire Giggle

Want a faster, better, cheaper, more available Internet? Painful Net neutrality regulations won’t help. Competition will.

Jonathan Feldman, CIO, City of Asheville, NC

January 17, 2014

7 Min Read

When I weighed in on Tuesday's court ruling reining in Net neutrality rules, I argued that more competition, not misguided regulation, is the best way to keep the Internet open and promote innovation. I stand by that argument, and I want to further explain why an FCC-gone-wild will only make the carrier duopoloy that you hate even stronger. If you want to destroy that duopoly, you must be open to other ideas.

We all hate the lack of broadband choice. But that's what we have as a result of our history, going back to when AT&T (Ma Bell) was the government-regulated monopoly. If you translate that into Internet terms, it was as if one entity operated 98% of all Internet connections and made 90% of all computer equipment.

An antitrust lawsuit resulted in the breakup of Ma Bell in 1984 into separate, for-profit Baby Bell telcos. Then the 1996 Federal Telecommunications Act, ostensibly enacted to enable competition, introduced complex regulation surrounding what are still called CLECs, or competitive local exchange carriers. The broken-up phone companies were called ILECs, or incumbent local exchange carriers.

If these confusing acronyms make you think that the governing regulations were also confusing, you're darned right. The experiment of regulating our way to competition was, by any measure, a failure. CLECs had their boom day but have since petered out, as the telecom market collapsed back to a far less competitive one, whereby SBC, a child of the broken-up AT&T, merged three of the Baby Bells into one in 2005 and acquired AT&T (and took on its name).

Regulation did not make the market more competitive. It did not make the market more attractive. And so we stayed, mostly, with the local telecom incumbents in one business and the local cable company in a different business, prior to the great Internet boom.

Prioritize or overbuild
Now, let's talk about the need for traffic prioritization, because this is also important when we talk about why Net neutrality will have the reverse effect of what is intended.

I was amused that some InformationWeek readers think that no provider should ever have to prioritize the traffic it delivers. Really? C'mon, guys. All you would have to do is run a truly large network but have no authority over all of the end users for more than 35 seconds, and you'd know that the ability to prioritize or block traffic is absolutely necessary in order to serve the many when the few are acting up. In my long-ago work as an infrastructure and security consultant, I helped universities and large companies configure equipment to either drop or deprioritize peer-to-peer or ridiculously high users.

Traffic prioritization is not a monstrous thing to implement. The alternative is to over-provision 5:1 so that the many aren't affected when the few act up. That's expensive. Who's going to pay for it? Those of you who are in love with the idea of Net neutrality? Because I sure don't want to pay for it. And the carriers aren't going to pay for it either. They're going to pass those costs on to you. And that state of affairs won't have the intended effect of a faster, better, cheaper, more available Internet.

Regulate others?
Now back to regulation. Regulation is to the masses a bit like workstation lockdown is to IT pros: Nobody cares when it's happening to someone else.

As someone who cut his teeth on infrastructure and has moved between private sector and government jobs, I've watched both regulation and IT lockdown for 20-plus years. The law of unintended consequences doesn't just apply to traffic prioritization and overbuilding costs. It also applies to competition.

Like the mythical energy monster that only gets stronger when you shoot it with a laser gun, the incumbents that you hate so much have no problem dealing with regulation -- it's far better than having to compete with market entrants. When I was in business school, some of my classmates were in telecom, and one of them who worked for an ILEC would laugh at the notion of new CLECs dealing with the regulatory environment. You see, the ILECs are used to dealing with bureaucracy, and have lawyered up and passed the expense to you, the consumer. Market entrants see lots of regulations as a threat, not a way to level the playing field. Because they don't level it.

Regulation, like medicine, should be used only when there's no alternative. The chief reason cited for Net neutrality is to prevent monopoly and antitrust types of behavior. My question for you is this: If we don't believe antitrust laws will be enforced on the Internet, why do we think that Net neutrality laws will be? And if we do think those antitrust laws will be enforced, there's no need for Net neutrality.

Moving forward
Piling on regulations with all of their delicious unintended consequences isn't the answer. So what is?

Let's focus on the actual problems and not what we imagine the problem could be in the future. Let's not focus on imagined anticompetitive traffic-shaping (which is illegal from an antitrust perspective). Let's not, as some readers have, focus on the imagined problems of redundant infrastructure -- that it's "wasteful" to build new fiber paths when incumbent backbones already exist. Your brain has redundant pathways, too. It's not a bad thing. Incumbent network operators have been exceedingly jealous about sharing their infrastructure with competitors, so new infrastructure gets built. Don't worry about it.

Let's focus instead on how to get broadband to the many rural readers who wrote in to bemoan their lack of choice. Let's focus, again, on incentivizing competition. That's an OK thing for government to do.

And government has done that, with reasonable success lately. The NTIA's BTOP (Broadband Technology Opportunities Program) has done a remarkable job of extending broadband coverage in many states over the last several years. You can see a map here. The program is no panacea, but it's an example of what can happen when we apply incentives instead of crushing regulations.

So-called "white spaces" in newly freed-up radio spectrum offer a fantastic opportunity for some enterprising young libertarian engineers who want to create a peer-to-peer "Radio Free Internet." But I guarantee you that traffic management would be a necessary evil of even that network.

If we insist upon the government having a role making the Internet open and accessible, it's possible that "unbundling," the practice of forbidding carriers from being both middle and last-mile providers, could also create competition and reduce anticompetitive behavior. It has worked in Europe, but we're not Europe. And we would do well to consider the law of unintended consequences if we choose that route.

Bottom line, there are competitive broadband success stories across the US. Let's replicate them, preferably without government assistance but with that assistance if it's needed. One local-to-me example is SkyRunner, a wireless ISP that has served western North Carolina since 1997. It provides excellent Internet service to both municipal and rural clients over WiFi.

In this case -- and, I would submit, many others -- no crushing regulation was needed, just hard work and great customer service.

Jonathan Feldman writes for InformationWeek on the topics of leadership, innovation, IT people skills, and running large organizations "like a startup." He is CIO for the City of Asheville, N.C., where he encourages innovation through better business technology and process.

Can the trendy tech strategy of DevOps really bring peace between developers and IT operations -- and deliver faster, more reliable app creation and delivery? Also in the DevOps Challenge issue of InformationWeek: Execs charting digital business strategies can't afford to take Internet connectivity for granted.

About the Author(s)

Jonathan Feldman

CIO, City of Asheville, NC

Jonathan Feldman is Chief Information Officer for the City of Asheville, North Carolina, where his business background and work as an InformationWeek columnist have helped him to innovate in government through better practices in business technology, process, and human resources management. Asheville is a rapidly growing and popular city; it has been named a Fodor top travel destination, and is the site of many new breweries, including New Belgium's east coast expansion. During Jonathan's leadership, the City has been recognized nationally and internationally (including the International Economic Development Council New Media, Government Innovation Grant, and the GMIS Best Practices awards) for improving services to citizens and reducing expenses through new practices and technology.  He is active in the IT, startup and open data communities, was named a "Top 100 CIO to follow" by the Huffington Post, and is a co-author of Code For America's book, Beyond Transparency. Learn more about Jonathan at

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like

More Insights