| |||||||||||||
Multipath TCP: an overviewMultipath TCP: an overviewPosted Mar 27, 2013 8:35 UTC (Wed) by dlang (✭ supporter ✭, #313)In reply to: Multipath TCP: an overview by jezuch Parent article: Multipath TCP: an overview
They address this with the comment about how much of the Internet allows TCP and UDP but not any other protocols.
I'm actually a bit surprised that they didn't layer it on top of UDP.
(Log in to post comments)
Multipath TCP: an overview Posted Mar 27, 2013 8:54 UTC (Wed) by marcH (subscriber, #57642) [Link]
> I'm actually a bit surprised that they didn't layer it on top of UDP.
I guess this saves them re-implementing congestion control, which is insanely complicated http://lwn.net/Articles/128681/
Multipath TCP is not really "layered" in the usual sense since it needs one native TCP connection for every stream. It looks a bit like... a "plugin" :-)
Multipath TCP: an overview Posted Mar 28, 2013 2:30 UTC (Thu) by martinfick (subscriber, #4455) [Link]
But then it wouldn't just work where TCP already works. In other words middle boxes might let through TCP but not UDP, such paths could not use UDP for MPTCP. Of course, I suppose MPTCP could be extended to use any other transport including UDP at some point.
Multipath TCP: an overview Posted Apr 1, 2013 21:57 UTC (Mon) by marcH (subscriber, #57642) [Link]
To be honest most "middle boxes" I've seen rejecting UDP were just... web proxies and thus not letting *anything* go through.
Of course any intermediate kind of network crippling is possible in theory.
Multipath TCP: an overview Posted Apr 1, 2013 23:31 UTC (Mon) by martinfick (subscriber, #4455) [Link]
Are you sure? I suspect most firewalls, load-balancers, and other middle boxes which do port forwarding or filtering are filtering by protocol, so they will filter out UDP if only the TCP port is open/forwarded.
|
|||||||||||||