throbber
Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 1 of 12
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`IRELL & MANELLA LLP
`Jonathan S. Kagan (SBN 166039)
`kagan@irell.com
`Alan Heinrich (SBN 212782)
`aheinrich@irell.com
`Joshua Glucoft (SBN 301249)
`glucoft@irell.com
`Casey Curran (SBN 305210)
`ccuran@irell.com
`Sharon Song (SBN 313535)
`ssong@irell.com
`1800 Avenue of the Stars, Suite 900
`Los Angeles, California 90067-4276
`Telephone: (310) 277-1010
`Facsimile: (310) 203-7199
`
`Rebecca 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
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Plaintiff,
`
`vs.
`
`JUNIPER NETWORKS, INC., a Delaware
`Corporation,
`
`Defendant.
`
`SAN FRANCISCO DIVISION
`FINJAN, INC., a Delaware Corporation,
`
`Case No. 3:17-cv-05659-WHA
`DEFENDANT JUNIPER NETWORKS,
`INC.’S REPLY IN SUPPORT OF
`JUNIPER NETWORK’S MOTION TO
`EXCLUDE THE TESTIMONY OF
`MR. KEVIN M. ARST
`
`Date: November 29, 2018
`Time: 8:00 a.m.
`Courtroom: Courtroom 12, 19th Floor
`Before: Hon. William Alsup
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`10611869
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 2 of 12
`
`TABLE OF CONTENTS
`
`Page
`
`I.
`
`
`
`II.
`
`FINJAN CANNOT DEFEND MR. ARST’S OPINION UNDER THE
`CORRECT DAMAGES BASE .......................................................................................... 2
`
`FINJAN’S PUFFERY ABOUT THE VALUE OF CLAIM 10 IS
`UNSUPPORTED ................................................................................................................ 4
`
`III. MR. ARST’S DEPARTURE FROM FINJAN’S OWN LICENSING
`POLICY IS UNSUPPORTED ............................................................................................ 4
`
`IV. MR. ARST FAILS TO APPLY A RELIABLE METHODOLOGY .................................. 5
`
`V.
`
`MR. ARST’S COST SAVINGS ANALYSIS IS UNRELIABLE ...................................... 7
`
`VI. MR. ARST SHOULD NOT BE GIVEN LEAVE TO DO A NEW
`ANALYSIS ......................................................................................................................... 8
`
`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
`
`10611869
`
`
`- i -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 3 of 12
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`Cases
`
`
`
`Enplas Display Device Corp., v. Seoul Semiconductor Co., Ltd.,
`2018 WL 6033533 (Fed. Cir. Nov. 19, 2018) ..............................................................................4
`
`Finjan, Inc. v. Secure Computing Corp.,
`626 F.3d 1197 (Fed. Cir. 2010) ....................................................................................................3
`
`Metaswitch Networks Ltd. v. Genband US LLC,
`2016 WL 874737 (E.D. Tex. Mar. 5, 2016) .................................................................................5
`
`Microsoft Corporation v. Corel Corp.,
`2017 WL 6492468 (N.D. Cal. Dec. 19, 2017) .........................................................................6, 7
`
`Monolithic Power Sys., Inc. v. O2 Micro Int’l Ltd.,
`476 F. Supp. 2d 1143 (N.D. Cal. 2007), clarified on denial of reconsideration,
`2007 WL 1108615 (N.D. Cal. Apr. 11, 2007) .............................................................................7
`
`Nazomi Comm., Inc. v. Nokia Corp.,
`739 F.3d 1339 (Fed. Cir. 2014) ....................................................................................................3
`
`Network Prot. Scis., LLC v. Fortinet, Inc.,
`2013 WL 5402089 (N.D. Cal. Sept. 26, 2013) .............................................................................8
`
`Tights, Inc. v. Kayser-Roth Corp.,
`442 F. Supp. 159 (M.D.N.C. 1977) ..............................................................................................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
`
`10611869
`
`
`- ii -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 4 of 12
`
`
`
`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
`
`Mr. Arst’s proposed $60-$70 million “reasonable royalty” on accused revenues of less than
`
`$1.8 million is economically nonsensical. Rather than attempt to defend Mr. Arst’s absurd math,
`
`Finjan’s Opposition seeks to inflate the amount of accused revenues to
`
` by expanding
`
`the scope of its infringement claim to encompass SRX devices alone. But while Finjan accused
`
`“Sky ATP alone,” it only accused SRX devices “used in combination with Sky ATP.” Dkt. 98
`
`(Finjan’s MSJ) at 1-2. For good reason. Despite Finjan’s misleading argument in its Opposition,
`
`Finjan’s own technical expert admitted that SRX devices alone
`
`
`
` even under Finjan’s infringement theory—something Juniper could have
`
`easily demonstrated during summary judgment had Finjan accused the SRX alone of infringement.
`
`Finjan does not dispute that the revenues from the “Accused Products” as Finjan itself
`
`defined them—“Sky ATP alone” and SRX devices “used in combination with Sky ATP,” id—
`
`were less than $1.8 million. Nor does Finjan challenge the fact that only
`
` SRX devices could
`
`have been used with Sky ATP during the damages period. Given these facts, Mr. Arst’s opinion
`
`clearly flunks the requirements of Daubert for at least the following reasons:
`
`
`
`It would have been economically irrational for Juniper to pay a royalty of $60-$70 million
`dollars on accused revenues of $1.8 million.
`
` Mr. Arst’s proposed royalty, which amounts to an effective royalty of almost 4,000%, is
`orders of magnitude more than the rates at which Finjan itself begins negotiations (8% for
`
`hardware, 16% for software) under its own licensing policy.
`
` Mr. Arst did not apply a proper “cost savings” analysis, which requires consideration of
`the defendant’s next best alternative. Even Finjan’s own technical expert did not consider
`
`the alternative Mr. Arst used (“sandboxing” every file) to be commercially viable.
`
` Mr. Arst does not account at all for Juniper’s alternative of waiting 14 months until the
`’494 Patent expired before releasing Sky ATP. No economically rational actor would have
`
`done otherwise if the alternative would have been to incur an additional $60-$70 million in
`
`costs (or pay the identical amount to Finjan) to generate $1.8 million in revenue.
`
` Mr. Arst’s calculation of Juniper’s alleged “cost savings” by multiplying Juniper’s
`Amazon Web Services (“AWS”) costs by 359-419 is arbitrary and unreliable.
`
`10611869
`
`
`- 1 -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`
`
`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 247 Filed 11/23/18 Page 5 of 12
`
`Finjan cannot rescue Mr. Arst’s damages theory by changing the scope of its infringement
`
`claim. Mr. Arst’s damages opinion is unsupported by the facts, and should be excluded.
`I.
`FINJAN CANNOT DEFEND MR. ARST’S OPINION UNDER THE CORRECT
`DAMAGES BASE
`
`
`In its Opposition, Finjan fails to acknowledge that it expressly defined “Accused Products”
`as “(1) Juniper’s SRX Gateways used in combination with Sky ATP, and (2) Sky ATP alone
`(‘Accused Products’).” Dkt. 98 (Finjan’s MSJ) at 1-2. These Accused Products generated less than
`$1.8 million in revenues during the damages period. Finjan does not even attempt to defend
`Mr. Arst’s $60-$70 million damages opinion in light of the actual damages base at issue.
`Instead, throughout its Opposition, Finjan attempts to sneak into its infringement claim a
`new, third category of products—SRX devices alone.1 See, e.g., Opp. at 3 (“accused SRX
`products”), id. at 11 (“accused SRX gateways”). Based on this new infringement theory, Finjan
`
`claims that the damages base is actually around
`
` Opp. at 1. This is Finjan’s only
`
`response to Juniper’s argument that Mr. Arst’s opinion should be excluded because it defies basic
`
`economics. Opp. § III.A. Finjan’s new infringement theory fails for at least two reasons.
`
`First, Finjan’s new theory is untimely. While Finjan accused “Sky ATP alone” of
`
`infringing Claim 10, Finjan never accused SRX devices alone. Dkt. 98 (Finjan MSJ) at 1-2. Finjan
`
`cannot change course now, after expert discovery and on the eve of trial.
`
`Second, Finjan has no colorable infringement claim against SRX devices alone. The only
`
`argument Finjan advances is its contention that
`
` Opp. at 12-14, n.14. This is misleading, if not completely false.
`
` as Finjan’s own technical expert admitted.
`
`
`
`
`
`
`
`
`
`
`
`
`
`1 Contrary to Finjan’s suggestion, the Court explicitly limited its summary judgment
`holding to “SRX Gateways used in combination with Sky ATP” and held that the issue of “the
`extent of damages” would be decided at trial. See Dkt. 189 at 3, 21 (emphasis added).
`
`10611869
`
`
`- 2 -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 6 of 12
`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 6 of 12
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`aA&WwNO
`OoOoNYDW
`
`12.201 215-21?
`
`Finjan’s reliance on Finjan, Inc. v. Secure Computing Corp., 626 F.3d 1197 (Fed. Cir.
`
`2010), is unavailing. Opp. at 12. In that case, the court found that a system claim was infringed by
`
`a product that was shipped with all necessary software for implementing the accused system. Id.
`
`at 1205 (“the useris only activating meansthat are already present in the underlying software’’). In
`
`contrast, SRX devices are not shipped with the necessary software. That software is part of Sky
`
`ATP, which a useronly gains access to after registering for, and activating, a Sky ATP license.
`
`The Federal Circuit distinguished Secure Computing on this very basis in Nazomi Comm., Inc. v.
`
`Nokia Corp., 739 F.3d 1339 (Fed. Cir. 2014), where it held defendants’ products did not infringe
`
`10
`
`because they required the installation of additional software to perform the patented system—
`
`11
`
`12
`
`13
`
`unlike in Secure Computing, where “the infringing software capable of practicing the claim
`
`limitations wason the accused devices.” Jd. at 1346.
`
`Further, Finjan’s new “SRX devices alone” infringement theory is untethered to Mr. Arst’s
`
`14
`
`cost savings theory, which is based on the additional costs that would allegedly be incurred if Sky
`
`15
`
`ATP performed sandboxing for all incoming files. Even under Mr. Arst’s deeply flawed theory,
`
`16
`
`17
`
`18
`
`Juniper would enjoy no cost savings with respect to SRX devices that were never used in
`
`combination with Sky ATP, because no additional sandboxing would be required for these
`
`devices. In other words, the alleged cost savings of $60-$70 million would only apply to the $1.8
`
`19
`
`million in revenues, regardless of which damagesbaseis considered.
`Finjan does not dispute that, during the damages period, SRX customers only activated[il
`paid and|| free licenses to Sky ATP, so there were a maximum of|| SRX devices that could
`have been used with Sky ATP. Finjan also does not dispute that the revenues associated with those
`|| SRX devices and associated Sky ATP licenses were less than $1.8 million. Yet Finjan does
`
`20
`
`21
`
`22
`
`23
`
`
`
`10611869
`
`-3-
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 7 of 12
`
`
`
`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
`
`not attempt to explain why Mr. Arst’s proposed $60-$70 million royalty makes economic sense in
`
`light of these facts. The conclusory arguments Finjan musters in defense of Mr. Arst’s opinion are
`
`all premised on the faulty assumption that the damages base is
`
` But almost all of that
`
`amount is attributable to SRX devices alone, which are not Accused Products. And it is settled law
`
`that a damages expert may not base damages on revenues from non-accused products. See Enplas
`
`Display Device Corp., v. Seoul Semiconductor Co., Ltd., 2018 WL 6033533, at *10 (Fed. Cir.
`
`Nov. 19, 2018) (overturning jury’s damages award where expert testimony supporting it was
`
`“based, in part, on non-infringing sales of non-accused [products],” because “acts that do not
`
`constitute patent infringement cannot provide a proper basis for recovery of damages”).
`II.
`
`FINJAN’S PUFFERY ABOUT THE VALUE OF CLAIM 10 IS UNSUPPORTED
`
`Finjan’s effort to turn the benefits Juniper allegedly received from Claim 10 into a “factual
`
`dispute” fails together with Finjan’s attempt to inflate the damages base. Opp. at 4. Finjan asserts,
`
`without any support, that: (1) “Juniper[] [had an] essential need for the patented technology;” (2)
`
`Juniper received “extensive benefits” from Claim 10 “across Juniper’s entire network from its
`
`infringement;” and (3) Juniper’s use of Claim 10 was “extensive and pervasive;” “[r]evenues of
`
`products that incorporate the infringing technology . . . do not capture the value of the significant
`
`benefits Juniper received, including to its entire network, based upon its infringement.” Opp. at 1,
`
`4. Each of these statements is contradicted by the fact that a mere
`
`
`
`arguably compatible SRX devices sold during the damages period were enabled to be used in
`
`combination with Sky ATP. Dkt. 229-6 (Ugone Rpt.) at 40 (Table 4) & Ex. 5.
`III. MR. ARST’S DEPARTURE FROM FINJAN’S OWN LICENSING POLICY IS
`UNSUPPORTED
`Finjan provides no coherent explanation for Mr. Arst’s dramatic deviation from Finjan’s
`own licensing policy, with its 8%/16% starting rates. Finjan states that those rates have been
`applied to “total revenue.” Opp. at 6. This does not help Finjan, as Juniper’s “total revenue” for
`the Accused Products is less than $1.8 million. Mr. Arst’s royalty amounts to a nearly 4,000%
`rate. Finjan claims that this is a “manufactured” and “outrageous” number, id., but it is just simple
`math from Mr. Arst’s proposed $70 million royalty on accused sales of less than $1.8 million.
`Finjan’s citation to Tights, Inc. v. Kayser-Roth Corp., 442 F. Supp. 159, 165 (M.D.N.C.
`
`10611869
`
`
`- 4 -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 8 of 12
`
`
`
`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
`
`1977), provides no support for Mr. Arst’s dramatic departure from Finjan’s own licensing policy.
`
`Tights, which was decided over forty years ago by an out-of-district court, found that prior
`
`licenses were arrived at by wielding the threat of litigation over an “impecunious patentee.” Id.
`
`Here, Finjan has a number of license agreements decided outside the context of litigation. See Dkt.
`
`229-6 (Ugone Rpt.) at 58-60.
`
`
`
`
`
`See Dkt. 230-10 (Blue Coat Trial Tr.) at 256:5-12; Dkt.
`
`228-10 (Hartstein Dep.) at 42:25-43:5. Mr. Arst’s opinion cannot be squared with that policy.
`IV. MR. ARST FAILS TO APPLY A RELIABLE METHODOLOGY
`Finjan states that Juniper’s Motion does “not challenge Mr. Arst’s methodology.” Not so.
`
`As Juniper’s Motion explained, Mr. Arst’s methodology is unreliable. See Mot. at 8-12.
`
`A cost savings analysis of the sort Mr. Arst attempted to perform requires consideration of
`
`the costs associated with the defendant’s next best alternative. See Metaswitch Networks Ltd. v.
`
`Genband US LLC, 2016 WL 874737, at *2 (E.D. Tex. Mar. 5, 2016) (“‘cost approach’ . . .
`compares the cost of using the patented technology with the cost of implementing ‘the next-best
`acceptable non-infringing alternative.’”). But neither Mr. Arst nor Dr. Cole did anything to
`
`determine what Juniper’s “next best alternative” was. Dr. Cole admitted he was not given the
`
`“direct task” of analyzing Juniper’s non-infringing alternatives. Ex. 1 at 44:19-21, 36:22-37:9.
`
`Following Dr. Cole’s deposition on November 14, 2018, the arbitrary nature of Mr. Arst’s
`
`cost savings analysis has become all the more apparent. Mr. Arst testified that he understood from
`
`Dr. Cole that Juniper’s “next best alternative to infringing Claim 10” would have involved the re-
`
`processing of files, which would require “increased sandboxing.” Ex. 2 (Arst Dep.) at 106:14-
`
`107:1. But Dr. Cole confirmed that he did not actually assess which of the various alternatives
`
`would have been Juniper’s “next best” option. Ex. 1 (Cole Dep.) at 44:19-21. Moreover, while
`
`Finjan characterizes increased sandboxing as the “only viable noninfringing alternative presented
`
`during fact discovery” (Opp. at 9), Dr. Cole directly contradicted this characterization and Mr.
`
`Arst’s understanding. Dr. Cole testified that the alternative of reprocessing files, on which Mr.
`Arst bases his analysis, would not have been a viable option for Juniper:
`
`10611869
`
`
`- 5 -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 9 of 12
`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 9 of 12
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`
`
`In Microsoft Corporation v. Corel Corp., 2017 WL 6492468 (N.D. Cal. Dec. 19, 2017),
`
`the court confronted a similarly flawed cost savings analysis. The plaintiff's damages expert
`
`calculated damages “on the basis of the hypothetical negotiation approach,” including
`
`\ooo—la7)—WwN_
`
`10
`
`11
`
`12
`
`13
`
`14
`
`consideration of the defendant’s “design-around cost.” Jd. at *1. Defendant argued that plaintiffs
`
`damages expert should be precluded from presenting her design around cost calculations because
`
`she “provide[d] no sufficient facts or data to support her position that [the proposed design
`
`around] would have been considered by [defendant] in this hypothetical negotiation.” Jd. at *2.
`
`The court agreed, finding that plaintiff's damages expert failed to “explain why [the proposed
`
`design around] would be an economically rational choice for [defendant] in a hypothetical
`
`16
`
`17
`
`18
`
`19
`
`20
`
`licensing negotiation.” Jd.
`
`21
`
`Here, if one were to believe Mr. Arst that his proposed alternative—sandboxing every
`
`22
`
`file—would haveresulted in increased costs of $60-$70 million, then on its face this alternative
`
`23
`
`would not have been an “economically rational choice for [Juniper].” See id. Mr. Arst does not
`
`24
`
`explain why Juniper would even consider an alternative that would cost $60-$70 million to
`
`generate $1.8 million in revenue. Finjan’s technical expert concedes that this alternative is not
`
`26
`
`commercially viable. The icing on this methodologically flawed cake is that Mr. Arst does not
`
`27
`
`accountat all for Juniper’s alternative of waiting 14 months until the 494 patent expired before
`
`28
`
`releasing Sky ATP.
`
`10611869
`
`-6-
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 10 of 12
`
`
`
`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
`
`V. MR. ARST’S COST SAVINGS ANALYSIS IS UNRELIABLE
`Even on its own terms, Mr. Arst’s cost savings analysis is beset by numerous errors that
`
`render it unreliable and unsupported. Mot. at 8-12. Unable to explain those errors away, Finjan
`
`tries to reframe Juniper’s arguments into strawmen. For example, Finjan’s statement that “Juniper
`
`uses AWS . . . to perform the alleged infringing database lookups at a small fraction of the cost
`
`that would be required to analyze files using a sandboxing process” misses the point. Opp. at 7.
`
`Mr. Arst does not contend that Juniper’s database lookup costs would increase; he contends that
`
`Juniper’s sandboxing costs would increase. Notably, Finjan does not dispute that Juniper’s AWS
`
`invoices do not reflect any of Juniper’s sandboxing costs. Similarly, Finjan fails to address
`
`Juniper’s argument that
`
` Mot. at 11. Instead, Finjan
`
`misstates Juniper’s argument as contending that only
`
` Opp. at 11.
`
`Finjan also attempts to create discovery disputes to excuse Mr. Arst’s many errors.
`
`However, “[Finjan] as the patent holder, bears the burden of proving its damages[; if Juniper]
`
`refused to produce information that Mr. Arst required to determine the reasonable royalty [which
`
`it did not], then [Finjan] needed to get that information, if necessary through a motion to compel.
`
`[Finjan] fails to show any effort it took to get all the information necessary for its expert to
`
`provide a reasonable royalty calculation that does not rely on unreasonable inferences or
`
`speculation.” See Monolithic Power Sys., Inc. v. O2 Micro Int’l Ltd., 476 F. Supp. 2d 1143, 1155
`
`(N.D. Cal. 2007), clarified on denial of reconsideration, 2007 WL 1108615 (N.D. Cal. Apr. 11,
`
`2007); see also Microsoft Corp., 2017 WL 6492468, at *2 (excluding patentee’s damages expert’s
`
`testimony concerning design around costs and rejecting the expert’s argument that she had “no
`
`choice but to rely on [irrelevant evidence] because [defendant’s] witnesses could not provide a
`
`comparable estimate[;]” finding that if the patentee “believed that [defendant’s] provided
`
`insufficient information . . . [defendant] could have conducted discovery on that issue; and if
`
`[patentee] believed [defendant’s] responses to those discovery requests were inadequate,
`
`[patentee] could have moved to compel”).
`
`In addition to being irrelevant, Finjan’s complaints about Juniper’s discovery are wrong:
`
` Juniper did not represent that its production would be limited “to servers that host or
`
`10611869
`
`
`- 7 -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 11 of 12
`
`
`
`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
`
`directly interface with specifically accused features of the deployed or sold products at
`
`issue in this litigation,” but instead represented that its search would be so limited. As part
`
`of that search, Juniper located and then produced its AWS invoices, which include costs
`
`for the accused features of Sky ATP, but also include costs for products and services other
`
`than Sky ATP. Dkt. 239-3 (Juniper’s Responses to RFPs 95-97).
`
`
`
`In response to Finjan’s Interrogatory Number 11, Juniper explicitly informed Finjan that
`sandboxing is
` Ex. 3 (Juniper’s Response to Rog 11). Yet Finjan
`
`never asked Juniper to supplement its production nor did it request that Juniper produce its
`
` in advance of Mr. Arst’s report.
`
` Juniper never stated that the number of free Sky ATP licenses was unknowable, only that
`Juniper does not “maintain historical data” in the ordinary course. See Dkt. 125-8
`
`(Nagarajan Decl.) ¶ 6.
`
` and produced it
`
`on September 7, 2018—in advance of Mr. Arst’s report. Dkt. 228-6 (Icasiano Decl.) ¶ 4.
`
`
`
`
`
`
`
` Finjan chose not to request a deposition of any Juniper financial witness before it
`submitted its damages report, and instead chose to make (inaccurate) assumptions about
`
`Juniper’s financial documents. Finjan’s strategic choice not to take a deposition does not
`
`entitle it to exclude Juniper from presenting the facts.
`VI. MR. ARST SHOULD NOT BE GIVEN LEAVE TO DO A NEW ANALYSIS
`The errors in Mr. Arst’s report are fundamental to his analysis. To comply with Daubert,
`
`he would need to put forth an entirely new damages analysis. It would be highly prejudicial to
`
`Juniper to allow Mr. Arst to do so, with trial less than three weeks away. Finjan should be held
`
`accountable for its “overreaching bite.” See Network Prot. Scis., LLC v. Fortinet, Inc., 2013 WL
`
`5402089, at *8 (N.D. Cal. Sept. 26, 2013) (“where the report is not even close, there is a positive
`
`need to deny a second bite in order to encourage candor in the first place”). Finjan is a
`
`sophisticated party that has litigated many patent infringement cases. It surely knew that Mr.
`
`Arst’s report does not come close to complying with the dictates of Daubert and Rule 702.
`
`10611869
`
`
`- 8 -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

`

`Case 3:17-cv-05659-WHA Document 247 Filed 11/23/18 Page 12 of 12
`
`Dated: November 23, 2018
`
`IRELL & MANELLA LLP
`
`By: /s/ Rebecca L. Carson
`Rebecca L. Carson
`Attorneys for Defendant
`JUNIPER NETWORKS, INC.
`
`
`
`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
`
`10611869
`
`
`- 9 -
`
`JUNIPER'S REPLY ISO MOT TO EXCLUDE MR ARST
`(Case No 3:17-cv-05659-WHA)
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`

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