throbber
Case 5:18-md-02834-BLF Document 457-1 Filed 07/03/19 Page 1 of 6
`Case 5:18-md-02834—BLF Document 457-1 Filed 07/03/19 Page 1 of 6
`
`
`
`
`EXHIBIT 1
`
`
`EXHIBIT 1
`
`
`
`

`

`Case 5:18-md-02834-BLF Document 457-1 Filed 07/03/19 Page 2 of 6
`
`From:
`Sent:
`To:
`Cc:
`
`Subject:
`
`Sandy Seth <sseth@stubbsalderton.com>
`Monday, July 1, 2019 4:43 PM
`Melanie Mayer; Ravi Ranganath; David Hadden; Amazon_PersonalWeb_Team
`Viviana Boero Hedrick; Ted Maceiko; Wesley Monroe; Jeffrey Gersh; Stanley H. Thompson Jr.; Michael
`Sherman
`RE: PersonalWeb Patent Litigation - Invalidity Contentions/Report
`
`Melanie, following up on the email below please advise on some available times tomorrow when we can discuss.   
`
`Thank you. 
`
`Regards, 
`
`Sandy 
`
`From: Sandy Seth  
`Sent: Friday, June 28, 2019 4:55 PM 
`To: Melanie Mayer <mmayer@fenwick.com>; Ravi Ranganath <rranganath@fenwick.com>; David Hadden 
`<DHadden@fenwick.com>; Amazon_PersonalWeb_Team <Amazon_PersonalWeb_Team@fenwick.com> 
`Cc: Viviana Boero Hedrick <vhedrick@stubbsalderton.com>; Ted Maceiko <ted@maceikoip.com>; Wesley Monroe 
`<wmonroe@stubbsalderton.com>; Jeffrey Gersh <jgersh@stubbsalderton.com>; Stanley H. Thompson Jr. 
`<sthompson@stubbsalderton.com>; Michael Sherman <masherman@stubbsalderton.com> 
`Subject: RE: PersonalWeb Patent Litigation ‐ Invalidity Contentions/Report 
`
`Melanie: 
`
`Why do you believe Amazon would be entitled to rely upon any obviousness combinations?  Rule 3‐3(b) requires a 
`disclosure of ‘[w]hether each item of prior art anticipates each asserted claim or renders it obvious,’ and if ‘obviousness 
`is alleged, an explanation of why the prior art renders the asserted claim obvious, including an identification of any 
`combinations of prior art showing obviousness.’ Vague or ‘catch‐all phrases’ of obviousness are insufficient.” Slot 
`Speaker Technologies, Inc. v. Apple, Inc. 2017 WL 235049 at *5 (N.D. Cal 2017). 
`
`Amazon and Twitch charted 24 references in their invalidity contentions.  Amazon and Twitch did not chart even a single 
`obviousness combination nor did they provide any explanation of why any given combination of references would 
`render any given claim obvious.  In the more than seven months since providing its invalidity contentions has Amazon 
`ever provided any excuse for such failure or moved to supplement its invalidity contentions .  
`
`As we already stated in our email to Ravi, it is our position that Amazon and Twitch’s expert report cannot include any 
`obviousness combinations in light of the above.  The report is limited to discussing why any of the 24 charted references 
`anticipate or individually render each asserted claims obvious. 
`
`PersonalWeb therefore is not inclined to enter any stipulation that would allow the invalidity report to include any 
`obviousness combinations without an agreed limit to a reasonable number of anticipation references and obviousness 
`combinations.   
`
`We would welcome a discussion to see what, if any, stipulation can be reached.  Are you and Ravi available Monday? 
`
`Regards, 
`
`1
`
`

`

`Case 5:18-md-02834-BLF Document 457-1 Filed 07/03/19 Page 3 of 6
`

`Sandy 


`From: Melanie Mayer <mmayer@fenwick.com>  
`Sent: Tuesday, June 25, 2019 3:24 PM 
`To: Sandy Seth <sseth@stubbsalderton.com>; Ravi Ranganath <rranganath@fenwick.com>; David Hadden 
`<DHadden@fenwick.com>; Amazon_PersonalWeb_Team <Amazon_PersonalWeb_Team@fenwick.com> 
`Cc: Viviana Boero Hedrick <vhedrick@stubbsalderton.com>; Ted Maceiko <ted@maceikoip.com>; Wesley Monroe 
`<wmonroe@stubbsalderton.com>; Jeffrey Gersh <jgersh@stubbsalderton.com>; Stanley H. Thompson Jr. 
`<sthompson@stubbsalderton.com>; Michael Sherman <masherman@stubbsalderton.com> 
`Subject: RE: PersonalWeb Patent Litigation ‐ Invalidity Contentions/Report 

`Sandy,  

`Under Amazon and Twitch’s proposal, Amazon and Twitch will identify the specific prior art references and obviousness 
`combinations they will rely on.  The local rules of the Court do not require Amazon and Twitch to limit the number of 
`prior art references or combinations and we are not proposing any such limits.  

`Regards,  
`Melanie 

`MELANIE MAYER 
`Partner | Fenwick & West LLP | +1 206‐389‐4569 | mmayer@fenwick.com 
`Admitted to practice in Washington. 



`From: Sandy Seth [mailto:sseth@stubbsalderton.com]  
`Sent: Friday, June 21, 2019 3:53 PM 
`To: Ravi Ranganath <rranganath@fenwick.com>; David Hadden <DHadden@fenwick.com>; 
`Amazon_PersonalWeb_Team <Amazon_PersonalWeb_Team@fenwick.com> 
`Cc: Viviana Boero Hedrick <vhedrick@stubbsalderton.com>; Ted Maceiko <ted@maceikoip.com>; Wesley Monroe 
`<wmonroe@stubbsalderton.com>; Jeffrey Gersh <jgersh@stubbsalderton.com>; Stanley H. Thompson Jr. 
`<sthompson@stubbsalderton.com>; Michael Sherman <masherman@stubbsalderton.com> 
`Subject: RE: PersonalWeb Patent Litigation ‐ Invalidity Contentions/Report 

`Ravi, 

`Thanks for your email. 

`Before we respond, how many anticipation references and how many obviousness combinations are you willing to limit 
`your identification to three weeks before your expert reports are due?  Also are you willing to limit the obviousness 
`references to be selected only from the charted set? 

`Regards, 

`Sandy 


`
`2
`
`

`

`Case 5:18-md-02834-BLF Document 457-1 Filed 07/03/19 Page 4 of 6
`
`From: Ravi Ranganath <rranganath@fenwick.com>  
`Sent: Thursday, June 20, 2019 5:15 PM 
`To: Sandy Seth <sseth@stubbsalderton.com>; David Hadden <DHadden@fenwick.com>; Amazon_PersonalWeb_Team 
`<Amazon_PersonalWeb_Team@fenwick.com> 
`Cc: Viviana Boero Hedrick <vhedrick@stubbsalderton.com>; Ted Maceiko <ted@maceikoip.com>; Wesley Monroe 
`<wmonroe@stubbsalderton.com>; Jeffrey Gersh <jgersh@stubbsalderton.com>; Stanley H. Thompson Jr. 
`<sthompson@stubbsalderton.com>; Michael Sherman <masherman@stubbsalderton.com> 
`Subject: RE: PersonalWeb Patent Litigation ‐ Invalidity Contentions/Report 

`Sandy: 
`
`  
`While Amazon and Twitch’s invalidity contentions fully complied with the patent local rules, we agree it is in the parties’ 
`interests to help narrow issues in advance of expert reports. 
`
`  
`Along these lines, PersonalWeb’s Patent L.R. 3‐8 damages contentions provide no information about its actual damages 
`theory.  For example, the contentions do not identify specific licenses on which PersonalWeb and its expert will rely, do 
`not describe how the claimed inventions drive Amazon or Twitch’s revenue or success, or provide any analysis under the 
`Georgia‐Pacific factors.  Instead, those contentions merely lay out basic principles of law and describe approaches and 
`factors PersonalWeb “plans to consider” without any specific contentions related to damages or factual support for 
`those contentions.  Amazon and Twitch thus have no reasonable notice of PersonalWeb’s damages theories. 
`
`  
`To address both sides’ concerns, we propose that 3 weeks before the opening expert report deadlines: 
`  
`
`(1) Amazon and Twitch will identify the specific prior art references and obviousness combinations they will rely on, 
`and to the extent not already disclosed in the invalidity contentions, will identify which elements are met by 
`each prior art reference in an obviousness combination; 
`(2) PersonalWeb will supplement its Patent L.R. 3‐8 damages contentions, identifying separately for Amazon and 
`Twitch, at least the following:  (i) the type of damages PersonalWeb will seek (e.g., reasonable royalty, lump 
`sum, etc.); (ii) the license agreements, if any, PersonalWeb will rely on to support their damages contentions; 
`(iii) a description of the factual and legal bases for PersonalWeb’s contention, if any, that the claimed inventions 
`drive consumer demand and revenue for Amazon and Twitch’s accused products; and (iv) a description of the 
`relevant royalty base and how, if at all, PersonalWeb contends that base should be apportioned. 
`
`  
`
`Let us know if PersonalWeb agrees. 
`
`  
`Best regards, 

`RAVI RANGANATH 
`Associate | Fenwick & West LLP | +1 650‐335‐7614 | rranganath@fenwick.com 
`Admitted to practice in California. 

`From: Sandy Seth [mailto:sseth@stubbsalderton.com]  
`Sent: Tuesday, June 18, 2019 1:40 PM 
`To: David Hadden <DHadden@fenwick.com>; Amazon_PersonalWeb_Team 
`<Amazon_PersonalWeb_Team@fenwick.com> 
`Cc: Viviana Boero Hedrick <vhedrick@stubbsalderton.com>; Ted Maceiko <ted@maceikoip.com>; Wesley Monroe 
`<wmonroe@stubbsalderton.com>; Jeffrey Gersh <jgersh@stubbsalderton.com>; Stanley H. Thompson Jr. 
`<sthompson@stubbsalderton.com>; Michael Sherman <masherman@stubbsalderton.com> 
`Subject: RE: PersonalWeb Patent Litigation ‐ Invalidity Contentions/Report 

`Dear David, 

`
`3
`
`

`

`Case 5:18-md-02834-BLF Document 457-1 Filed 07/03/19 Page 5 of 6
`We write concerning Amazon’s and Twitch’s invalidity contentions.   

`The respective invalidity charts are just shy of 6,000 pages each and chart anticipation/obviousness for 24 references 
`and cite to a total 19 patents, 26 non‐patent publications and 8 systems/services.  Moreover, in these invalidity 
`contentions, Amazon and Twitch take the position that (at least) any one of these 24 charted references may be used in 
`combination with any other of the 53 total references in uncharted obviousness combinations.  That would include 
`thousands of potential obvious combinations.  We do not believe in their current form these invalidity contentions give 
`us reasonable notice of the actual obviousness combinations you will be relying upon since there is no accompanying 
`analysis as to which specific combinations you allege to disclose which specific elements.   

`Consequently, we believe your expert report cannot get into specific element‐by‐element combinations that are not 
`disclosed in your contentions, and therefore there would be no obviousness combinations your expert could make in the 
`report.  In other words, our position is that your expert report could only include the 24 charted references used by 
`themselves (and not in combination with any other reference) to opine that a given claim is obvious. 

`Our goal is always to come up with a stipulated solution before troubling Magistrate Van Keulen or the Court with any 
`matter.  To that end we propose two possible solutions: 

`
`1. You can inform us six weeks ahead of time (so three weeks before your invalidity expert report is due) what 
`precise anticipation references and obviousness combinations the expert report will include and include an 
`element‐by‐element disclosure for obviousness combinations as well as the motivation to combine each specific 
`prior art combinations; or 
`

`
`2. We will have an additional month to submit our rebuttal report after receiving your invalidity expert report. 

`We are happy to discuss further details of either of these solutions in the hopes we can stipulate to one.   Please let us 
`know a time in the next couple of days that you (or any colleague of yours) can discuss and resolve this with one of us. 

`Thank you. 

`Regards, 

`Sandy 



`
`
`
`
`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` V-card
`
`
`
` Website
`
`
`
`Sandeep "Sandy" Seth
`Of Counsel
`sseth@stubbsalderton.com
`
`Stubbs Alderton & Markiles, LLP
`15260 Ventura Blvd., 20th Floor
`Sherman Oaks, CA 91403
`
`1453 3rd Street Promenade, Suite 300
`Santa Monica, CA 90401
`
`
`
`
`
`
`
`
`Bus/Fax/Text: 818.444.9273
`Mobile: 832.875.1470
`
`
`
`
`
`4
`
`

`

`Case 5:18-md-02834-BLF Document 457-1 Filed 07/03/19 Page 6 of 6
`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 an 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.
`
`To ensure compliance with requirements imposed by the U.S. Internal Revenue Service, we inform you that any tax advice contained in this communication
`(including any attachments) was not intended or written to be used, and cannot be used, by any taxpayer for the purpose of (1) avoiding tax-related penalties
`under the U.S. Internal Revenue Code or (2) promoting, marketing or recommending to another party any tax-related matters addressed herein.
`
`
`


`
`‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 
`NOTICE:  
`This email and all attachments are confidential, may be legally privileged, and are intended solely for the individual or entity to 
`whom the email is addressed.  However, mistakes sometimes happen in addressing emails.  If you believe that you are not an 
`intended recipient, please stop reading immediately.  Do not copy, forward, or rely on the contents in any way.  Notify the sender 
`and/or Fenwick & West LLP by telephone at (650) 988‐8500 and then delete or destroy any copy of this email and its 
`attachments.  Sender reserves and asserts all rights to confidentiality, including all privileges that may apply. 
`
`5
`
`

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