Static vs SLAAC - Static expected to be preferred?

[Mark Smith]

Hi Steinar,

On Wed, 27 Apr 2011 14:08:33 +0200
"Steinar H. Gunderson" <sesse at google.com> wrote:

> Den 27. april 2011 14:05 skrev Mark Smith
> <nanog at 85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org> følgende:
> > It has been suggested that in this SLAAC vs static address scenario,
> > it's not a common expectation that static addresses (with the default
> > infinite preferred and valid lifetimes) would always be used in
> > preference to the SLAAC addresses.
> 

Do you have any comments on your general static address
expectations?

> What about SLAAC vs. privacy addresses? Usually the latter would have
> a shorter preferred lifetime.
> 

That's true. Privacy addresses seem to be covered by rule 7, which
refers to them as temporary addresses, with non-privacy addresses
referred to as public addresses. By default is says to prefer public
addresses, unless overridden by an application via an API, or if
privacy is enough of a concern, then it is acceptable to prefer privacy
addresses over public addresses.

Rule 8 says to use the longest matching prefix between the candidate
sources and the destination, and also says rule 8 may be superseded if,
for example, the implementation can make a better source
address choice.

So perhaps using the value of the preferred lifetime as a tie-breaker
could occur either between rule 7 and 8.


Thanks,
Mark.