Brian, >>> 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. > > Or fully operational shim6, which was conceived and designed for this > exact problem.
right. I tend to think that the problems of multi-homing, multi-endpoint, mobility, and renumbering are tightly coupled. you might need to expose some of this to the transport and applications. I have more hope of solving this at L4.5 or even L5 (I suppose talking about a “session layer” would get me banned from the IETF. ;-)), than at L3.5. to take the digression back to homenet; if we agree this is a problem for transport or above, then at least we can declare victory by claiming it isn’t our problem. cheers, Ole
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
