Re: [quicwg/base-drafts] Bundle new client connection ID and path challenge in migration probes (#1730)

[MikkelFJ <[e-mail]>]

mikkelfj commented on this pull request.



> @@ -2074,6 +2074,9 @@ path validation with other frames.  For instance, an endpoint may pad a packet
 carrying a PATH_CHALLENGE for PMTU discovery, or an endpoint may bundle a
 PATH_RESPONSE with its own PATH_CHALLENGE.
 
+When probing a new path, an endpoint may want to ensure that the response, if
+any, is sent to a specific connection ID. The endpoint achieves that by bundling
+NEW_CONNECTION_ID and PATH_CHALLENGE frames, in that order.

OTOH, if this PR is have any effect, it means that an endpoint must be prepared to process later frames in order to proceed. This is still an inter-frame dependency although ordering is relaxed. I think it needs to be made clear that this can happen (perhaps generally, not specifically here), otherwise an implementation may send frames in one order and a receiver fail to make use of that order.

-- 
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/1730#discussion_r216200004