On Wed, 4 Mar 2015, Ole Troan wrote:
Much as I love MPTCP, it only helps TCP sessions. And it requires both
hosts to
be updated to be effective.
IPv6 multi-prefix multi-homing requires both hosts to support it. which means
transport fixes.
Yes, as far as I can see there are only two ways to fix this, either you
fix one end and this would require tunneling for the client that wants to
be endpoint address independent (LISP or something else), or if you fix
both ends, you could use MPTCP, SHIM6 etc.
So one way of doing this would be to use tunneling approach for traffic
that isn't address-independent, and MPTCP/SHIM6 approach with direct
routing for things that are (I guess this would require some MIF/PVD kind
of approach). This of course means you have to have a decent notion about
what is what, which either means caching results (this DST address seems
to support address-independence protocol BLAH), or it means explicitly
telling the client about it (DNS SRV records or something), or both.
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
