Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios

[Philip Homburg <[e-mail]>]

> The main issue I see with incorporating an explicit rule in RFC6724
> about "freshness" is that in multi-prefix scenarios, it's guaranteed
> that the default SA will oscillate among the different prefixes,
> and that if you only implement this workaround, you wouldn't be
> able to communicate with hosts actively employing your stale prefix.

Assuming that only the preferred lifetime is changed quickly in response
to receiving an RA, what problems do you expect with the oscillating 
source addresses?

As far as I know, there exist NATs for IPv4 that distribute traffic over
multiple public IPv4 addresses. That seems to work.

I don't know if there are IPv6 stacks that distribute traffic over multiple
addresses that all have preferred lifetime > 0, but as far as I know, that
is allowed.