C01-MQ: No
Rationale
The selected Multipath QUIC composition routes packets to numeric IP/UDP peer addresses. Connection IDs allow an established connection to survive address changes, but they are not independently routable destination addresses. Multipath-21 explicitly excludes address discovery and management. If the destination attachment loses its address, connection/path continuity mechanisms do not make that same numeric destination reachable at the replacement attachment.
Assessment method
Primary specification review; no runtime experiment
Source context
RFC 9000 and selected multipath-21 address-management boundary
Outstanding qualification
This No distinguishes stable destination addressing from migration of an established connection. QUIC can validate another path and preserve connection state while using a changed peer address; that remains credited in F23 and does not satisfy C01's unchanged-address condition. Recovery of transit to an unchanged IP prefix is also insufficient under this criterion. No Mobile IP, LISP, application naming/redirection or destination-address mapping layer is selected. Prevalidated paths and preferred addresses do not turn a connection ID into a network address. The finding concerns the selected multipath-21 draft, not every future QUIC extension or independent infrastructure arrangement. No runtime experiment.
Public sources
- https://www.ietf.org/archive/id/draft-ietf-quic-multipath-21.html
- https://www.rfc-editor.org/rfc/rfc9000.html#section-5.1
- https://www.rfc-editor.org/rfc/rfc9000.html#section-9
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round530.html
- round530-sources.json