Tag: fcc

Is Net Neutrality (And Everything Else) Not Dead Yet or Pining For the Fjords? Contemplating Trump’s Telecom Policy.

, , , , , , , , , , ,

The election of Donald Trump has prompted great speculation over the direction of telecom policy in the near future. Not surprisingly, everyone assumes that the primary Republican goal will be to completely roll back net neutrality and just about every other rule or policy adopted by the Wheeler FCC — perhaps even eliminating the FCC altogether or scaling back it’s authority to virtual non-existence. Why not? In addition to controlling the White House, Republicans have majorities in the Senate and the House.  Jeff Eisenach, the head of Trump’s FCC transition team (now called “Landing Teams”), has been one of the harshest critics of the FCC under both Wheeler and Genachowski. So it is unsurprising to see a spate of articles and blog posts on the upcoming death of net neutrality, broadband privacy, and unlicensed spectrum.

 

As it happens, I have now been through two transitions where the party with the White House has controlled Congress. In neither case have things worked out as expected. Oh, I’m not going to pretend that everything will be hunky-dory in the land of telecom (at least not from my perspective). But having won things during the Bush years (expanding unlicensed spectrum, for example), and lost things in the Obama years (net neutrality 2010), I am not prepared to lay down and die, either.

 

Telecom policy — and particularly net neutrality, Title II and privacy — now exists in an unusual, quantum state that can best be defined with reference to Monty Python. On the one hand, I will assert that net neutrality is not dead yet. On the other hand, it may be that I am simply fooling myself that net neutrality is simply pining for the fjords when, in fact, it is deceased, passed on, has run up the curtain and joined the choir invisible.

 

I give my reasons for coming down on the “not dead yet” side — although we will need to work our butts off to keep from getting clopped on the head and thrown into the dead cart. I expect the usual folks will call me delusional. However, as I have said a great deal over the years: “If I am delusional, I find it a very functional delusion.”

 

More below . . . .

Continue reading

Are Police Jamming Cell Phones At Standing Rock Protest? The FCC Should Investigate.

, , , , , , , ,

Given the lack of coverage in mainstream media, you might not have heard about the ongoing protest against the construction of the Dakota Access Pipeline immediately upstream from the Standing Rock Sioux reservation aka #NoDAPL. You can find some good statistics on the pipeline and number of arrests associated with the protest here. Setting aside my personal feelings about democracy, freedom to peacefully protest, and how the Sioux concerns seem rather justified in light of the Alabama pipeline explosion, this has now raised an interesting communications issue that only an FCC investigation can solve. Are police jamming, or illegally spying, on communications at the protest and associated Sacred Stone Camp?

 

Over the last week, I have seen a number of communications from the protest about jamming, particularly in the period immediately before and during the Thursday effort by police to force protesters off the land owned by Dakota Access Pipeline. In addition, this article in Wired documents why tribal leaders connected with the tribal telecom provider, Standing Rock Telecom, think they are being jammed. I’ve had folks ask to speak to me using encrypted channels for fear that law enforcement will use illegal monitoring of wireless communications. As this article notes, there are a number of telltale signs that law enforcement in the area have deployed IMSI catchers, aka Stingrays, to monitor communications by protesters. However, as I explain below, proving such allegations — particularly about jamming — is extremely difficult to do unless you are the FCC.

 

Which is why the FCC needs to send an enforcement team to Standing Rock to check things out. Given the enormous public interest at stake in protecting the free flow of communications from peaceful protests, and the enormous public interest in continuing live coverage of the protests, the FCC should move quickly to resolve these concerns. If law enforcement in the area are illegally jamming communications, or illegally intercepting and tracking cell phone use, the FCC needs to expose this quickly and stop it. If law enforcement are innocent of such conduct, only an FCC investigation on the scene can effectively clear them. In either case, the public deserves to know — and to have confidence in the Rule of Law with regard to electronic communications.

 

More below . . . .

Continue reading

Ninth Circuit Knee-Caps Federal Trade Commission. Or: “You Know Nothing, Josh Wright.”

, , , , , , , , , ,

Back in October 2014, before the Federal Communications Commission (FCC) reclassified as Title II, both the FCC and the Federal Trade Commission (FTC) brought complaints against AT&T Mobility for failure to disclose the extent they throttled “unlimited” customers once they passed a fairly low monthly limit. You can see the FCC Notice of Apparent Liability (NAL) here. You can see the FTC complaint, filed in the district court for Northern California, here (press release here). As some of you may remember, the FCC was still debating whether or not to reclassify broadband as a Title II telecom service.  Opponents of FCC reclassification (or, indeed, of any FCC jurisdiction over broadband) pointed to the FTC enforcement action as proof that the FTC could handle consumer protection for broadband and the FCC should avoid exercising jurisdiction over broadband altogether.

 

In particular, as noted in this Washington Post piece, FTC Commissioner Maureen Olhausen (R) and then-FTC Commissioner Joshua Wright (R), both vocal opponents of FCC oversight of broadband generally and reclassification specifically, tweeted that the FTC complaint showed the FTC could require broadband providers to keep their promises to consumers without FCC net neutrality rules. Wright would subsequently reiterate this position in Congressional testimony, pointing to the FTC’s enforcement complaint under Section 5 of the Federal Trade Commission Act (FTCA) (15 U.S.C. 45) as an “unfair and deceptive” practice to prove that the FTC could adequately protect consumers from potential harms from broadband providers.

 

Turns out, according to the Ninth Circuit, not so much. As with so much the anti-FCC crowd asserted during the net neutrality debate, this turns out (pending appeal) to be dead wrong. Why? Contrary to what some people seem to think, most notably the usual suspects at Cable’s Team Rocket (who are quoted here as saying “reclassifying broadband means the FTC can’t police any practices of common carriers, at least in the Ninth Circuit” which is either an utterly wrong reading of the case or an incredibly disingenuous remark for implying that reclassification had something to do with this decision. You can see their full press release, which borders on the Trump-esque for its incoherence, here.)

 

As I explain below, the Ninth Circuit’s decision did not rest on reclassification of broadband. To the contrary, the court made it explicitly clear that it refused to consider the impact of reclassification because, even assuming mobile broadband was not a Title II service, AT&T Mobility is a “common carrier” by virtue of offering plain, ordinary mobile voice service (aka “commercial mobile radio service,” aka CMRS). The Ninth Circuit agreed with AT&T that because AT&T offers some services as common carrier services, AT&T Mobility is a “common carrier” for purposes of Section 5(a)(2) of the FTCA and thus exempt from FTC enforcement even for its non-common carrier services.

 

Given that Tech Freedom and the rest of the anti-FCC gang wanted this case to show how the Federal Trade Commission could handle all things broadband, I can forgive — and even pity — Tech Freedom’s desperate effort in their press release to somehow make this the fault of the FCC for reclassifying and conjuring an imaginary “gap” in broadband privacy protection rather than admit Congress gave that job to the FCC. After all, denial is one of the stages of grief, and it must come as quite a shock to Cable’s Team Rocket to once again see that Team PK-chu was right after all (even if it doesn’t make me particularly happy that we were, for reasons I will explain below). But this is policy, not therapy.  As of today, instead of two cops on the beat for broadband consumer protection access, we have one — the Federal Communications Commission. Fortunately for consumers, the FCC has been taking this job quite seriously with both enforcement actions and rulemakings. So while I consider it unfortunate that Ninth Circuit has cut out the FTC on non-common carrier related actions by companies offering a mix of common carrier and non-common carrier services, the only people who need to panic are Tech Freedom and the rest of the anti-FCC crowd.

 

OTOH, longer term, this does create a more general concern for consumer protection in more deregulated industries (such as airlines) covered by the exemptions in Section 5 of the FTCA. Yes, I know most folks reading this blog think the universe revolves around broadband, but this decision impacts airlines, bus services, private mail services like UPS, and any other company offering a common carrier service “subject to the Acts to regulate Commerce.” (15 U.S.C. 45(a)(2))  (Also meat packers and a few other named exceptions). So while I am hopeful the FTC appeals this to the full Ninth Circuit for en banc review (and even the Supreme Court, if necessary) from a general consumer protection perspective, the only direct result of this case for broadband policy is to underscore how important it is for the FCC to do its job despite the industry nay-sayers and their Libertarian cheerleaders.

 

More below . . .

 

Continue reading

The FCC Sets the Ground Rules For Shutting Down The Phone System — And Sets the Stage For Universal Broadband.

, , , , , , , , , , , , , ,

Here’s the funny thing about the world. The two Orders the FCC will vote on tomorrow (Thursday, July 14) probably have more impact on the future of our communications infrastructure than the Title II reclassification of broadband. But like most momentous things in technology, no one notices because they are technical and everyone’s eyes glaze over.

 

In particular, no one notices the sleep inducing and incredibly vaguely named item “Technology Transitions,” we are talking about the conclusion of a 4 year proceeding on how to shut down the legacy phone system and move all our national communications platforms to a mix of digital platforms. That does not mean we’re getting rid of copper and going to all fiber (a common misconception). In fact, in many communities, the old copper lines might get pulled out and replaced with wireless technologies (what we call wire-to-wireless transition). Those who still remember when Verizon tried this after Super Storm Sandy on Fire Island will understand why so many of us wanted to make sure we have an organized transition with quality control and federal oversight.

 

But most people don’t remember this anymore. And, if you are not one of the 60 million or so people (mostly rural, poor or elderly) who still depends on the traditional copper line telephone, you may wonder what this has to do with your life. The short answer is: the old phone system still provides the backbone of our communications system of shiny digital thingies we take for granted. The old copper line phone system is also the workhorse of most ATMs, retail cash registers, and thousands of other things we take for granted every day. Why? Because the old copper line network has been around forever. It’s an open system everyone can – by law – plug into and no one ever imagined would go away.

 

But even more important for the future of our communications infrastructure – the Federal Communications Commission made this a values driven transition. In a bipartisan unanimous 5-0 vote back in January 2014, the FCC rejected the idea of making the Tech Transition a “get out of regulation free zone” and adopted four basic principles to guide the transition: Universal Access, Competition, Consumer Protection and Public Safety.

 

As a result, for once, for once, we actually have a chance to prevent the inequality before it happens. It took 100 years, but if there is one thing Americans took for granted, it was that we all had the same phone system and could all communicate with each other on equal terms. The rules the FCC adopts will make it possible to preserve this principle of universal access. Because this network forms the backbone of the broadband network, if we work together and don’t blow it, we can achieve the same success with broadband that we achieved with basic telephone service.

 

I dig into this below . . .

Continue reading

Broadband Privacy Can Prevent Discrimination, The Case of Cable One and FICO Scores.

, , , , , , ,

The FCC has an ongoing proceeding to apply Section 222 (47 U.S.C. 222) to broadband. For those unfamiliar with the statute, Section 222 prohibits a provider of a “telecommunications service” from either disclosing information collected from a customer without a customer’s consent, or from using the information for something other than providing the telecom service. While most of us think this generally means advertising, it means a heck of a lot more than that — as illustrated by this tidbit from Cable One.

 

Continue reading

Auto Industry Crosses The Line on 5.9 GHz By Using Dead Pedestrians To Justify Spectrum Squatting.

, , , , , , , , , ,

For the last 3 years, the auto industry and the Department of Transportation (DoT) have been at war with the open spectrum community of 75 MHz of spectrum up at 5.9 GHz. I will save the longer history for an upcoming “Insanely Long Field Guide To the 5.9 GHz Proceeding” post.  For now, it is enough to know that, as we enter the last few months of the Obama Administration, the auto industry and DoT have been doing everything they can to run out the clock and wait for this FCC to go away, hoping the next FCC will not be as interested in opening spectrum for sharing. You can read the history of 3 years of bad faith and bait and switch in this filing here. You can read the auto industries most recent insistence on testing that will take us well past the end of the Obama Administration here.

 

So far so normal. This is how spectrum politics works. Incumbents pay lip service to the idea of spectrum sharing, stress the awful terrible things that will happen if the FCC allows the new entrant to operate and cause interference, and insists on an endless series of tests while dragging their feet on anything that would make testing possible. The new entrant, meanwhile, complains bitterly about how the other side are stalling, the interference claims are baseless, and hundreds of billions of dollars in economic benefits are lost as the delay continues.  With the final months ticking down, both sides are now ratcheting up their efforts. Last week, PK, a number of our other spectrum public interest allies (OTI, PK, SHLB) and industry folks (Intel, MS, NCTA, WISPA) sent a letter to the President asking the White House to weigh in at DoT and tell them to stop helping the auto industry stall testing so we can open the spectrum to more unlicensed goodness. Yesterday, the auto industry sent its response.

 

And yesterday, the auto industry finally crossed a line on common decency that just pisses me off.

 

It is one thing to claim that your technology saves lives and that if the FCC doesn’t do what you want, people will die. It is another thing to knowingly and deliberately invoke actual, real dead pedestrians and dead cyclists you know damned well your proposed technology could not conceivably save  in an effort to support your own spectrum squatting. It is even worse when the technology you are pushing, “dedicated short-range communication” (DSRC), would replace the actual existing collision avoidance system you are deploying today that would save cyclists and pedestrians — car radar and sensing systems that use unlicensed spectrum and LIDAR.

 

 

Continue reading

H.R. 2666: House Prepares to Give ISPs License To Price Gouge (Even More).

, , , , , ,

The House Rules Committee has scheduled a floor vote for Friday April 15 (today!) for an amended version of H.R. 2666 aka the “No Rate Regulation of Broadband Internet Access Act,” aka the “Twice The Evil of the Beast” Act. Ostensibly, the bill is supposed to codify the commitment made by President Obama, FCC Chair Tom Wheeler, and just about everyone else that the FCC would never use the classification of broadband as a Title II service to engage in “utility style rate regulation.”

 

Surprise! As I explain in a much shorter version over here, H.R. 2666 basically removes the authority of the FCC to take action on any complaints relating to overcharges, fees or other nasty practices that broadband providers may do to overcharge you — provided they disclose them honestly (and, since there is not exactly a lot of competition, disclosure doesn’t help much). It also effectively strips the FCC of its authority to address zero-rating — even in the worst anticompetitive cases where a provider zero-rates its own content while applying its broadband cap (however discriminatory) to rival services. Along the way, it renders various merger commitments involving offering low cost service to the poor unenforceable and has lots of other nasty impacts.

 

Needless to say, the collective trade associations of the broadband industry are thrilled.

 

That’s not just me talking. That’s from the President’s veto threat message. Additionally, this group of 50 public interest groups think H.R. 2666 is a very, very bad bill, and 30 groups signed on to this letter explaining how H.R. 2666 will screw up privacy protection by letting ISPs charge you for it (aka “pay for privacy” like this from AT&T).

 

I’m going to repeat a pitch here I will repeat often: If you think letting broadband providers price gouge and undermine net neutrality is a bad thing, please call your Representative in the House directly, or use this link to go to BattleForTheNet.com and call your Representative (they have a tool to help find your Rep and have a script — but use your own words, that is always more convincing.

 

Made your call? Good. See below for lots more details so you can explain to your friends why they should call. . . .

Continue reading

What You Need To Know To Understand The FCC National Broadband Report.

, , , ,

The FCC is required by Congress to do lots of reports. Of these, the one that gets the most attention is the annual Report on broadband deployment under Section 706 of the 1996 Telecommunications Act (47 C.F.R. 1302). Sure enough, with the latest report announced as up for a vote at the FCC’s January open meeting, we can see the usual suspects gathering to complain that the FCC has “rigged the game” or “moved the goal post” or whatever sports metaphor comes to mind to accuse the FCC of diddling the numbers for the express purpose of coming up with a negative finding, i.e. That “advanced telecommunications capability” (generally defined as wicked fast broadband) is not being deployed in a timely fashion to all Americans.

 

As usual, to really understand what the FCC is doing, and whether or not they are actually doing the job Congress directed, it helps to have some background on the now 20 year old story of “Section 706,” and what the heck this report is supposed to do, and why we are here. At a minimum, it helps to read the bloody statute before accusing the FCC of a put up job.

 

The short version of this is that, because between 1998 and 2008 the FCC left the definition of “broadband” untouched at 200 kbps, Congress directed the FCC in the Broadband Data Improvement Act of 2008 (BDIA) (signed by President Bush, btw) to actually do some work, raise the numbers to reflect changing needs, and take into account international comparisons so as to keep us competitive with the world and stuff. This is why, contrary to what some folks seem to think, it is much more relevant that the EU has set a goal of 100% subscription of 30 mbps down or better by 2020 than what is the minimum speed to get Netflix.

 

Also, the idea that the FCC needs a negative finding to regulate broadband flies in the face of reality. Under the Verizon v. FCC decision finding that Section 706 is an independent source of FCC authority to regulate broadband, the FCC gets to regulate under Section 706(a) (general duty to encourage broadband deployment) without making a negative finding under Section 706(b) (requirement to do annual report on whether broadband is being deployed to all Americans in a “reasonable and timely manner”).

 

So why does the FCC do this report every year if they already have regulatory authority over broadband. Because Congress told them to do a real report every year. This is what I mean about reading the actual statute first before making ridiculous claims about FCC motivation. Happily, for those who don’t have several years of law school and are ld enough to have actually lived through this professionally, you have this delightful blog to give you the Thug Notes version.

 

 

More below . . . .

Continue reading

Net Neutrality: Tomorrow Is The Judgement Day (Well, Oral Argument).

, , , , , , , ,

So here we are. One day more until oral argument on the FCC’s February 2015 decision to reclassify broadband as a Title II telecom service and impose real net neutrality rules. We definitely heard the people sing — 4 million of them sang the songs of very angry broadband subscribers to get us where we are today. But will we see a new beginning? Or will it be every cable company that will be king? Will Judges Tatel and Srinivasen and Senior Judge Williams nip net neutrality in the bud? Or will we finally meet again in freedom in the valley of the Lord?

 

You can read my blog post on the Public Knowledge blog for a summary of the last 15 years of classification/declasification fights, rulemakings, and other high drama. You can read my colleague Kate Forscey’s excellent discussion of the legal issues in this blog post here. This blog post is for all the geeky Tales of the Sausage Factory type factoids you need to know to really enjoy this upcoming round of legal fun and games and impress your friends with your mastery of such details. Thing like, so how do you get in to the court to watch? What opinions have the judges on the panel written that give us a clue? What fun little things to watch for during argument to try to read the tea leaves? I answer these and other fun questions below . . .

Continue reading

My Insanely Long Field Guide To the LTEU Dust-Up Part II: A Storm of Spectrum Swords.

, , , , , , , , ,

 

The Vorlons have a saying: “Understanding is a 3-edged sword.” In this case, the three edges are the Wi-Fi dependent, the LTE dependent, and the Federal Communications Commission (FCC).

 

Last time on Spectrum Game of Thrones (hereinafter “SGoT”) I spent 6500 words discussing the first two edges of the sword. The Wi-Fi dependent side has strong reason to suspect the LTE-U crowd of either reckless indifference or actual malice toward deployment of Wi-Fi based streaming services in the newly refurbished U-NII-1 band up in 5 GHz. Even if the Wi-Fi Dependents could trust the motives of the LTE-U crowd, what happens if everyone is wrong about the ability of the two technologies to co-exist? Under the current structure, the Wi-Fi dependents would be screwed, and they could do nothing about it. So the rational Wi-Fi Dependent must fight tooth and nail against deployment of LTE-U.

 

It doesn’t help that the Wi-Fi Dependents know that this is an utterly impractical solution for the long term. Unless there is a way to answer the two questions central to the survival of Wi-Fi streaming in U-NII-1 in the face of LTE-U (what happens if something goes wrong, what happens if somebody deliberately does something bad post-deployment), rational Wi-Fi dependents have no choice but to fight deployment.

 

The LTE-U crowd, for its part, has good reason to want to deploy LTE-U and has a legitimate gripe that Wi-Fi Dependents cannot keep saying no without defining the conditions for yes. If we admit the possibility that we can deploy LTE-U consistent with reasonable use of Wi-Fi (which everyone does), then there has to be some way to actually deploy it. And while I savor the fine irony of seeing licensees in the same position I have been in countless times, it is still crappy policy. Also, unlike me and other would-be new entrants, the wireless guys and Qualcomm have enough political muscle to make the current stalemate untenable. Eventually, they will get to deploy something.

 

Which brings us to the third edge of the Vorlon sword of understanding – the FCC. As I shall explain below, government actually is the solution here. Not by imposing a standard or a rule, but by providing both sides with a process for resolving the problem. As a happy side effect, this will also help resolve the general class of problems that keeps coming up on how to manage more and more intense use of the airwaves. Just like we all learned in high school math, and most of us forgot about 30 seconds after the exam, you solve an intractable problem by trying to break it up and simplify it into solvable problems.

 

The only problem is, and I know most people are not going to believe me, the FCC actually hates asserting and clarifying its authority. Yes. Really. Which gives rise to the question of whether the FCC actually has the willingness to do what needs to be done and create a general solution, or if they will continue to try to do the minimum possible, what I call the “Snow Goons Are Bad News” approach immortalized in this classic Calvin and Hobbes strip.

 

So, as we get to SGoT 2: Storm of Spectrum Swords, we come to another dramatic turning point. Will the Wi-Fi Dependents and the LTE-U Dependents see the wisdom of allowing the FCC assert authority over the land of Spectrumos? Can the FCC be persuaded to fulfill its destiny and its duty? And will the anti-Regulatory Zombies from beyond the Wall crash the party and devour both Wi-Fi and LTE-U because of their hatred of the FCC?

 

More below . . .

Continue reading