| |||||||||||||
Multipath TCP: an overviewMultipath TCP: an overviewPosted Mar 27, 2013 3:50 UTC (Wed) by ebiederm (subscriber, #35028)In reply to: Multipath TCP: an overview by nhorman Parent article: Multipath TCP: an overview
Some API augmentation will doubtless be needed for refined control.
But you can establish a MP-TCP connection using the existing socket APIs. As part of that connect establishment the MP-TCP stack can share all of your routable IP addresses and see which IPs on either side can connect to each other.
With those additional connections MP-TCP can with proper congestion control load-balance your traffic across those flows.
Additionally MP-TCP can add and drop subflows as your device meanders around and connects and disconnects from different networks.
API augmentation is only needed for the times when the defaults aren't optimal for some configuration.
(Log in to post comments)
Multipath TCP: an overview Posted Apr 4, 2013 4:04 UTC (Thu) by kevinm (guest, #69913) [Link]
What do the getsockname() and getpeername() APIs do on a MPTCP connection?
Multipath TCP: an overview Posted Apr 4, 2013 6:24 UTC (Thu) by christophpaasch (subscriber, #54567) [Link]
It returns the info from the initial TCP subflow.
So, even if the host has moved away (e.g., moved away from its WiFi access-point and MPTCP switched to 3G), the syscalls still return the old address of the WiFi interface.
|
|||||||||||||