> From: Scott Brim <[email protected]>
>> Support for multiple PA addresses does certainly help with the
>> multi-homing aspects, but does it help with number (address)
>> portability at all?
> Just for clarity: Multipath transport does not assume or rely on the
> endpoint receiving multiple PA addresses from a network.
Huh? From the MPTCP architecture document:
"The multipath transport protocol must allow for a logical transport
endpoint as seen by the application to correspond to multiple physical
network attachment points, such as multiple IP addresses on the same or
different network interfaces."
Note the "multiple addresses on the same ... network interface[]".
Yes, it does mention other possible techniques for gaining access to multiple
parallel paths, but the first ("Use a path selector value") is not possible
at the moment, and the other ("Next-hop selection") will only affect outgoing
traffic, not incoming.
So as far as I can see, use of multiple addresses is the _principle_
technique used by MPTCP to support _site multi-homing_ (which is what I was
referring to with 'multi-homing"). Do you disagree with that?
(Yes, hosts with multiple interfaces may be more common in the future, and
MPTCP also handles that - but that's not what people generally refer to as
'multi-homing', which tends to mean 'site multi-homing' - which is, after all,
what has the routing people concerned.)
You may want to quibble with the use of "PA", but if a site has a PI address,
presumably it does site multi-homing that way.
Noel
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
