Rethink the single IPv4/IPv6 model #8
Description
The current model is that each producer is only allowed to produce a single IPv4 and a single IPv6 address. This works well in environments with a correct and fairly stable setup, and had allowed for simplifications to be made in some producer implementations to only track a single IP address per address family. Unfortunately, over time I have observed some niche cases this model does not handle well.
The Obvious: Multiple IPs per AF
Interfaces that, for whatever reason, are dynamically getting multiple non-temporary IP addresses of the same address family, are not supported.
New Addresses with Shorter Preferred Lifetime
Upstream configuration changes that result in the new IP address having a shorter preferred lifetime, may cause some producer implementations to lose track of the current IP address, once the old IP address with the longer preferred lifetime is gone.
This can be fixed at the producer level.