Source: http://www.internetlibrary.com/cases/lib_case334.cfm
Timestamp: 2019-04-26 00:00:13+00:00

Document:
An individual, utilizing Verizon as his Internet service provider, allegedly used the peer-to-peer software Kazaa to download approximately 600 copyrighted recordings by well-known artists from computers of third parties. This material was not stored on Verizon's network. Rather, Verizon's involvement was limited to providing this individual's connection to the Internet.
On behalf of the holders of the copyrights in the downloaded songs, the RIAA served a subpoena on Verizon under 17 U.S.C. § 512(h) of the DMCA, seeking information that would identify this individual. Disagreeing with the court below, the D.C. Court of Appeals held that such "a subpoena may be issued only to an ISP engaged in storing on its servers material that is infringing …". As Verizon's only involvement was to provide the Internet, connection via which an individual engaged in allegedly infringing activity accessed the Internet, and not in storing infringing material on its system, or in providing links thereto, it could not be compelled to comply with a subpoena issued under 17 U.S.C. § 512(h).
The Court of Appeals found that its determination was supported by the statutory language of 17 U.S.C. § 512(h). To obtain a subpoena under that statute, a copyright owner must provide the Clerk of the Court with "a copy of a notification described in [17 U.S.C. § 512](c)(3)(A); [the] proposed subpoena, and a sworn declaration to the effect that the purpose for which the subpoena is sought is to obtain the identity of an alleged infringer and that such information will only be used for the purposes of protecting rights under this title." 17 U.S.C. § 512(h)(2).
Verizon maintains the two subpoenas obtained by the RIAA fail to meet the requirements of § 512(c)(3)(A)(iii) in that they do not - because Verizon is not storing the infringing material on its server - and can not, identify material "to be removed or access to which is to be disabled" by Verizon.
Infringing material obtained or distributed via P2P file sharing is located in the computer (or in an off-line storage device, such as a compact disc) of an individual user. No matter what information the copyright owner may provide, the ISP can neither "remove" nor "disable access to" the infringing material because that material is not stored on the ISP's servers.
In reaching this result, the Court rejected the RIAA's contention that Verizon can "disable access" to the infringing material within the meaning of § 512(c)(3)(A) by terminating the offending subscriber's Internet account. The Court premised this determination on the statute's distinction between "providing access to infringing material" 512(j)(1)(A)(i) and "providing access to a subscriber or account holder … who is engaging in infringing activity … by terminating the accounts of the subscriber or account holder." 512(j)(1)(a)(ii).
These distinct statutory remedies establish that terminating a subscriber's account is not the same as removing or disabling access by others to infringing material resident on the subscriber's computer.
We think it clear, therefore, that the cross-references to § 512(c)(3) in §§ 512(b)-(d) demonstrate that § 512(h) applies to an ISP storing infringing material on its servers in any capacity - whether as a temporary cache of a web page created by the ISP per § 512(b), as a web site stored on the ISP's server per § 512(c), or as an information locating tool hosted by the ISP per § 512(d) - and does not apply to an ISP routing infringing material to or from a personal computer owned and used by a subscriber.
Finally, the Court rejected the RIAA's appeal to public policy. While the Court was "not unsympathetic" to the RIAA's concerns about the widespread infringement occurring over P2P networks, or the need for legal tools to protect the copyrights of its members, it was the job of Congress, and not the courts, to provide an appropriate remedy.

References: § 512
 § 512
 § 512
 § 512
 § 512
 § 512
 § 512
 § 512
 § 512
 § 512
 § 512
 § 512