Subject: [quicwg/base-drafts] incorrect setting of anti-deadlock timer (#3554)

From: Marten Seemann <[email-masked]>
Date: Sun, 29 Mar 2020 22:13:05 -0700

Consider the following situation: The client sent the ClientHello, and received both an ACK for it and a Handshake packet from the server.
When receiving the Handshake packet, it drops the Initial packet number space, and according to https://quicwg.org/base-drafts/draft-ietf-quic-recovery.html#name-upon-dropping-initial-or-ha it sets `time_of_last_sent_ack_eliciting_packet[Initial] = 0`.

The next run on `SetLossDetectionTimer` (which will happen when sending an ACK for the Handshake packet) will run `GetEarliestTimeAndSpace`, which will return `0`, and the timer will be set to a time long ago in the past (1970, if the timer is based on UNIX timestamps).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3554