Predictably, as we get closer to actually adopting Title II for broadband, we see much scrambling about by folks who never seriously considered the question of how Title II would actually work because no one in the press or the opposition ever really thought it could get that far. Opponents of Title II, needless to say, describe a blasted bureaucratic Hellscape smothering broadband service with (to quote the latest missive from a bunch of House and Senate Republicans) “1000 active rules that are based on Title II, and 700 pages of the C.F.R.”
After 6 solid years of Republicans opting for the partisan politics of obstruction rather than engaging on substance, such ridiculous claims hardly come as a surprise. It’s also a rather silly argument given that the bulk of those rules address things that would not apply to broadband and that everyone — even Republicans — actually like: making sure 9-1-1 works reliably, fixing rural call completion problems, keeping track of phone reliability and phone outages during natural disasters, protecting the privacy of our phone calls and requiring providers to report data breaches, etc.
Still, even without deliberate efforts to muck things up and exaggerate things, I recognize that this whole “Title II” thing doesn’t happen every day and lots of folks have questions about what the heck does this all mean. As I (and others) have noted in the past, classification doesn’t have to be a big deal. To illustrate this, I will go back to the last time the FCC classified a service — automatic voice roaming in the wireless world — as a Title II service. As we will see, this took remarkably little effort. The FCC explicitly rejected the requirement to do rate regulation or a requirement to file tariffs with the prices and did not need to engage in any extensive forbearance. They just said “nah, we’re not gonna do that.” The final adopted rules are less than a page and a half.
I will also note that despite classifying automatic voice roaming as a Title II service in 2007 (and classifying mobile wireless phone service as a Title II service in 1993), the wireless industry seems to be doing OK, with more than 300 million subscribers and (as CTIA never tires of telling us) several gagillion dollars worth of capital investment.
The automatic voice roaming decision also provides a nice comparison with a similar service classified under NOT TITLE II some years later. In 2011, the FCC issued an Order adopting data roaming rules, but couldn’t bring itself to go the Title II route. The result was an insanely complicated “commercial reasonableness” standard which requires wireless carriers to negotiate under a bunch of vague guidelines that still allow carriers to avoid coming to an actual deal. As the D.C. Circuit pointed out in affirming this approach, the FCC needed to leave enough room for carriers to discriminate against each other to avoid triggering the “common carrier prohibition.” Recently, T-Mobile (which opposes using Title II) filed a Petition on data roaming with the FCC alleging that the existing “commercially reasonable” standard is utterly useless unless the FCC adopts a bunch of “benchmarks” and presumptions to put some teeth into the standard. Without getting into the merits of the data roaming petition (which my employer Public Knowledge supports), it is interesting to compare how the Title II automatic voice roaming worked out v. the Title III/Title I data roaming rules.
I do not claim that reclassifying broadband as a Title II service (which, as I have noted before, was tariffed back in the day it was Title II) is exactly comparable. Rather, I offer this as an example of the principle of the Black Swan. Just as the appearance of a single black swan falsifies the statement “all swans are white,” the hysterical ravings of the anti-net neutrality crowd that classifying something as Title II would require the FCC to impose price controls, tariffs, and the occasional human sacrifice to avert structural separation is falsified by demonstrating that the FCC has, in the past, classified services as Title II and did not impose any of these things. In fact, the Title II solution worked out much better than the NOT TITLE II alternative.
More detail below . . . .