Re: [quicwg/base-drafts] Server sends Handshake probe packet which does not attribute to any progress (#3582)

[ianswett <[e-mail]>]

Q: I assume the server sent and the client received server_initial#0 as well in this example?

The interesting text is:
> When ack-eliciting packets are in-flight in multiple packet number spaces, the timer MUST be set for the packet number space with the earliest timeout, except for ApplicationData, which MUST be ignored until the handshake completes; see Section 4.1.1 of {{QUIC-TLS}}. Not arming the PTO for ApplicationData prevents a client from retransmitting a 0-RTT packet on a PTO expiration before confirming that the server is able to decrypt 0-RTT packets, and prevents a server from sending a 1-RTT packet on a PTO expiration before it has the keys to process an acknowledgement.

In this case, the text says to not arm PTO for ApplicationData until handshake complete and there's nothing in flight in Initial or Handshake, so I don't believe the PTO alarms should be set, so "server resent Handshake(server_handshake#1)" would never occur.

Admittedly, this text can be hard to read(it's certainly hard to write), so if you have any editorial suggestions, that'd be welcome.

-- 
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/3582#issuecomment-618624984