Back to column

Multipath QUIC — selected stack

IPv4 or IPv6 / UDP / QUIC (TLS 1.3) + multipath-21, optional proactive same-offset STREAM copies on two validated paths; numeric peers, locally generated certificates explicitly trusted by counterparts, mutual handshake authentication, no SNI requirement or online certificate service; independent private IPv4 deployment; separate trusted context keys, no cross-context tickets/token reuse, NAT or transit flow logging F16: local final-key allowlist, all-connection close on revocation, resumption and 0-RTT disabled.; G01 global deployment: conventional IPv6 Internet underlay with BGP/MP-BGP prefix routing; private deployment remains a separate S03 capability Global plausibility uses IPv6; retained private deployments and historical runtime/budget witnesses use IPv4. K01 configuration: picoquic c124cbe975f71b150ea929d325804335d2bdaa34, Picotls f06553b877ada93c860dd1db9002eabf7365292d, OpenSSL 3.5.0 default provider, with the initiating TLS context restricted to X25519MLKEM768 (4588). Classical fallback under default preferences does not inherit this Yes. The local witness tests key establishment and STREAM traffic in the native simulator, not multipath operation. F37/F38: optional router-local AQM and independently administered DiffServ policies explicitly selected in the existing IP transport carrying QUIC/UDP. Classification/conditioning of visible transport aggregates, without decrypting streams; no RSVP/IntServ or application QoS reservation. Private/global deployment distinctions remain unchanged.

Official project website · Logo credits · Methodology and limits