Comcast Corp. v. FCC

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Comcast Corp. v. FCC
District of Columbia Court of Appeals Seal.svg
Court United States Court of Appeals for the District of Columbia Circuit
Full case name Comcast Corporation v. Federal Communications Commission and United States of America
Argued January 8 2010
Decided April 6 2010
Citation(s) 600 F. 3d 642
Holding
The FCC does not have ancillary jurisdiction over Comcast's Internet service under the language of the Communications Act of 1934.
Court membership
Judge(s) sitting Chief Judge David B. Sentelle; Circuit Judges Arthur Raymond Randolph and David S. Tatel
Case opinions
Majority Judge Tatel, joined by Chief Judge Sentelle and Judge Randolph

Comcast Corp. v. FCC,[1] 600 F.3d 642, is a 2010 United States Court of Appeals for the District of Columbia case holding that the Federal Communications Commission (FCC) does not have ancillary jurisdiction over Comcast's Internet service under the language of the Communications Act of 1934. In so holding, the Court vacated a 2008 order issued by the FCC that asserted jurisdiction over Comcast's network management policies and censured Comcast from interfering with its subscribers' use of peer-to-peer software.

On August 1, 2012, Comcast sued the FCC again regarding an order to distribute Tennis Channel equally with Golf Channel and Versus (Comcast Cable v. FCC & USA, No. 12-1337 (D.C. Cir.)).

Background

In 2007, several subscribers of Comcast high-speed Internet discovered that Comcast was interfering with their use of peer-to-peer networking applications. Challenging Comcast's interference, Free Press and Public Knowledge—two non-profit advocacy organizations—filed a complaint with the FCC. The complaint stated that Comcast's actions violated the FCC Internet Policy Statement, particularly violating the statement's principle that “consumers are entitled to access the lawful Internet content of their choice... [and] to run applications and use services of their choice.”[1] Comcast defended its interference with consumers' peer-to-peer programs as necessary to manage scarce network capacity.

Following this complaint, the FCC issued an order censuring Comcast from interfering with subscribers' use of peer-to-peer software—the FCC's second attempt to enforce its network neutrality policy with the first being the Madison River investigation.[2] The order began with the FCC stating it had jurisdiction over Comcast's network management practices under the Communications Act of 1934 (47 U.S.C. § 154). Specifically, the Communications Act of 1934 granted the FCC the power to "perform any and all acts, make such rules and regulations, and issue such orders, not inconsistent with [the Act], as may be necessary in the execution of its functions."[3] Next, the FCC ruled that Comcast impeded consumers' ability to access content and use applications of their choice. Additionally, because other options were available for Comcast to manage their network policy without discriminating against peer-to-peer programs, the FCC found that Comcast's method of bandwidth management breached federal policy.

Comcast complied with the order and appealed.

Opinion of the Court

The D.C. Circuit Court of Appeals held that the FCC failed to justify its exercise of ancillary authority to regulate Internet service providers' network management practices. For an issue to fall within an agency's authority, the agency need only have ancillary authority—a sufficient statutory support requesting the agency at least take action in the first instance of the issue. Here, the Court did not find a sufficient statutory basis under the Communications Act of 1934 for the FCC's mandate to regulate the behavior of Internet service providers.

The Court relied on a two-part test for ancillary authority, laid out in Am. Library Ass'n v. FCC:[4] A commission may exercise ancillary authority only if “(1) the Commission's general jurisdictional granted under Title I [of the Communications Act] covers the regulated subject and (2) the regulations are reasonably ancillary to the Commission's effective performance of its statutorily mandated responsibilities.”[1]

Although Comcast conceded that the FCC satisfied the first prong, the court ruled that the FCC failed to satisfy the second prong. The FCC failed to show that its action of barring Comcast from interfering with its customer's peer-to-peer use was reasonably ancillary to the effective performance of its statutorily-mandated authority. Instead, the FCC relied on a Congressional statement of policy and various provisions of the Communications Act—neither of which the Court found created “statutorily mandated responsibilities.”[1] Additionally, by accepting the FCC's argument, the court believed it would “virtually free the Commission from its congressional tether,” thereby providing the FCC an almost unbounded limit to impose regulations on Internet service providers.[1]

Significance of the decision

The FCC Order was the Commission's first attempt to impose rules requiring network neutrality among ISPs. But in a unanimous decision, the Court found that the FCC lacked the power to enforce these rules. However, the D.C. Circuit hinted that the court would accept separate jurisdictional arguments under other titles of the communications act.[5] Not only does this affect the administrability of the FCC's current network neutrality principles, but it could also affect a wide variety of broadband issues, such as ensuring ISPs do not block websites like Hulu or YouTube or enforcing ISP's advertised broadband speeds.

Further, the court's decision prompted the FCC to establish new rules regarding internet regulations. Because of the ruling in this case, these rules justify themselves in new ways, namely claiming direct authority through section 706 of the Communications Act, as well as ancillary authority through Title II and VI of the Act. While these justifications avoid the direct complaints raised in this case, it is not clear whether they would hold up on appeal.[6]

Parties' response to judgment

Comcast's reaction

Comcast issued the following statement:

<templatestyles src="Template:Quote_box/styles.css" />

We are gratified by the Court's decision today to vacate the previous FCC's order. Our primary goal was always to clear our name and reputation. We have always been focused on serving our customers and delivering the quality open-Internet experience consumers want. Comcast remains committed to the FCC's existing open Internet principles, and we will continue to work constructively with this FCC as it determines how best to increase broadband adoption and preserve an open and vibrant Internet.

Comcast Statement on U.S. Court of Appeals Decision on Comcast v. FCC [7]

The FCC's reaction

The FCC released the following statement regarding the Comcast v. FCC decision:

<templatestyles src="Template:Quote_box/styles.css" />

The FCC is firmly committed to promoting an open Internet and to policies that will bring the enormous benefits of broadband to all Americans. It will rest these policies -- all of which will be designed to foster innovation and investment while protecting and empowering consumers -- on a solid legal foundation.... Today's court decision invalidated the prior Commission's approach to preserving an open Internet. But the Court in no way disagreed with the importance of preserving a free and open Internet; nor did it close the door to other methods for achieving this important end.

FCC Statement on Comcast v. FCC Decision [8]

The FCC's new net neutrality rules

In December 2010, FCC approved new net neutrality rules, formalized in an FCC order. While these rules did not reclassify a broadband service as a communications service under the Title II regulation, it would forbid cable and DSL Internet service providers from blocking or slowing online service. It would also prohibit mobile carriers from blocking VoIP applications such as Skype and blocking websites in their entirely, while restrictions are fewer than those on cable and DSL.[9]

In January 2011, Verizon filed an appeal in the United States Court of Appeals for the District of Columbia Circuit, which was the same court that heard Comcast Corp. v. FCC, to overturn this new rule, although the new rules had not yet been in effect.[10] Verizon brought this lawsuit because they were concerned by the FCC's assertion of broad authority for sweeping new regulation of broadband networks and the internet itself, which Verizon believed was well beyond any authority provided by Congress to the FCC.[11]

A few days after the filing by Verizon, MetroPCS, which had already been accused of violating the new rules, also asked the same court to hear the challenge against the new rules.[12] However, in March, 2013, five days after the FCC approved MetroPCS's pending merger with T-Mobile, MetroPCS announced it was dropping its suit, leaving Verizon the sole challenger of the rules.[13]

The court ruled in favor of Verizon by vacating portions of the FCC Open Internet Order of December 2010.

References

  1. 1.0 1.1 1.2 1.3 1.4 Lua error in package.lua at line 80: module 'strict' not found.
  2. "In the Matter of Madison River Communications, LLC and affiliated companies". Consent Decree DA 05-543. FCC. 2005. Retrieved 30 April 2014.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. FCC Passes Compromise Net Neutrality Rules WIRED (Dec. 21, 2010)
  10. Verizon Sues F.C.C. to Overturn Order on Blocking Web Sites The New York Times, Jan. 20, 2011
  11. Verizon Files Appeal in Federal Court Regarding FCC Net Neutrality Order Verizon's statement (Jan. 20, 2011)
  12. Accused of Violating Net Neutrality, MetroPCS Sues FCC WIRED (Jan. 25, 2011)
  13. MetroPCS Ditches Challenge to FCC Net Neutrality Regs Law360.com, May 17, 2013

See also