Re: [quicwg/base-drafts] Clarify path validation and connection migration (#4102)

[Eric Kinnear <[e-mail]>]

@ekinnear commented on this pull request.



> @@ -2314,33 +2320,31 @@ Therefore, a migrating endpoint can send to its peer knowing that the peer is
 willing to receive at the peer's current address. Thus an endpoint can migrate
 to a new local address without first validating the peer's address.
 
+To establish reachability on the new path, an endpoint initiates path
+validation ({{migrate-validate}}) on the new path.  An endpoint MAY defer path
+validation until after a peer sends the next non-probing frame to its new
+address.

Yeah, I'd really hope that people _not_ do that and immediately validate in response (since state usage is still governed by how many CIDs they handed out) so that a client can pre-warm the validation a few RTTs before we need to migrate. Perhaps we should call out that delay as a reason to avoid deferring unless the server is out of resources?

-- 
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/4102#discussion_r492888148