Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Explicit Client Migration #1575

Closed
nibanks opened this issue May 11, 2021 · 1 comment
Closed

Support Explicit Client Migration #1575

nibanks opened this issue May 11, 2021 · 1 comment
Labels
Area: API Area: Core Related to the shared, core protocol logic help wanted Extra attention is needed
Milestone

Comments

@nibanks
Copy link
Member

nibanks commented May 11, 2021

Describe the feature you'd like supported

Minimal support for migration is already supported on the server side, but we have no official support on the client yet. There was some code initially added to set a new local address, but it doesn't work at all on kernel and had issues on client as well. More over, we should instead support a model where the app "adds" and "removes" addresses and then can (optionally) set the main one to use for the active path.

There is a lot of complexity involved in this and requires extensive testing.

@nibanks nibanks added help wanted Extra attention is needed Area: API Area: Core Related to the shared, core protocol logic labels May 11, 2021
@nibanks nibanks added this to the Future milestone May 11, 2021
@nibanks
Copy link
Member Author

nibanks commented Nov 11, 2021

Closing this issue in favor of tracking with #1946.

@nibanks nibanks closed this as completed Nov 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: API Area: Core Related to the shared, core protocol logic help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant