On Tue, 3 Mar 2015, Ted Lemon wrote:
This is probably the use case we most care about. I think it's actually
a strong argument for going with a longer deprecation period. E.g., if
your deprecation period were three hours, we simply wouldn't have a
problem.
I don't agree with this at all.
I can easily come up with an equivalent scenario that would require an
even longer overlap in time, for instance a long video conferencing
session, and also there are longer movies than 3 hours.
We need to make applications be able to renumber to new addresses, and it
doesn't matter if the use-case is that they're moving between APs, going
from fixed to wifi to mobile, or they're being renumbered within the
existing access method. Applications need to stop to rely on the address
being stable over time. We need to give application developers the tools
they need to not have to care about this, which means they need to have
some kind of middleware, be it MP-TCP or something else. This needs to be
easy for the most common use-cases, and it needs to be transparent to the
application developer.
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
