Court Challenges FCC in Early Network Neutrality Test

Chief Judge to FCC lawyer: “How do you want to lose?”

If a recent oral argument before the U.S. Court of Appeals for the D.C. Circuit is any guide, the FCC may have a tough time imposing its proposed network neutrality policies. Unless Congress steps in to give it a hand.

The case (argued on January 8) arose from complaints that Comcast’s Internet service had deliberately and selectively interfered with BitTorrent file-sharing services. Comcast claimed it was just managing traffic on the network; opponents suspected Comcast of trying to shield the parent company’s cable operations from competition.

The FCC sided with the complainants. It did not fine Comcast, but imposed conditions intended to ensure that the practice had ended. Read the details here.

Comcast brought an appeal to the D.C. Circuit, raising two main grounds: (1) the FCC had no actual rule in place prohibiting what Comcast did (due process argument); and (2) the FCC could not have had such a rule because it lacks authority over an Internet provider’s handling of content (jurisdictional argument).

While it is always risky to predict the outcome of a case on the basis of oral argument, things look bad for the FCC – not only as to the Comcast case, but also in regards to its stated goal of adopting network neutrality rules.

The judges seemed to feed “softballs” to the attorney for Comcast, while giving the FCC lawyer a much harder time. We noted three particularly telling moments:

  • The Chief Judge asking the FCC lawyer, “How would you prefer to lose – [on due process or on jurisdiction]?”
  • Another judge pointedly asking the FCC lawyer, “Are there any limits” to the FCC’s jurisdictional claim? The lawyer seemed unable to come up with an answer that both satisfied the court and squared with his own theory.
  • The Chief Judge remarking, “The impact of our decision [on the FCC’s pending network neutrality rules] will be perfectly clear,” in a context suggesting the court expects to undercut the FCC’s ability to adopt those rules.

But even if the FCC loses this case, it would be a mistake to suppose that marks the end of network neutrality. There are two points to remember.

First, the FCC believes it has a decent argument for jurisdiction based on the Supreme Court’s Brand X decision, which has language supporting the FCC’s authority to regulate at least some aspects of Internet service.  The Comcast court appeared uninterested in hearing about Brand X. But the FCC could ask the Supreme Court to rule in its favor under that precedent.

Second, a loss here on jurisdictional grounds will be an invitation to Congress to step in and give the FCC whatever authority it needs to impose network neutrality. Recent congressional proposals have been a lot tougher than the FCC’s proposed rules.

Either way, an FCC loss in this court will only set off the next stage of the dispute.

FHH On The Road: Paul Feldman In Florida (And On The Internet)

FHH member and noted Net Neutrality maven Paul Feldman recently appeared at the TM Forum’s Management World America Conference in sunny Orlando. He spoke at the Conference’s keynote event, “Hype vs. Reality: What is the Role of Deregulation in Delivering a 21st Century Digital World?” (That's Paul on the right in the photo to the left.) For those of you who didn’t make it down to Florida for the festivities, no problem – you can catch Paul’s 15-minute Q-and-A presentation on net neutrality by clicking on this link.

Net Neutrality Hard To Enforce

FCC’s proposed rules good on paper, may do little in practice

The IEEE, a widely respected association of electrical engineers, posted the reflections of FH&H lawyer (and former engineer) Mitchell Lazarus on why the FCC’s proposed network neutrality rules may miss their target.  Read the piece here:

http://spectrum.ieee.org/telecom/internet/policing-net-neutrality

How to Solve the Network Neutrality Problem

Giving ISPs a choice about giving customers a choice

As we have reported elsewhere, the FCC has proposed rules to mandate “network neutrality.” Those rules would bar a broadband Internet service provider (ISP) from, among other things, discriminating for or against a provider’s content.

The big ISPs are implacably opposed to all such rules. We own the networks, they say, and we can run them any way we want. On the other side, in favor of the rules, are content providers who fear discrimination by the ISPs. The big providers in particular, like Google, not only want to compete with the cable and telephone companies, but they want to do it through the cable and telephone companies’ own ISPs.

Ironically, the problem that network neutrality would solve is one of the FCC’s own making.

In the dial-up days, there were two kinds of ISPs: (a) the ones run by the phone companies, and (b) all the others. The phone company ISPs had an enormous potential advantage in easy access to the innards of the phone system. Other things being equal, they could have out-performed and undersold everyone else and had the industry to themselves. But the FCC wanted a competitive market. In the 1985 Computer III proceeding, it required the phone companies to offer to all ISPs the same functional network access available to the phone companies’ own ISPs. (This oversimplifies a very complex ruling; for more, click here.)

The result of Computer III was a lot of ISPs. Customers in many areas could choose from hundreds. Eager to preserve clientele in such an intensely competitive environment, no ISP would dare tamper with any customer’s content. What we now call network neutrality was such a pervasive fact of life as to not even need a name.

With the advent of broadband, the FCC changed course. Phone-company DSL, in the early days of broadband, still implicitly came under the Computer III rules, and thus had to be shared with competing ISPs. But cable TV companies, which had never been subject to Computer III, had no such obligations. Non-cable ISPs clamored for access; the cable companies fought back. The FCC settled the issue in 2002: cable TV is not like telephone service and need not share its facilities. A cable company could require its broadband subscribers to use the cable company’s ISP.

That decision outraged the phone companies, who still had to share their broadband channels. But in 2005, the FCC extended the same ISP exclusivity to the phone companies. The Commission decided that DSL is a lot like cable after all, and so abolished the DSL sharing rules. If you wanted DSL, you took the local phone company as your ISP.

Now, having let the broadband ISPs lock in their customers with nowhere else to go, the FCC is shocked to learn that some of those same ISPs are blocking or slowing content that might compete with their parent companies’ offerings. How can the Commission protect broadband customers from the undesirable circumstances which the Commission’s own regulatory decisions have unintentionally fostered?

It is too late for the FCC to re-apply Computer III to broadband Internet. That opportunity has passed.  And so the FCC goes to Plan B: duct-tape network neutrality rules over the problem and make discrimination victims run the gauntlet of lengthy and possibly expensive enforcement proceedings.

There may be another way. The ISPs cannot easily be forced into giving access to competing ISPs. But perhaps they might be persuaded to give that access voluntarily.

Here is how it might work.

The FCC lays out a set of detailed, no-nonsense network neutrality rules that specify clearly what ISP behavior is banned. (Not like the newly proposed rules, which are vague and general.) The FCC also sets up a swift and certain enforcement procedure that penalizes violations. But it gives each broadband ISP a choice: (a) the ISP can opt to abide by the network neutrality rules; or (b) it can offer competing ISPs access to the broadband channel, equivalent to its own. If an ISP chooses network neutrality, it keeps the entire customer base for itself, but must be neutral as to content. If it opts to open its network, it can block or favor content as it chooses, although it risks losing customers who dislike the discrimination.

Many details remain be worked out. Could a cable or telephone company use its relationships with subscribers to market ISP services? Could an ISP reject network neutrality, yet still hold in customers with optional long-term contracts and early termination fees? How would the rules operate in a rural area with no competing ISPs?

But the principle is simple enough. A provider that chooses to abide by network neutrality must live up to that commitment, in exchange for its role as the exclusive ISP. Another that chooses to open its network will have to work with competitors as promised, in exchange for the right to play favorites with customer content.

In short, a broadband provider can have all the customers, or it can manipulate their content. It just can’t do both.

FCC Releases Net Neutrality NPRM - Let the Jousting Begin!

Regular readers of the CommLawBlog who know a lot about Network Neutrality (see, e.g., recent posts here, here and here) also knew the FCC planned to open a proceeding to adopt formal Net Neutrality rules. True to its word, on October 22 it issued a Notice of Proposed Rulemaking (NPRM) that did just that.

In 61 pages of detailed legal, economic, technical and policy analysis, the FCC proposed:

  • to codify the four principles the Commission previously articulated in its 2005 Internet Policy Statement;
  • to codify a fifth principle that would require a broadband Internet access service provider (IASP) to treat lawful content, applications, and services in a nondiscriminatory manner;
  • to codify a sixth principle that would require an IASP to disclose information concerning network management and other practices reasonably required for users and providers of content, applications and services to enjoy the protections specified in this rulemaking; and
  • to make clear that the principles are subject to reasonable network management, and would not limit an IASP in delivering emergency communications or addressing the needs of law enforcement, public safety, or national or homeland security.

The NPRM also requests comments on:

  • a category of “managed” or “specialized” services, how to define them, and what principles or rules, if any, should apply;
  • how the new rules should govern non-wireline forms of Internet access, such as mobile wireless (an especially fertile ground for dispute), unlicensed wireless, licensed fixed wireless, and satellite; and
  • enforcement procedures that the Commission should use to ensure compliance.

Some noteworthy details:

  • While the proposed rules would apply to broadband Internet access, they would not apply to dial-up Internet access, or to private “intranets.” The exemption for dial-up may offer some comfort to small and rural Internet service providers.
  • Unlike the FCC’s existing Internet Principles – which state what “consumers are entitled to” – the proposed rules are phrased as obligations imposed on IASPs. But this raises the issue of what sorts of entities the rules should apply to. AT&T has called on the FCC to apply Net Neutrality rules to application service providers such as Google, as well IASPs. While the NPRM seeks comments on that idea, the rules as proposed would apply only to IASPs.
  • The proposed Non-Discrimination Rule would prohibit IASPs from charging content, application, and service providers for enhanced or prioritized access to subscribers, but makes no mention of charges to the end users. This might allow, for example, the end user to subscribe to a service that increases throughput (and hence quality) for a video channel, even if it reduces throughput to the same user’s other applications. The Chairman did say at the meeting that users should have the final say on their own Internet experience.
  • The NPRM tees up the issue of whether so-called “managed services” should be exempt from some or all of the Net Neutrality rules. Examples include IP-enabled cable television-like services (AT&T’s U-verse, Verizon’s FIOS video), facilities-based VoIP services, and telemedicine applications. These are delivered over the same network facilities as Internet access, but are not themselves traditional Internet services. This issue will almost certainly be hotly contested.
  • The NPRM asks whether only “unreasonable” discrimination should be prohibited. Such a limitation would allow forms of discrimination that may be desirable for end users (e.g., to promote quality of service for a particular application). While the IASPs can be expected to support that approach, there may be a catch: the concept of prohibiting “unreasonable discrimination” has traditionally be a fundamental component of common carrier regulation, and IASPs do not want to be treated as common carriers. Additionally, drawing the line that defines “unreasonable” will be a contentious task.
  • In exploring the “transparency” rule, the NPRM seeks comment on the proper balance between giving consumers the information that they need and overwhelming them with detail. The NPRM also asks whether the transparency rule should require IASPs to give details of network management to content/application/service providers, and/or to the FCC. While the IASPs may have limited concerns about providing this information to consumers, they will likely fight this extension of the concept.
  • There will be numerous FCC “workshops” in this proceeding, and more importantly, a formal process of technical outreach led by the FCC’s Office of Engineering and Technology. The latter seeks details on what is reasonable network management, what is workable in terms of transparency, and how the FCC can prevent the rules from having detrimental impact.
  • Commissioners McDowell and Baker dissented in part, laying down their “markers” as to how they would oppose the Chairman’s proposal with the “factual and legal predicates” of the NPRM. Commissioner McDowell agreed on the need to preserve an open Internet, but wanted it done through non-government management entities such as ICANN and other voluntary entities – a “bottom up” rather than a “top down” approach. He argued that countries that regulate the Internet more than the U.S. tend to be less free than the U.S., and are waiting for the U.S. to enact more regulation in order to justify their own more intrusive and political regimes. And while the Chairman has stated that a goal of Net Neutrality is to protect innovation at the “edge” of the network, McDowell noted an unprecedented overlap between “edge” applications and “core” ISPs. He also suggested that any anti-competitive conduct by IASPs could be addressed by anti-trust laws.

Comments on the NPRM are due to be filed by January 14, 2010. Reply comments are due March 5, 2010.

Recent history suggests that the proceeding will be a titanic battleground. Time to strap on your armor, grab your lance, and head to the field of combat.  Let the tilting begin!

"Net Neutrality = the First Amendment of the Internet"? Not Really

A good slogan perhaps, but NOT the law

As the FCC prepares to impose its version of net neutrality upon wireless and wired Internet service providers (ISPs), the Internet is buzzing with comments on how such governmental intervention may affect the future development of the Internet. 

On the one hand are the application service providers (with Google leading the charge) who promote net neutrality as necessary for the preservation of the Internet. These folks did not invest in any of the transmission facilities that comprise the hardware pipeline of the Internet – but they are happy to rely on that pipeline to distribute their services.

On the other side are the ISPs (including folks who DID invest in the hardware) and technical experts who believe net neutrality is a solution in search of a problem and a dangerous overlay of regulation upon a dynamic, constantly evolving set of relationships.

This battle presents a range of legal issues. The question mentioned perhaps most often involves the FCC’s authority to regulate at all here:  the Commission (with a thumbs-up from the Supreme Court in the Brand X case) has held Internet data transmission to be an “information service” that cannot be regulated – well, at least not as common carriage. But if that’s the case, how can the Commission now try to impose common carrier-like obligations on ISPs?

Then there is the First Amendment of the U.S. Constitution.

Talk to the advocates of net neutrality, and they will tell you that net neutrality advances the interests embodied in the First Amendment. To them, net neutrality is the “First Amendment of the Internet.” This is an interesting way of looking at the First Amendment . . . because it is backward. To quote Adam Thierer in his very compelling blog about the issue:

After all, the language of the First Amendment could not be more clear when it says, “Congress shall make no law…” It doesn’t contain any caveats or footnotes. And the First Amendment most certainly was not intended as a tool for government to control the editorial discretion of private individuals or institutions. It was about restricting the power of the government to curtail speech and expression.

But net neutrality would open the door for government to exercise at least some control – and very possibly a lot of control – over speech and expression. So the advocates of net neutrality as the “First Amendment of the Internet” have it backwards. Further, they seem not to appreciate that those who would be most directly burdened by net neutrality, the ISPs, enjoy First Amendment rights like the rest of us. ISPs, too, have the right to be free from government regulation of their speech.  Ignoring (whether or not intentionally) that right, the net neutrality advocates  fail to acknowledge the burdens that would be imposed by net neutrality on the ISPs’ First Amendment right to choose to transmit, or not to transmit, particular viewpoints or messages. 

“What?” you say. “ISPs are not newspapers! They’re merely service providers.” If you were to believe that ISPs have no free speech rights, you would be wrong. Think about cable television, which is somewhat similar. Sure, cable companies have been required to carry local commercial television stations without being paid a dime for the carriage. But such carriage has been subject to repeated First Amendment attacks, attacks which were barely parried by a razor-thin 5-4 vote in the last go-around before the Supreme Court (in Turner). And the Supreme Court has repeatedly held – in the 1979 Midwest Video case, and again in the 1986 Preferred opinion, and once again in the 1994 Turner case – that cable companies do have First Amendment rights that exceed those of broadcasters.   (Of course, the more ISPs claim First Amendment protection because they are “speakers”, the more they expose themselves to additional potential liability, as suggested by our previous posts here and here. But that’s a blog for a different day.)

You might also argue that providing access to web sites, applications and content selected by the user is what the Internet is all about and, thus, net neutrality is merely requiring ISPs to do what it is that ISPs do. That is an interesting argument, but it ignores the fact that nothing compels an ISP to adopt any particular business model and nothing compels the ISP not to be a speaker. As stated above, the FCC treats ISPs as “information service” providers who cannot be compelled by the FCC to offer any service at all, let alone any particular type of service.  And this argument also begs the question of what will ISPs being doing in the future?

You might also be thinking that my view on the application of the First Amendment to ISPs is just a theory, and not something that has been decided by, say, a Federal court. Not entirely true. In 2000, a Federal District Court sitting in south Florida considered the constitutionality of a Broward County ordinance which required cable companies who use their systems for Internet access services to allow any and all ISPs to have access to the service on a nondiscriminatory basis. (It may come as no surprise that the ordinance was written by a local telephone company.) The court conducted a thorough analysis of this ordinance under the First Amendment and decided that a cable company offering Internet access service enjoys First Amendment rights and must be free to reject any ISP it wants to reject.

This observer believes that the FCC will have to conduct a thorough and searching First Amendment review of any net neutrality rules it may want to promulgate. I believe that the battle ground will be over the level of First Amendment scrutiny to which any FCC decision will eventually be subject. The FCC will undoubtedly argue that the toughest standard of judicial review -- i.e., “strict scrutiny” – is not applicable here.  The FCC will have to make that argument because “strict scrutiny” is almost always fatal to a speech restriction. To justify a more regulation-friendly “intermediate” level of review, the Commission can be expected to turn to the Turner and Preferred cases to support its theory that net neutrality regulations are content neutral.

This observer believes strict scrutiny is the appropriate standard here because ISPs cannot claim that they possess the type of “bottleneck monopoly” which cable possessed in 1994, and which led the Turner court to apply the intermediate level of scrutiny. Nonetheless, let’s say, for sake of discussion, that the FCC’s regulations will receive an intermediate scrutiny analysis, and the FCC will rely upon the Supreme Court’s opinion in Preferred to urge that, “[w]here speech and conduct are joined”, the interests of the regulator must be considered. Still, Preferred and Turner would require that the burden of proof be placed on the FCC.  That, in turn, would require the FCC to show a factual basis for its belief that net neutrality is needed. And as the Turner court held, “a content neutral regulation will be sustained if it furthers an important governmental interest that is unrelated to the suppression of free expression and the incidental restriction on alleged First Amendment freedoms is no greater than is essential to the furtherance of that interest.”

This is where it gets sticky for the net neutrality proponents. Web sites and applications are not being blocked as a matter of course now or historically, except in instances in which sites depict the exploitation of children or in certain cases in which peer-to-peer applications hog too much bandwidth.  And if ISPs were to begin to block web sites and applications, what would the harm be? ISPs are operating in a competitive environment, and many new competitors are around the corner. For example, Clearwire has announced that it will bring WiMax services with a huge amount of channel capacity (i.e., more ability to move more bits) to over one-third of the population by the end of 2010 and two thirds of the population by 2017. Verizon Wireless, AT&T Mobility and other wireless service providers have announced that their 4G LTE offerings are just around the corner.

And let’s not forget the costs of regulation. As a regulatory lawyer of almost three decades  (and a former FCC employee, to boot), I can tell you without any reservation that regulatory authority inherently retards new and creative conduct  because of fears that the regulator may not like it, and because regulation inherently guides and restrains the development of markets and technology.

Regulating the Internet without hindering its development presents an especially difficult problem because the Internet is a rapidly evolving set of relationships that owe their evolution to technological developments and unique ideas for content and applications that simply cannot be anticipated.   The FCC appears to recognize that it may have problems attempting to regulate the Internet without thwarting its development – at least that’s the signal I get from  the broad principles which the Commission has proposed as its rules of the road for the Internet.

But how can the FCC’s proposed broad principles provide the clear rules of conduct that everyone will know and appreciate? They cannot. Litigation before the FCC will be the result. (Hint to FCC: better hire 50 or 100 lawyers for the Internet Litigation Bureau).   

Now you may be thinking that the FCC can react when its rules are found to hinder Internet development. Perhaps, but how fast?   Not fast enough. Regulators have a very difficult time adapting regulation to a fast changing marketplace. For one, the rules they must abide by under the Administrative Procedure Act and the Due Process Clause of the U.S. Constitution require a slow and cumbersome rule making process that cannot keep up with a fast changing industry. It is typical for the rule creation process to run for two or more years.

As I stated at the beginning of this blog, the Internet is buzzing with comments about the FCC’s soon-to-be-proposed net neutrality rules. And the net gets more robust every year, all without this proposed Government intervention that, excuse me, will meet some understandable and real crisis I have never seen. Doesn’t that say it all? In conducting my own research, everything I saw, I saw though my Internet connection. Strangely enough, I found only two articles that mentioned my position, and a host of articles that promoted “net neutrality as the First Amendment of the Internet.” Message to the ISPs: you are not doing a very good job of suppressing access to ideas that may hurt you.

AT&T Allows VoIP On iPhone Subscribers' Broadband Channels

Abrupt reversal precedes FCC announcement of network neutrality proposals

Here is one of those little coincidences that make Washington such an interesting place to work.

Regular readers know about the friction among Apple, maker of the iPhone; AT&T, the iPhone’s broadband provider; and Google Voice, a VoIP service (among other things) that seeks to carry the calls of iPhone users.

The iPhone and its close competitors, like the Palm Pre, have two ways to access broadband: a “3G” channel provided by the carrier and paid for as part of the subscriber’s data plan; and Wi-Fi, much like that in a laptop, which of course works only at Wi-Fi-equipped locations. Apple has long allowed VoIP on the iPhone's Wi-Fi link, but never on the 3G channel. This matters to users, because relatively few of the locations where a person might want to place or receive a call have Wi-Fi service. AT&T, in responding to an FCC inquiry, was blunt about why it (and Apple) block VoIP from 3G: VoIP is a much cheaper substitute for minutes of voice service. Its use thus cuts into carrier revenues, including the revenues needed to recover the subsidy that lets Apple price the iPhone at far below its actual cost. Read more here.

But now AT&T has abruptly reversed course.

It will allow VoIP on the iPhone 3G channel after all. If you hear loud cheers from the general direction of Mountain View, CA, that’s the Google folks breaking out the Red Bull. Apple still has not formally approved the Google Voice app, but a big obstacle is now out of the way.

The coincidence? Exactly one day before AT&T’s about face, the FCC announced the date, two weeks from now, on which it will formally propose its network neutrality rules. One of the key factors that precipitated the current surge of interest in network neutrality was a 2007 request from Skype, a VoIP company, asking the FCC to prohibit wireless companies (like AT&T) from blocking VoIP service. So the rules that might eventually be adopted, a year or two from now, may require action along the lines that AT&T took today.

Down here in the bunker we are a little surprised at the news. The wireless carriers have been erecting a protective wall of press releases that say network neutrality rules will bring about the end of technical innovation, social progress, and cheap cell phones. And AT&T’s decision may fundamentally change the economics of wireless phone service. We can expect vigorous marketing of VoIP services to iPhone users. That will probably cause a significant drop in paid-for voice minutes. Will AT&T start charging more for its data plan? Will Apple abandon the subsidy on the iPhone and start charging customers what the phone actually costs? AT&T may have brought us a little closer to a system in which customers have free choice and pay only for what they choose.

Sometimes the FCC can get the results it wants without actually regulating. Sometimes just announcing the date on which it plans to begin to consider regulating is enough.

Upcoming Appearances: FHH Attorney Paul Feldman To Give Webinar On "Net Neutrality"

Net Neutrality, a long-simmering issue, has exploded into the foreground of public debate as the future of broadband takes shape.  (If you have any doubt about that, check out our posts here, here, here and here, among others.)  And with the announcement that the FCC will be looking, in the very near future, to codify both existing and new Net Neutrality principles, we can expect it to stay in the foreground for some time to come.

If you’re looking for expert, in-depth, analysis of the Net Neutrality debate, FHH member Paul Feldman will be presenting a one-hour webinar on “Net Neutrality – What is it? Where is it going?” on Thursday, October 8, at 1:00 p.m. (ET). 

As an established telecommunications lawyer, Paul has been following the development of Net Neutrality closely for years.  He has written multiple analyses on the topic, including blogs here and here.  In his webinar he will be reviewing the debate over the substance of Net Neutrality proposals, and the FCC’s response – in its 2005 Internet Policy Statement and its 2008 Comcast/BitTorrent Order – to the evolving broadband landscape.  He will look at the Comcast conduct (some might say “misconduct”) that attracted the Commission’s regulatory attention last year, and the changes Comcast made to its network management practices as a result of that attention.  Paul will also address the Net Neutrality obligations which NTIA and RUS are tying to BTOP/BIP broadband stimulus funding.  Lastly, he will examine the new “Fifth and Sixth Principles” recently proposed by FCC Chairman Julius Genachowski to supplement the Commission’s Four Principles of Net Neutrality.

Clearly, the concept of Net Neutrality – however it is ultimately defined – will have an overwhelming impact on all aspects of the broadband industry.  Webinar attendees will come away with answers to important questions, including:

  • What practices have been focus of Net Neutrality discussions and regulations? 
  • What issues may trigger Net Neutrality concerns in the immediate future?

The webinar is being produced by Team Lightbulb.  A registration fee of $99 per computer will be charged.  For registration, go to https://event.on24.com/eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=166037&sessionid=1&key=0B2AB783D63843E31A695E8145B8BFC9&sourcepage=register or call Mr. Sean Sullivan at 703-596-4133.

Two Cheers for Network Neutrality

Those who think network neutrality is the answer might be asking the wrong question

The recent announcement by the FCC Chairman of impending rules on network neutrality caused a lot of stir in the press, including our own coverage here. On the whole, we think network neutrality is a good idea. But it may not achieve the Chairman's stated goal: to preserve the open character of the Internet that fostered so much creativity and innovation in its early days. Those times are slipping away. No set of FCC rules, however well intentioned, will bring them back.

We quickly forget how the Internet used to be. Early technologies of other kinds – 8-track tape players, manual typewriters, tail-finned cars – are easy to remember because we have still examples to look at. But the early Internet has vanished without a trace, save in the reminiscences of the one-time early adopters.

Ah, The Good Old Days

Before the Internet was the precursor ArpaNet, which linked a few dozen major universities and Government facilities. Mainly it was a way to transmit research data, with a pasted-on afterthought called “email” to help researchers coordinate their exchanges.

As students and employees left the ArpaNet sites, they worked out ways to stay linked to the system over ordinary phone lines. Some set up connections their friends and colleagues could dial into, thus becoming the first Internet service providers (ISPs). Using the Internet in those days took technical know-how. Conveniences like URLs and clickable links had yet to be invented. There were few graphics, mostly just text. Access was by typing into command lines. Needed functions like “finger” and “Archie” and “Telnet” were complex and hard to use. Also we walked five miles to school in the snow.

Then, in 1991, came the World Wide Web.

Today many people think the Web and the Internet are the same thing, but in fact the Web was a late add-on. Suddenly anyone, with or without technical aptitude, could learn to use the Internet in a few minutes. One needed only to type an address or click a link. Thousands of ISPs sprung up to serve all the new users. In part because the FCC's earlier Computer II and III rules had assured ISPs equal access to the phone lines, competition among them was fierce. ISPs vied to bring the most content possible to their customers. People with obscure interests had a new way to find each other, to form on-line communities, and to trade conspiracy theories or antique car parts, as the case may be.

It is hard to remember now what a big shift this was. Before the Web, to reach a large audience required going through a book publisher, TV network, or some other powerful gatekeeper. But the Web allowed anyone with a computer and a phone line to make his or her views available to millions. Conversations surged around the globe on every conceivable topic, from the conventional to the bizarre, from cookie recipes to outlandish sexual practices. And yet, amid all this vigorous dialogue, there was almost no large-scale commercial content.   Big companies distrusted the Internet because they could not control it. The medium was too open, too accessible, too accommodating of contrary views.

When people talk about the good old days of the Internet, this is often the period they have in mind – roughly the early 1990s. The Internet itself was big, and getting bigger very fast, as new subscribers signed on in droves and new sites appeared by the millions. Amazingly, though, no one was in charge. The only form of control was a simple system for registering domain names. Any user could post any information and visit any site. Even if a company or government had wanted to limit information or access, there was simply no way to do it.

Large companies soon woke up to the fact that all those millions of computer screens were lighting up the faces of millions of consumers. Cautiously at first, companies began to test out the Internet, first as a marketing tool and then as a channel for conducting actual sales. One early use was for brochures promoting new cars and the like. Internet-only retailers such as Amazon appeared. Chains like CompUSA and Lands End began offering Internet sales in parallel with their physical stores and phone operations. And then came the insight that set off the dot-com boom. If you can sell something that need not be physically delivered in a box, like mortgages or insurance or travel services, then you can sell it on the Internet for little more than the cost of electricity.

As more big firms came to rely on the Internet, they took an interest in seeing it run reliably. The casual patchwork that served in the early days was gradually supplanted by a much larger and more expensive infrastructure run by behemoths like MCI. Other companies installed massive facilities around the country that replicated popular sites willing to pay for the service. A click to access Amazon.com would deliver the content quickly, from a server close by, while the site of a small, specialized bookstore across the country might take much longer to reach the screen. The simple domain-name set-up was replaced by a more complicated scheme that gave big companies a leg up over smaller ones. A plumber named Jim McDonald who wanted to use mcdonald.com for his company website was plumb out of luck.

With commercialization, web-page design evolved from a hobby to a profession. Content became richer and more slickly produced, with more graphics and photos and sound and even videos. End users became impatient with the time it took these increasingly sophisticated pages to load. Once modem makers had wrung the last few bits out of ordinary phone lines, the only recourse was broadband. Consumers signed up for it in droves.

The Narrowing Effect of Broadband

Building out a new broadband connection to every home and business was prohibitive. Fortunately there were wires already in place, and ways to upgrade them. Adding components to the phone company's gear made DSL possible over voice lines, while additions to the cable system allowed for two-way Internet along with one-way video. Other providers offer broadband over electric power lines, via satellite, and through fixed wireless connections, but none of these has made much of a dent in the market.

Where a dial-up customer could choose among a great many ISPs, a broadband customer usually had two at most: the phone company and the cable company.  That limited menu worried the FCC, which considered extending the principle of Computer II and III so competing ISPs could connect through the DSL and cable facilities. But the phone and cable companies insisted they would have no incentive to build out the networks if they had to share them with competitors. The FCC bought the argument, with the result that broadband ISP customers in most markets are limited to two providers at most. Only a few consumers live within range of municipal public Wi-Fi. Cell-phone modems are an option for some, although expensive. FIOS fiber-optic service is available here and there, but again is provided by a major phone company.

Protecting the Parent

When thousands of ISPs competed for subscribers, no one cared about network neutrality. Now we do. Why might the cable and telephone ISPs be more likely to discriminate than their predecessors?

The early ISPs were mostly small businesses, many of them literally mom-and-pop operations. Even the bigger players, like Netcom, were primarily ISPs. Today’s broadband ISPs, in contrast, are all in some other business. The ISP offering in each case started out as a sideline. While it has become a growing piece, the parent companies still have other interests to protect. 

That creates incentives for ISPs to discriminate against certain content. One category at risk is anything that directly competes with some other part of the ISP company. There was an outcry when Comcast blocked subscribers' access to BitTorrent videos, possibly to protect Comcast’s own video-on-demand service. (We reported that here.) Also in danger is anything that might expose the ISP parent to even a remotely theoretical chance of criminal investigation. The major ISPs shut down vast segments of Usenet, a widely-used group discussion service, because a minuscule portion might have been used for distributing child pornography. Subscribers needlessly lost access to enormous amounts of fully legal material. Another category to watch is anything the ISP parent company fears might offend someone’s political sensitivities. Verizon once refused to assign a text-messaging short code to a political group solely because it feared the political content of the messages might be controversial.

In the early days, vigorous competition corrected any such inclinations. But today a home or business broadband subscriber who wants access to blocked content has few options. In principle there is more competition for wireless broadband services, because there are more companies in the market. They certainly tout the fact. “The wireless industry is ultra-competitive,” says their trade association website, “and that means you win with a wide variety of service plans, options, and features from which to choose.” In practice, though, the providers’ use of handset tie-ins and early termination fees makes competition largely ineffective. AT&T won’t let iPhone users run VoIP services over its broadband network, and Apple won’t let any other carrier connect to the iPhone, so iPhone users who want VoIP are stuck. For many of the Verizon users outraged by the company’s hindering their political message, changing carriers would mean paying early termination fees and buying new handsets.

Network neutrality rules will help. The ISPs and carriers no doubt will make the same bat-and-ball argument they have in the past: they built the networks, they own them, and they can run them as they please. In fact, though, the broadband networks could be viewed as a semi-monopoly, and we often take measures to ensure that privately owned monopolies treat their customers fairly.

But let’s be realistic. Although network neutrality rules will look good on paper, they will be frustratingly hard to enforce. The Chairman proposes to evaluate alleged violations “as they arise, on a case-by-case basis.” To anyone who has spent time around the FCC, this is the formula for a slow and expensive process. An innovator with novel content who runs afoul of discrimination by the broadband ISPs will not often have the time and money to litigate against a deep-pocket telephone or cable company.

Network neutrality rules may deter some of the worst abuses. But they will not bring back the anything-goes character of the early Internet. Anything went, in those days, because control was physically impossible. Now that a few companies do have control – or at least the capacity for control – all we can do is tell them not to use it. That may not be enough.

Network Neutrality: The Chairman Sets A Course

Genachowski announces plans to expand, codify Network Neutrality Principles

In a speech this morning, FCC Chairman Julius Genachowski announced his intention to initiate a proceeding looking to the adoption of new rules designed to preserve and enhance the “openness” of the Internet, in accordance with the principles of “network neutrality.” (You can read the speech here or watch it being delivered here.) While the Chairman’s support for a so-called “Fifth Principle”, prohibiting discrimination by Internet service providers, was widely anticipated, he also made the surprising announcement of a “Sixth Principle” requiring broadband Internet service providers to be transparent about their network management practices.   A Notice of Proposed Rulemaking, to be issued in the near future, will certainly precipitate a hotly contested battle over the nature of “discrimination” and “reasonable network management.” 

Fifth and Sixth Principles? What are the first Four? Back in a different Internet era (2005), the FCC took a tentative first step in addressing the issues of Network Neutrality with its Internet Policy Statement (“IPS”). That laid out four “principles” designed to “preserve and promote the open and interconnected nature of the public Internet”. Specifically, the FCC stated that consumers are entitled to:

  • access the lawful Internet content of their choice;
  • run applications and use services of their choice, subject to the needs of law enforcement;
  •  connect their choice of legal devices that do not harm the network; and 
  • competition among network providers, application and service providers, and content providers.

Two elements of the IPS helped bring us to today’s announcement.

First, the IPS acknowledged the need for Internet service providers to engage in “reasonable network management” on their networks to minimize congestion and to limit illegal activities on the Net. Second, the FCC chose to give itself maximum flexibility by announcing only “policies”, rather than rules, in light of the rapidly developing nature of the Internet and the market for Internet services. This choice would come back to haunt the FCC in its first major network neutrality enforcement action. In a 2008 Order, the FCC held that Comcast’s practice of blocking consumers’ use of peer-to-peer applications violated the principles of the IPS. The Commission required Comcast to alter its network management techniques, and make its new techniques known to subscribers. While Comcast claimed to have already complied with those requirements, it nonetheless appealed the FCC’s Order to the D.C. Circuit, arguing that the Commission lacks the authority to regulate Internet traffic generally, and specifically with use of “policies” rather than “rules.” Comcast’s appeal is still pending – the FCC’s brief to the Court was filed today – and no decision is likely until the first part of 2010, at the earliest. (For some history on the Comcast dust-up, read our previous post here.)

One motive for the Chairman’s launch of a new proceeding may be to beef up the FCC’s enforcement abilities by enacting actual rules, in case the Comcast Court holds that “policies” alone just don’t cut it.  And the proposed “Sixth Principle” seems designed to prevent Internet service providers from engaging in discrimination disguised as traffic management, as Comcast may have done. Still, there will be serious debate as to the level of “transparency” that best balances consumer interests with legitimate operator requirements for network security and prevention of harmful or illegal use of the Internet.  

The debate will be even more heated over the proposed rule embodying the “Fifth Principle” of non-discrimination.  As summarized by the Chairman today, “broadband providers cannot discriminate against particular Internet content or applications.This means they cannot block or degrade lawful traffic over their networks, or pick winners by favoring some content or applications over others in the connection to subscribers’ homes. Nor can they disfavor an Internet service just because it competes with a similar service offered by that broadband provider.” But even the Chairman acknowledged that the inquiry will reveal difficult policy issues.  For example, what if a consumer wants to use an application that maximizes the through-put and thus the quality of streaming music or video, but that application reduces the quality of the consumer’s other Internet applications while in use? Should this be prohibited “discrimination,” even if it is openly chosen by the consumer? One could easily answer “no.”

Similarly difficult questions will be triggered regarding the FCC’s legal authority to regulate an “information service” such as broadband Internet. There will be complex technical issues involved in defining “reasonable network management.” And, in light of the core role of the Internet in personal and political speech, First Amendment issues could get a rigorous work-out. But, as Bruce Springsteen has sung, “sooner or later it all comes down to money,” and that’s what the real battle will be fought over.

Some will argue that heavy regulation of Internet operations threatens the current business models under which large ISPs invest the funding necessary to expand and maintain a high-speed network. Large Internet application and content providers, as well, have their own marketing and financial interests in how traffic is transmitted. Many of these parties will argue that innovation in the network requires the government to keep its hands off. But the Chairman has already anticipated these arguments. He argued in his speech that truly transformative innovation has historically come from small entrepreneurs operating on the “edges” of the Internet. Non-discrimination is required, according to the Chairman and his supporters, in order to make possible the next Facebook, eBay or YouTube. 

Things have already begun to move quickly after the Chairman’s speech:  the Republican Commissioners, McDowell and Baker, have already fired back their critique of the Chairman’s approach.  (You can read it here.)  They express concerns that “factual and legal conclusions may have already been drawn” prior to the release of the NPRM.  They also stress their views that rules should not be based merely on “anecdotes” of problems, and that innovation and investment need to be protected in the core of the network, as well as at the edges. It appears that the battle is on!

The Commission is to be commended for opening up the debate, and making it accessible through new media. Check out the FCC’s new web site at www.openinternet.gov, which contains a video blog from the Chairman and space debating the issues. But even the best technology will not, by itself, yield easy answers to complex questions.

Apple to FCC: "No Answer" Doesn't Mean "No"

Apple, AT&T answer FCC inquiry about rejection of Google Voice

We reported here on the FCC’s requests to Apple and AT&T, the iPhone maker and service provider, asking why Apple had rejected an iPhone App called Google Voice. This provides access to a range of advanced voice features free of charge, in some instances bypassing services that AT&T charges for. The FCC also wanted to hear Google’s side of the story.

The answers came in several days ago, and we have been mulling them over ever since. (Okay, we did some of our mulling at the beach.)

Apple has not actually rejected Google Voice, it says. But neither has it accepted Google Voice. Rather, Apple continues to study the application.

Over 95% of applications are approved within 14 days of submission, so this one must fall in the other five percent. Most non-approvals occur because the program crashes or fails to function properly, according to Apple, but somehow we doubt Google submitted buggy code. Other submissions are rejected for sexual or violent content, also not a factor here. Apple’s problem with Google Voice, rather, is that the application “appears to alter the iPhone’s distinctive user experience” by, for example, handling voice mail and contact lists differently.

While it makes up its mind, Apple generously invites Google to put the application on other, non-iPhone platforms “and let consumers make their choices.” Apple apparently misses the irony. If it truly favored consumer freedom, it would let customers include Google Voice in their choice of user experiences on the iPhone.

AT&T, for its part, claims no involvement in Apple’s decision (or failure to make one) regarding Google Voice. But AT&T is equally irony-challenged. Much of its response (a) touts the benefits of wireless competition, while (b) defending AT&T’s arguably anticompetitive policy of blocking VoIP services on its broadband network. The response is surprisingly frank about the rationale. VoIP users run up fewer minutes of voice service. AT&T needs the revenues from voice minutes to pay back the subsidy that lets consumers buy the iPhone at an artificially low price, which in turn has attracted many new customers to AT&T’s network (and billings for voice minutes).

Here’s an idea: a wireless network that offers its users maximum choice, and charges only for services actually selected and delivered. No limitations on handset applications; no handset “subsidies” recovered through excessive monthly charges. The wired phone system once had carrier-imposed equipment subsidies and service restrictions. Their removal by the FCC triggered the current telecommunications revolution and helped to produce the Internet. Maybe it’s time to try the same approach for wireless services as well.

Google’s response to the FCC on Google Voice might be interesting and helpful, but we will never know. Except for a glowing account of the advantages of Google Voice and Android, a Google-supported operating system for wireless phones, public copies of the response are heavily redacted, especially as to communications between Google and Apple about getting Google Voice approved. Again, the irony is hard to miss. Google has the legal right to redact information that it thinks might unfairly help its competitors. But as a company that has long championed openness on the Internet, it might have been more open with information that affects not only Google and Apple, but all of us interested in making the best use of communications resources.

FCC Examines Exclusion of Google Voice from iPhones

Letters sent to Apple, AT&T in expansion of “network neutrality” inquiry

The FCC recently expanded its “network neutrality” inquiries into an ongoing contretemps among three giants of consumer technology: Google, Apple, and AT&T. The dispute follows Apple’s disallowing Google Voice service on its iPhone handsets, possibly at the request of AT&T, the carrier having exclusive rights to the iPhone.

Network neutrality is the idea that communications customers, such as Internet and cell phone subscribers, should be able to use all lawful services and hardware without interference from the provider. It sounds simple enough, but in practice the issues get a little complicated. See here and here and here. Back in 2005, the FCC enunciated four “principles” of network neutrality, but has not adopted actual rules on the subject.

Wireless phone providers have traditionally favored the opposite of neutrality: a “closed” model in which the same company supplies over-the-air service, sells the handsets, and picks the services users can access. If you obtain cell phone service through one of the major carriers – Sprint, AT&T, Verizon, or T-Mobile – you probably bought your phone from them, too. And if you use the phone for on-line banking and certain other lucrative services, chances are the company you’re dealing with pays the carrier for the privilege of having your business.

The FCC has two proceedings underway that could eventually challenge this kind of arrangement.

One started with a petition from Skype, which provides free or inexpensive phone service over the Internet.  Most wireless carriers do not allow access to Skype over their handsets, because the customer could call via Skype instead of running up expensive minutes. The other proceeding began with a group of small rural cell companies asking the FCC to ban exclusive arrangements for handsets. Because such deals limit the most desirable handsets to the majors, the small carriers lose business to customers who want the latest in hardware. So far, though, the FCC has only invited public comment on these requests, with no hint as to whether it might act.

The newest wrinkle comes out of Apple’s decision against Google Voice.

Broadly speaking, Google Voice brings phone service into the Internet Age. A subscriber receives a new phone number, local in any region of the subscriber’s choosing. Calling that number rings all the customer’s phones, wherever they are: office, home, cell, etc. Different callers can be automatically routed to different phones, or forwarded selectively to still other phones, or fed different voice mail greetings, or given different rings, or blocked altogether. All the voice mails from all the phones end up in one place, where they can be read in printed form, like emails, or listened to online from anywhere. There are provisions for setting up conference calls, and for recording phone conversations for online storage. Parallel features cover SMS messaging.

And calling anywhere in the United States is free.

Apple rejected Google’s application to sell Google Voice through the App Store, the only legal source of iPhone software. And Apple revoked previous App Store approvals for third-party software intended to work with Google Voice. Early speculation supposed that Apple had acted at the request of AT&T, whose network uses the iPhone, but press reports say that AT&T has denied any involvement. Apple’s motivation for stirring up its customers remains unknown.

Now the FCC has sent letters to all three companies: Google, Apple, and AT&T, asking Apple and AT&T which one of them made the decision to bar Google Voice, and why, and whether Apple and AT&T offer competing applications. The letter to Google asks for details on how Google Voice works, and for a summary of the discussions with Apple and AT&T.

What the FCC will do with this information is not clear. Also not clear is whether it will even get the information. Or whether it has the authority to ask. Back in the 1976 Computer II proceeding, the FCC relinquished jurisdiction over information flowing through communications systems. It would regulate the lines, it then decided, but not the bits and bytes moving over them. (In the broadband environment, it has since deregulated even the lines.) With only limited exceptions for certain forms of VoIP , the FCC has indeed kept its hands off Internet applications. Apple and AT&T have to concede the FCC’s authority over wireless voice service, and may even acknowledge some control over handsets, but may well argue that Computer II put optional software applications beyond Commission reach.

For those of us who enjoy corporate conflict as a spectator sport – over-muscled, over-equipped gladiators struggling in the arena – the Google-Apple-AT&T spat is a welcome addition to the long-running Google-Microsoft and Apple-Microsoft events. “The enemy of my enemy is my friend,” the saying goes. But now the two biggest enemies of Microsoft have become enemies themselves.

Pass the popcorn, and keep your scorecard ready.

Broadband Stimulus 101: FYI - NTIA/RUS BIP/BTOP FAQ'S

Feds clarify frequent questions about stimulus programs, including application of “net neutrality” considerations

You think you’re the only one with questions about the broadband stimulus programs? Guess again. There are enough questions flying around that the Feds have posted, with a minimum of fanfare, a 13-page set of Frequently Asked Questions regarding the BTOP and BIP programs. Check them out here

We have been concerned with a question about the reach of the net neutrality requirements imposed on BTOP and BIP awardees. 

FAQs to the rescue! 

Section VI.A of the FAQs asks and answers:

Q:        Do the nondiscrimination and interconnection requirements apply to the portions of the applicant's network that are not funded by BIP or BTOP?

A:        No

(A brilliantly concise answer which we applaud.)  Logic appears to prevail.

But there is more:

 Q:        Is last mile infrastructure subject to the same nondiscrimination and interconnection obligations as middle mile infrastructure?

 A:        Yes. The same nondiscrimination and network interconnection obligations apply to both Last Mile and Middle Mile projects. (See NOFA section V.C.2.c.) For BTOP only, Broadband Infrastructure applications will be evaluated on the applicant’s commitment to exceeding the minimum requirements. Section VII.A.2.c of the NOFA (“Project Benefits”) explains how Last Mile and Middle Mile applicants may exceed the minimum requirements, based on the different technical characteristics of the two types of projects.

As straightforward as these answers seem, the practical aspects of compliance may not be so easy to resolve. After all, if one or more parts of a network are subject to net neutrality obligations, it may be difficult to sector the network so as to be net neutrality-compliant only in funded portions, while still retaining operational flexibility in non-funded portions. And conceptually, it might be challenging to justify such a bifurcation.

Also, as our colleague Mitchell Lazarus has previously noted, it may be hard to tie down precisely where in a particular network a net neutrality violation actually occurs. Thus, any network with any BTOP/BIP-funded component could theoretically be pulled into a net neutrality battle.

So while the FAQs give concise, logical answers, the practical and conceptual realities are less clear.

Also less clear is the FAQs’ authoritative significance, if any. The FAQs don’t say where they came from. Federal agencies act through the issuance of formal orders, notices and the like, pursuant to the Administrative Procedure Act and other statutes. In their current posture, the FAQs, while no doubt intended to help clarify matters, may not have any binding effect on RUS, NTIA, the FCC, or anybody else. Trust, but verify. Or, better – first verify, then trust.

"Reverse" Net Neutrality -- Balkanizing the Web?

Should Internet service providers (ISPs) be allowed to give faster service to certain content, in exchange for a fee? That question started the debate over network neutrality. It has no clear answer, as yet, and other questions have sprung up in the meantime. But now we have the original question in reverse – with the money flowing in the opposite direction.

An online video service called “ESPN360,” a spinoff from the ESPN cable channels, sends more than 3,500 sporting events over the Internet each year. But not to everybody. ISPs have to sign up and pay for the content. Not all do. If your ISP subscribes (or if you get Internet service on a U.S. college campus or military base), you have access to the content; otherwise, not.

Traditional pay sites, from the Oxford English Dictionary to pornography vendors, sell directly to the end user, who typically exchanges a credit card number for password-protected access. Not everyone receives the service, but everyone has the option. Not so with ESPN360. The decision as to that content rests not with the individual subscriber, but with the subscriber’s ISP.

The existence of this business model means we can no longer talk about “the Internet,” as though it were one thing. Now there are at least two Internets: the one with ESPN360, and the one without. This is not the first instance of Internet fragmentation. We wrote earlier about different ISPs carrying different components of Usenet. But all of Usenet is still available to everyone through third-party services. ESPN360 is different. Those with the wrong ISP have no way to reach it.

Back in 2005, the FCC issued a policy statement that promised consumers access to "the lawful Internet content of their choice." That worthy goal may be unenforceable as to ISP-purchased services like ESPN360. The FCC has no authority over ESPN as an Internet content provider, and it cannot force an ISP to pay money for a service it does not want.

The answer to this kind of problem is supposed to be competition. In principle, a consumer who wants ESPN360 can simply switch to an ISP that offers it. But in practice, the FCC has made that difficult to do.

In the dark ages of dial-up Internet access, the phone companies offered ISP service, but were required to open their facilities to competing ISPs. That set of rules, collectively called “Computer III,” never quite worked as intended. But even so, there were thousands of ISPs. A dissatisfied customer could move easily from one to another.

Things are different in the broadband environment, following two FCC decisions that largely ended competition among broadband ISPs. The first was a 2002 ruling that deregulated cable modem service. The second, coming a few weeks after the U.S. Supreme Court upheld the first, did the same for DSL service. Cable companies and phone companies breathed a sigh of relief. They could provide broadband Internet access without having to let other ISPs use their networks.

The large majority of residential broadband customers today receive their service through either a cable company or a phone company. Thanks to the FCC deregulation decisions, these people must also take the cable company or phone company as the ISP. Few have any other choices. The high cost and relatively low speed of satellite service limits it mostly to remote areas. Fixed wireless and broadband-over-power-line have limited availability. Mobile broadband wireless is expensive and relatively slow.

Some customers live in areas with only one broadband provider. They have no choice at all. For most others, the only alternative to their present ISP is a switch from cable modem service to DSL (or fiber) from the phone company, or vice versa. But the change is rarely fast or easy. The old provider may charge early termination fees. The new provider will likely charge for its modem and for activation, and may demand a one- or two-year commitment. Waiting for the installer takes time. If the subscriber’s email address includes the name of the old provider, then changing providers turns off that address – a powerful incentive to stay put.

In short, most broadband consumers are at the mercy of their present ISP. If the ISP chooses not to provide certain content, the consumer is unable to receive it.

ESPN is a TV content provider that sells video channels to cable systems. For the company to replicate the same business model on the Internet is a natural step. But its doing so threatens the vision that has made the Internet such a strong force: all the information on the planet, all of it available to everyone. ESPN's approach, if widely adopted, would result in many little Internets, a different one for every ISP. That might make business sense for the content providers. But it would seriously disserve everyone else.

Thanks to John Chapin for bringing this issue to my attention.

Comcast vs. Network Neutrality - Comcast Replies

Back on January 20, we noted here that the FCC had asked Comcast to explain its VoIP service. Comcast had earlier promised that its Internet service would not discriminate among types of content. Its later advertising said that network management efforts might slow other forms of VoIP – but not VoIP  provided by Comcast. The FCC demanded to know how Comcast could protect its own VoIP service without discriminating against other VoIP providers.

Comcast has now replied.

Comcast told the FCC that its VoIP “Comcast Digital Voice” (CDV) service does not run over its high-speed Internet service – or over the public Internet – and so is not subject to its promises concerning network management. Comcast notes that its CDV customers need not even subscribe to its high-speed Internet service. Because other providers’ VoIP does use the public Internet, Comcast says, those services can be affected by overall traffic slow-downs.

Comcasts’s letter, while saying how CDV does not work, discloses almost nothing about how it does work. That reticence may relate to the other issue raised in the FCC’s inquiry: whether CDV should be subject to telephone-style regulation. The more Comcast argues that CDV is not an Internet service, and instead runs over its own separate facilities, the more CDV looks like “telecommunications service,” a status that would trigger additional rules, and possibly payment obligations as well. Comcast insists that question is outside the scope of network management issues, and is properly under consideration in other FCC proceedings.

The Comcast letter is here.

Comcast vs. Network Neutrality - The Sequel

Comcast just can’t get the hang of this network neutrality thing.

Last summer, the FCC chastised Comcast, a cable and Internet provider, for selectively blocking certain kinds of customer Internet traffic – specifically, services that threatened competition to its cable business. We reported on the incident here, and followed up here and here. Going forward, said the FCC, Comcast was free to manage traffic on its network, but not in ways that discriminate based on the customer's content.

Comcast responded with a reasonable plan. In essence, it gives a customer's data packets lower priority when the neighborhood system is danger of overloading, and that same customer has been running at near-capacity data rates for at least 15 minutes. The temporary priority shift gives other people's data a chance to get through. Comcast warned that a customer running voice-over-Internet (VoIP ) along with high-volume traffic runs the risk of “choppy” sounding calls when the voice packets get shunted aside.

The plan seems in line with the FCC's requirements. A non-story. But for one small detail.

The Comcast website tells customers they can preserve voice quality by subscribing to Comcast's own VoIP service, while using those other VoIP providers can result in degradation. This looks like the kind of discrimination Comcast promised to avoid. It caught the eye of the FCC, which wants Comcast to justify the disparate treatment. With a touch of sarcasm, the FCC also asks how Comcast’s own VoIP service affects network congestion differently from other Internet traffic.

Comcast made additional trouble for itself by describing its VoIP service as “facilities-based.”   The marketing intern who wrote the copy probably didn’t know it, but this is a code word. Along with other factors, it can trigger a requirement for very expensive payments to other carriers. (Just a reminder, people – show everything to your lawyers.) The FCC invites Comcast to rethink its explanation of how the service works.

Google vs. Everybody Else

Last year Google thrust itself into the network neutrality debate by promoting open-platform wireless handsets. Now it has reentered the fray from the other side.

“Network neutrality” has several competing definitions. Not surprisingly, parties to the argument tend to frame the question in ways that favor their own interests, with the result that people talk past each other.

Our own preferred view dates back to the origin of the controversy. The executives of two major Internet service companies announced they saw nothing wrong with giving some content providers faster service for a higher price. If Amazon.com, for example, were willing to pay the premium, its website would download faster than that of the local bookstore, and thus give customers a better experience, disadvantaging the local bookstore. Network neutrality, in our view, is the principle that says this is wrong – that Internet providers must treat all content providers equally.

Google once seemed to agree, at least in the wireless phone context. It urged the FCC to auction a block of spectrum in which customers could use any compliant handset and access any lawful service. (Elsewhere in the spectrum, cell-phone providers can and do limit handsets and services to those of their partners.) Google subsequently participated in developing the “Android” operating system that makes it easy for independent developers to offer new applications for mobile phones.

This week, though, Google made a controversial announcement. It proposed to locate its own servers on the premises of major broadband Internet providers, with the goal of speeding service to their subscribers.

The Wall Street Journal on December 15 accused Google of changing sides on network neutrality.

Other companies, though, have long collocated servers with the broadband providers. Akamai, Limelight, and others provide a service called “edge caching,” which locally replicates the content of major websites to allow faster access by subscribers. The practice is not widely seen as a violation of network neutrality. For one thing, edge caching is necessary to prevent logjams at popular sites. Today’s Internet could not function without it. For another, the companies that provide edge caching compete with each other in signing up as many websites as possible. Smaller websites work fine without edge caching; larger ones have a choice of providers. Everyone benefits.

Google now says it only wants to do what Akamai and Limelight and the others have been doing for years.

But there is a big difference. Akamai et al. do not manufacture their own content. They merely help with distributing the content of others. Google, with its search engine, YouTube, and dozens of other operations is probably the biggest single content provider on the planet. It has no incentive to share its edge servers with competitors. Despite the company’s protestations, Google’s plans seem to exemplify a fundamental violation of network neutrality.

So far, though, Google faces no legal barriers. Nothing in the FCC rulebook prohibits discrimination in broadband Internet services. The FCC did announce four Internet “principles” back in 2005, but never adopted them as rules, so they may not be enforceable. (We will find out, now that Comcast has appealed the FCC’s use of the principles in ordering it to alter network management practices.) But even then, Google’s plan may not amount to a violation. The most relevant principle just entitles consumers to “competition among network providers, application and service providers, and content providers.” So long as Google is not the only provider on the block, it may be able to discriminate with impunity.

But it can’t do that and still keep saying it supports network neutrality.

Should We Regulate The Internet? Should We Care?

Once upon a time, boys and girls, there were no big Internet sites like Google and Ebay, and no big Internet service providers (ISPs) like Comcast and Verizon.  People accessed the Internet through thousands of small ISPs operating out of dorm rooms and coat closets.  The sites they reached were mostly small and home-grown.  Users formed networks serving all kinds of interesting and off-beat interests.  Pornography, the universal early adopter for every new communications technology, flourished as well.

The FCC had resolved back in 1976 not to regulate “enhanced services,” a decision that applied to the later-arriving Internet.  That was just as well, because the emerging Internet was so hopelessly decentralized that any effort at regulation would have been ludicrous.  Users operated with complete freedom, beyond the reach of any authorities that might have cared.

No more.  A small number of interests now run the facilities that most consumers need to access the Internet.  As control continues to centralize, regulation becomes more feasible.  But is it desirable?

Over the last few years, the FCC reiterated its 1976 hands-off decision as to facilities used for broadband Internet access.  The current question is whether it should now step back in – not to control content, which would be unconstitutional, but to maintain free access to content.  Four distinct viewpoints have emerged:

  • Old-time users and their younger allies seek to preserve the Internet’s original wide-open, anything-goes character at all costs – even if that (paradoxically) takes regulation.
  • Big ISPs invoke the Internet’s original wide-open, anything-goes character to fight Government regulation that might limit their profit opportunities.
  • Operators of big commercial websites support or oppose regulation as needed to ensure unimpeded (or preferred) delivery of their own content to their customers.
  • Law-and-order interests favor even intrusive regulation to thwart use of the Internet for illegal activity, ranging from child pornography and terrorism to copyright infringement.

Two case studies illustrate the problem.

Comcast vs. BitTorrent

Comcast is the largest cable TV company and the second largest ISP in the United States.  Among other services, the cable business offers video-on-demand (VOD) for a fee.

BitTorrent is a popular Internet application that helps users share very large files, such as movies.  As a group, people who obtain movies for free with BitTorrent are probably less likely to pay for Comcast’s VOD.

Comcast programmed its ISP servers to peek into subscribers' communications looking for BitTorrent packets.  When they found one, the servers sent out forged signals that instructed both ends of the communication to hang up.  Comcast put out successive denials and explanations, all later shown to be untrue.

The FCC suspected that Comcast was interfering with BitTorrent to protect its VOD service from competition, and ordered it to stop all discrimination based on content.  By then, Comcast had already done so.  But it nonetheless appealed the order in federal court, questioning the FCC’s authority over its internal network management practices.  Since the FCC had not fined Comcast, and the company was already in compliance with the FCC’s order, the appeal was purely a matter of principle.

Even so, Comcast may have a point.  Possibly two points.  The FCC gets all of its authority from Congress via particular statutes.  Ordinarily an FCC order disposes of the authority question by citing the relevant statute.  But the Comcast order, lacking a statute to cite, struggles through a dozen single-spaced, heavily footnoted pages to establish its authority.  Comcast is betting the court won’t buy it.  Moreover, the FCC does not claim that Comcast violated any specific regulation, there being none on this topic.  The FCC does point to a published policy statement on broadband services under which, among other things, consumers are “entitled to access the lawful Internet content of their choice,” and “to run applications and use services of their choice.”  But the FCC did not follow the procedure needed to put this language into an enforceable rule.  Although Comcast’s actions may have been anticompetitive, discriminatory, and just plain unfair, they might not have been illegal.  And the FCC has still not proposed rules to prohibit similar future conduct by others.

alt.no-more-usenet

An early Internet application that long predated the World Wide Web, Usenet is hundreds of thousands of discussion groups covering every imaginable human activity (and also some others).  The groups are organized into “hierarchies” with names like comp.*, rec.*, soc.*, and dozens of others.   ISPs have traditionally made Usenet available as part of the service.

Eight of the major hierarchies – the so-called “big eight” – have loose rules for starting new groups.  A ninth big hierarchy, alt.* does not.  Anyone can start an alt.* group.  Many have.  Roughly 100,000 such groups exist, ranging from alt.history.ocean-liners to alt.swedish.chef.bork.bork.bork.  Some concern out-of-the-way sexual interests.  A few dozen are suspected of having been used to distribute child pornography.

That activity is unlawful.  Enforcement authorities could have used appropriate procedures to shut down the offending groups, plus any new ones that pop up.  But they did not.  Instead, the New York attorney general called in the large ISPs and asked them to voluntarily block the entire alt.* hierarchy – including the 99.9% that is fully legitimate.  AT&T, Comcast, RoadRunner, Sprint, Time Warner, and Verizon all complied.  Verizon went further, and blocked all of Usenet except the big eight.  Comcast went further still.  It shut off its subscribers from all of Usenet.

Of course no large company wants to be seen as aiding child pornography.  Yet subscribers have every right to the vast majority of Usenet that deals with other material.  For an attorney general or a legislature to order the complete shut-down of alt.* would be unconstitutional.  The same action, if carried out voluntarily by an ISP, would seem contrary to the Comcast ruling.  Yet, the FCC’s response to the widespread blocking of Usenet, affecting a large fraction of U.S. Internet users, has been . . . nothing.

More Regulation, Fewer Restrictions

The Internet’s inventors thought they had built something so decentralized as to be immune to authoritarian control.  They failed to foresee access becoming concentrated into a handful of large companies, or those companies caving so easily to law-enforcement authorities making improper requests.  To achieve the dream of the unregulated Internet – everyone able to access content posted by anyone on the globe – the FCC may have to step in and regulate after all.

Comcast Defers to, Defies, Derides FCC Order

Comcast has both obeyed and appealed an FCC rule relating to its Internet access management.

A month ago, the FCC cracked down on Comcast for selectively interfering with the communications of customers using BitTorrent, a peer-to-peer (P2P) application.  Comcast said it was entitled to take action because BitTorrent users were hogging bandwidth.  The FCC disagreed.  Comcast singled out BitTorrent users, it said, regardless of the actual bandwidth usage, and even at times and places where the network had plenty of capacity.  Hinting at darker motives, the FCC noted that BitTorrent and other P2Ps make available high-quality video in direct competition to Comcast's cable service.

The FCC did not impose a fine on Comcast, but ordered it to stop discriminating based on users' content (Comcast said it already had), and to disclose any new network management practices it planned to use instead.

Last week Comcast announced a cap on residential users of 250 gigabytes per month.  This is a lot of usage, attained by under one percent of subscribers.  And even those busy browsers will not be cut off when they reach the cap, or even be charged more.  Comcast will just ask them to slow down.

Comcast thinks it addressed the anticompetitive issue by applying the cap without regard to which applications generate the usage.  But its executives may still be snickering into their coffee.  In reality, the only way to hit 250 gigabytes monthly is to download a lot of video.  Emails and pictures of the kids just won't do it.  It takes a few DVD-quality movies a day, on average, or a long stretch of high-definition video each day.  Somebody watching all those movies and TV over the Internet is probably not also subscribing to cable video service.  So Comcast's usage cap may still be hindering its competition.

Yet Comcast is still not satisfied.  Yesterday it appealed the FCC's order curtailing its previous actions against BitTorrent users.  Its ground for appeal?  The FCC never adopted a rule that specifically prohibits Comcast's admittedly discriminatory practices.  All the FCC has to go on is a broadly-worded policy statement.  Without a rule, Comcast seems to say, the FCC has no authority to take any action whatsoever.

All this is just delaying the inevitable.  Comcast has already complied with the order it is appealing, so presumably it is appealing as a matter of principle.  The FCC can make the principle moot as well, just by adopting a rule.  We should all have better things to do than continuing to litigate a case long after it is over.

FCC Shakes Stern Finger at Comcast

Today the FCC determined that Comcast deliberately interfered with its customers' Internet usage by selectively blocking peer-to-peer (P2P) applications, particularly BitTorrent.  "In essence," said the FCC, "Comcast opens its customers' mail because it wants to deliver mail not based on the address on the envelope but on the type of letter contained therein."  The FCC noted a possible anticompetitive motive -- BitTorrent and other P2P applications can let users watch high-quality video they might otherwise have to pay for on cable TV systems, such as Comcast's.

The FCC rejected Comcast's argument that its actions were necessary to manage traffic on the network, because Comcast:

  • interfered with even low-volume P2P users;
  • blocked traffic at times of the day when congestion was not a problem;
  • targeted neighborhoods not experiencing congestion; and
  • tolerated very high bandwidth customers who did not use a disfavored application.

Moreover, Comcast repeatedly lied about its practices, according to the FCC.  First, it denied any responsibility for its customers' connection problems, then admitted targeting P2P traffic -- but only during peak congestion, it said -- and finally admitted that it blocked P2P at all times of day and regardless of congestion levels.

And yet, in the end, the FCC did little more than issue a warning.  Comcast is required to do three things:  (1) give the FCC details of its discriminatory practices, (2) explain how it will stop those practices, and (3)  tell its customers and the FCC about any new practices it will use instead.

The FCC took the occasion to announce it would oversee "federal Internet policy" in resolving any other claims of discriminatory network practices.  After seeing the penalties imposed on Comcast (i.e., none), we doubt that other network operators are losing much sleep.

In fairness, though, the decision does plant a flag on the beach.  Since the 1970s, in the pre-Internet days when people began sending large amounts of data over telephone lines, the FCC has consistently forborne from regulating any aspect of transmitted content.  A series of decisions over the past few years explicitly extended that policy to cable, DSL, wireless, and broadband-over-power-line, exempting the providers of each from the traditional forms of regulation that would have blocked Comcast's methods.  Network operators might have thought themselves free to run their systems as they wished.  Today, though, the FCC put an important limit on that freedom:  operators may not discriminate against categories of content.

But another question, equally important, remains unanswered:  can an operator discriminate in favor of certain users?  That is the issue that launched the "network neutrality" debate -- whether an Internet service provider can move some sites to customers faster than others, in exchange for money.  Considering that today's decision went on a 3-2 vote, and that composition of the Commission may well change after the election, we are not making any predictions.