When I was developing the server, I found that when triggering connection migration, it can only succeed on the first attempt and cannot be completed afterwards. The DCID remained unchanged throughout the entire process.
Here is the event I printed.
02:57:09.926 io.netty.handler.ssl.SslHandshakeCompletionEvent
02:57:09.926 io.netty.incubator.codec.quic.QuicStreamLimitChangedEvent
02:57:22.371 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
02:57:22.371 io.netty.incubator.codec.quic.QuicPathEvent$New
02:57:22.851 io.netty.incubator.codec.quic.QuicPathEvent$Validated
02:57:22.851 io.netty.incubator.codec.quic.QuicPathEvent$PeerMigrated
02:57:39.345 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
02:57:40.608 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
02:57:40.609 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
02:57:43.619 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
02:57:43.620 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
02:57:44.354 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
02:57:50.320 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
02:57:50.320 io.netty.incubator.codec.quic.QuicPathEvent$ReusedSourceConnectionId
When I was developing the server, I found that when triggering connection migration, it can only succeed on the first attempt and cannot be completed afterwards. The DCID remained unchanged throughout the entire process.
Here is the event I printed.