We used to migrate connection immediately on the client side without checking the connectivity of the new path before switching over. This causes some sessions fail which would not necessarily happen if stay on the original network.
To fix this, we introduce connection migration version 2, which does two things on top of version 1:
- add decision picking logics to choose direct migrate or probing then migrate;
- add mechanisms to probe new path so as to discover the connectivity on the new path;
- add logic to "migrate back to default network" which is required if session is using non-default network for some reason.
This bug will be used to track the progress of the implementation.
Comment 1 by zhongyi@chromium.org
, Oct 17 2017