Re: [quicwg/base-drafts] Allow endpoints to generate traffic keys asynchronously (#3874)

[Marten Seemann <[e-mail]>]

@marten-seemann commented on this pull request.



>  When ack-eliciting packets in multiple packet number spaces are in flight,
-the timer MUST be set for the packet number space with the earliest timeout,
-with one exception. The ApplicationData packet number space (Section 4.1.1
-of {{QUIC-TLS}}) MUST be ignored until the handshake completes. 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.
+the timer MUST be set to the earlier value of the Initial and Handshake packet
+number spaces.

@ianswett When you drop keys, you're also supposed to drop the corresponding packets in that packet number space, so the Handshake packets in your example would not be considered outstanding.

That being said, I have to admit I don't understand why the existing text is ambiguous. @kazuho's change here (the one to the -recovery document), if I understand it correctly, is purely editorial.

-- 
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/pull/3874#discussion_r452573469