On 04/29/2013 12:03 PM, Christian Huitema wrote: >> The "problem" here is that don't have all the names/IDs we'd like. >> For example, using the MAC address as the Interface_ID would do for >> this purpose... but the the IPv6 address is tied to the MAC >> address, and would change upon replacement of the NIC (which is >> generally undesirable)... > > Undesirable by whom? For a laptop, for example, the most likely cause > of a MAC address change is that the user/owner used an administrative > command to change it, probably in an attempt at getting privacy. > Keeping the same IID would defeat the purpose.
I don't think that's the rule for users, though. That said, in such scenarios you should probably do *only* RFC4941. And, if you're bothering to run an administrative command to change the MAC each time you connect, why not run just another command and short-cut SLAAC to get any address you want? > On the other hand, if I am managing a big server, I would like to > retain the same IPv6 addresses to avoid disrupting service. But then, > if I want a fixed address, I would probably ensure that by > configuring a fixed address, not by relying on a side effect of > automatic address configuration. There are many deployments that employ SLAAC, where address changes would be undesirable (probably the case for most organizational networks doing slaac). 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 --------------------------------------------------------------------
