Summary Of VirnetX/RPX/Apple/Board Conference Calls

Jan. 22, 2014 4:45 PM ETVHC, RPXC, AAPL1 Comment
Dustin Moore profile picture
Dustin Moore's Blog
Please Note: Blog posts are not selected, edited or screened by Seeking Alpha editors.

Value, Growth At A Reasonable Price, Special Situations, Tech

Contributor Since 2010

Dustin Moore is a research writer focusing on smaller companies and technologies. He enjoys diving deep into very specific technologies/companies/topics and connecting complex information back to relevant audiences in digestible, easy-to-understand articles.

Summary of VirnetX/RPX/Apple/Board Conference Calls

Jan 8th call:

VirnetX: RPX says they are the sole party of interest in these IPRs. We want discovery rights to see if Apple worked with RPX in any way on these.

RPX: No. We are completely acting alone.

Board: No discovery rights for VirnetX at this time. VirnetX can include arguments in their preliminary response.

Jan10th call:

VirnetX: RPX filed a corrected copy of their IPR back in November. Those corrections happened to amend data regarding the exact claims that Apple infringed per the district ruling. We have evidence in the metadata of the PDF of the corrected filing that the document first came from Apple's lawyers and was later sent to RPX to submit. [Whoopsie!] That coordination is grounds to allow for further discovery.

RPX and Apple: Well that lawyer worked for both of us.

Board: Why didn't we hear about this earlier?

RPX: VirnetX is seeking discovery in district court. They don't need it here.

VirnetX: No guarantee we will get it or have it in time to use it, since these IPRs are being expedited.

Jan 14th call:

Board: We will allow VirnetX to file a motion to request discovery and the parameters of such discovery. RPX/Apple will be allowed to respond. We will then make a decision.

Recommended For You

Comments (1)

To ensure this doesn’t happen in the future, please enable Javascript and cookies in your browser.
Is this happening to you frequently? Please report it on our feedback forum.
If you have an ad-blocker enabled you may be blocked from proceeding. Please disable your ad-blocker and refresh.