Based on certain questions the FCC asks in the Notice of Proposed Rulemaking (NPRM), we are concerned that the FCC (or at least Chairman Pai and the authors of the NPRM) appears to lack a fundamental understanding of what the Internet's technology promises to provide, how the Internet actually works, which entities in the Internet ecosystem provide which services, and what the similarities and differences are between the Internet and other telecommunications systems the FCC regulates as telecommunications services.

This false distinction between “Internet access service” and “a distinct transmission service” is utterly ridiculous and completely ungrounded from reality. As the FCC would have it, there is some sort of “transmission” that is separate from the Internet that ISPs provide access to.

The FCC needs to realize that the Internet is nothing more than transmission between interconnected machines. The FCC’s understanding of the Internet borders on the mystical, as if the Internet itself were some vaguely defined other realm that an ISP opens a portal to. But there is no other realm, only a collection of networks, including the ISP’s networks. There’s no Internet separate from accessing the Internet; the Internet is just machines accessing each other. It’s worrying that such a mischaracterization may be the basis of a federal regulation that will have wide-ranging effects.

The FCC Still Doesn’t Understand How DNS Works

Besides not understanding how Internet access works, the FCC also has a troublingly limited knowledge of how the Domain Name System (DNS) works—even though hundreds of engineers tried to explain it to them this past summer.

Here’s the thing: “address translation” and “storage and retrieval” are fundamental parts of any software implementation; these implementation details have little to do with the service that a system provides. DNS is a fundamental piece of the transmission puzzle. Code translation is a general purpose technique. Every machine translates IP addresses from machine-order to network-order; that doesn’t make every translation point a gateway.

But that’s hardly the case. Most users don’t know what DNS is, let alone expect that their ISP provides it. As for users who know enough about DNS to have expectations about who provides it, many choose to use third-party services for their speed and value-add functionality separate from the name translation service. ISPs choose to point users to their own DNS service; they could just as easily point to a third-party service instead of their own, and users would rarely ever notice a difference.

The FCC Still Doesn’t Understand How Caching Works

The FCC is also confused on the matter of caching. Like DNS, it treats caching as if it were some specialized service rather than an implementation detail and general-purpose computing technique. In its discussion of Web caching services, which the earlier Notice of Proposed Rulemaking asked for commentary on, the FCC included an irrelevant line about the general computing technique of caching which is usually used as part of implementing a DNS service. This implementation detail certainly has no bearing on either Web caching or DNS as services, and shows how little it understands these services on the whole.

Although the FCC tries to claim that offering web caching is an integral part of the functionality that ISPs provide, this is not the case. In fact, Sonic, a San Francisco-based ISP, does not run web caching equipment for its customers (although they do host a number of boxes from non-affiliated CDN platforms, including the Google Global Cache, Netflix OpenConnect, and Akamai—but they don't operate those boxes).

And if the FCC doesn’t understand the Internet in general, it understands mobile telephony and broadband Internet access even less.

The FCC Doesn’t Understand How the Phone System Works

The FCC’s apparent understanding of the phone system seems to be stuck in the days of rotary phones. For users on a modern American network, voice calling is just one of many applications that a phone enables. If the user has poor signal, that voice call might travel at some point over the circuit-switched PSTN, but it might also never leave a packet-switched network if it’s sent over VoIP or LTE/EPC.

The FCC’s Plan to Kill Net Neutrality is Based on Faulty Technical Premises

There are at least two possible explanations for all of these misunderstandings and technical errors. One is that, as we’ve suggested, the FCC doesn’t understand how the Internet works. The second is that it doesn’t care, because its real goal is simply to cobble together some technical justification for its plan to kill net neutrality. A linchpin of that plan is to reclassify broadband as an “information service,” (rather than a “telecommunications service,” or common carrier) and the FCC needs to offer some basis for it. So, we fear, it’s making one up, and hoping no one will notice.

We noticed. And we need your help. The one group Chairman Pai might listen to is Congress—after all, Congress has oversight authority over the FCC. If enough members of Congress signal to Pai that his plan will cost them at the ballot box he might just get the message—and reverse course before it’s too late.

In 2018, California established the gold standard of what states should be doing on net neutrality by passing a model law for other states to copy. So, naturally, that makes the job of any legislator truly interested in protecting net neutrality pretty easy: just copy and paste. But that...

The Electronic Frontier Foundation recently joined several California-based ISPs, tech companies, non-profits, and local governments to commend Governor Newsom for adopting a “Broadband for All” vision. But simply saying “broadband” without a clear eye towards the future risks having government policies adopt infrastructure plans that work in the short run...

Ever since the FCC repealed net neutrality protections in 2017, we’ve been fighting to return as many protections to as many Americans as possible. In 2019, the battles in the courts and Congress both kept those committed to a free and open Internet very busy. Mozilla v. FCC Takes Center...

Users, advocates, and service providers have been waiting for months to find out whether an appellate court will bless the Federal Communications Commission’s effort to repeal net neutrality protections, and whether the FCC can simultaneously force the states to follow suit. The answer: yes, and no. Bound by its interpretation...

We pause this week to celebrate our longtime friend Gene Crick, a digital rights activist and former president of EFF-Austin, who passed away August 14 in Texas at age 73. Gene was a tireless advocate for free speech, a free, open, and inclusive Internet, and digital rights for everyone in...

When it comes to politics, in-person meetings make a huge difference. Just a few questions from constituents during town halls can show a representative or senator which issues are resonating with the residents of their district or state. Even if you’ve never met an elected representative before, showing up IRL...

As we head into the August, Congress will be on recess and most of your senators and representatives will be heading back to their home states. That means it’ll be easier for you to reach out and talk to them or their staff and ask them to act on important...