Core Communications, Inc. v. Verizon Pennsylvania, Inc.Core Communications, Inc. v. Verizon Pennsylvania, Inc.
This аppeal involves the question of whether a federal district court, in the first instance, may hear disputes concerning the breach of an interconnection agreement formed and approved pursuant to the Federal Telecommunications Act of 1996, Pub.L. No. 104-404, 110 Stat. 56 (1996) (“Telecommunications Act” or “Act”). The United States District Court for the Eastern District of Pennsylvania held that the Act prevents parties from taking such claims to federal court until they have been litigated before a state commission. Core Communications, Inc. (“Core”), argues that the District Court erred by misapplying Chevron deference to graft onto the Act an exhaustion requirement for enforcement actions when Congress did not provide for one. For the reasons that follow, we will affirm the judgment of the District Court dismissing Count III of Core’s complaint without prejudice, vacate the dismissal of the remaining counts, and remand for further proceedings consistent with this opinion.
I.
The dispute in this case centers on the duties an incumbent provider of telecommunications services owes with respect to new entrants who wish to compete with the incumbent in a particular local market, and how those duties are enforced. Such questions are governed by the Telecommunications Act of 1996, which was enacted “to promote competition and reduce regulation in order to secure lower prices and higher quality servicе for American telecommunications consumers and encourage the rapid deployment of new telecommunications technologies.” Preamble, Telecommunications Act of 1996, Pub.L. No. 104-404, 110 Stat. 56 (1996). “As the legislative history explains, the Act creates ‘a pro-competitive, de-regulatory national policy framework designed to accelerate rapidly private sector deployment of advanced telecommunications and information technologies and services to all Americans by opening all telecommunications markets to competition.’ ”
Puerto Rico Tel. Co. v. Telecomms. Regulatory Bd.,
To achieve these goals, the Act provides that various responsibilities are to be divided between the state and federal governments, making it “an exercise in what has been termed cooperative federalism.”
Id.
at 8. That is, “Congress enlisted the aid of state public utility commissions to ensure that local competition was implemented fairly and with due regard to the local conditions and the particular historical circumstances of local regulation under the prior regime.”
Global Naps, Inc. v. Mass. Dept. of Telecomm. and Energy,
There are two sections of the Act that are at issue in this case: §§ 251 and 252. Section 251 requires companies that traditionally provide local phone service— known as incumbent local exchange carriers (“ILECs”) — to interconnect their networks with the networks of competitors— known as competing local exchange carriers (“CLECs”).
The duty to provide, for the facilities and equipment of any requesting telecommunications carrier, interconnectionwith the local exchange carrier’s network—
(A) for the transmission and routing of telephone exchange service and exchange access;
(B) at any technically feasible point within the carrier’s network;
(C) that is at least equal in quality to that provided by the local exchange carrier to itself or to any subsidiary, affiliate, or any othеr party to which the carrier provides interconnection; and
(D) on rates, terms, and conditions that are just, reasonable, and nondiscriminatory, in accordance with the terms and conditions of the agreement and the requirements of this section and section 252 of this title.
To implеment these new duties, the Act relies on a system of private negotiations, followed by arbitration, if necessary, both under the supervision of state commissions. All of these steps to attain an interconnection agreement may be followed by federal court review, if it is sought by the parties. The process commences when an ILEC receives a “request for interconnection” from another telecommunications company. Id. § 252(a)(1). The Act then requires the ILEC to “negotiate in good faith in accordance with section 252 ... the particular terms and conditions of agreements to fulfill” its substantive duties under the Act. Id. § 252(c)(1). A requesting carrier may also choose to adopt all of the terms and сonditions of an existing state commission-approved agreement that the incumbent has with another carrier. Id. § 2620).
To deal with problems that may arise during the negotiation period, the Act provides that, if the parties are unable to agree, either party may petition the state commission to arbitrate “open issues.” Id. § 252(b)(1). As a final procedural safeguard, all interconnection agreements must be submitted to the state commission for approval. Id. § 252(e)(1). The commission’s “determinations” with respect to the agreements are subject to review in federal court. Id. § 252(e)(6).
Pursuant to the Act, Core entered into an interconnection agreement with Verizon Pennsylvania, Inc.’s (“Verizon”) predecеssor in interest on March 31, 2000. Rather than negotiating from scratch, Core opted into the existing agreement between Verizon’s predecessor (Bell Atlantic-Pennsylvania, Inc.) and MCImetro Access Transmission Services, Inc.
Between the fall of 2000 and October 2002, Core requested interconnection to various markets in Pennsylvania. Core alleges that Verizon deliberately and unjustifiably refused to interconnect with Core at technically feasible points in a timely manner. Rather than using existing facilities with spare capacity to interconnect, Verizon cited its internal policy of requiring the construction of new, dedicated facilities to interconnect with Core. No technical or business justificatiоn was given explaining the need for this requirement. Core claims that Verizon intentionally took these steps in order to maintain its competitive advantage in Pennsylvania markets and to intimidate and financially harm Core.
On September 24, 2004, Core filed the complaint underlying this action in the United States District Court for the East
On November 4, 2004, Verizon filed a motion to dismiss, seeking the dismissal of Counts I, II, and IV for failure to state a claim upon which relief can be granted under
On April 5, 2006, Core filed a motion for reconsideration or amended judgment. Following this motion, Core and Verizon entered into a tolling agreement that tolled the statute of limitations on Core’s claims until forty-five days after the entry of an order resolving or otherwise disposing of an appeal to this Court from the District Court’s decision. In accordance with that agreement, Core filed a praecipe to withdraw its motion for reconsideration or amended judgment on April 19, 2006. In the wake of this agreement, Core filed a notice of appeal on April 20, 2006. On April 26, 2006, this Court issued a stay pending the District Court’s disposition of Core’s motion for reconsideration, which was dismissed as moot on May 3, 2006. This appeal followed.
II.
Before moving to any of the claims raised by Core, we must first determine whether or not we have jurisdiction to hear this case. Verizon argues that there is no appellate jurisdiction under
“A party generally may not take an appeal under
Thus, it is far from clear that Core could simply re-plead its claims. To the contrary, it seems certain that at least some of the claims will be time barred if Core is forced to litigate its claim for breach of the interconnection agreement before the PA PUC. Count I of the complaint, for example, contains a limitations period of two years that began tо run in October 2002, when Verizon failed to interconnect in Wilkes-Barre.
See
III.
Moving to the merits, the essence of Core’s argument is that it was not required to litigate its claim for breach of the interconnection agreement in front of the PA PUC as an intermediate step before the District Court could hear the case. The District Court held, and Verizon argues, that the statutory scheme under the Telecommunications Act requires that Core first present this claim to the state commission before proceeding in a federal district court. It reached this conclusion by applying
Chevron
deference to the FCC’s decision in
In re Starpower Communications.
We exercise plenary reviеw over such claims, which implicate the District Court’s conclusions of law.
See, e.g., Epstein Family P’ship v. Kmart Corp.,
Under
Chevron U.S.A., Inc. v. Natural Resources Defense Council,
A.
Under this framework, the first question we must answer is “whether Congress has directly spoken to the precise question at issue.”
Chevron,
In this case, the “precise question at issue” involves the proper procedure for the interpretation and enforcement of previously approved interconnection agreements. Specifically, we must determine whether a party may proceed directly to federal court to litigate such claims, or if it must first present them to the state commission that originally approved the agreement. We turn to the Telecommunications Act to determine whether or not Congress has spoken on this question.
The “[procedures for negotiation, arbitration, and approval of [interconnection] agreements” are discussed in § 252 of the Act. Subsection (e), titled “Approval by state commission,” explains the role of state commissions like the PA PUC. It provides that “[a]ny interconnection agreement adopted by negotiation or arbitration shall be submitted for approval to the State commission. A State commission to which an agreement is submitted shall approve or reject the agreement, with written findings as to any deficiencies.”
In a case in which a State fails to act as described in paragraph (5),[ 2 ] the proceeding by the Commission under such paragraph and any judicial review of the Commission’s actions shall be the exclusive remedies for a State commission’s failure to act. In any case in which a State commission makes a determination under this section, аny party aggrieved by such determination may bring an action in an appropriate Federal district court to determine whether the agreement or statement meets the requirements of section 251 of this title and this section.
Core, however, argues that Act provides a procedure for post-formation disputes in §§ 206 and 207. Section 206 is entitled “Carriers’ liability for damages” and provides that
[i]n case any common carrier shall do, or cause or permit to be done, any act, matter, or thing in this chapter prohibited or declared to be unlawful, or shall omit tо do any act, matter, or thing in this chapter required to be done, such common carrier shall be liable to the person or persons injured thereby for the full amount of damages sustained in consequence of any such violation of the provisions of this chapter, together with a reasonable counsel or attorney’s fee, to
be -fixed by the court in every case of recovery, which attorney’s fee shall be taxed and collected as part of the costs in the case.
[a]ny person claiming to be damaged by any common carrier subject to the provisions of this chapter may either make complaint to the Commission as hereinafter provided for, or may bring suit for the recovery of the damages for which such common carrier may be liable under the provisions of this chapter, in any district court of the United States of competent jurisdiction; but such person shall not have the right to pursue both such remedies.
The precise claim at issue in this appeal, however, is Core’s claim for breach of the interconnection agreement, not its claims under §§ 201, 202, and 251 of the Act. Divorced from any provision of the Act, it appears that
B.
Faced with a gap in the relevant statutory scheme, we turn to step two of
Chevron,
which instructs that “if Congress has not specifically addressed the question, a reviewing court must respect the agency’s cоnstruction of the statute so long as it is permissible.”
Brown & Williamson Tobacco Corp.,
Arguing that the District Court’s deference to the FCC’s determination in
Star-power
was an error, Core first contends that the decision is irrelevant to the current case. Although the FCC’s decision is
However, given the FCC’s behavior and the structure of the statutory scheme as a whole, we believe that more can be drawn from the FCC’s conclusion “that dispute[s] arising from interconnection agreements and seeking interpretation and enforcement of those agreements [are] within the states’ ‘responsibility’ under
In following this broader reading of
Starpower,
we are mindful of the Supreme Court’s admonition that we must interpret the statute “ ‘as a symmetrical and coherent regulatоry scheme,’ and ‘fit, if possible, all parts into an harmonious whole.’ ”
Brown & Williamson Tobacco Corp.,
[a] state commission’s authority to approve or reject an interconnection agreement would itself be undermined if it lacked authority to determine in the first instance the meaning of an agreement that it has approved. A court might ascribe to the agreement a meaning that differs from what the state commission believed it was "approving — indeed, the agreement as interpreted by the court may be one the state commission would never have approved in the first place. To deprive the state commission of authority to interpret the agreement that it has approved would thus subvert the role that Congress prescribed for state commissions.
BellSouth Telecomms., Inc. v. MCImetro Access Transmission Servs., Inc.,
Notwithstanding this analysis, Core argues that
Starpower
is not entitled to
Chevron
deference because Congress merely delegated authority to the FCC to preempt affirmative refusals by state commissions to carry out their responsibilities under
Core’s next argument is that
Starpower
is not owed deference because the FCC’s decision was guided by two “instructive” federal appellate court cases, rather than by the agency’s expertise. However, a primary source of an agency’s power under
Chevron
deference is delegation, not simply expertise. By not speaking on the
By virtue of that Congressional delegation, an administrative agency need not cite any cases in reaching its interpretation; its interpretation is authoritative because it has been posited by the agency. Of course, the agency’s interpretation cannot be “procedurally defective, arbitrary or capricious in substance, or manifestly contrary to the statute,” [United States v.] Mead Corp., 533 U.S. [218,] 227 [121 S.Ct. 2164 ,150 L.Ed.2d 292 (2001)], and legal errors in the agency’s decision might transgress these limits. Within these boundaries, however, an agency is entitled to deference simply because it has acted.
Finally, Core invokes the United States Court of Appeals for the District of Columbia Circuit’s decision in
Murphy Exploration & Production Co. v. U.S. Department of the Interior,
Accordingly, we conclude that the FCC has offered a reasonable solution to fill a gap that currently exists in the Telecommunications Act. Pursuant to the FCC’s guidance, we hold that interpretation and enforcement actions that arise after a state commission has approved an interconnection agreement must be litigated in the first instance before the relevant state commission. A party may then proceed to federal court to seek review of the commission’s decision or move on to the appropriate trial court to seek damages for a breach, if the commission finds one.
C.
Having concluded that Core’s claim for breach. of the interconnection agreement must be presented to the PA PUC in the first instance, we now turn to the remainder of its claims. Without discussing anything other than Core’s breach of contrаct claim, the District Court dis
The District Court did not find, and Verizon does not argue, that any of Core’s other claims must be presented to the PA PUC, or that the PA PUC even has the authority to hear them. In addition, no party argues that these claims must be presented together. As such, the District Court’s action was tantamount to dismissing viable claims without any justification.
Cf. Ahmed,
IV.
“It would be gross understatement to say that the [Telecommunications] Act is not a model of clarity. It is in many important respects a model of ambiguity or indeed even self-contradiction.”
AT & T Corp. v. Iowa Utils. Bd.,
Notes
. During oral argument, counsel for Verizon agreed that it would interpret the tolling agreement as extending through the proceedings before the PA PUC. However, we will not premise a refusal to exercise jurisdiction on the representations of one attorney when the intent of the parties is so clearly expressed in the agreement, and both parties had all of the relevant information before them when the agreement was made. That is, both Core and Verizon were aware of the possibility of a PA PUC proceeding, and chose not to toll the appliсable statutes of limitations for that event.
. Paragraph (5) provides that
[i]f a State commission fails to act to carry out its responsibility under this section in any proceeding or other matter under this section, then the Commission shall issue an order preempting the. State commission's jurisdiction of that proceeding or matter within 90 days after being notified (or taking notice) of such failure, and shall assume the responsibility of the State commission under this section with respect to the proceeding or matter and act for the State commission.
. We do not reach Verizon’s argument that
. We emphasize that our conclusion that the Act is silent on the question at issue here is based on our view of the unusual nature of the statutory scheme. Had we limited ourselves to considering portions of the statutory text in isolation, we could conclude that Congress meant its statement that “[a]ny interconnection agreement adopted by negotiation or arbitrаtion shall be submitted for approval to the State commission,”
. Neither party in this case challenges the FCC’s position as the agency charged with implementing the Telecommunications Act.
See Nat’l Cable & Telecomms. Ass'n,
.
. Indeed, every federal appellate court to consider the issue has determined or assumed that state commissions have the authority to hear interpretation and enforcement actions regarding approved interconnection agreements, despite the Act’s silence on that point.
See P.R. Tel. Co. v. Telecomms. Regulatory Bd..,