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. > > 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. > > -- Christian Huitema > > > Right. But a bad side effect of manually configuring fixed addresses is that you derail all of the good work around renumbering.
It might prove operationally useful to be able to configure a static IID, but still continue to use of a variable network prefix (derived from RA). regards, RayH -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
