US 7,418,504 C2 (1,669th)
Agile network protocol for secure communications using secure domain names
Victor Larson, Fairfax, VA (US); Robert Dunham Short, III, Leesburg, VA (US); Edmund Colby Munger, Crownsville, MD (US); and Michael Williamson, South Riding, VA (US)
Filed by Victor Larson, Fairfax, VA (US); Robert Dunham Short, III, Leesburg, VA (US); Edmund Colby Munger, Crownsville, MD (US); and Michael Williamson, South Riding, VA (US)
Assigned to VIRNETX INC., Scotts Valley Drive, CA (US)
Reexamination Request No. 95/001,851, Dec. 13, 2011.
Reexamination Certificate for Patent 7,418,504, issued Aug. 26, 2008, Appl. No. 10/714,849, Nov. 18, 2003.
Reexamination Certificate C1 7,418,504, issued Aug. 13, 2020.
Application 95/001,851 is a continuation of application No. 09/558,210, filed on Apr. 26, 2000, abandoned.
Application 09/558,210 is a continuation in part of application No. 09/504,783, filed on Feb. 15, 2000, granted, now 6,502,135.
Application 09/504,783 is a continuation in part of application No. 09/429,643, filed on Oct. 29, 1999, granted, now 7,010,604.
Claims priority of provisional application 60/106,261, filed on Oct. 30, 1998.
Claims priority of provisional application 60/137,704, filed on Jun. 7, 1999.
Inter Partes Reexamination Certificate issued on Jun. 3, 2024.
Int. Cl. H04L 9/40 (2022.01); G06F 16/951 (2019.01); G06F 21/60 (2013.01); H04L 12/46 (2006.01); H04L 41/00 (2022.01); H04L 45/00 (2022.01); H04L 45/24 (2022.01); H04L 45/28 (2022.01); H04L 61/00 (2022.01); H04L 61/30 (2022.01); H04L 61/3015 (2022.01); H04L 61/4511 (2022.01); H04L 61/5007 (2022.01); H04L 61/5076 (2022.01); H04L 61/5092 (2022.01); H04L 67/14 (2022.01); H04L 67/141 (2022.01); H04L 101/30 (2022.01); H04L 101/604 (2022.01)
CPC H04L 63/0485 (2013.01) [G06F 16/951 (2019.01); G06F 21/606 (2013.01); H04L 12/4641 (2013.01); H04L 41/00 (2013.01); H04L 45/00 (2013.01); H04L 45/24 (2013.01); H04L 45/28 (2013.01); H04L 61/30 (2013.01); H04L 61/3015 (2013.01); H04L 61/35 (2013.01); H04L 61/4511 (2022.05); H04L 61/5007 (2022.05); H04L 61/5076 (2022.05); H04L 61/5092 (2022.05); H04L 63/0227 (2013.01); H04L 63/0272 (2013.01); H04L 63/04 (2013.01); H04L 63/0407 (2013.01); H04L 63/0421 (2013.01); H04L 63/0428 (2013.01); H04L 63/0435 (2013.01); H04L 63/0478 (2013.01); H04L 63/08 (2013.01); H04L 63/0876 (2013.01); H04L 63/1408 (2013.01); H04L 63/1416 (2013.01); H04L 63/1458 (2013.01); H04L 63/1466 (2013.01); H04L 63/164 (2013.01); H04L 63/168 (2013.01); H04L 67/14 (2013.01); H04L 67/141 (2013.01); H04L 63/105 (2013.01); H04L 2101/30 (2022.05); H04L 2101/604 (2022.05)]
OG exemplary drawing
Attention is directed to the decision of VirnetX Inc. v. Cisco Systems, Inc., No. 2018-1751, (Fed. Cir.) (Jun. 28, 2019).; VirnetX Inc. v. Cisco Systems, Inc., No. 2022-2234, (Fed. Cir.) (Oct. 20, 2023). This reexamination may not have resolved all questions raised by these decisions. See 37 CFR 1.552(c) for ex parte reexamination and 37 CFR 1.906(c) for inter partes reexamination.
 
AS A RESULT OF REEXAMINATION, IT HAS BEEN DETERMINED THAT:
Claims 36-60 were previously cancelled.
Claims 1-35 are cancelled.
1. A system for providing a domain name service for establishing a secure communication link, the system comprising:
a domain name service system configured to be connected to a communication network, to store a plurality of domain names and corresponding network addresses, to receive a query for a network address, and to comprise an indication that the domain name service system supports establishing a secure communication link.