throbber
Page 1 of 3
`
`VIRNETX EXHIBIT 2029
`Apple v. VirnetX
`Trial IPR2014-00237
`
`

`
`Request for Reexamination of U.S. Patent No. 6,502,135
`
`tunnels. See Beser at col. 1, l. 54 to col. 2, l. 18. Beser also points out the importance of
`assuring the secure and private nature of IP tunnels between the first and second network
`devices. See, e.g., Id. at col. 2, ll. 36-40 (“It is therefore desirable to establish a tunneling
`association that hides the identity of the originating and terminating ends of the tunneling
`association from the other users of a public network. Hiding the identities may prevent a hacker
`from intercepting all media flow between the ends.”); col. 12, ll. 13-19 (‘‘In this manner, the
`identities of the originating 24 and terminating 26 telephony devices are inside the payload fields
`84 of the IP 58 packets and may be hidden from hackers on the public network. The negotiation
`may occur through the trusted-third-party network device 30 to further ensure the anonymity of
`the telephony devices (24, 26).”) Beser further explains other than situations where it would be
`impractical, VPNs and encryption of IP traffic in IP tunnels using the IPsec protocol should be
`used. See id. at col. 1, l. 54 to col. 2, l. 18.
`
`% describes use of IPSec to establish VPNs including by IP tunneling. See, e. g., Kent
`at 8 (“A tunnel mode SA is essentially an SA applied to an IP tunnel.”) The IPSec protocol calls
`for encryption of all IP traffic being sent between nodes of the VPN network — the protocol is
`designed to automatically encrypt traffic being sent between nodes.
`
`Kent also teaches that the encryption and tunneling mechanisms of IPSec work
`automatically. In particular, in the IPsec protocol, outbound and inbound IP packets are
`examined and afforded the specified protection based on the IP and transport layer header
`information (e.g., the outbound packet is analyzed and encrypted according to a specified
`method). This occurs automatically according to policies that have been established for the
`connection. See generally id. at 13 (describing handling of inbound and outbound IPsec traffic);
`Id. at 29-34 (describing the protocols for handling outbound and inbound IP packets).
`
`A person of ordinary skill in the art would have relied on m to modify the design of
`Beser to incorporate IPsec to encrypt all traffic being sent in IP tunnels between a first and
`second network device in the IP tunneling procedures being described in Beser, rather than to
`encrypt only the traffic used to establish the IP tunnel. Accordingly, Beser in view of%
`would have rendered obvious claim 1 under 35 U.S.C. § 103.
`
`2.
`
`Claim 2
`
`Claim 2 depends from claim l, and specifies that steps (2) and (3) of claim l are
`performed at a DNS server separate from the client computer.
`
`Beser expressly describes processes and systems where the DNS server (the trusted third
`party network device) is separate from the client computer (the first network device that
`generates the request). In particular, Beser explains that the trusted-third-party network device
`can be a domain name server, and that this device is a distinct network device from the first
`network device. See, e.g., Beser at Figures 1 and 4; at col. 2, ll. 50-56 (“The method includes
`receiving a request to initiate the tunneling association on a first network device. The first
`network device is associated with the originating end of the tunneling association, and the
`request includes a unique identifier for the terminating end of the tunneling association. A
`trusted-third-party network device is informed of the request on a public network.”); and col. ll,
`ll. 33-35 (“In one exemplary preferred embodiment, the trusted-third-party network device is a
`
`Page 2 of 3
`
`166
`
`Page 2 of 3
`
`

`
`Request for Reexamination of U.S. Patent No. 6,502,135
`
`VIII. CONCLUSIONS
`
`Based on the explanations provided herein, Requester believes that substantial new
`questions of patentability have been established for each of claims l-l 8 of the ’ l35 patent.
`Requester accordingly submits that an inter partes reexamination should be established, and
`claims l-l8 of the ’l35 patent should be rejected on each of the grounds specified above that
`establishes a substantial new question of patentability.
`
`Requester authorizes the Director to charge any fees not already provided with this
`request that are determined to be required to Deposit Account No. l8-1260.
`
`Respectfully submitted,
`
`/ Jeffrey P. Kushan /
`Jeffrey P. Kushan
`Registration No. 43,401
`
`SIDLEY AUSTIN LLP
`
`1501 K Street, N.W
`Washington, D.C. 20005
`
`Date:
`
`July l0, 20ll
`
`Page 3 of 3
`
`223
`
`Page 3 of 3

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