IP Library › Granted Patent US 12,231,521
Granted Patent B1
US 12,231,521 · App. 17/234,668 · Granted Feb 18, 2025

Methods, systems, and computer program products for sharing information for detecting a time period

Inventor: Robert Paul Morris (Madison, GA)
Assignee: Jenam Tech, LLC
H04L69/16
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,231,521
App. No.
17/234,668
Granted
Feb 18, 2025
Kind
B1
Abstract

In one embodiment, an apparatus and method are provided to: receive, by the apparatus from a node, a set up packet during a setup of a connection, the set up packet for use in a protocol that is not transmission control protocol (TCP); identify first metadata in a time period parameter field in the set up packet, for a time period, where, as a result of a detection of the time period, the connection is at least partial deactivated; and determine, based on the first metadata, a timeout attribute associated with the connection.

Claims (168)

1. A method, comprising:

at at least a portion of a first node:

communicating a first packet including a first parameter field identifying first metadata for use in determining a second duration for detecting a first type of time period, for setting up a first connection, by: sending, from the at least portion of the first node to a second node, the first packet to provide the first metadata to the second node, for use by the second node in determining the second duration for detecting the first type of time period, after sending the first packet and without any other communication between the at least portion of the first node and the second node to set up the first connection after sending the first packet, receiving, at the at least portion of the first node from the second node, a second packet, and after receiving the second packet and without any other communication between the at least portion of the first node and the second node to set up the first connection after receiving the second packet, sending, from the at least portion of the first node to the second node, a third packet; such that the first packet is communicated for enabling, based on detecting, as a function of a first duration during at least a portion of the first connection including at least a portion of the first connection set up, a first time period of the first type of time period, at least partial closure of the first connection, where a start of the first time period is detected based on at least one packet being sent or received during the at least portion of the first connection including the at least portion of the first connection set up, and the detection of the first time period of the first type of time period is a function of the first duration, by being a function of whether, during the first duration after the first time period is started, no packet is received and processed to keep the first connection active; and further such that the first packet is communicated for enabling, based on detecting, as a function of the second duration after a use of the first duration is changed to a use of the second duration, a second time period of the first type of time period, at least partial closure of the first connection, where a start of the second time period is detected based on at least one packet being sent or received after the use of the first duration is changed to the use of the second duration, and the detection of the second time period of the first type of time period is a function of the second duration, by being a function of whether, during the second duration after the second time period is started, no packet is received and processed to keep the first connection active; where during the second time period of the first type of time period, an empty packet is sent without causing a reset of a timer utilized to detect the second time period.

2. The method of claim 1 , wherein the first packet is communicated such that, based on detecting, as a function of a third duration, a third time period, the first connection is at least partially closed.

3. The method of claim 2 , wherein the first packet is communicated such that:

the third time period is detected based on no acknowledgement packet being received in the first connection and processed, during the third duration that starts based on a sent packet being sent in the first connection, to acknowledge the sent packet;

the first duration is not capable of being negotiated between the first and second nodes during the first connection set up, the second duration is capable of being negotiated between the first and second nodes for the first connection, and the third duration of the third time period is capable of being negotiated between the first and second nodes for the first connection;

the third time period is a second type of time period, and is an acknowledgment timeout period; and

the third duration is determined using the first parameter field identifying the first metadata.

4. The method of claim 3 , wherein the first packet is communicated such that: the first duration is not negotiated between the first and second nodes during the first connection set up, and the second duration is negotiated between the first and second nodes during the first connection set up for the first connection.

5. The method of claim 4 , wherein the first packet is communicated such that: the first duration is used and the second duration is not used, for detecting the first type of time period until being changed to the second duration.

6. The method of claim 5 , wherein the first packet is communicated such that:

the first packet is not a synchronize (SYN) packet;

the first connection does not involve a Transmission Control Protocol (TCP) extension; and

the first type of time period does not include a user timeout period.

7. The method of claim 5 , wherein the first packet is communicated such that:

the start of the first time period is detected based on the at least one packet being received during the at least portion of the first connection including the at least portion of the first connection set up; and

the start of the second time period is detected based on the at least one packet being received after the use of the first duration is changed to the use of the second duration.

8. A method, comprising:

via at least a portion of an apparatus:

communicate, based on first information, a set up packet including a time period parameter field identifying first metadata, the set up packet for use in a protocol that is not transmission control protocol (TCP) to set up a connection, by sending, to a node, the set up packet to provide the first metadata to the node, for use by the node in determining a timeout attribute associated with the connection, such that a time period, during which no packet is received in the connection and processed to keep the connection active, is detected to, in response to detecting the time period, at least partially deactivate the connection.

9. The method of claim 8 , wherein the time period includes a second time period that is of a first type of time period and that is detected based on a second duration, where the set up packet is communicated such that:

in response to detecting, based on a first duration during at least a portion of the connection including at least a portion of the connection set up, a first time period of the first type of time period, at least partially deactivate the connection;

in response to detecting, based on the second duration after the connection set up, the second time period of the first type of time period, at least partially deactivate the connection; and

in response to detecting, based on a third duration, a third time period of a second type of time period, perform at least one action, where the third time period is detected based on the third duration, by being detected when no acknowledgement packet is received by the at least portion of the apparatus in the connection and processed as an acknowledgement, during the third duration, for a sent packet sent by the at least portion of the apparatus in the connection.

10. The method of claim 9 , wherein the set up packet is further communicated such that: during the second time period of the first type of time period, an empty packet is sent without causing a timer utilized to detect the second time period to be reset;

where the set up packet is further communicated such that:

the protocol is not a TCP-extension;

the first duration is not capable of being negotiated for the connection during the connection set up, at least one aspect of the second duration is capable of being negotiated for the connection, and at least one aspect of the third duration of the third time period is capable of being negotiated for the connection;

the set up packet is not a synchronize (SYN) packet; and

the first time period and the second time period are started in response to at least one of a received packet or a transmitted packet,

where the set up packet is further communicated such that: the connection set up further includes, in addition to (a-1) sending the set up packet:

(a-2) after sending the set up packet and without any other communication between the at least portion of the apparatus and the node after (a-1) and before (a-2), receiving, at the at least portion of the apparatus from the node, another set up packet, and

(a-3) after receiving the another set up packet and without any other communication between the at least portion of the apparatus and the node after (a-2) and before (a-3), sending, from the at least portion of the apparatus to the node, yet another set up packet.

11. A method, comprising:

at at least a portion of an apparatus:

receiving, from a node, a set up packet during a setup of a connection, the set up packet for use in a protocol that is not transmission control protocol (TCP), by identification of first metadata in a time period parameter field in the set up packet, for a time period, where, as a result of a detection of the time period, the connection is at least partially deactivated, and where, based on the first metadata, a timeout attribute associated with the connection is determined.

12. The method of claim 11 , wherein the time period includes a second time period detected based on a second duration, and where, in response to detecting, based on a first duration, a first time period, the connection is at least partially deactivated.

13. The method of claim 12 , wherein:

the second duration is detected after the first duration is used to at least attempt to detect the first time period;

the first duration is detected during at least a portion of the connection including at least a portion of the connection set up;

the first time period and the second time period are a same type of time period;

the first duration is not negotiated during the connection set up, and at least one aspect of the second duration is negotiated during the connection set up for the connection; and

the first duration is based on previous metadata previously exchanged with the node during a connection set up for a previous connection.

14. The method of claim 11 , wherein the time period includes a second time period that is of a first type of time period and that is detected based on a second duration, and where the set up packet is received for causing the following operations:

in response to detecting, based on a first duration during at least a portion of the connection including at least a portion of the connection set up, a first time period of the first type of time period, at least partially deactivating the connection;

in response to detecting, based on the second duration after the first duration is changed to the second duration, the second time period of the first type of time period, at least partially deactivating the connection; and

in response to detecting, based on a third duration, a third time period of a second type of time period, performing at least one action.

15. The method of claim 14 , wherein;

the at least one action does not include connection deactivation;

the at least one action includes sending a signal;

the third duration is determined based on a first algorithm that is different from a second algorithm on which a determination of the second duration is based; and

the first duration is not negotiated during the connection set up, at least one aspect of the second duration is negotiated during the connection set up for the connection, and at least one aspect of the third duration of the third time period is negotiated during the connection set up for the connection.

16. The method of claim 15 , wherein the third time period is detected based on the third duration, by being detected when no acknowledgement packet is detected during the third duration, as being received and processed as an acknowledgement in the connection to acknowledge a sent packet of a plurality of sent packets which are associated with the third duration of the third time period and which are sent, where the third duration starts for each of the plurality of sent packets when at least one of the plurality of sent packets is sent, and where a single timer and a single timeout variable are utilized for detecting the third time period in connection with the plurality of sent packets.

17. The method of claim 16 , wherein at least one of:

the at least portion of the apparatus, includes a wire;

the at least portion of the apparatus, includes a line;

the at least portion of the apparatus, includes only a wire;

the at least portion of the apparatus, includes only a line;

the at least portion of the apparatus, includes at least portion of a particular node, including a wire;

the at least portion of the apparatus, includes at least portion of a particular node, including a line;

the at least portion of the apparatus, includes at least portion of a particular node, including only a wire;

the at least portion of the apparatus, includes at least portion of a particular node, including only a line;

the at least one action includes at least partial closure of the connection;

the receiving, the identification, and the determination are acts;

the at least one action includes a closure of the connection;

the at least one action does not include a closure of the connection;

the at least one action does not include any part of a closure of the connection;

the apparatus includes a particular node;

the apparatus includes a device, including a network interface, that is a component of the apparatus;

the apparatus includes a network interface that is a component of the apparatus;

the apparatus includes a web server;

the timer includes a hardware timer;

the timer includes a software timer;

the set up packet is an initial non-TCP packet;

the set up packet is first-in-time;

the time period parameter field is part of a data portion in the set up packet;

the time period parameter field is part of a header of the set up packet;

the set up packet is informational;

the connection includes one or more features of TCP, and one or more features not of TCP;

the set up packet includes one or more features of a TCP packet, and one or more features not of a TCP packet;

the connection includes one or more features of a TCP connection, and one or more features not of a TCP connection;

the first duration for detecting the first type of time period is based on the first information, by the first information identifying the first duration;

the first duration for detecting the first type of time period is based on the first information, by the first information specifying the first duration;

the first duration for detecting the first type of time period is based on the first information, by the first information identifying at least one generator for generating the first duration;

only the first duration for detecting the first type of time period is based on the first information;

the second duration of the second time period is different from the duration of the first time period;

the second duration of the second time period is the same as the duration of the first time period;

the third duration of the third time period is different from the duration of the first time period;

the third duration of the third time period is the same as the duration of the first time period;

the third duration of the third time period is different from the duration of the second time period;

the third duration of the third time period is the same as the duration of the second time period;

the set up packet also includes data for use in determining the first time period;

the first information includes a first value representative of the first duration of the first time period, and a second value representative of the second duration of the second time period;

the first information includes a first value representative of the first duration of the first time period, and identification of a generator for generating a second value representative of the second duration of the second time period;

the first information includes identification of a generator for generating a first value representative of the first duration of the first time period, and for generating a second value representative of the second duration of the second time period;

the first information includes identification of a first generator for generating a first value representative of the first duration of the first time period, and identification of a second generator for generating a second value representative of the second duration of the second time period;

the first time period is detected in a first use scenario without the second nor third time periods being detected, the second time period is detected in a second use scenario without the first nor third time periods being detected, the third time period is detected in a third use scenario without the first nor second time periods being detected, and neither the first, second, nor third time periods are detected in a fourth use scenario;

the first duration of the first time period is determined based on the first information, after identifying the first information;

the first duration of the first time period is determined based on the first information, before setting up the connection;

the first duration of the first time period is determined based on the first information, during setting up the connection;

the first duration of the first time period is determined based on the first information, after setting up the connection;

the first time period is triggered by one or more non-duration-related criteria that triggers the second time period;

the first time period is triggered by the same one or more non-duration-related criteria that triggers the second time period;

the first time period is triggered by different one or more non-duration-related criteria than that which triggers the second time period;

the first time period is that during which no packet is received in the connection nor expected to be received;

the first time period is that during which no packet is received in the connection;

the third time period is triggered by one or more non-duration-related criteria that triggers the second time period;

the third time period is triggered by the same one or more non-duration-related criteria that triggers the second time period;

the third time period is triggered by different one or more non-duration-related criteria than that which triggers the second time period;

the third time period is that during which no packet is received in the connection nor expected to be received;

the third time period is that during which no packet is received in the connection;

the first metadata is based on the first information;

the change occurs while detection of the first time period is attempted;

the change occurs via a negotiation;

the second time period is a changed version of the first time period;

the second time period is a changed instance of the first time period;

the first time period and the second time period have at least one additional difference, in addition to duration, despite both being of the first type of time period;

the first time period and the second time period do not have at least one additional difference, in addition to duration;

the second time period is determined based on the first information;

the first duration of the first time period is negotiated between the apparatus and the node for the connection, during the connection set up;

the connection set up includes all communications that precede completion of the connection set up;

the duration of the second time period is determined based on the first information;

the duration of the third time period is determined based on the first information;

the first and second time periods are of a same duration;

the first and second time periods are of a different duration;

the first and second time periods are different instances of the same type of time period;

the first and second time periods are of the same type of time period, but are applied at different times during the connection;

the first duration of the first time period is determined by being negotiated;

the second duration of the second time period is determined by being negotiated;

the third duration of the third time period is determined by being negotiated;

the first metadata is also for use in determining the second duration of the second time period;

the first metadata is not for use in determining the second duration of the second time period;

the first metadata is also for use in determining the third duration of the third time period;

the first metadata is not for use in determining the third duration of the third time period;

the first metadata describes a definition of at least one duration;

the first metadata defines at least one duration;

the first metadata includes at least one duration;

the first metadata describes a definition of at least one time period;

the first metadata describes other data that defines at least one duration;

the first metadata describes other data that defines at least one time period;

the first metadata describes other criteria-related data that defines at least one time period;

the first metadata describes duration data that defines at least one time period;

the first metadata describes duration criteria-related data that defines at least one time period;

the at least portion of the connection includes only a subset of setting up the connection;

the at least portion of the connection includes an entirety of setting up the connection;

the at least portion of the connection set up includes one or more packet exchanges that occur after the set up packet is sent;

the at least portion of the connection set up includes one or more packet exchanges that occur after the set up packet is sent prior to completion of the connection set up;

the set up packets are non-TCP;

the set up packets are non-TCP by not being required by any TCP standard specification;

the first time period is detected based on the first duration, by being detected when packet activity or a lack thereof meets one or more criteria for a span of the first duration;

the second time period is detected based on the second duration, by being detected when packet activity or a lack thereof meets one or more criteria for a span of the second duration;

the first type of time period includes an idle time period type;

the first and second time periods of the first type of time period differ only in duration;

the first and second time periods of the first type of time period are capable of differing in duration, but may have a same duration;

the first and second time periods of the first type of time period are capable of differing only in duration, but may have a same duration;

the first and second time periods of the first type of time period differ in duration and at least one criteria involving packet activity or a lack thereof over a duration span;

the first and second time periods of the first type of time period are capable of differing in duration and further differ in at least one criteria involving packet activity or a lack thereof over a duration span;

the set up packet includes a portion of data sent at any layer;

the set up packet includes a frame;

the set up packet is a non-TCP frame;

the first time period is started in response to a received packet and the second time period are started in response to a sent packet;

the first time period is started in response to a sent packet and the second time period are started in response to a received packet;

the first time period is started in response to a received packet and the second time period are started in response to a received packet;

the first time period is started in response to a sent packet and the second time period are started in response to a sent packet;

the first time period and the second time period are started in response to different packets;

the first time period and the second time period are started in response to different types of packets;

the protocol that is not TCP is a non-TCP protocol; or the protocol that is not TCP is a TCP a variant.

Continuity (9)
Continuation 17148140 · Jan 13, 2021
Continuation 16914267 · Jun 26, 2020
Continuation 16368811 · Mar 28, 2019
Continuation 16040522 · Jul 19, 2018
Continuation 15915047 · Mar 7, 2018
Continuation 15694802 · Sep 3, 2017
Continuation In Part 14667642 · Mar 24, 2015
Continuation In Part 13477402 · May 22, 2012
Continuation 12714454 · Feb 27, 2010
References Cited (305)
US 4885577A · Nelson · 1989 [cited by examiner]
US 5371852A · Attanasio et al. · 1994 [cited by applicant]
US 5495480A · Yoshida · 1996 [cited by applicant]
US 5884032A · Bateman et al. · 1999 [cited by applicant]
US 6212175B1 · Harsch · 2001 [cited by applicant]
US 6273622B1 · Ben-David · 2001 [cited by applicant]
US 6289224B1 · Boxall et al. · 2001 [cited by applicant]
US 6412006B2 · Naudus · 2002 [cited by applicant]
US 6412009B1 · Erickson et al. · 2002 [cited by applicant]
US 6415327B1 · Beckerman et al. · 2002 [cited by applicant]
US 6584546B2 · Kavipurapu · 2003 [cited by applicant]
US 6665727B2 · Hayden · 2003 [cited by applicant]
US 6674713B1 · Berg et al. · 2004 [cited by applicant]
US 6704786B1 · Gupta et al. · 2004 [cited by applicant]
US 6757248B1 · Li et al. · 2004 [cited by applicant]
US 6880013B2 · Kashyap · 2005 [cited by applicant]
US 6981048B1 · Abdolbaghian et al. · 2005 [cited by applicant]
US 7002917B1 · Saleh · 2006 [cited by applicant]
US 7010597B2 · Hayden · 2006 [cited by applicant]
US 7035214B1 · Seddigh et al. · 2006 [cited by applicant]
US 7050940B2 · Basso et al. · 2006 [cited by applicant]
US 7152111B2 · Allred et al. · 2006 [cited by applicant]
US 7389512B2 · Tucker · 2008 [cited by applicant]
US 7404210B2 · Lin · 2008 [cited by applicant]
US 7426569B2 · Dunk · 2008 [cited by applicant]
US 7428595B2 · Deshpande · 2008 [cited by applicant]
US 7464326B2 · Kawai et al. · 2008 [cited by applicant]
US 7535913B2 · Minami et al. · 2009 [cited by applicant]
US 7606191B1 · Breau et al. · 2009 [cited by applicant]
US 7636805B2 · Rosenberg · 2009 [cited by applicant]
US 7657644B1 · Zheng · 2010 [cited by applicant]
US 7684346B2 · Valli · 2010 [cited by applicant]
US 7720989B2 · Dunk · 2010 [cited by applicant]
US 7729271B2 · Tsuchiya et al. · 2010 [cited by applicant]
US 7808941B2 · Ramos et al. · 2010 [cited by applicant]
US 7848351B2 · Kim et al. · 2010 [cited by applicant]
US 7876678B2 · Ong · 2011 [cited by applicant]
US 7962623B2 · Undery et al. · 2011 [cited by applicant]
US 7984192B2 · Burr et al. · 2011 [cited by applicant]
US 8031617B2 · Mogul et al. · 2011 [cited by applicant]
US 8073964B2 · Dunk · 2011 [cited by applicant]
US 8077737B2 · Ji · 2011 [cited by applicant]
US 8219606B2 · Morris · 2012 [cited by applicant]
US 8228830B2 · Babin et al. · 2012 [cited by applicant]
US 8259716B2 · Diab · 2012 [cited by applicant]
US 8375134B2 · Herzog et al. · 2013 [cited by applicant]
US 8483095B2 · Hegde et al. · 2013 [cited by applicant]
US 8700695B2 · Sundarrajan et al. · 2014 [cited by applicant]
US 8711851B1 · Subramonian et al. · 2014 [cited by applicant]
US 9060310B2 · Ji · 2015 [cited by applicant]
US 9923995B1 · Morris · 2018 [cited by applicant]
US 9923996B1 · Morris · 2018 [cited by applicant]
US 10069945B1 · Morris · 2018 [cited by applicant]
US 10306026B1 · Morris · 2019 [cited by applicant]
US 11050855B1 · Morris · 2021 [cited by examiner]
US 20030131135A1 · Yun · 2003 [cited by applicant]
US 20040001474A1 · Simelius · 2004 [cited by examiner]
US 20040093376A1 · Boor et al. · 2004 [cited by applicant]
US 20040098748A1 · Bo et al. · 2004 [cited by applicant]
US 20050054347A1 · Kakani · 2005 [cited by applicant]
US 20050063304A1 · Sillasto et al. · 2005 [cited by applicant]
US 20050135248A1 · Ahuja et al. · 2005 [cited by applicant]
US 20050204013A1 · Raghunath et al. · 2005 [cited by applicant]
US 20060034179A1 · Carter et al. · 2006 [cited by applicant]
US 20060195547A1 · Sundarrajan et al. · 2006 [cited by applicant]
US 20070005804A1 · Rideout · 2007 [cited by applicant]
US 20070008884A1 · Tang · 2007 [cited by applicant]
US 20070064677A1 · Xiong · 2007 [cited by applicant]
US 20070086461A1 · Ward et al. · 2007 [cited by applicant]
US 20070110046A1 · Farrell et al. · 2007 [cited by applicant]
US 20070140193A1 · Dosa et al. · 2007 [cited by applicant]
US 20070171921A1 · Wookey et al. · 2007 [cited by applicant]
US 20080084826A1 · Ong · 2008 [cited by applicant]
US 20080095124A1 · Ramos et al. · 2008 [cited by applicant]
US 20080144603A1 · Chouksey et al. · 2008 [cited by applicant]
US 20080261596A1 · Khetawat et al. · 2008 [cited by applicant]
US 20090201857A1 · Daudin et al. · 2009 [cited by applicant]
US 20090207738A1 · Denis-Courmont et al. · 2009 [cited by applicant]
US 20090252072A1 · Lind et al. · 2009 [cited by applicant]
US 20100057844A1 · Johnson · 2010 [cited by applicant]
US 20100074273A1 · Ji · 2010 [cited by applicant]
US 20100189036A1 · Liu et al. · 2010 [cited by applicant]
US 20110213820A1 · Morris · 2011 [cited by applicant]
US 20120063298A1 · Yi et al. · 2012 [cited by applicant]
CN 101193406A · 2008 [cited by applicant]
EP 1242882A2 · 2002 [cited by applicant]
EP 1446970A1 · 2004 [cited by applicant]
EP 1242882B1 · 2005 [cited by applicant]
WO 2007069046A1 · 2007 [cited by applicant]
“A Border Gateway Protocol 4 (BGP-4)” RFC 1771, published in Mar. 1995, available at https://tools.ietf.org/html/rfc1771. [cited by applicant]
“Discussion Lists,” IETF, available at https://www.ietf.org/how/lists/discussion/. [cited by applicant]
“IETF Announce Mailing List,” IETF, Apr. 2004. [cited by applicant]
“IETF Document Management System Datatracker 2 for Eggert,” IETF, Datatracker. [cited by applicant]
“IETF TCP Maintenance,” IETF, Apr. 2004. [cited by applicant]
“TCP Option Kind Numbers,” Network Working Group, RFC 2780. [cited by applicant]
“Using SCTP as a Transport Layer Protocol for HTTP,” draft-natarajan-httpbis-sctp-00.txt, published Oct. 27, 2008, available at https://tools.ietf.org/id/draft-natarajan-httpbis-sctp-00.html. [cited by applicant]
Allman, M., Paxson, V., Stevens, W., “TCP Congestion Control”, RFC 2581, Internet Engineering Task Force, http://tools.ietf.org/rfc/rfc2581.txt,—Apr. 1999. [cited by applicant]
Apogee Communications, Rapport de Veille Technologique Securite No. 69, (Security Technology Watch Report) (Apr. 2004). [cited by applicant]
BT Mobile BlackBerry Enterprise Server 4.0, Information Sheet, published in 2005, available at https://www.bt.com/static/i/media/pdf/blackberry_ITadvice_june05.pdf. [cited by applicant]
Busatto, Fabio, “TCP Keepalive Overview”, TCP Keepalive HOWTO, Section 2, http://tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/#overview, accessed Jan. 2010, May 2007. [cited by applicant]
Cisco 7200 Series Network Processing Engine NPE-G1 Data Sheet, published in Jun. 2006, available at https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/network-processor-modules/product_data_sheet09186a… [cited by applicant]
Cisco 7200 Series Router Architecture, published in Feb. 2008, available at https://www.cisco.eom/c/en/us/support/docs/routers/7200-series-routers/5810-arch-7200-5810.pdf. [cited by applicant]
Cisco 7200 VXR Series Routers Data Sheet, published in 2008. [cited by applicant]
Cisco 7200 VXR Series Routers Quick Look Guide published in Nov. 2007. [cited by applicant]
Cisco IOS BGP Configuration Guide, Release 12.4T, Chapter: Cisco BGP Overview, published in 2007, available at https://www.cisco.com/c/en/us/td/docs/ios/12_2sr/12_2srb/feature/guide/tbgp_c/tbrbover.html. [cited by applicant]
Cisco IOS BGP Configuration Guide, Release 12.4T, Chapter: Configuring BGP Neighbor Session Options (“Cisco IOS BGP Options”), published in 2007, available at https://www.cisco.com/c/en/us/td/docs/ios/12_2sr/12_2srb/fea… [cited by applicant]
Cristian Zamfir, Live Migration of User Environments Across WideArea Networks, Master's Thesis, Department of Computing Science, University of Glasgow (Oct. 2008). [cited by applicant]
Digital cellular telecommunications system (Phase 2+); Generic access to the A/GB interface; Stage 2 (3GPP TS 43.318 version 6.7 0 Release 6) (“TS 43.318”), published in Jun. 2006. [cited by applicant]
Eggert, L., Gont, F., “TCP User Timeout Option”, RFC 5482, Internet Engineering Task Force (IEFT), http://tools.ietf.org/html/rfc5482.txt, Mar. 2009. [cited by applicant]
F. Gont, “TCP Adaptive User TimeOut (AUTO) Option,” Network Working Group, May 19, 2004. [cited by applicant]
HP Compaq Business Desktop d530 Series, QuickSpecs (“d530 QuickSpecs”), published on Jul. 14, 2003, available at http://www.hp.com/ecomcat/hpcatalog/specs/emeapsg/99/D530SERIES pdf. [cited by applicant]
HP iPAQ H4000 Series User Guide, published in Aug. 2003. [cited by applicant]
Hypertext Transfer Protocol—HTTP/1.1 RFC 2068, published in Jan. 1997, available at https://tools.ietf.org/html/ffc2068. [cited by applicant]
Hypertext Transfer Protocol RFC 2616, published in Jun. 1999, available at https://tools.ietf.org/html/rfc2616. [cited by applicant]
IESG Statement: Normative and Informative References, Apr. 19, 2006, available at https://www.ietf.org/blog/iesg-statement-normative-and-informative-references/. [cited by applicant]
IETF Document Management System Datatracker 1 for Eggert, available at https://datatracker.ietf.org/doc/draft-eggert-tcpm-tcp-abort-timeout-option/. [cited by applicant]
IETF face-to-face meeting (San Diego, Aug. 2, 2004). [cited by applicant]
Internet Domain Survey, Jan. 2010, Internet Systems Consortium available at https://downloads.isc.org/www/survey/reports/2010/01/. [cited by applicant]
J. Moy, “The OSPF Specification,” Network Working Group, RFC 1131, Oct. 1989. [cited by applicant]
Jacobson et al., “TCP Extensions for High Performance,” Network Working Group, RFC 1323, May 1002, available at https://tools.ietf.org/html/rfc1323. [cited by applicant]
Jacobson et al., “TCP Extensions for Long-Delay Paths,” Network Working Group, RFC 1072, Oct. 1988, available at https://tools.ietf.org/html/rfc1072. [cited by applicant]
Jim Roskind, QUIC Quick UDP Internet Connections, Multiplexed Stream Transport Over UDP, Nov. 7, 2013 (first draft earlier), available at https://www.ietf.org/proceedings/88/slides/slides-88-tsvarea-10.pdf. [cited by applicant]
Jon Postel, “Transmission Control Protocol,” DARPA Internet Program Protocol Specification, RFC 793, dated Sep. 1981. [cited by applicant]
Koziero, Charles M., TCP Connection Management and Problem Handling, the Connection Reset Function, and TCP “Keepalives”, The TCP/IP Guide, p. 3, http://www.tcpipguide.com/free/t_TCPConnectionManagementandProblemHandlin… [cited by applicant]
Mathis et al., “TCP Selective Acknowledgment Options,” Network Working Group, RFC 2018, Oct. 1996, available at https://tools.ietf.org/html/rfc2018. [cited by applicant]
Mathis, M., Mahdave, J., Floyd, S., Romanow, A., “TCP Selective Acknowledgement Options”, RFC 2018, Internet Engineering Task Force, http://tools.ietf.org/rrc/rfc2018.txt, Oct. 1996. [cited by applicant]
Mobile IP Traversal of Network Address Translation (NAT) Devices RFC 3519 (“RFC 3519”), published in Apr. 2003, available at https://tools.ietf.org/html/rfc3519. [cited by applicant]
Nagle, John, “Congestion Control in IP/TCP Internetworks”, RFC 896, Ford Aerospace and Communications Corporation, http://tools.ietf.org/rfc/ifc896.txt, Jan. 1984. [cited by applicant]
NetEx “‘C’ Configuration Manager and NetEx® Alternate Path Retry (APR) Release 4.0” software reference manual, published in 2002, available at http://www.netexsw.com/nesi/support/ReleasedDocs/ConfMgr/man-cnet-conf-mgr-0… [cited by applicant]
NetEx/IP™ for UNIX Systems Release 6.0 Software Reference Manual, published in 2004, available at http://www.netexsw.com/nesi/support/ReleasedDocs/Hxx0IP/man-hunxip-03.pdf. [cited by applicant]
Network Support for Intermittently Connected Mobile Nodes, Simon Schutz, published on Jun. 13, 2004, available at https://eggert.org/students/schuetz-thesis.pdf. [cited by applicant]
Network Working Group, “QUIC0: A UDP-Based Secure and Reliable Transport for HTTP/2 draft-tsvwg-quic-protocol-00”, Jun. 17, 2015. [cited by applicant]
Office Action Summary in U.S. Appl. No. 12/714,063 dated Jun. 21, 2012. [cited by applicant]
Office Action Summary in U.S. Appl. No. 12/714,063 dated Mar. 4, 2013. [cited by applicant]
Office Action Summary in U.S. Appl. No. 12/714,063 dated Sep. 27, 2013. [cited by applicant]
Office Action Summary in U.S. Appl. No. 12/714,454 dated Feb. 23, 2012. [cited by applicant]
Office Action Summary in U.S. Appl. No. 13/477,402 dated Sep. 24, 2014. [cited by applicant]
Office Action Summary in U.S. Appl. No. 15/694,802 dated Nov. 29, 2017. [cited by applicant]
Office Action Summary in U.S. Appl. No. 17/079,397. [cited by applicant]
Office Action Summary in U.S. Appl. No. 17/148,824. [cited by applicant]
Palm Treo 650 Manual, published in 2004, available at https://www.wireless.att.com/download/phone_manual/treo_650.pdf. [cited by applicant]
Postel, J. “The TCP Maximum Segment Size and Related Topics,” Network Working Group, RFC 879, available at https://tools.ietf.org/html/rfc879. [cited by applicant]
Postel, John(ed.), Editor; “Transmission Control Protocol—DARPA Internet Protocol Specification”, RFC 793, USC/Information Sciences Institute, http://tools.ietf.org/rfc/rfc793.txt, Sep. 1981. [cited by applicant]
Protocol Enhancements for Intermittently Connected Hosts, Schutz et al., ACM SIGCOMM Computer Communication Review, vol. 35, No. 2, Jul. 2005, published in Jul. 2005. [cited by applicant]
Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs (aka Framing Parameters for GAN) (“RFC 3267”), published… [cited by applicant]
Requirements for Internet Hosts—Communication Layers RFC 1122 (“RFC 1122”), published in Oct. 1989, available at https://tools.ietf.org/html/rfc1122. [cited by applicant]
Roskind, Jim “Multiplexed Stream Transport Over UDP,” QUIC, Dec. 2, 2013, 51 pages. [cited by applicant]
S. Bradner “IETF Working Group Guidelines and Procedures,” Network Working Group, RFC 2418, Sep. 1998. [cited by applicant]
S. Bradner, “The Internet Standards Process—Revision 3” Network Working Group, RFC 2026. [cited by applicant]
Stream Control Transmission Protocol (SCTP)—(“SCTP”) RFC 2960, R. Stewart et al., published in Oct. 2000, available at https://tools.ietf.org/html/rfc2960. [cited by applicant]
Sun Blade 1000 and Sun Blade 2000 Getting Started Guide, Part No. 816-3216-10, published in Jan. 2002, available at https://docs.oracle.com/cd/E19127-01/blade1000.ws/816-3216-10/816-3216-10.pdf. [cited by applicant]
T Bova et al. “Reliable UDP Protocol” (Internet-Draft for the Internet Engineering Task Force, dated Feb. 25, 1999. [cited by applicant]
TCP Abort Timeout Option (draft-eggert-tcpm-tcp-abort-timeout-option-00), published Apr. 14, 2004, available at https://tools.ietf.org/html/draft-eggert-tcpm-tcp-abort-timeout-option-00. [cited by applicant]
TCP User Timeout Option RFC 5482, published in Mar. 2009, available at https://tools.ietf.org/html/rfc5482. [cited by applicant]
TCP/IP Illustrated, vol. 1: The Protocols, W. Richard Stevens, published in 1994. [cited by applicant]
The Federal Networking Council, The Networking and Information Technology Research and Development Program, Oct. 10, 1997, available at https://www.nitrd.gov/historical/fnc-material.aspx. [cited by applicant]
Transmission Control Protocol RFC 793, published in Sep. 1981, available at https://tools.ietf.org/html/rfc793. [cited by applicant]
Heavens, Ian, IETF, “Problems with TCP Connections Terminated by RSTs or Timers,” Internet Draft, Jul. 1995, available at https://tools.ietf.org/html/draft-heavens-problems-rsts-00.html. [cited by applicant]
IETF Hypertext Transfer Protocol RFC 2616 (“RFC 2616”), published in Jun. 1999. [cited by applicant]
IETF Internet-Draft Standard 2326. [cited by applicant]
IETF Internet-Draft Standard RFC 1072. [cited by applicant]
IETF Internet-Draft Standard RFC 1105. [cited by applicant]
IETF Internet-Draft Standard RFC 1123. [cited by applicant]
IETF Internet-Draft Standard RFC 1208. [cited by applicant]
IETF Internet-Draft Standard RFC 1889. [cited by applicant]
IETF Internet-Draft Standard RFC 2001. [cited by applicant]
IETF Internet-Draft Standard RFC 2018. [cited by applicant]
IETF Internet-Draft Standard RFC 2525. [cited by applicant]
IETF Internet-Draft Standard RFC 2581. [cited by applicant]
IETF Internet-Draft Standard RFC 2582. [cited by applicant]
IETF Internet-Draft Standard RFC 4884. [cited by applicant]
IETF Internet-Draft Standard RFC 768. [cited by applicant]
IETF Internet-Draft Standard RFC 791. [cited by applicant]
IETF Internet-Draft Standard RFC 792. [cited by applicant]
ITU-T Recommendation X.224, Data Networks and Open System Communications Open Systems Interconnection—Connection-Mode Protocols Specifications. [cited by applicant]
Jim Roskind, QUIC Quick UDP Internet Connections, Multiplexed Stream Transport Over UDP (First Draft Apr. 2012) available at https://docs google.eom/document/d/1RNHkx_VvKWyWg6Lr8SZ-saqsQx7rFV-ev2jRFUoVD34/. [cited by applicant]
Microsoft Corporation's Real-Time Streaming Protocol Windows Extensions. [cited by applicant]
Multimedia Engineering: A Practical Guide for Internet Implementation. [cited by applicant]
NETBLT: A Bulk Data Transfer Protocol, RFC 998 (“RFC 998”), published Mar. 1987. [cited by applicant]
NetEx “‘C’ Configuration Manager and NetEx® Alternate Path Retry (APR) Release 4.0” software reference manual “NetEx Configuration Manual”), published in 2002. [cited by applicant]
NetEx “Supporting Both NetEx® and TCP Communications Stacks” document, published in 2001. [cited by applicant]
NetEx/IP™ for UNIX Systems Release 6.0 Software Reference Manual, published in 2004. [cited by applicant]
OpenVPN 2.0 HOWTO, available at https://web.archive.org/web/20070203073328/http://openvpn.net/howto.html (captured Feb. 3, 2007). [cited by applicant]
OpenVPN 2.0.9 Source Code, available at https://web.archive.org/web/20090531064619/http://openvpn.net/index.php/opensource/downloads.html (captured May 31, 2009). [cited by applicant]
OpenVPN 2.0.x Manual, available at https://web.archive.org/web/20090912032334/http://openvpn.net/index.php/opensource/documentation/manuals/65-openvpn-20x-manpage.html#IbAV (captured Sep. 12, 2009). [cited by applicant]
OpenVPN Bridging with Windows HOWTO, available at https://web.archive.org/web/20090214224848/http://www.pavelec.net/adam/openvpn/bridge/. [cited by applicant]
OpenVPN FAQ, available at https://web.archive.org/web/20070203061312/http://openvpn.net/faq.html. [cited by applicant]
Path Computation Element (PCE) Communication Protocol, RFC 5440 (“Vasseur”), published in 2009. [cited by applicant]
Piscitello et al.. Open Systems Networking TCP/IP and OSI, Addison-Wesley Publishing Company (1993)—Part I. [cited by applicant]
Piscitello et al.. Open Systems Networking TCP/IP and OSI, Addison-Wesley Publishing Company (1993)—Part II. [cited by applicant]
Real Time Streaming Protocol (RTSP), RFC 2326 (“RFC 2326”), published Apr. 1998. [cited by applicant]
Requirements for Internet Hosts—Communication Layers RFC 1122 (“RFC 1122”), published in Oct. 1989. [cited by applicant]
RFC 1001, “Protocol Standard for A NetBIOS Service On a TCP/UDP Transport: Concepts and Methods”, Mar. 1987, available at https://tools.ietf.org/html/rfc1001. [cited by applicant]
RFC 1644—“T/TCP—TCP Extensions for Transactions / Functional Specification”(“RFC 1644”) (Jul. 1994). [cited by applicant]
Session Timers in the Session Initiation Protocol (SIP), RFC 4028 (“RFC 4028”), published in Apr. 2005. [cited by applicant]
Sivasankar Radhakrishnan, Yuchung Cheng, Jerry Chu, Arvind Jain, “TCP Fast Open” (ACM CoNEXT 2011, Dec. 6-9, 2011, Tokyo, Japan). [cited by applicant]
Solar Tunable Parameters Reference Manual, Sun Microsystems, Inc. (May 2002). [cited by applicant]
Tactical Communications Protocol 2 (TAC02) for the National Imagery Transmission Format Standard MIL-STD-2045-44500 (U.S. Dept. of Defense), published Jun. 1993. [cited by applicant]
TCP Abort Timeout Option (draft-eggert-tcpm-tcp-abort-timeout-option-00), published on Apr. 14, 2004. [cited by applicant]
The Tau Project, available at http://protocols.netlab.uky.edu/˜calvert/Tau/index.html (last updated Sept. 4, 1998). [cited by applicant]
Transmission Control Protocol RFC 793 (“RFC 793”), published in Sep. 1981. [cited by applicant]
Vasseur et al., IETF RFC 5440 “Path Computation Element (PCE) Communication Protocol (PCEP),” Mar. 2009, available at https://tools.ietf.org/html/rfc5440. [cited by applicant]
Webpage, “Introducing QUIC Support for HTTPS Load Balancing,” Google, Jun. 13, 2018, available at https://cloudplatform.googleblog.com/2018/06/Introducing-QUIC-supportfor-HTTPS-load-balancing.html. [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Informational Draft Version 00 (R. Hamilton, J. Iyengar, I Swett, A. Wilk) available at https://datatracker.ietf.org/doc/html/draft-ham… [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Informational Draft Version 01 (R. Hamilton, J. Iyengar, I. Swett, A. Wilk) available at https://datatracker.ietf.org/doc/html/draft-ha… [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 00 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-00 (Nov. 28, 2016). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 01 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-01 (Jan. 14, 2017). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 02 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-02 (Mar. 13, 2017). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 03 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-03 (Mar. 21, 2017). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 04 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-04 (Jun. 13, 2017). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 05 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-05 (Aug. 15, 2017). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 06 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-06 (Sep. 22, 2017). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 07 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-07 (Oct. 13, 2017). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 08 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-08 (Dec. 5, 2017). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 09 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-09 (Jan. 28, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 10 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-10 (Mar. 5, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 11 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-11 (Apr. 17, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 12 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-12 (May 22, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 13 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-13 (Jun. 28, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 14 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-14 (Aug. 15, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 15 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-15 (Oct. 3, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 16 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-16 (Oct. 23, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 17 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-17 (Dec. 18, 2018). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 18 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-18 (Jan. 23, 2019). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Version 19 through 19 (J. Iyengar, M. Thompson) available at https://tools.ietf.org/html/draft-ietf-quic-transport-19 (Mar. 11, 2019). [cited by applicant]
“Version-Independent Properties of QUIC,” IETF Internet-Draft Standard Version 00 (M. Thomson)availabIe at https://tools.ietf.org/html/draft-ietf-quic-invariants-00 (Feb. 28, 2018). [cited by applicant]
“Version-Independent Properties of QUIC,” IETF Internet-Draft Standard Version 01 (M. Thomson)availabIe at https://tools.ietf.org/html/draft-ietf-quic-invariants-01 (Mar. 20, 2018). [cited by applicant]
“Version-Independent Properties of QUIC,” IETF Internet-Draft Standard Version 02 (M. Thomson)availabIe at https://tools.ietf.org/html/draft-ietf-quic-invariants-02 (Sep. 11, 2018). [cited by applicant]
“Version-Independent Properties of QUIC,” IETF Internet-Draft Standard Version 03 (M. Thomson)availabIe at https://tools.ietf.org/html/draft-ietf-quic-invariants-03 (Oct. 3, 2018). [cited by applicant]
“Version-Independent Properties of QUIC,” IETF Internet-Draft Standard, Original Draft(M. Thomson) available at https://datatracker.ietf.org/doc/html/draft-thomson-quic-invariants (Dec. 1, 2017). [cited by applicant]
A Border Gateway Protocol 4 (BGP-4) (“RFC 1771”), published in Mar. 1995. [cited by applicant]
Berners-Lee et al., IETF RFC 1866 “Hypertext Markup Language—2.0”, Nov. 1995, available at https://tools.ietf.org/html/rfc1866. [cited by applicant]
BGP, by Iljitsch Van Beijnum, published in Sep. 2002 by O'Reilly. [cited by applicant]
Case No. 4:19-cv-00250. [cited by applicant]
Case No. 6:20-cv-00453. [cited by applicant]
Case No. IPR2020-00630. [cited by applicant]
Case No. IPR2020-00845. [cited by applicant]
Case No. IPR2020-00867. [cited by applicant]
Case No. IPR2020-00868. [cited by applicant]
Case No. IPR2020-00869. [cited by applicant]
Case No. IPR2020-00870. [cited by applicant]
Case No. IPR2021-00627. [cited by applicant]
Case No. IPR2021-00628. [cited by applicant]
Case No. IPR2021-00629. [cited by applicant]
Case No. PGR2021-00082. [cited by applicant]
Case No. PGR2022-00013. [cited by applicant]
Cisco 7200 Series Network Processing Engine NPE-G1 Data Sheet (“Cisco 7200 NPEG1”), published in Jun. 2006. [cited by applicant]
Cisco 7200 Series Router Architecture (“Cisco Router Architecture”), published in Feb. 2008. [cited by applicant]
Cisco 7200 VXR Series Routers Overview (“Cisco 7200 Overview”), published in Mar. 2008. [cited by applicant]
Cisco IOS BGP Configuration Guide, Release 12.4T, Chapter: Cisco BGP Overview (“Cisco IOS BGP Overview”), published in 2007. [cited by applicant]
Cisco IOS BGP Configuration Guide, Release 12.4T, Chapter: Configuring BGP Neighbor Session Options (“Cisco IOS BGP Options”), published in 2007. [cited by applicant]
Clayton et al., A Reactive Implementation of the Tau Composition Mechanism. [cited by applicant]
Feilner et al., Beginning OpenVPN 2.0.9 (Packt Publishing 2009). [cited by applicant]
“A Reactive Implementation of NETBLT” at https://web.archive org/web/20010719084153/https://www.cc.gatech.edu/computing/Telecomm/playground/dsa/nbc.html (captured Jul. 19, 2001). [cited by applicant]
“Applicability of the QUIC Transport Protocol,” IETF Internet-Draft Informational Version 00 (M. Kuehlewind, B. Trammell) available at https://datatracker.ietf.org/doc/htrnl/draft-ietf-quic-applicability-00 (Jul. 3, 201… [cited by applicant]
“Applicability of the QUIC Transport Protocol,” IETF Internet-Draft Informational Version 01 (M. Kuehlewind, B. Trammell) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-applicability-01 (Oct. 25,. [cited by applicant]
“Applicability of the QUIC Transport Protocol,” IETF Internet-Draft Informational Version 02 (M. Kuehlewind, B. Trammell) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-applicability-02 (Jul. 2, 2018… [cited by applicant]
“Applicability of the QUIC Transport Protocol,” IETF Internet-Draft Informational Version 03 (M. Kuehlewind, B. Trammell) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-applicability-03 (Oct. 22, 201… [cited by applicant]
“Applicability of the QUIC Transport Protocol,” IETF Internet-Draft Informational, Original Draft (M. Kuehlewind, B. Trammell) available at https://datatracker.ietf.org/doc/html/draft-kuehlewind-quic-applicability (Mar.… [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 00 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-00 (Nov. 28, 2016). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 01 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-01 (Jan. 14, 2017). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 02 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-02 (Mar. 13, 2017). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 03 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-03 (May 21, 2017). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 04 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-04 (Jun. 13, 2017). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 05 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-05 (Aug. 15, 2017). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 06 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-06 (Sep. 22, 2017). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 07 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-07 (Oct. 13, 2017). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 08 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-08 (Dec. 5, 2017). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 09 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-09 (Jan. 28, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 10 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-10 (Mar. 5, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 11 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-11 (Apr. 17, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 12 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-12 (May 22, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 13 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-13 (Jun. 28, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 14 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-14 (Aug. 15, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 15 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-15 (Oct. 3, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 16 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-16 (Oct. 24, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 17 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-17 (Dec. 18, 2018). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 18 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-18 (Jan. 23, 2019). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational Version 19 (M. Bishop) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-19 (Mar. 11, 2019). [cited by applicant]
“Hypertext Transfer Protocol Version 3 (HTTP/3),” IETF Internet-Draft Informational, Original Draft (R. Shade, M. Warres) available at https://datatracker.ietf.org/doc/html/draft-shade-quic-http2-mapping (Jul. 8, 2016) … [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Original Version (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-iyengar-quic-loss-recovery (Oct. 31, 2016). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 00 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-00 (Nov. 28, 2016). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 01 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-01 (Jan. 14, 2017). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 02 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-02 (Mar. 13, 2017). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 03 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-03 (May 21, 2017). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 04 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-04 (Jun. 13, 2017). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 05 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-05 (Aug. 15, 2017). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 06 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-06 (Sep. 22, 2017. [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 07 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-07 (Nov. 14, 2017). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 08 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-08 (Dec. 5, 2017). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 09 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-09 (Jan. 28, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 10 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-10 (Mar. 5, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 11 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-11 (Apr. 17, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 12 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-12 (May 22, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 13 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-13 (Jun. 28, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 14 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-14 (Aug. 15, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 15 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-15 (Oct. 3, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 16 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-16 (Oct. 23, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 17 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-17 (Dec. 18, 2018). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 18 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-18 (Jan. 23, 2019). [cited by applicant]
“QUIC Loss Detection and Congestion Control”, IETF Internet-Draft Standard Version 19 (J. Iyengar, I. Swett) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-19 (Mar. 11, 2019). [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Experimental Draft Version 00(B. Trammell, M. Kuehlewind) avaialable at https://datatracker.ietf.org/doc/html/draft-ietf-quic-spin-exp-… [cited by applicant]
“QUIC: A UDP-Based Multiplexed and Secure Transport,” IETF Internet-Draft Standard, Experimental Draft Version 01 (B. Trammell, M. Kuehlewind) available at https://datatracker.ietf.org/doc/html/draft-ietf-quic-spin-exp-… [cited by applicant]
Communication from related case USPAN U.S. Appl. No. 17/148,140 dated Apr. 16, 2021. [cited by applicant]
USPTO Communication for USPAN U.S. Appl. No. 18/314,041 dated May 26, 2023. [cited by applicant]