On Tuesday 2012-05-22 22:51, Nicolas Maître wrote: > >MPTCP is an extension of TCP which enables it to use multiple paths as >part of a single "MPTCP connection", answering to a multihoming and >performance demand. It acts as a higher-level, using TCP connections >as subflows and it has been designed to be backward-compatible with >regular TCP. [...] >It's currently being standardized by the IETF. >[0] http://tools.ietf.org/html/draft-ietf-mptcp-multiaddressed-07 A mindshare about MPTCP itself, not any particular implementation: Another standard, eh? xkcd #927 is calling. I would expect that MPTCP will end up in limbo -- like most of the other RFC prose. SHIM6 seems to already offer multihoming/loadsharing - and does so at the IP level, so I really wonder why one would want to use MPTCP when that's one up and seems to limit itself to TCP. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
