In your previous mail you wrote: > There is an issue with using a MAC-based link local address on an interface > that does not have that MAC address, which is that any other interface > using that MAC that turns up is going to fail DAD. Normally this will be > another interface on the same device, but even then it can be an issue. > Therefore it is better guidance to say that one should simply change link > locals at the time one changes the MAC address... not necessarily to a > MAC-derived address, but it is impolite to continue to use the old link > local.
=> I still believe you assume too much about layer 2 (MAC) and layer 3 (IPv6) address relationship. The worst which can happen is "impolite" and of course when you mess the MAC addressing you can't expect address generation based on MAC will still work without conflict. BTW a MAC address is attached to a device according to the IEEE spec, not to an interface, so there is at least one computer vendor who interprets device as the whole computer, not a NIC... Regards francis.dup...@fdupont.fr PS: the only point IMHO could be standardized (as a BCP) is to use interface IDs not based on MACs when there are some interests to change a MAC (it seems common sense, i.e., no need to provide long explanations). And implementations should give an easy way to do this (from my past experience this could be more critical). -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
