>
>
> > However, in the case of
> > roaming the feature is highly debatable. If a host visits the same
> > network multiple times, should it always reuse the same ID, or should
> > it get a new identifier each time? It is very easy to argue that
> > "different each time" has better privacy properties.
>
> Agreed. For instance, draft-ietf-6man-stable-privacy-addresses-06.txt is
> not a replacement for RFC4941. If you're a roaming node, you probably
> want RFC4941 enabled (in addition to having
> draft-ietf-6man-stable-privacy-addresses-06.txt enabled).
Have you considered adding a date/time parameter in generating the new
RID?
e.g. RID ’= F(Prefix, Interface_Index, Network_ID, DAD_Counter,Date/time,
secret_key)
That will result in different IIDs from time to time, and the time could
be chosen
a wide range, e.g., the year, the month, so that when a node move within a
certain time,
the running sessions will not break because of time change.
For conveniency, the time parameter could be decided optional.
Of course, changing secret key will also have a similar effect, at the
owner's will,
but adding a optional time parameter will add more flexibility.
>
> Cheers,
> --
> Fernando Gont
> SI6 Networks
> e-mail: [email protected]
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [email protected]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
