Re: [quicwg/base-drafts] disable_active_migration with SPA (#3765)

[Igor Lubashev <[e-mail]>]

The issue is telling the client that it should avoid changing the source address/network attachment (active client migration) during a connection while still allowing for SPA (destination address change).  Is that what you agree with?

Before the change in `disable_active_migration` semantics, `disable_active_migration` was such a signal.  Now, there is not one.  The semantics were changed to accomodate a useful use case, for sure.  Looking for a replacement signal...

> the current state of PR is incorrect in sense that it requires the client to use the same source address only when migration is disabled for the preferred address

I am not sure what "only" is emphasizing.  I read the current PR as stating that when Migration Disable flag is set, the handshake source address MUST/SHOULD be used when changing destination to SPA and thereafter.  It still needs work to clarify whether one can set Migration Disable flag, when `disable_active_migration` is not set.  And it needs to clarify how to perform address family change when Migration Disable flag is set.

-- 
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/issues/3765#issuecomment-657917176