throbber

`
`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
`
`Case 3:17-cv-05659-WHA Document 62 Filed 04/18/18 Page 1 of 5
`
`KRAMER LEVIN NAFTALIS &
`FRANKEL LLP
`Paul Andre (SBN 196585)
`pandrea@kramerlevin.com
`Lisa Kobialka (SBN 191404)
`lkobialka@kramerlevin.com
`James Hannah (SBN 237978)
`jhannah@kramerlevin.com
`Kristopher B. Kastens (SBN 254797)
`kkastens@kramerlevin.com
`990 Marsh Road
`Menlo Park, CA 94025
`Telephone: (650)752-1700
`Facsimile: (650)752-1800
`
`Attorneys for Plaintiff
`FINJAN, INC.
`
`
`IRELL & MANELLA LLP
`Jonathan S. Kagan (SBN 166039)
`jkagan@irell.com
`Joshua P. Glucoft (SBN 301249)
`jglucoft@irell.com
`Casey Curran (SBN 305210)
`ccurran@irell.com
`1800 Avenue of the Stars, Suite 900
`Los Angeles, California 90067-4276
`Telephone: (310) 277-1010
`Facsimile: (310) 203-7199
`
`Rebecca L. Carson (SBN 254105)
`rcarson@irell.com
`Kevin Wang (SBN 318024)
`kwang@irell.com
`840 Newport Center Drive, Suite 400
`Newport Beach, California 92660-6324
`Telephone: (949) 760-0991
`Facsimile: (949) 760-5200
`
`Attorneys for Defendant
`JUNIPER NETWORKS, INC.
`
`
`
`UNITED STATES DISTRICT COURT
`NORTHERN DISTRICT OF CALIFORNIA
`SAN FRANCISCO DIVISION
`
`
`
`FINJAN, INC.,
`
`
`Plaintiff,
`
`
`
`
`JUNIPER NETWORKS, INC.,
`
`
`v.
`
`Defendant.
`
`
`
`
`
`
`
`Case No. 3:17-cv-05659-WHA
`
`JOINT RESPONSE REGARDING
`STIPULATED ESI DISCOVERY
`PROCESS
`
`
`Hon. William H. Alsup
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`
`
`JOINT RESPONSE REGARDING
`STIPULATED ESI DISCOVERY PROCESS
`Case No. 3:17-cv-05659-WHA
`
`

`

`Case 3:17-cv-05659-WHA Document 62 Filed 04/18/18 Page 2 of 5
`
`
`
`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
`
`Finjan, Inc. (“Finjan”) and Juniper Networks, Inc. (“Juniper”) hereby jointly submit this
`
`response regarding their stipulated ESI discovery process. See Dkt. Nos. 51 and 56.
`
`Paragraphs 6-8 of Dkt. No. 51
`
`The parties agree that the stipulated process set forth in Dkt. No. 51 at ¶¶ 6-8 shall be the
`exclusive mode for responding to requests for production covering emails,1 superseding all
`obligations to manually search for additional relevant emails, except for the following:
`
`Juniper’s Position: Juniper agrees with Finjan that emails that counsel for the parties
`already know or already should know exist shall be exempt from the exclusive application of the
`
`process set forth in Dkt. No. 51 at ¶¶ 6-8, and will be produced subject to any applicable
`
`objections (including privilege). Juniper disagrees with Finjan’s position that “principal
`
`employees of each party that are responsible for or materially involved in managing this action”
`
`shall be exempt from the exclusive application of the process set forth in Dkt. No. 51 at ¶¶ 6-8.
`
`This exception would substantially increases the potential number of custodians, and much of the
`
`parties’ negotiations concerned the total number of custodians each party is to designate.
`
`Finjan’s Position: Finjan contends that emails that principal employees of each party, who
`are responsible for or materially involved in managing this action, already know or already should
`
`know exist, should also be exempt from the process set forth in Dkt. No. 51 at ¶¶ 6-8, and those
`
`emails should be produced subject to any applicable objections (including privilege). This
`
`provision fosters full and complete disclosure from the parties. Contrary to Juniper’s contention,
`
`it does not increase the number of custodians because no additional custodians are subject to email
`
`search terms. Rather, it simply ensures that employees of a party who are heavily involved in this
`
`litigation notify their counsel of any relevant emails that they are or should be aware of. Counsel
`
`for the parties do not possess as much knowledge of relevant emails as the employees who are
`
`managing the litigation for each party and often rely upon their clients for the production of
`
`relevant email. If Juniper is aware of relevant emails, they should be produced. Juniper should not
`
`
`1 To be clear, this paragraph applies only to emails or other forms of electronic correspondence. It
`does not include any other electronically stored information that is not stored as attachments to an
`email or as part of an email archiving system. See Dkt. 51 at ¶ 6.
`
`
`
`
`- 1 -
`
`JOINT RESPONSE REGARDING
`STIPULATED ESI DISCOVERY PROCESS
`Case No. 3:17-cv-05659-WHA
`
`

`

`Case 3:17-cv-05659-WHA Document 62 Filed 04/18/18 Page 3 of 5
`
`
`
`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
`
`be allowed to hide behind a loophole by not telling its outside counsel of the existence of relevant
`
`email.
`
`Paragraph 10 of Dkt. No. 51
`
`The parties agree that the last sentence of Dkt. No. 51 at ¶ 10 (“No other remedies are
`
`available.”) shall be stricken.
`
`Paragraph 18 of Dkt. No. 51 (Privilege Logs)
`
`The parties agree that paragraph 18 of the Court’s Supplemental Order to Order Setting
`Initial Case Management Conference should apply to this case.2
`Paragraph 20 of Dkt. No. 51 (Document Production and Depositions)
`
`Juniper’s Position: Juniper contends that paragraph 20 of the Supplemental Order should
`apply, subject to the following modifications:
`
`• “If any objections to a request for materials isare overruled, and the information contained
`in such documents is material and not substantially reflected in other discovery responses,
`and if the disputed request was due and pending at the time of a deposition, the
`withholding party or counsel must, subject to the requirements and limitations of F.R.C.P.
`30 and L.R. 30-1 and at the request of any other party, re-produce all deponents under its
`control or represented by them for further deposition examination asrelated only to any
`new, materials information produced in response that areis germane to that deponent and
`must bear the expense of doing so. If a party chooses to proceed with a deposition without
`providing search terms for the deponent’s documents at least 3 weeks prior to the
`deposition, that party shall not have the opportunity to further depose any such deponents.”
`
`Juniper believes this modification will help ensure that individuals are only subjected to
`
`the burden of additional depositions when necessary in light of the significance of the new
`
`information improperly withheld. Finjan’s actions in propounding discovery reveal its intent to
`
`abuse paragraph 20. Specifically, Finjan has requested to depose Yuly Tenorio (a Juniper
`
`employee) no later than May 9, 2018 but has refused to provide Juniper with requested search
`
`terms in sufficient time to allow Juniper to complete email production prior to the deposition;
`
`Finjan is engaging in such gamesmanship in hopes of securing an otherwise avoidable second
`
`
`2Finjan’s Position: Finjan agreed to Juniper’s request to exclude paragraph 18 of the Court’s
`standing order from this case, and already produced certain documents that were partially redacted
`for privilege pursuant to that agreement. Now that it appears paragraph 18 will apply, Finjan will
`work diligently to comply with paragraph 18 by producing a privilege log for the documents it
`already produced.
`
`
`
`
`- 2 -
`
`JOINT RESPONSE REGARDING
`STIPULATED ESI DISCOVERY PROCESS
`Case No. 3:17-cv-05659-WHA
`
`

`

`
`
`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
`
`Case 3:17-cv-05659-WHA Document 62 Filed 04/18/18 Page 4 of 5
`
`deposition of Yuly Tenorio. Additionally, Juniper agreed to the stipulated ESI discovery process
`
`based in part on its expectation that certain provisions would be adopted. Finjan’s reversal on the
`
`issue now would result in a windfall to Finjan, as Juniper would have negotiated the ESI
`
`stipulation differently with the knowledge that the Court was less amenable to certain
`
`modifications. Finally, Finjan’s contention that it needs to conduct serial depositions of Juniper’s
`
`witnesses because of the early summary judgment proceedings is meritless. To the extent Finjan
`
`has questions for a witness about topics pertaining to claims that are not at issue in the early
`
`summary judgment proceedings, there is no reason why it cannot ask those questions at the
`
`upcoming depositions.
`
`Finjan’s Position: Juniper is attempting to prevent the production of important discovery.
`Finjan sees no reason to, and does not, agree to Juniper’s request to deviate from paragraph 20 of
`
`this Court’s standing order, which encourages timely and complete document production and
`
`fosters meaningful depositions and full disclosure from both parties. By contrast, Juniper’s
`
`proposal introduces ambiguity (and likely unnecessary motion practice) regarding what
`
`information is deemed “material” or “not substantially reflected” in other discovery responses.
`
`Juniper’s proposal also encourages delayed production of documents, and delayed depositions of
`
`witnesses as a result, which is at odds with the early summary judgment schedule in this case.
`
`Furthermore, Juniper introduces a loophole with regard to the production of email which may not
`
`be subject to a motion to compel. Indeed, if Finjan is successful on a motion to compel any
`
`documents, it should have the right to redepose relevant witnesses regardless of whether email
`
`search terms were provided or not. Finjan is entitled to prompt and full discovery, and Juniper
`
`should not be allowed to withhold such discovery with the introduction of a self-serving
`technicality.3
`
`
`3 Finjan’s position: With regard to currently noticed depositions, Juniper fails to inform the Court
`that it has refused to produce 2 of the 3 witnesses that Finjan has noticed. Thus, Juniper’s claim of
`gamesmanship rings hollow as Juniper continues to withhold relevant discovery from Finjan.
`Juniper’s position: One witness that Finjan attempted to notice (without conferring) is on
`paternity leave but Juniper is happy to produce him as a witness when he returns, and the other
`witness that Finjan attempted to notice (again without conferring) is a sales employee located in
`Europe and does not have any unique knowledge relevant to this case.
`JOINT RESPONSE REGARDING
`STIPULATED ESI DISCOVERY PROCESS
`Case No. 3:17-cv-05659-WHA
`
`- 3 -
`
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 62 Filed 04/18/18 Page 5 of 5
`
`
`
`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
`
`KRAMER LEVIN NAFTALIS & FRANKEL LLP
`
`By: /s/ Paul J. Andre
`Paul Andre
`
`Attorneys for Plaintiff
`FINJAN, INC.
`
`
`
`
`
`IRELL & MANELLA LLP
`
`
`
`By: /s/ Joshua Glucoft
`Joshua Glucoft
`
`Attorneys for Defendant
`Juniper Networks, Inc.
`
`
`
`Dated: April 18, 2018
`
`
`
`
`Dated: April 18, 2018
`
`
`
`
`
`ATTESTATION
`In accordance with Civil Local Rule 5-1(i)(3), I attest that concurrence in the filing of this
`
`document has been obtained by any other signatory to this document.
`
`
`
`
`
`
`
`
`/s/ Paul J. Andre
`Paul J. Andre
`
`
`
`
`
`- 4 -
`
`JOINT RESPONSE REGARDING
`STIPULATED ESI DISCOVERY PROCESS
`Case No. 3:17-cv-05659-WHA
`
`

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