Re: [IPv6] Adoption call for draft-bctb-6man-rfc6296-bis

[Philip Homburg <[e-mail]>]

> I have a network:
>  - multi-homed - offering external services from stable addresses
>  - have applications / host stacks that do not support MPMH nor
>  handle ephemeral addresses well
> 
> Whats the solution that is available for that network today? Stick
> to IPv4 because you Mr User isnt found worthy to use IPv6 is of
> course one answer.

In my limited experience, applications and hosts respond quite well to
deprecation and invalidation of prefixes. Of course, the 2 hour
minimum for invalidation is annoying in this context.

Deprecation is instant. So for new flows, a switch from one prefix to another
is instant. 

The tricky part is applications that use TCP connections but do not check if
the connection is life. This is sometimes a matter of configuration. For
example, openssh supports a keepalive mechanism that aborts the connection
if the connection fails for some period of time.

So by and large, the vaste majority of internet use works fine on todays hosts
and applications, assuming routers actively deprecate and invalidate unwanted
prefixes.

If we can assume a NPT implementation in the network, then we can also 
assume up-to-date prefix information from routers. It is the same source
address selection process.

There is one exception I can think of, if the NPT box would select different
source addresses based on the destination of a packet, then that is something
that currently hard support in a different way.