Move a connection to a new path
06Connection IDs help route packets to an existing connection when a client address changes. New paths need reachability validation.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 9 ↗
RFC 9000 · § 9EXAMPLE
3 / 3
03
Validate and use the new path.
A matching PATH_RESPONSE supports continued traffic on the new route.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Keep connection identity distinct from the network address.
- Active migration is not initiated before handshake confirmation.
- PATH_CHALLENGE carries unpredictable data; PATH_RESPONSE echoes it to prove reachability on the tested path.
- New connection IDs help reduce linkability; migration can require new congestion and RTT state.
Migration can be disabled by the peer’s transport parameter. NAT rebinding and a server’s advertised preferred address have additional rules; not every address change is unrestricted.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy