throbber
Case 3:17-cv-05659-WHA Document 221 Filed 11/08/18 Page 1 of 2
`
`
`
`Paul Andre
`Partner
`T 650-752-1700
`F 650-752-1800
`PAndre@KRAMERLEVIN.com
`
`November 8, 2018
`
`
`990 Marsh Road
`Menlo Park, CA 94025-1949
`T 650.752.1700
`F 650.752.1800
`
`Honorable William Alsup
`U.S. District Court, Northern District of California
`San Francisco Courthouse
`Courtroom 12 – 19th Floor
`450 Golden Gate Avenue
`San Francisco, CA 94102
`
`
`
`Re:
`
`Finjan, Inc. v. Juniper Networks, Inc., Case No. 3:17-cv-05659-WHA
`
`Dear Judge Alsup:
`
`Plaintiff Finjan, Inc. (“Finjan”) respectfully requests permission to file Daubert motions
`according to the same schedule that the Court set for Juniper Networks, Inc. (“Juniper”).
`Specifically, Finjan requests permission to file opening Daubert motions on November 12,
`requiring Juniper to file its opposition on November 19 at noon, and requiring Finjan to file
`its reply on November 23 at noon. See Dkt. 215 (setting the same schedule for Juniper).
`
`On October 26, 2018, the Court denied the parties’ stipulation to an amended briefing
`schedule for Daubert motions (Dkt. 213). After Juniper filed a letter brief requesting
`reconsideration (Dkt. 214), the Court set a briefing schedule for Juniper’s motions but did
`not provide a schedule for Finjan’s motions (Dkt. 215). Juniper has since refused to
`stipulate to allow Finjan to file Daubert motions on the same schedule.
`
`Yesterday, Juniper filed two separate “rebuttal” damages reports, one from Dr. Ugone
`(Juniper’s damages expert) and one from Dr. Rubin (Juniper’s technical expert). These
`reports contain many deficiencies that call for Daubert motions, as set forth below:
`
`Deficiencies in Dr. Ugone’s Report:
`
` Unreliable methodology based on reliance on uncomparable Juniper licenses,
`including software licenses, as “reasonableness check” and a lump sum picked
`from thin air.
`
` Based on insufficient or incorrect facts, including (1) using the wrong royalty base
`for the accused product revenues, yielding a difference for just United States
`accused product revenues of over $140M, (2) no facts for improper reliance on
`
`KRAMER LEVIN NAFTALIS & FRANKEL LLP
`
`
`
`
`
`
` SILICON VALLEY | NEW YORK | PARIS
`
`

`

`Case 3:17-cv-05659-WHA Document 221 Filed 11/08/18 Page 2 of 2
`
`Hon. William Alsup
`November 8, 2018
`
`
`
`historic data from “free” licenses, especially because Juniper previously
`submitted a sworn declaration to the Court stating that Juniper did not perform
`historic tracking of free licenses, (3) no basis for his tracking of SRX Products using
`serial numbers (4) no facts to support effective royalty rates based on certain
`Finjan licenses.
`
` Reliance on information not disclosed during discovery or disclosed days before
`Ugone’s report, including (1) costs associated with servers, (2) alleged non-
`infringing alternatives or use of the alternatives as a “constrain[t] on royalty
`payment” (3) portion of Amazon invoices associated with certain accounts, (4)
`individuals not disclosed in his report referred to just as “juniper personnel.”
`
`Deficiencies in Dr. Rubin’s Report:
`
` Dr. Rubin provides opinions that are not relevant to the December 10th trial,
`including: (1) challenges to validity of Claim 10 under 35 U.S.C. §§102 and 103;
`(2) arguing the claim is abstract; and (3) inequitable conduct and prosecution
`laches.
`
` Dr. Rubin applies the incorrect legal standard for whether there is an “inventive
`concept” in Claim 10 of the ‘494 Patent.
`
`Given these deficiencies and Juniper’s delays in disclosure, it would be inequitable to
`allow Juniper to file Daubert motions but not allow Finjan to do the same. Thus, Finjan
`respectfully requests a briefing schedule to file its Daubert motions identical to the
`schedule and page limits that the Court provided for Juniper at Dkt. 215.
`
`Sincerely,
`
`
`
`Paul J. Andre
`Counsel for Plaintiff Finjan, Inc.
`
`
`
`
`
`2
`
`

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