throbber
Case 5:18-md-02834-BLF Document 720 Filed 01/13/22 Page 1 of 4
`
`
`
`MICHAEL A. SHERMAN (SBN 94783)
`masherman@stubbsalderton.com
`JEFFREY F. GERSH (SBN 87124)
`jgersh@stubbsalderton.com
`WESLEY W. MONROE (SBN 149211)
`wmonroe@stubbsalderton.com
`STUBBS ALDERTON MARKILES, LLP
`15260 Ventura Boulevard, 20TH Floor
`Sherman Oaks, CA 91403
`Telephone:
`(818) 444-4500
`Facsimile:
`(818) 444-4520
`
`Attorneys for PERSONALWEB
`TECHNOLOGIES, LLC
`
`J. DAVID HADDEN (CSB No. 176148)
`dhadden@fenwick.com
`SAINA S. SHAMILOV (CSB No. 215636)
`sshamilov@fenwick.com
`MELANIE L. MAYER (admitted pro hac vice)
`mmayer@fenwick.com
`TODD R. GREGORIAN (CSB No. 236096)
`tgregorian@fenwick.com
`RAVI R. RANGANATH (CSB No. 272981)
`rranganath@fenwick.com
`FENWICK & WEST LLP
`Silicon Valley Center
`801 California Street
`Mountain View, CA 94041
`Telephone:
`650.988.8500
`Facsimile:
`650.938.5200
`
`Attorneys for AMAZON.COM, INC.,
`AMAZON WEB SERVICES, INC., and
`TWITCH INTERACTIVE, INC.
`
`UNITED STATES DISTRICT COURT
`NORTHERN DISTRICT OF CALIFORNIA
`SAN JOSE DIVISION
`
`Case No.: 5:18-md-02834-BLF
`Case No.: 5:18-cv-00767-BLF
`Case No.: 5:18-cv-05619-BLF
`
`JOINT CASE MANAGEMENT
`CONFERENCE STATEMENT
`
`
`IN RE: PERSONAL WEB TECHNOLOGIES,
`LLC ET AL., PATENT LITIGATION
`
`AMAZON.COM, INC., and AMAZON WEB
`SERVICES, INC.,
`Plaintiffs
`
`v.
`PERSONALWEB TECHNOLOGIES, LLC and
`LEVEL 3 COMMUNICATIONS, LLC,
`Defendants,
`
`PERSONALWEB TECHNOLOGIES, LLC, and
`LEVEL 3 COMMUNICATIONS, LLC,
`
`Plaintiffs,
`
`v.
`
`TWITCH INTERACTIVE, INC.,
`
`Defendant.
`
`
`
`
`
`JOINT CMC STATEMENT
`
`
`
`CASE NOS. 5:18-md-02834-BLF,
`5:18-cv-00767-BLF, and
`5:18-cv-05619-BLF
`
`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`ATTORNEYS AT LAW
`
`FENWICK & WEST LLP
`
`
`
`
`

`

`Case 5:18-md-02834-BLF Document 720 Filed 01/13/22 Page 2 of 4
`
`
`
`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`ATTORNEYS AT LAW
`
`FENWICK & WEST LLP
`
`
`
`
`1
`
`Plaintiff PersonalWeb Technologies, LLC (“PersonalWeb”) and defendants Amazon.com,
`Inc., Amazon Web Services, Inc., and Twitch Interactive, Inc. (collectively, “Amazon”) jointly
`submit this case management conference statement pursuant to Judge Freeman’s Standing Order re
`Civil Cases, the Standing Order for All Judges of the Northern District of California – Contents of
`Joint Case Management Statement, and Civil Local Rules 16-9 and 16-10.
`AMAZON’S STATEMENT
`I.
`Amazon previously submitted a statement of its positions in its request for a case
`management conference. (Dkt. 717 (18-md-2834).) Amazon’s position remains the same and there
`has been no meaningful change in the parties’ respective positions. PersonalWeb has made no
`additional document production since August 6, 2021 and has refused to supplement or amend its
`interrogatory responses to comply with the Court’s past orders.
`PERSONALWEB’S STATEMENT
`II.
`PersonalWeb, SAM and Mr. Gersh intend to submit a statement in response to Dkt 717, but
`unfortunately Mr. Gersh, who is the primary draftsperson of this submission, is quite with ill with
`COVID and is unable to go through each and every argument on such short notice, though either
`he or others at Stubbs Alderton & Markiles, LLP (“SAM”) may supplement his submission early
`next week.
`As this court is aware, SAM is caught in the middle given that it has been discharged by
`PersonalWeb on all post judgment matters other than the appeals, has sought to withdraw from
`these proceedings which was opposed by Amazon and its counsel and ultimately denied by this
`court. The request for a CMC, Dkt 717, reads more like a personal attack on SAM and Mr. Gersh
`and muddies the facts. The Receivership action was not filed by SAM and neither SAM nor Mr.
`Gersh are involved or represent anyone in those proceedings. In fact, neither SAM nor Mr. Gersh
`are on the service list in those proceedings so there is little that is known about the status of same
`absent reading the state court documents.
`Amazon and its counsel complain about the nature of the receivership proceedings in the
`state court action (see exhibits to Mr. Gregorian’s declaration), yet Amazon and its counsel have
`known about those proceedings for approximately 6 months. Although Mr. Gersh sent an email
`CASE NOS. 5:18-md-02834-BLF,
`5:18-cv-00767-BLF, and
`5:18-cv-05619-BLF
`
`JOINT CMC STATEMENT
`
`
`
`

`

`Case 5:18-md-02834-BLF Document 720 Filed 01/13/22 Page 3 of 4
`
`
`
`to Amazon’s counsel about the stay and his understanding of the impact on the discovery and
`collection efforts of Amazon, it is clear from Mr. Gregorian’s declaration that Amazon and its
`counsel knew about the receivership action well before Mr. Gersh’s email given that Amazon and
`its counsel actively participated in the state court action at least as early as August 2021 and filed
`a number of motions including attempting to intervene in that action which was denied without any
`opposition having been filed. Neither SAM nor Mr. Gersh appear on the service list for Amazon’s
`intervention efforts and represented no one in connection with those intervention proceedings.
`The conundrum is that this court issued an order regarding discovery; SAM and Mr. Gersh
`have complied with their ethical obligations as the court was told they would; as set forth in the
`recent filing by Amazon the California state court has issued an injunction against anyone
`“…prosecuting, commencing or enforcing any suit, judgment, levy lien or proceeding against
`Defendant PersonalWeb…” (Dkt 717 page 5)
`The effect of the California state court receivership action is not a matter over which SAM
`expresses an opinion. SAM has been advised that PersonalWeb is being managed by a receiver,
`Amazon lost its attempt to intervene in the state case, there is an injunction against Amazon from
`pursuing any further collection, Amazon appealed the order denying their motion to intervene.
`SAM represents no one in the state court receivership action. Amazon expresses frustration that its
`actions in the state court proceedings have not been successful. But that does not mean that SAM
`and/or Mr. Gersh, or PersonalWeb, has done anything improper or not in conformity with
`applicable order in the state court action.
`
`
`
`
`
`
`
`
`JOINT CMC STATEMENT
`
`
`
`2
`
`CASE NOS. 5:18-md-02834-BLF,
`5:18-cv-00767-BLF, and
`5:18-cv-05619-BLF
`
`
`1 1
`
`2 2
`
`3 3
`
`4 4
`
`5 5
`
`6 6
`
`7 7
`
`8 8
`
`9 9
`
`10 10
`
`11 11
`
`12 12
`
`13 13
`
`14 14
`
`15 15
`
`16 16
`
`17 17
`
`18 18
`
`19 19
`
`20 20
`
`21 21
`
`22 22
`
`23 23
`
`24 24
`
`25 25
`
`26 26
`
`27 27
`
`28 28
`
`ATTORNEYS AT LAW
`
`FENWICK & WEST LLP
`
`
`
`

`

`Case 5:18-md-02834-BLF Document 720 Filed 01/13/22 Page 4 of 4
`
`
`
`Dated: January 13, 2022
`
`Respectfully submitted,
`
`FENWICK & WEST LLP
`
`
`By: /s/ Todd R. Gregorian
`TODD R. GREGORIAN (CSB No. 236096)
`
`Attorneys for AMAZON.COM, INC.,
`AMAZON WEB SERVICES, INC., and
`TWITCH INTERACTIVE, INC.
`
`
`
`STUBBS ALDERTON & MARKILES LLP
`
`By: /s/ Jeffrey F. Gersh
`JEFFREY F. GERSH (CSB No. 87124)
`
`Attorneys for PERSONALWEB
`TECHNOLOGIES, LLC
`
`
`
`
`
`
`Dated: January 13, 2022
`
`
`
`
`
`
`
`
`CERTIFICATION OF CONCURRENCE IN FILING
`I, Todd R. Gregorian, am the ECF user whose identification and password are being used
`to file this Joint Case Management Conference Statement. In compliance with N.D. Cal. Civil L.R.
`5-1(h)(3), I hereby attest that Jeffrey F. Gersh has concurred in this filing.
`
`
`Dated: January 13, 2022
`
`
`
`
`
`
`By: /s/ Todd R. Gregorian
`
` TODD R. GREGORIAN
`
`
`
`
`
`
`
`JOINT CMC STATEMENT
`
`
`
`3
`
`CASE NOS. 5:18-md-02834-BLF,
`5:18-cv-00767-BLF, and
`5:18-cv-05619-BLF
`
`
`1 1
`
`2 2
`
`3 3
`
`4 4
`
`5 5
`
`6 6
`
`7 7
`
`8 8
`
`9 9
`
`10 10
`
`11 11
`
`12 12
`
`13 13
`
`14 14
`
`15 15
`
`16 16
`
`17 17
`
`18 18
`
`19 19
`
`20 20
`
`21 21
`
`22 22
`
`23 23
`
`24 24
`
`25 25
`
`26 26
`
`27 27
`
`28 28
`
`ATTORNEYS AT LAW
`
`FENWICK & WEST LLP
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket