Strike 3 Holdings, LLC v. Doe

District Court, S.D. California·Decided February 19, 2020·No. 3:19-cv-02452·Unknown

Opinion

1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 SOUTHERN DISTRICT OF CALIFORNIA 10 11 STRIKE 3 HOLDINGS, LLC, Case No.: 19cv2452-JAH-LL

12 Plaintiff, ORDER GRANTING EX PARTE 13 v. APPLICATION TO EXPEDITE DISCOVERY 14 JOHN DOE subscriber assigned IP

address 70.95.76.252, 15 [ECF No. 4] Defendant. 16

17 18 Currently before the Court is Plaintiff’s January 17, 2020 “Ex Parte Application for 19 Leave to Serve a Third Party Subpoena Prior to a Rule 26(f) Conference.” ECF No. 4 20 (“Mot.”). Because the Defendant has not been identified, no opposition or reply briefs have 21 been filed. Having reviewed Plaintiff’s motion and all supporting documents, the Court 22 GRANTS the motion for the reasons set forth below. 23 BACKGROUND 24 Plaintiff alleges that it “is the owner of original, award winning motion pictures 25 featured on its brand’s subscription-based adult websites.” Mot. at 6. On December 19, 26 2019, Plaintiff filed a complaint against John Doe, a subscriber assigned IP address 27 70.95.76.252, alleging copyright infringement. ECF No. 1 (“Compl.”). Plaintiff alleges that 28 Defendant has infringed Plaintiff’s content by downloading and distributing sixty-five of 1 Plaintiff’s copyrighted works using the BitTorrent file distribution network “over an 2 extended period of time.” Id. at ¶ 4. 3 Plaintiff alleges it uses its “proprietary forensic software”—VXN Scan (“VXN”)— 4 to monitor and detect the infringement of its copyrighted works. Mot. at 6. In this case, 5 Plaintiff asserts VXN detected that Defendant’s IP address was “illegally distributing a 6 large number of [Plaintiff]’s motion pictures.” Id. Notably, Plaintiff alleges that while the 7 “BitTorrent protocol contains some default and automatic functions, none of these 8 operations can take place without human interaction.” Id. 9 Plaintiff argues Defendant’s IP address is assigned “by his or her Internet Service 10 Provider (‘ISP’)” and that the ISP is the “only party with the information necessary to 11 identify Defendant by correlating the IP address with John Doe’s identity.” Id. Plaintiff 12 further argues Defendant’s ISP only maintains “the internal logs of the requested 13 information for a brief period of time.” Id. 14 Plaintiff therefore seeks an order from the Court permitting it to serve a subpoena, 15 pursuant to Federal Rule of Civil Procedure 45, on Defendant’s ISP, Spectrum, requiring 16 Spectrum to supply the true name and address of its subscriber to Plaintiff. Id. at 7. 17 LEGAL STANDARD 18 As a general rule, a party may not seek discovery from any source before the Rule 19 26(f) conference unless that party first obtains a stipulation or court order permitting early 20 discovery. Fed. R. Civ. P. 26(d)(1). In certain cases, courts have permitted “limited 21 discovery to ensue after filing of the complaint to permit the plaintiff to learn the 22 identifying facts necessary to permit service on the defendant.” Columbia Ins. Co. v. 23 seescandy.com, 185 F.R.D. 573, 577 (N.D. Cal. 1999). 24 Generally, courts in the Ninth Circuit apply the “good cause” standard in deciding 25 whether to permit early discovery. Semitool, Inc. v. Tokyo Electron America, Inc., 208 26 F.R.D. 273, 276 (N.D. Cal. 2002). Good cause exists “where the need for expedited 27 discovery, in consideration of the administration of justice, outweighs the prejudice to the 28 responding party.” Id. 1 District courts in the Ninth Circuit apply a three-factor test for determining whether 2 good cause exists to allow for expedited discovery to identify certain defendants. Columbia 3 Ins. Co., 185 F.R.D. at 578-80. First, the plaintiff should “identify the missing party with 4 sufficient specificity such that the court can determine that the defendant is a real person 5 or entity who could be sued in federal court.” Id. at 578. Second, the plaintiff must describe 6 “all previous steps taken to locate the elusive defendant.” Id. at 579. Third, the plaintiff 7 should establish that its lawsuit “could withstand a motion to dismiss.” Id. 8 DISCUSSION 9 A. Identification of Missing Party with Sufficient Specificity 10 Plaintiff has the burden to identify Doe Defendant with sufficient specificity to 11 establish Defendant is a real person or entity subject to the Court’s jurisdiction. Columbia 12 Ins. Co., 185 F.R.D. at 578. 13 Some district courts in the Ninth Circuit have determined that “[a] plaintiff identifies 14 Doe defendants with sufficient specificity by providing the unique IP addresses assigned 15 to an individual defendant on the day of the allegedly infringing conduct, and by using 16 ‘geolocation technology’ to trace the IP addresses to a physical point of origin.” 808 17 Holdings, LLC v. Collective of Dec. 29, 2011 Sharing Hash 18 E37917C8EEB4585E6421358FF32F29C D63C23C91, No. 12cv00186 MMA-RBB, 2012 19 U.S. Dist. LEXIS 62980, at *10-11 (S.D. Cal. May 8, 2012) (citations omitted). Other 20 courts have found “merely identifying the IP addresses assigned to the defendants on the 21 day of the purported infringement is sufficient.” Id. (citations omitted). 22 Here, Plaintiff has met its burden of identifying the Doe Defendant with sufficient 23 specificity. Plaintiff provides a declaration from David Williamson, an information 24 systems and management consultant currently employed as Plaintiff’s Chief Technology 25 Officer. Mot., Ex. A at ¶¶ 11-12. Mr. Williamson states he “oversaw the design, 26 development, and overall creation” of VXN, which Plaintiff owns and uses to “identify the 27 IP addresses used by individuals infringing Plaintiff’s movies via the BitTorrent protocol.” 28 Id. at ¶ 40. 1 As Mr. Williamson explains, the VXN system is comprised of a number of 2 components. First, the “Torrent Collector” conducts lexical searches of Plaintiff’s titles 3 “within well-known torrent websites.” Id. at ¶ 45. Once the Torrent Collector finds a match, 4 “the Downloader” component downloads the .torrent file and correlating target file “so that 5 [Plaintiff] can confirm that the targeted computer file . . . is in fact an infringing copy of a 6 copyrighted work” that Plaintiff owns. Id. at ¶¶ 47-48. 7 Next, the “Proprietary Client” will “connect to peers within the swarm associated 8 with that infringing computer file,” which “begins the process of downloading a piece or 9 multiple pieces of the infringing computer file from [] computers connected to the Internet 10 . . . which are offering those infringing computer files for download.” Id. at ¶ 54. 11 Concurrently, the “PCAP Recorder” records in real-time the PCAP (“Packet 12 Capture”) files for all BitTorrent transactions that the Proprietary Client is involved in. Id. 13 at ¶ 63. According to Mr. Williamson, a “PCAP” file is a “computer file containing 14 captured or recorded data transmitted between network devices.” Id. at ¶ 58. Specifically, 15 the PCAP contains: (1) evidence of “particular IP addresses” connecting to and sending 16 pieces of a computer file to the Proprietary Client; and (2) an “Info Hash” associated with 17 an infringing computer file. Id. at ¶¶ 61-62. 18 A “PCAP Stamper” then sends an index of every recorded PCAP file to a third-party 19 provider. Id. at ¶ 72. The third-party provider signs the index with a qualified timestamp. 20 Id. A “PCAP Analyzer” then: (1) retrieves the stored PCAP files; (2) “extracts infringing 21 transaction data” from the PCAP file; (3) “verifies that each retrieved data piece is a part 22 of a .torrent related file”; and (4) “organizes and summarizes the infringing transaction data 23 in a tabular format.” Id. at ¶ 74. 24 Plaintiff further provides the declaration of Patrick Paige, a Partner at Computer 25 Forensics, LLC, who was retained by Plaintiff to analyze the evidence captured by VXN.

Free access — add to your briefcase to read the full text and ask questions with AI

Strike 3 Holdings, LLC v. Doe, (S.D. Cal. 2020).

Strike 3 Holdings, LLC v. Doe (Strike 3 Holdings, LLC v. Doe) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related