Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

How is multipath tcp different from classical tcp?


Asked by Moshe Christian on Dec 13, 2021 FAQ



Their main difference with classical TCP congestion control schemes is that they need to react to congestion on the different paths without being unfair with single path TCP sources that could compete with them on one of the paths.
One may also ask,
Multipath TCP (MPTCP) [17] is a recent TCP extension that addresses this problem since it enables a TCP connection to send data over different paths. MPTCP can aggregate the bandwidth of the different paths that it uses [41].
In this manner, In contrast to Ethernet channel bonding using 802.3ad link aggregation, Multipath TCP can balance a single TCP connection across multiple interfaces and reach very high throughput. Multipath TCP causes a number of new issues.
In respect to this,
We know that TCP is single path. It means that there can be only one path between two devices that have TCP session open. That path is sealed as a communication session defined by source and destination IP address of communicating end devices.
Subsequently,
Parallel access schemes used to accelerate transfers by taking advantage of HTTP range requests to initiate connections to multiple servers of a replicated content, are not equivalent to Multipath TCP as they involve the application layer and are limited to content of known size.