Re: [quicwg/base-drafts] Server's preferred address (#1251)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> +time during the connection after the handshake is completed.  If this packet
+contains a PATH_CHALLENGE frame, the server sends a PATH_RESPONSE frame as per
+{{migrate-validate}}, but the server MUST continue sending all other packets
+from its original IP address.
+
+Once the server has received a non-probing packet on its preferred address which
+is the largest packet number seen so far, the server begins sending to the
+client exclusively from its preferred IP address.
+
+
+## Interaction of Client and Server Migration
+
+A client might need to perform a connection migration before the server's
+connection migration has completed.  In this case, the client SHOULD perform
+path validation to both the original and preferred server address from the
+client's new address concurrently.

It increases the complexity of implementations.  Right now, you probe one path, and if a new path presents itself, you abandon any previous path.  Having to move from 1 to N (even if N == 2), is more complex than we need.  The odds of needing to move just after the handshake are low enough that I would prefer to just say that the client can hold off on migration until after the server completes.  I guess that your response is that this only affects discretionary migrations.  But we can at least write that consideration down.

-- 
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/1251#discussion_r178687105