throbber
Sean Li
`
`From:
`Sent:
`To:
`
`Cc:
`Subject:
`
`Karineh Khachatourian <karinehk@rimonlaw.com>
`Tuesday, October 09, 2018 8:50 AM
`Cox, Brady; Hotze, Melissa; Sean Li; intel.alacritech.ipr; 'McPherson, Patrick D.'; Douglas,
`Christopher; Bradley, Kirk; 'benjamin.weed.PTAB@klgates.com';
`'erik.halverson@klgates.com'; Neilson, Derek; David Xue
`Alacritech-IPR-Team
`RE: Alacritech/Intel Oct. 2 call with Board
`
`Hi Sean
`
`For the 401 Petition, Cavium’s position is the same as Intel’s. Thanks.
`
`
`From: Cox, Brady <Brady.Cox@alston.com>
`Sent: Tuesday, October 9, 2018 8:48 AM
`To: Hotze, Melissa <melissa.hotze@weil.com>; Sean Li <seanli@quinnemanuel.com>; Karineh Khachatourian
`<karinehk@rimonlaw.com>; intel.alacritech.ipr <intel.alacritech.ipr@weil.com>; 'McPherson, Patrick D.'
`<PDMcPherson@duanemorris.com>; Douglas, Christopher <Christopher.Douglas@alston.com>; Bradley, Kirk
`<Kirk.Bradley@alston.com>; 'benjamin.weed.PTAB@klgates.com' <benjamin.weed.PTAB@klgates.com>;
`'erik.halverson@klgates.com' <erik.halverson@klgates.com>; Neilson, Derek <Derek.Neilson@alston.com>; David Xue
`<david.xue@rimonlaw.com>
`Cc: Alacritech-IPR-Team <alacritech-ipr-team@quinnemanuel.com>
`Subject: RE: Alacritech/Intel Oct. 2 call with Board
`
`Hi Sean,
`Adding on to the below response from Intel, while Dell was not a part of the conference call with the Board and does not
`know the full extent of what was discussed there (and is not yet joined to the IPRs at issue), Dell does not consent to the
`use of its designated confidential materials produced in the district court litigation in Intel’s or Cavium’s IPRs.
`Best,
`-Brady
`
`
`From: Hotze, Melissa [mailto:melissa.hotze@weil.com]
`Sent: Monday, October 8, 2018 7:31 PM
`To: Sean Li <seanli@quinnemanuel.com>; 'Karineh Khachatourian' <karinehk@rimonlaw.com>; intel.alacritech.ipr
`<intel.alacritech.ipr@weil.com>; 'McPherson, Patrick D.' <PDMcPherson@duanemorris.com>; Douglas, Christopher
`<Christopher.Douglas@alston.com>; Bradley, Kirk <Kirk.Bradley@alston.com>; 'benjamin.weed.PTAB@klgates.com'
`<benjamin.weed.PTAB@klgates.com>; 'erik.halverson@klgates.com' <erik.halverson@klgates.com>; Cox, Brady
`<Brady.Cox@alston.com>; Neilson, Derek <Derek.Neilson@alston.com>; 'David Xue' <david.xue@rimonlaw.com>
`Cc: Alacritech-IPR-Team <alacritech-ipr-team@quinnemanuel.com>
`Subject: RE: Alacritech/Intel Oct. 2 call with Board
`
`Sean,
`
`First, as Intel has repeatedly stated, Intel does not agree that its protected information in the district court litigation can
`be used in the IPRs. See, e.g., January 11, 2018 Constant email. The Protective Order in the litigation specifically
`precludes such use. See, e.g., Protective Order at Paragraph 11 (“in no event shall any Party’s Protected material be
`submitted, extracted, digested or otherwise referred to” in connection with an IPR “without written consent of the
`Party”). During the teleconference with the Board, Intel’s referenced the litigation only in response to Judge Boudreau’s
`question. Rough at 19:1-14 (“JUDGE BOUDREAU: All right. And just to be clear, the indemnification agreement between
`
`1
`
`Alacritech Ex. 2402 Page 01
`
`

`

`Intel and Dell has not been produced in the related District Court litigation either?”). To be unambiguously clear, Intel
`does not agree that Alacritech can use any of its protected information from the district court litigation in any
`IPR. Alacritech must first obtain permission from the Board for any additional discovery it seeks to use in these IPRs. As
`the Federal Circuit has explained, “[d]iscovery in inter partes review proceedings is more limited than in proceedings
`before district courts or even other proceedings before the PTO” and “[g]iven the time deadlines imposed on these
`proceedings, it was intended that the PTO would ‘be conservative in its grants of discovery.’” Wi-Fi One, LLC v. Broadcom
`Corp., 887 F.3d 1329, 1338 (Fed. Cir. 2018) (citations omitted).
`
`Second, Alacritech’s requests below are nothing more than an attempt to obtain additional discovery prior to obtaining
`authorization from the Board. The Board specifically warned Alacritech about attempting to obtain additional discovery
`prior to a decision on its motion. 10/2/2018 Rough Transcript at 27:13-15 (“Just to be clear, we're not authorizing the
`additional discovery at this point, only a motion for additional discovery.”) As Intel has explained repeatedly, Alacritech
`has not shown that it is entitled to the indemnity agreements and information requested below under the Garmin
`factors. Intel intends to explain this in detail to the Board in Intel’s opposition to Alacritech’s motion for additional
`discovery in IPR2018-00226 and IPR2018-00234. Alacritech has done nothing more than speculate that the indemnity
`agreements (the existence of which are in the public record) will provide any additional “useful” information. This is
`insufficient to obtain discovery in an IPR. See e.g., Wi-Fi One, 887 F.3d at 1340 (declining to find Board abused its
`discretion in concluding that production of the indemnity and JDG agreements, among other things, was not warranted
`where Patent Owner alleged Petitioner was time barred based on parties it indemnified because nothing existed but a
`“mere possibility” that something useful would be found).
`
`Thanks,
`
`Melissa
`
`
`
`
`
`
`Melissa Hotze
`
`Weil, Gotshal & Manges LLP
`700 Louisiana, Suite 1700
`Houston, TX 77002-2755
`melissa.hotze@weil.com
`+1 713 546 5033 Direct
`+1 713 224 9511 Fax
`
`
`
`From: Sean Li <seanli@quinnemanuel.com>
`Sent: Sunday, October 7, 2018 12:22 PM
`To: Hotze, Melissa <melissa.hotze@weil.com>; 'Karineh Khachatourian' <karinehk@rimonlaw.com>; intel.alacritech.ipr
`<intel.alacritech.ipr@weil.com>; 'McPherson, Patrick D.' <PDMcPherson@duanemorris.com>;
`'christopher.douglas@alston.com' <christopher.douglas@alston.com>; 'kirk.bradley@alston.com'
`<kirk.bradley@alston.com>; 'benjamin.weed.PTAB@klgates.com' <benjamin.weed.PTAB@klgates.com>;
`'erik.halverson@klgates.com' <erik.halverson@klgates.com>; 'Brady.Cox@alston.com' <Brady.Cox@alston.com>;
`'Neilson, Derek' <Derek.Neilson@alston.com>; 'David Xue' <david.xue@rimonlaw.com>
`Cc: Alacritech-IPR-Team <alacritech-ipr-team@quinnemanuel.com>
`Subject: Alacritech/Intel Oct. 2 call with Board
`
`Counsel,
`
`During the Oct. 2, 2018 call with the Board Intel’s counsel represented that Intel’s standard terms and conditions are
`available on the Internet publicly. See Rough Tr. at 20:23-25 (“Also, Intel's standard terms and conditions which govern
`
`2
`
`Alacritech Ex. 2402 Page 02
`
`

`

`sales to other parties are available on the Internet publicly.”). We cannot locate such allegedly standard terms and it
`was not clear to us whether Intel is claiming that those terms are applicable to any of its relationships with its customers
`in the underlying suits. Please provide us the link for the terms and conditions, and confirm that an identical contract
`was entered into with each of the defendants in the underlying cases, with no other terms or conditions. Additionally,
`Intel did not deny during the Board teleconference that there are separate memorializations of its agreement to
`indemnify each of the defendants in the underlying cases. See Rough Tr., passim; see also id. at 26:8 et seq. In fact, Intel
`has admitted that its indemnity in the underlying cases is only applicable to certain claims and patents, which is
`undoubtedly not memorialized in any of the mentioned generic agreements. As such, please identify the nature and
`scope of the documentation memorializing Intel’s relationships with each of the defendants specific to the underlying
`cases. We request the same of Cavium for its indemnity of any defendant in the underlying cases.
`
`
`Also, both Intel and Cavium referenced commercial agreements with Dell (but not the other defendants) without
`referencing their full names and dates. See Rough Tr. at 20:19-21 (“We checked with Dell, and they said they did
`produce that indemnity agreement, the sales agreement that governs indemnity between Intel and Dell”); id. at 24:22-
`25:1 (“And in answer to your question about agreements between Cavium and Dell that may or may not discuss
`indemnification, my recollection and understanding is that those documents were produced in the litigation long ago.”).
`We request Intel and Dell provide us the full names and dates and bates numbers of those agreements. Additionally,
`please confirm that Intel and Cavium have not produced their commercial agreements with any of the Wistron and
`CenturyLink entities.
`
`
`Finally, please confirm that Dell or Cavium no longer object to the use of any documents and information designated
`under the PO in the underlying cases in connection with Petitioners’ IPRs. We were surprised by Petitioners
`representations about protected material from the underlying cases during the Board call given that Petitioners have
`previously and repeatedly objected to Alacritech’s use of any such information designated in the underlying cases. We
`assume that by referencing litigation productions, Dell and Cavium have no intentions to object our use of those
`agreements or any other protected information from the underlying cases going forward and will proceed with that
`understanding in future filings unless told otherwise.
`
`In light of the short briefing schedule, please let us know your response by the end of the day Monday.
`
`Best regards,
`Ziyong (Sean) Li
`Associate,
`Quinn Emanuel Urquhart & Sullivan, LLP
`
`50 California Street, 22nd Floor
`San Francisco, CA 94111
`415-875-6373 Direct
`415.875.6600 Main Office Number
`415.875.6700 FAX
`seanli@quinnemanuel.com
`www.quinnemanuel.com
`
`NOTICE: The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message
`may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended
`recipient or agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any
`review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately
`by e-mail, and delete the original message.
`
`
`
`
`
`The information contained in this email message is intended only for use of the individual or entity named above. If the
`reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended
`recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly
`prohibited. If you have received this communication in error, please immediately notify us by email, postmaster@weil.com,
`and destroy the original message. Thank you.
`
`3
`
`Alacritech Ex. 2402 Page 03
`
`

`

`
`
`NOTICE: This e-mail message and all attachments may contain legally privileged and confidential information
`intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified
`that you may not read, copy, distribute or otherwise use this message or its attachments. If you have received
`this message in error, please notify the sender by email and delete all copies of the message immediately.
`
`4
`
`Alacritech Ex. 2402 Page 04
`
`

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