Home / Blogs

Is Defining Broadband by Speed a Good Policy?

I’ve lately been looking at broadband policies that have shaped broadband, and I don’t think there has been any more disastrous FCC policy than the one that defines broadband by speed. This one policy has led to a misallocation of funding and getting broadband to communities that need it.

The FCC established the definition of broadband as 25/3 Mbps in 2015, and before then, the definition of broadband was 4/1 Mbps, set a decade earlier. The FCC defines broadband to meet a legal requirement established by Congress and codified in Section 706 of the FCC governing rules. The FCC must annually evaluate broadband availability in the country—and the agency must act if adequate broadband is not being deployed in a timely manner. The FCC chose broadband speed as the way to measure its success, and that decision has become embedded in policies both inside the FCC and elsewhere.

There are so many reasons why setting an arbitrary speed as the definition of broadband is a poor policy. One major reason is that if a regulatory agency is going to use a measurement index to define a key industry parameter, that numerical value should regularly be examined on a neutral basis and updated as needed. It’s ludicrous not to have updated the speed definition since 2015.

Cisco has reported for years that the demand for faster speeds has been growing at a rate of about 21% per year. Let’s assume that the 25/3 definition of broadband was adequate in 2015—I remember at the time that I thought it was a fair definition. How could the FCC not have updated such a key metric since then? If you accept 25 Mbps download as an adequate definition of broadband in 2015, then applying the expected growth in demand for speed by 21% annually produces the following results.

Download Speeds in Megabits / Second
2015201620172018201920202021
25303744546579

This is obviously a simplified way to look at broadband speeds, but a definition of the minimum speed to define broadband at 79 Mbps feels a lot more realistic today than 25 Mbps. Before arguing about whether that is a good number, consider the impact of extending this chart a few more years. This would put the definition of broadband in 2022 at 96 Mbps and at 116 Mbps in 2023. Those higher speeds not only feel adequate—they feel just. Eighty percent of the homes in the country already have access to cable company broadband where a speed of at least 100 Mbps is available. Shouldn’t the definition of broadband reflect the reality of the marketplace?

We know why the FCC stuck with the old definition—no FCC wanted to redefine broadband in a way that would define millions of homes as not having broadband. But in a country where 80% of households can buy 100 Mbps or faster, it’s impossible for me to think this one fact doesn’t mean that 100 Mbps must be the bare minimum definition of broadband.

There have been negative consequences of this definition-based policy. One of the big problems is that the 25/3 Mbps speed is slow enough that DSL and fixed wireless providers can claim to be delivering broadband even if they are delivering something less. Most of the FCC mapping woes come from sticking with the definition of 25/3 Mbps. If the definition of broadband today were 100 Mbps, then DSL providers would not be able to stretch the truth, and we would not have misallocated grant funding in recent years. Stubbornly sticking with the 25/3 definition is what saw us giving federal broadband grants to companies like Viasat.

As long as we are going to define broadband using speeds, then we’ll continue to have political fights over the definition of broadband. Congress recently ran headlong into this same issue. The original draft of the Senate bill had proposed a definition of broadband as 100/100 Mbps. An upload speed set at that level would have prohibited broadband grants for cable companies, WISPs, and Starlink. Sure enough, by the time that lobbyists made their calls, the definition of upload speed was lowered to 20 Mbps in the final legislation. Congress clearly gave in to political pressure—but that’s the line of business they are in. But we’ve had an FCC unwilling to be honest about broadband speeds for political reasons—and that is totally unacceptable.

By Doug Dawson, President at CCG Consulting

Dawson has worked in the telecom industry since 1978 and has both a consulting and operational background. He and CCG specialize in helping clients launch new broadband markets, develop new products, and finance new ventures.

Visit Page

Filed Under

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

VINTON CERF
Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Comments

Todd Knarr  –  Oct 8, 2021 10:22 PM

I have to agree with you that “broadband” should be defined in terms of the normal speeds available to people and necessary for normal use of the Internet. I’d go with a standard that combined the speeds available to most people (I think the “what at least 80% of homes have available” standard sounds good here) and what the average usage of that 80% is when the connection is active (divide the total traffic by the time the connection has a non-negligible traffic rate). The latter is hard to calculate exactly on a per-user basis, but I’m guessing it could be reduced to a statistical calculation (my router’s traffic daemon tracks all the information needed, it’d just be a matter of recording traffic when the short-term rate on the WAN interface exceeds a set threshold).

I wrote a piece "Why You Shouldn't Believe Network Speed Tests" Karl Auerbach  –  Oct 19, 2021 4:56 PM

A while back I wrote a piece titled “Why You Shouldn’t Believe Network Speed Tests”

It also contains some suggestions about what kinds of metrics we do need to characterize network paths.

https://blog.iwl.com/blog/do_not_trust_speed_tests

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

Related

Topics

IPv4 Markets

Sponsored byIPXO

Brand Protection

Sponsored byAppdetex

Threat Intelligence

Sponsored byWhoisXML API

Cybersecurity

Sponsored byVerisign

Domain Names

Sponsored byVerisign

Domain Management

Sponsored byMarkMonitor