Re: [quicwg/base-drafts] Stateless Reset during Path Migration (#1259)

[MikkelFJ <[e-mail]>]

mikkelfj commented on this pull request.



> @@ -1489,7 +1489,9 @@ Differences in routing on the Internet might cause the same destination address
 and connection ID to reach a different server instance which does not posses the
 necessary connection state. Receiving a Stateless Reset in response to a probing
 packet SHOULD NOT terminate the connection, but MUST cause the endpoint to
-consider path validation to have failed.
+consider path validation to have failed.  After receiving a Stateless Reset, the
+client MUST NOT send additional packets with the Connection ID used on the
+probing packet.
 

If you create a new Initial packet for a new connection, you use a random CID before using the server provided CID. If you consider this a separate namespace, then your are right. And if you are only referring to the current connection you are also right. But otherwise you risk accidentially creating an already used ID in a new connection, and with, say, 32 bit CID's it is non-neglectible.

-- 
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/1259#discussion_r179227833