throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`In re Inter Partes Reexaminations of:
`
`Edmund Colby Munger et al.
`
`U. 3. Patent No. 7,490,151
`
`Issued: February 10, 2009
`
`For: ESTABLISHMENT OF A SECURE
`COMMUNICATION LINK BASED ON A
`
`DOMAIN NAME SERVICE (DNS) REQUEST
`
`Mail Stop Inter Partes Reexam
`Commissioner for Patents
`PO. Box 1450
`
`Alexandria, VA 22313-1450
`
`VVVVVVVVVVV
`
`Control Nos.: 95/001,714; 95/001,697
`
`GrouP A" um" 3992
`
`Examiner: Michael J. YIgdall
`
`C°nfirmation NOS- 347-84 2‘61
`
`DECLARATION OF DR. ROBERT DUNHAM SHORT III
`
`1, Robert Dunham Short III, declare as follows:
`
`1.
`
`I have been the Chief Technology Officer of VirnetX Inc. (“VirnetX”) since June
`
`2010 and the Chief Scientist for VirnetX since May 2007. Prior to joining VirnetX, from 1994 to
`
`April 2007,
`
`1 held various positions including Assistant Vice President and Division Manager at
`
`Science Applications International Corporation (“SAIC”). Prior to SAIC, I worked at ARCO Power
`
`Technologies 1nc., Sperry Corporate Technology Center, and Sperry Research Center.
`
`I have a PhD.
`
`in Electrical Engineering from Purdue University as well as a MS. in Mathematics and a BS. in
`
`Electrical Engineering from Virginia Tech.
`
`2.
`
`1 am one of the named inventors of US. Patent No. 7,490,151 (“the ’151 patent”),
`
`which I understand is the subject of the above-identified reexamination proceedings.
`
`1 am familiar
`
`with the ’151 patent, including its claims.
`
`3.
`
`Prior to and at the time of the inventions claimed in the ’151 patent, there was a
`
`significant and increasing concern with the security of computer network communication. The
`
`widespread connectivity between computers that was enabled by the swift increase in network access
`
`in homes and businesses also led to many security breaches as well as concerns regarding the safety of
`
`confidential information sent over computer networks. This problem received significant attention
`
`from the research and development community. Practical experience showed that there was a need
`
`for a system that could be easily and correctly used to enable secure communications, because a
`
`system that made it difficult for an end-user to enable secure communications would likely lead to a
`
`Petitioner Apple - EX. 1053, p. 1
`
`Petitioner Apple - Ex. 1053, p. 1
`
`

`

`Control Nos. 95/001,714; 95/001,697
`
`lack of use or incorrect use. The inventions disclosed and claimed in the ’ 151 patent and other patents
`
`in this family met this need. For instance, the inventions disclosed and claimed in the ’151 patent
`
`include systems and methods of automatically initiating an encrypted channel between a client and a
`
`secure server. As an example, independent claim 1 recites “[a] data processing device, comprising
`
`memory storing a domain name server (DNS) proxy module that intercepts DNS requests sent by a
`
`client and, for each intercepted DNS request, performs the steps of:
`
`(i) determining whether the
`
`intercepted DNS request corresponds to a secure server;
`
`. .. and (iii) when the intercepted DNS
`
`request corresponds to a secure server, automatically initiating an encrypted channel between the
`
`client and the secure server.”
`
`(’151 patent 46:55-67.) Likewise, independent claim 7 recites “[a]
`
`computer readable medium storing a domain name server (DNS) proxy module comprised of
`
`computer readable instructions that, when executed, cause a data processing device to perform the
`
`steps of: (i) intercepting a DNS request sent by a client; (ii) determining whether the intercepted DNS
`
`request corresponds to a secure server; .
`
`.
`
`. and (iv) when the intercepted DNS request corresponds to
`
`a secure server, automatically initiating an encrypted channel between the client and the secure
`
`server.” (Id. at 47:25-38.) And, independent claim 13 recites “[a] computer readable medium storing
`
`a domain name server (DNS) module comprised of computer readable instructions that, when
`
`executed, cause a data processing device to perform the steps of:
`
`(i) determining whether a DNS
`
`request sent by a client corresponds to a secure server; .
`
`.
`
`. and (iii) when the intercepted DNS request
`
`corresponds to a secure server, automatically creating a secure channel between the client and the
`
`secure server.” (1d. at 48:18-29.)
`
`4.
`
`As one example of the manifestation of the long-felt need, the Defense Advanced
`
`Research Projects Agency (“DARPA”) funded various research programs to further the science and
`
`technology of information assurance and survivability. DARPA programs, such as the “Information
`
`Assurance” and “Dynamic Coalitions” programs, were focused on the need to provide easy-to-enable
`
`secure communications.
`
`These projects received significant
`
`funding to be spent developing
`
`technologies that could solve this need. For example, one such project entitled “Next Generation
`
`lntemet” received funding in fiscal year 1998 of approximately $39.3 million, in fiscal year 1999 of
`
`approximately $49.5 million, and in fiscal year 2000 of approximately $40 million.
`
`(Ex. 3-] at
`
`VNET00219302, 319-321.) Another program funded by DARPA, “Dynamic Coalitions,” was created
`
`to address
`
`the ability of the Department of Defense to quickly and easily enable secure
`
`communications over the Internet. (See, e.g., Ex. 8-2 at VNET00219244, 284, 298-299, 593, 625.)
`
`5.
`
`According to DARPA officials at the time, “existing group membership protocols
`
`d[id] not support the security needs of multidimensional organizations. The overarching challenge
`
`Petitioner Apple - EX. 1053, p. 2
`
`Petitioner Apple - Ex. 1053, p. 2
`
`

`

`Control Nos. 95/001,714; 95/001,697
`
`[wa]s creating secure groups rapidly. This [wa]s a significant issue when countries [we]re faced with
`
`an operation that require[d] immediate multinational attention.” (Ex. 3-3 at 1.) DARPA contracted
`
`with some of the most skilled organizations in the area of secured communications in an effort to meet
`
`its security needs (e.g., NAI Labs, a division of PGP Security, Network Associates Incorporated, Los
`
`Angeles, and the Microelectronics Center of North Carolina, Research Triangle Park, North Carolina,
`
`as well as Johns Hopkins University, Baltimore; Northeastern University, Boston; and Veridian-PSR,
`
`Arlington, Virginia).
`
`(Id. at 1.)
`
`In all, more than 15 organizations were researching the various
`
`components that made up the programs initiated by the Department of Defense. (Id.) However, none
`
`of these prestigious institutions came up with a solution, during the relevant time frame, close to what
`
`is disclosed and claimed in the ‘151 patent.
`
`(Id. at 1-4.) That is, they did not develop a solution that
`
`automatically initiated an encrypted channel between a client and a secure server when an intercepted
`
`DNS request sent by the client corresponds to a secure server.
`
`6.
`
`As a second example of the long-felt need for the inventions of the ’151 patent,
`
`In-Q-Tel, which is a venture capital
`
`firm that
`
`invests in companies developing cutting edge
`
`technology aimed at supporting the United States intelligence community,
`
`including the Central
`
`Intelligence Agency (CIA), funded the original development of the technology with approximately
`
`$3.4 million.
`
`In-Q-Tel’s willingness to enter into a relationship with SAIC (the original assignee of
`
`the application that led to the ‘151 patent) for the development of this technology further evidences a
`
`long-felt need for technology that made it easy and convenient to enable secure communications.
`
`7.
`
`A third example was the extent to which SAIC internally funded the research and
`
`development of the technology. When 1 was employed at SAIC, its business model was to sell hours
`
`to the federal government. SAIC was not structured to bring products to the market, which typically
`
`requires significant internal investments in research and development.
`
`In an average year during the
`
`development of the technology that led to the ’151 patent, SAIC would spend approximately $2
`
`million on internal research and development efforts.
`
`In the case of the technology claimed in the
`
`’151 patent, SAIC invested $1.7 million, which represents almost the entirety of SAlC’s internal
`
`research and development budget for one whole year. A technology review committee also approved
`
`our team’s patent development efforts and costs on an ongoing basis. A third party (Cambridge
`
`Strategic Management Group or CSMG) also substantiated the value of the technology. Moreover, a
`
`significant percentage of all of SAIC’s patent development efforts have focused on this technology.
`
`I
`
`understand that SAIC spent one-third of its total patent portfolio efforts on our patent portfolio at that
`
`time.
`
`Petitioner Apple - EX. 1053, p. 3
`
`Petitioner Apple - Ex. 1053, p. 3
`
`

`

`Control Nos. 95/001,714; 95/001,697
`
`8.
`
`In fact, as demonstrated in an article written before the claimed inventions of the ’15]
`
`patent,
`
`it was widely recognized that providing secure remote access to a LAN or WAN was
`
`extremely difficult for IT support desks.
`
`(Ex. B-4 at 1.)
`
`In that time period, remote access was “a
`
`nightmare for support desks. Staffers never kn[e]w what combination of CPU, modem, operating
`
`system and sofiware configuration they [were] going to have to support,” and adding the
`
`commercially-available VPN software only made matters worse. (Id)
`
`9.
`
`This article precisely captured the computer and Internet security industry’s attitude
`
`toward the tradeoff between the ease of use of a secure system, such as a VPN system, for the average
`
`computer user and the security that the VPN system provided. The article recognized that the “ease of
`
`installation isn’t always a good thing:
`
`In many cases, the easier the client is to install, the less secure
`
`it is.” (Id. at 2.) The claimed inventions of the ’151 patent, which provide systems and methods of
`
`automatically initiating an encrypted channel between a client and a secure server, combine both ease
`
`of use and security aspects without sacrificing one or the other.
`
`10.
`
`Moreover, many others before and around the time of the inventions claimed in the
`
`’151 patent have attempted to solve the need of easy-to-use methods of enabling secure
`
`communications over the Internet. But, as discussed above, many of these attempts have failed. For
`
`example, despite investing enormous amounts of money and enlisting the resources of numerous
`
`prestigious institutions and their talented employees, DARPA’s projects still fell far short of the
`
`claimed inventions of the ’ 151 patent. (See 111] 4-5, supra.)
`
`1 1.
`
`Additionally, as discussed above, no one had yet achieved the results of the claimed
`
`inventions of the ’ 151 patent in that time period, because remote access was “a nightmare” for support
`
`desks to handle, and adding the commercially-available VPN software was even more difficult.
`
`In
`
`fact, at this time, the security industry generally viewed ease of use and VPN security as mutually
`
`exclusive.
`
`(See 111] 8-9, supra.) By providing systems and methods of automatically initiating an
`
`encrypted channel between a client and a secure server, the inventions of the ’151 patent provided a
`
`solution for easily establishing secure communication links without sacrificing security,
`
`thereby
`
`succeeding where others failed.
`
`12.
`
`The claimed inventions of the ’151 patent have been commercially successful, for
`
`example, through the licensing revenues they have generated for VimetX.
`
`In July 2002, SafeNet, a
`
`leading provider of Internet security technology that is the de facto standard in the VPN industry,
`
`entered into a portfolio license with SAIC to incorporate features into SafeNet’s underlying VPNs.
`
`SafeNet licensed the patents because of features disclosed and claimed in the patents, including those
`
`in the ’151 patent. Microsoft has also entered into a similar license that includes the ’151 patent.
`
`Petitioner Apple - EX. 1053, p. 4
`
`Petitioner Apple - Ex. 1053, p. 4
`
`

`

`Control Nos. 95/001,714; 95/001,697
`
`Microsoft entered into its license with VirnetX after it was found to have infringed two other VirnetX
`
`patents in the same family, resulting in a damages award of over one hundred million dollars, leading
`
`ultimately to a license agreement of two hundred million dollars. And on May 3, 2012, Aastra USA,
`
`Inc. entered into a license with VirnetX that includes the ’151 patent. Likewise, on July 11, 2012,
`
`Mitel Networks Corporation entered into a license with VirnetX that also includes the ’ 151 patent.
`
`13.
`
`The claimed inventions of the ’ 151 patent were also contrary to the accepted wisdom
`
`at the time of the inventions. For example, there was a general understanding that reliable security
`
`could only be achieved through difficult-to-provision VPNs and easy-to-set-up connections could not
`
`be secure. This belief was reinforced by the IT offices of many large companies and institutions,
`
`whose livelihood depended on the need for highly-trained specialists to arrange secure network
`
`connections.
`
`14.
`
`The industry had long accepted as a fact that secure systems, such as VPN systems,
`
`would be difficult
`
`to set up, and the secure communication modes could not be easily and
`
`conveniently enabled.
`
`In a 1999 article entitled “CEOs Chew the VPN Fat” that predicted what the
`
`future held for the start-up companies that developed VPNs, the wish list did not even address the type
`
`of solutions provided by the ’ 151 patent, such as systems and methods for automatically initiating an
`
`encrypted channel between a client and a secure server. (Ex. 8-5 at 1-2.)
`
`15.
`
`The technology of the ’151 patent was also met with skepticism by those skilled in
`
`the art who learned of our inventions. Sami Saydjari, a program manager for DARPA, informed
`
`Edmund Munger, a co-inventor of the ’151 patent, that our technology would never be adopted.
`
`Moreover, the IT offices of many large companies and institutions expressed skepticism that secure
`
`connections could ever be enabled easily by regular computer users.
`
`16.
`
`Several events also demonstrate praise for the inventions in the ’ 151 patent by those
`
`in the field. As discussed above, SAIC invested a disproportionately large percentage of its internal
`
`resources in the technology. SafeNet, Microsoft, and Aastra have all licensed the technology of the
`
`’15l patent. A study done by CSMG also praised the inventions.
`
`Jim Rutt at Network Solutions,
`
`which was acquired by Verisign, praised and expressed significant interest in the technology and
`
`would have invested but for a change in circumstances at his company.
`
`Petitioner Apple - EX. 1053, p. 5
`
`Petitioner Apple - Ex. 1053, p. 5
`
`

`

`Control Nos. 95/001,714; 95/001,697
`
`l7.
`
`I declare that all statements made herein of my own knowledge are true and that all
`
`statements made on information and belief are believed to be true, and further, that these statements
`
`were made with the knowledge that willful false statements and the like so made are punishable by
`
`fine or imprisonment, or both, under Section 1001 of Title 18 of the United States Code, and that such
`
`willful false statements may jeopardize the validity of the ’151 patent.
`
`Dated: July 19, 2012
`
`By:
`
`/Robert Dunham Short [11/
`
`Robert Dunham Short [[1
`
`Petitioner Apple - EX. 1053, p. 6
`
`Petitioner Apple - Ex. 1053, p. 6
`
`

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