[quicwg/base-drafts] Handling un-ackable packets (#751)

[ekr <[e-mail]>]

Consider the case f the client is attempting 0-RTT and sends the sequence:

 CI (1), Data(2), Data(3)  // packet numbers in parens

Now, what happens if CI(1) is lost? The server cannot ACK packets 2, 3 because (a) it's forbidden and (b) it can't validate their integrity. So, it seems like what happens is just that eventually the client times out and retransmits CI, which means that the performance here is limited by the client's RTO, as opposed to if (say) the server's first flight was lost, when the QUIC ACKs can force faster retransmission. 

What I've been considering for DTLS is to have the receiver send an empty ACK (i.e,, one that acknowledges no packets), but that's not possible because of the QUIC ACK structure which requires you to ACK at least one packet.






-- 
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/751