I read the draft and wasn't sure what problem they were trying to solve. They
talk about moving from network to network which seems aimed at laptops or
mobile devices. But randomizing the interface id but keeping it the same on a
particular network allows consistency on each network but you could still be
tracked on that network (like using the MAC address) even though you couldn't
be tracked across networks (unlike using the MAC address).
Why not just use temporary addresses (RFC 4941)?
On the server side, this draft could be implemented in rtadvd. Not sure who
maintains that.
Is that what you're looking for? To see if someone is working on changes to
rtadvd?
Thanks,
Tom
> On Sep 6, 2014, at 6:46 PM, Garrett Wollman <woll...@bimajority.org> wrote:
>
> So is anyone working on an RFC 7217 ("Stable and Opaque IIDs with
> SLAAC") implementation for FreeBSD yet?
>
> -GAWollman
>
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
