Re: [quicwg/base-drafts] describe how 0-RTT is accepted and rejected (#2841)

[Marten Seemann <[e-mail]>]

marten-seemann commented on this pull request.



>  
-A server rejects 0-RTT by rejecting 0-RTT at the TLS layer.  This also prevents
-QUIC from sending 0-RTT data. A server will always reject 0-RTT if it sends a
-TLS HelloRetryRequest.
+A server rejects 0-RTT by sending a ServerHello without the EarlyDataIndication.
+A server will always reject 0-RTT if it sends a TLS HelloRetryRequest.  When
+rejecting 0-RTT, a server MUST NOT process any 0-RTT packets, even if it is in
+possesion of the keys to do so.  When 0-RTT was rejected, a client MUST treat
+receipt of an acknowledgement for a 0-RTT packet as a connection error of type

I don't think you need to explicitly track the packet numbers. Here's how I would implement this:
When 0-RTT is rejected, I clear all recovery state for the 0-RTT packets that I sent earlier. Now when receiving an ACK, I just need to run the standard check that it only acknowledges packets that I actually sent. No special case is required to handle this MUST.

-- 
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/2841#discussion_r297043018