The 0.87
release of the multipath TCP patch set is available. Improvements
include better hardware offload support, zero-copy sendfile/splice support,
working NFS support, better middlebox handling, and more. See this article for an overview of multipath TCP.
(Log in to post comments)
Multipath TCP 0.87
Posted Jul 29, 2013 8:03 UTC (Mon) by bagder (subscriber, #38414)
[Link]
So is there any fancy success-stories or killer-apps for multipath TCP out there yet?
Or perhaps the reversed, is there anything in particular that still fails over it?
Multipath TCP 0.87
Posted Jul 30, 2013 13:05 UTC (Tue) by bjartur (guest, #67801)
[Link]
Yes, content delivery networks might not implement this. Akamai, for one, has multiple hosts with the same IP. This has mostly worked so far because in practice, network paths don't change much during the lifetime of a TCP connection. This allows for the assumption to break. Depending on the geographical distance between Akaimai's servers, their setup just might keep on working anyway. Then you can seamlessly switch from your home network to a cellular network, to your train network. Your TCP connection will endure just until you switch Akamai servers. Then the new server will reset your connection. Your client will stutter but cope. The network wound up being unreliable, but slightly less so than before.
Sharing IPs among servers connected to different ISPs within the same area will fail horribly. If you're doing that, however, you are doing it wrong. Use ISP infrastructure, ISP allocated IPs and ISP DNS.
The authors might have given this thought. I haven't even read the RFC.
Multipath TCP 0.87
Posted Jul 31, 2013 11:12 UTC (Wed) by christophpaasch (subscriber, #54567)
[Link]
Citrix has added Multipath TCP in their NetScaler platform: