Multipath TCP (MPTCP)
What is Multipath TCP (MPTCP)?
Multipath TCP (MPTCP) extends ordinary TCP so a single connection can use more than one network path at once, such as a phone's WiFi and cellular radios together, instead of staying tied to one address pair for its whole lifetime. AdminKit's My IP tool shows the single address a check sees, even when a connection itself is spread across several.
By AdminKit team, Netbase JSC · Updated
Multipath TCP (MPTCP), defined in RFC 8684 (obsoleting the earlier RFC 6824; IETF Datatracker lists RFC 8684’s status as a Proposed Standard), extends ordinary TCP so a single connection can use more than one network path at the same time — for example, a phone’s WiFi and cellular radios together — instead of being tied to one source and destination address pair for its entire lifetime. After the initial TCP handshake, either side can negotiate additional “subflows” over other available address pairs, and MPTCP schedules application data across whichever subflows are currently open, reassembling it in order at the receiving end so the application still sees one ordinary TCP socket. The Linux kernel ships an implementation: its MPTCP documentation explains that a socket created with the IPPROTO_MPTCP protocol starts with one subflow, a regular TCP connection over one interface, that more subflows can be negotiated later, and that MPTCP use is signalled through a new field in the TCP options. Because MPTCP signals itself through TCP options that an unaware middlebox can strip without the connection actually failing, a path that drops those options silently downgrades the connection to plain single-path TCP rather than breaking it outright, which makes partial MPTCP support hard to notice from the outside. Apple has used MPTCP for the Siri voice assistant since iOS 7, and several network operators use it to bond WiFi and LTE/5G for a single faster connection — Apple’s own support documentation confirms Siri still tries an MPTCP connection over Wi-Fi with a cellular backup today. Each subflow runs its own Path MTU Discovery independently, since different paths can have different MTUs.
AdminKit groups multipath TCP (MPTCP) under its IP & network cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
How does MPTCP use more than one network path at once?
After the initial TCP handshake, either side can negotiate additional 'subflows' over other available address pairs, and MPTCP schedules application data across whichever subflows are currently open, reassembling it in order at the receiving end.
What happens if a middlebox doesn't understand MPTCP?
MPTCP signals itself through TCP options that an unaware middlebox can strip without the connection actually failing -- a path that drops those options silently downgrades to plain single-path TCP rather than breaking it outright.
Does an application need to be rewritten to use MPTCP?
No -- MPTCP reassembles data from all active subflows so the application still sees one ordinary TCP socket, which is how Apple has used it for Siri since iOS 7 without apps needing MPTCP-specific code.
Why does each MPTCP subflow run its own Path MTU Discovery?
Because different paths -- like a phone's WiFi and cellular radios -- can have different MTUs, so each subflow has to discover its own largest deliverable packet size independently.
Sources
- RFC 8684 -- TCP Extensions for Multipath Operation with Multiple Addresses
- RFC 6824 -- TCP Extensions for Multipath Operation with Multiple Addresses
- IETF Datatracker -- RFC 8684 document status
- Apple Support -- Use Multipath TCP to create backup connections for iOS
- Linux kernel documentation -- Multipath TCP (MPTCP)