Re: [quicwg/base-drafts] Rework Retry packet (#1498)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> +
+Retry Token:
+
+: An opaque token that the server can use to validate the client's address.
+
+The server populates the Destination Connection ID with the connection ID that
+the client included in the Source Connection ID of the Initial packet.
+
+The server includes a connection ID of its choice in the Source Connection ID
+field.  The client MUST use this connection ID in the Destination Connection ID
+of subsequent packets that it sends.
+
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.

I don't think so.  The server cannot decrypt 0-RTT, so it's only option is to 

1. buffer it in the hopes that it might complete the handshake when it is done, or

2. discard it, which seems the most likely choice if the server is predisposed to send a Retry.

-- 
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/1498#discussion_r199054856