The Internet Distinction

(Original article at Techcrunch)

“Application-agnostic network management with a definition of an application should include apps, sites and web services. To the extent that there are specialized services that network providers want to put in market they should do that—but they need to be distinguished from the open internet.”

By John Borthwick

[Techcrunch] Editor’s note: Guest author John Borthwick is the CEO and founder of betaworks and in a previous life was a senior strategist for Time Warner and a witness in the Microsoft antitrust case.

Access to fast, affordable and open broadband, for users and developers alike is, I believe, the single most important driver of innovation in our business. The FCC will likely vote next week on a framework for net neutrality—we got aspects of this wrong ten years ago, we can’t afford to be wrong again. For the reasons I outline below, we are at an important juncture in the evolution of how we connect to the Internet and how services are delivered on top of the platform. The lack of basic “rules of the road” for what network providers and others can and can’t do is starting to hamper innovation and growth. The proposals aren’t perfect but now is the time for the FCC to act.

Brad Burnham stopped by our office earlier this week to talk about his proposal for the future of net neutrality. The FCC has circulated a draft of a set of rules about neutrality that the Commission will likely vote on this week. Though the rules are not public, Chairman Genachowski outlined their substance last week. Through a combination of the Chairman’s talk, the Waxman Proposal, and the Google/Verizon proposal, one can derive the substance of the issue and understand its opportunities and risks. I strongly support much of what the Chairman has proposed and I support the clarifications that Burnham outlines. But before further discussing this point, I have to ask, why does this matter now? Over the past few years there has been a lot of discussion, a lot of promises, and some proposals with regard to net neutrality. Here are three reasons why this matters now:

1. The Internet and how we build things on the network is undergoing meaningful change as we transition to broadband and wireless access.

[. . .]

2. Most of the innovation that has taken place online over the past 15 years was born out of a handful of architectural decisions. Two of these decisions are now being challenged.

Non-discriminatory pricing of bits and the clear definition of layers (i.e. the logical separation of conduit and content) that make up the Internet stack are two of the key architectural foundations of the network. The fact that bits containing applications, images, text or videos are handled in the same manner is central to how the Internet works. Network providers can shape or manage traffic on an aggregate, best-effort basis but identifying a single application or any content in an application or page will change the way the network is used. Specifically, it will hamper innovation by end-users such as individuals, developers and new or existing companies. Similarly, the layers are building blocks that are vital to how we develop and build Internet companies. This goes back to seminal pieces of Internet literature like the rise of the stupid network. I agree that, in the short term, tightly coupled systems can provide more efficient means to drive end-to-end innovation when you know precisely what you want to build. But I fundamentally believe that the essence of innovation is that you don’t usually know exactly what you want to build.

Innovators aim to solve problems—they start in one place and then they iterate. All too often real innovation is simply stumbled upon. Ideas and companies evolve (or pivot, as we now call it) as they better understand the problem they are seeking to solve. The Internet has demonstrated time and time again that loosely coupled systems and edge-based innovation is what drives the kind of massive change we have seen over the past two decades. This freedom to create “on the edge”, and to evolve ideas, is what gets me up in the morning and keeps me up late at night.

Like all good architecture, structural principles are remarkably resilient to change and scale. There have been continual challenges to these principles over the past few decades but this has all been part of the persistent tension that exists in a network between centralization and decentralization. Today, given our current transition to wireless and broadband access, the challenges faced are more fundamental as network providers attempt to change these building blocks as preconditions to future investment. The conflation of access (and control of access) with control of the stack of the open Internet is wrong.

3. Edge-based innovation has been the driver of change and creativity online, yet the edge has no single representative.

The edge-based innovation I talk of is predicated on access to a handful of things and the persistent tension between centralization and decentralization is a hallmark of a healthy web, evident in debates all the way back to Napster, CompuServe and AOL and, more recently, Facebook and Wikileaks. We have many native Internet companies relative to ten years ago. Though these native Internet companies come from the edge, no single company represents the edge. Moreover, as companies scale, they become increasingly misaligned with the edge. Google, Amazon, Facebook, eBay, and Yahoo, for example, all came from edge-based innovation but no longer represent the edge. Despite intentions to the contrary, there is a natural evolutionary path through which a large company becomes less likely to let edge-based innovations flourish and more likely to preserve the status quo. There is currently an over-representation of the center in Washington DC and the edge needs a louder voice. That’s up to us and, most likely, also up to you.

So what to do? As Burnham outlines, there are a handful of areas that merit attention. The key points are:

Application discrimination and specialized services

Burnham advocates Barbara van Schewick’s approach to “all application-specific discrimination”. I believe this approach can work because it works today. It is hard to understand where to draw lines here but we know what we think when a network provider discriminates against a specific application or specific content. We know it when we see it. Schewick proposes a generalized rule to ensure that this discrimination does not happen. If you doubt this approach, read the Zedevia letter as evidence that companies hesitate to invest without clarity—companies need clearly drawn lines. How much edge-based telephony (i.e. voice-based communication) innovation have you seen on the iPhone? Not a lot. Today—the list of issues and examples of discrimination is starting to grow. This is happening as the adoption of over the top services (IPTV etc.) places pressure on the cable companies’ video based revenues or the wireless companies’ voice and data revenues. Application-agnostic network management with a definition of an application should include apps, sites and web services. To the extent that there are specialized services that network providers want to put in market they should do that—but they need to be distinguished from the open internet.

[. . .]