Back to matrix

F23-MQ: Yes

Rationale

QUIC connection IDs permit an established client connection and its streams to continue when the client changes network path/address, with validation of the new path. This is a supported endpoint-mobility case within the selected multipath-QUIC stack, without needing to credit simultaneous paths. Credit assumes a confirmed handshake, usable connection IDs, retained connection state and a peer permitting active migration. Base RFC 9000 client migration does not establish arbitrary server migration or simultaneous movement of both endpoints. Loss and timeout remain possible.

Assessment method

RFC 9000 migration capability in selected QUIC composition; no execution

Source context

RFC 9000 sections 5.1 and 9

Outstanding qualification

Pin the multipath-21 implementation and migration configuration. Move the client to a new local IP/access network during active streams; verify validation and stream continuity without a new TLS/application relationship. Test migration-disabled and timeout cases; measure outage and loss. No runtime test performed.

Public sources