throbber
From:
`To:
`Cc:
`
`Subject:
`Date:
`
`Coulson, Chris
`"Day, Evan S. (Perkins Coie)"
`Bernstein, Matthew C. (Perkins Coie); Ng, Chun (Perkins Coie); PerkinsServiceBradiumIPR@perkinscoie.com;
`Zachary, Michael; Ulrich, Clifford
`RE: Microsoft Corp. v. Bradium Techs. LLC (IPR2016-00448, IPR2016-00449): Limited Waiver
`Monday, March 20, 2017 4:01:29 PM
`
`Dear Evan,
`
`Bradium provided a proposal on March 12 which offers Mr. Lavi the assurances that were
`suggested by the Board. However, we have not heard back regarding Mr. Lavi other than
`your e-mail below of March 13, 2017.
`
`Please advise Mr. Lavi’s response to Bradium’s proposal, and please advise whether Mr. Lavi
`will appear in the U.S. for deposition by the March 24, 2017 compromise date that Bradium
`offered via my March 12 e-mail. If Mr. Lavi will not be offered in the U.S. and Microsoft
`plans to voluntarily withdraw Exhibit 1017 (Lavi declaration), please let us know that.
`
`
`
`Best regards.
`
`Chris Coulson
`ANDREWS KURTH KENYON LLP
`Tel: 212.908.6409
`
`From: Day, Evan S. (Perkins Coie) [mailto:EDay@perkinscoie.com]
`Sent: Monday, March 13, 2017 7:19 PM
`To: Coulson, Chris
`Cc: Bernstein, Matthew C. (Perkins Coie); Ng, Chun (Perkins Coie);
`PerkinsServiceBradiumIPR@perkinscoie.com; Zachary, Michael; Ulrich, Clifford
`Subject: RE: Microsoft Corp. v. Bradium Techs. LLC (IPR2016-00448, IPR2016-00449): Limited Waiver
`
`Chris,
`
`Proposed revisions are attached. This is also subject to further review/approval from Microsoft. I will
`be sending to Mr. Lavi later tonight (tomorrow morning in Tel Aviv).
`
`We disagree with the assertions in your second paragraph, but we can address timing if and when we
`get an agreement for Mr. Lavi to appear. We have discussed the length of the deposition on multiple
`previous occasions and Microsoft’s position has not changed.
`
`Regards,
`Evan
`
`Evan Day | Perkins Coie LLP
`COUNSEL
`11988 El Camino Real Suite 350
`San Diego, CA 92130-2594
`D. +1.858.720.5743
`F. +1.858.720.5799
`E. EDay@perkinscoie.com
`
`(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:21)(cid:19)(cid:27)(cid:20)(cid:3)
`(cid:37)(cid:85)(cid:68)(cid:71)(cid:76)(cid:88)(cid:80)(cid:3)(cid:55)(cid:72)(cid:70)(cid:75)(cid:81)(cid:82)(cid:79)(cid:82)(cid:74)(cid:76)(cid:72)(cid:86)(cid:3)(cid:47)(cid:47)(cid:38)(cid:3)(cid:16)(cid:3)(cid:83)(cid:68)(cid:87)(cid:72)(cid:81)(cid:87)(cid:3)(cid:82)(cid:90)(cid:81)(cid:72)(cid:85)(cid:3)
`(cid:48)(cid:76)(cid:70)(cid:85)(cid:82)(cid:86)(cid:82)(cid:73)(cid:87)(cid:3)(cid:38)(cid:82)(cid:85)(cid:83)(cid:82)(cid:85)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:3)(cid:16)(cid:3)(cid:83)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:3)
`(cid:44)(cid:51)(cid:53)(cid:21)(cid:19)(cid:20)(cid:25)(cid:16)(cid:19)(cid:19)(cid:23)(cid:23)(cid:27)
`
`1
`
`

`

`From: Coulson, Chris [mailto:CCoulson@kenyon.com]
`Sent: Sunday, March 12, 2017 4:41 PM
`To: Day, Evan S. (SDO)
`Cc: Bernstein, Matthew C. (SDO); Ng, Chun (SEA); *Perkins-Service-MSFT-Bradium-IPR; Zachary,
`Michael; Ulrich, Clifford
`Subject: RE: Microsoft Corp. v. Bradium Techs. LLC (IPR2016-00448, IPR2016-00449): Limited Waiver
`
`Dear Evan,
`
`Bradium and Mr. Levanon are still considering the language of the attached limited waiver
`agreement, but have authorized us to send this draft to you. The final agreement will be subject to
`approval by Bradium and Mr. Levanon. Please confirm that you will promptly forward this draft to
`Mr. Lavi for his consideration.
`
`Regarding schedule, at this point even if agreement is reached, Bradium will be prejudiced by a late
`deposition. Bradium is willing to compromise to provide time for Mr. Lavi to comply with his
`obligation to appear in the United States, but will need Mr. Lavi to appear for deposition for up to
`two days, to be completed no later than March 24, 2017.
`
`
`
`Chris Coulson
`ANDREWS KURTH KENYON LLP
`Tel: 212.908.6409
`
`
`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