There is very little to be said about auto-conf/DHCPv6 interaction: DHCPv6 and stateless address auto-configuration and the addresses assigned through each process are independent of each other. A node may run either, both or neither DHCPv6 and SLAAC.
How are privacy addresses an issue? - Ralph On 3/22/06 1:21 AM, "Christian Huitema" <[EMAIL PROTECTED]> wrote: > >> More to the point, if you are in a shop that has decided to allocate >> addresses by DHCP, calculating an address via autoconfiguration is >> the wrong answer. Not because it is politically correct or otherwise, >> but because it is the policy of the network, and the IETF doesn't get >> to decide that. > > We went through that before. The proper way for a network to indicate > that nodes should not use auto-conf is simply to not advertise prefixes > with the auto-conf bit set. If the auto-conf bit is set, then hosts may > obviously auto-configure addresses. > > In fact, it would be good to be a bit more specific about the expected > behavior when both auto-conf and DHCP are allowed (both M and A bits). > Is the host expected to auto-allocate an address and then confirm it > through DHCP? Does it use the union of DHCP and auto-config? What about > privacy addresses? > > -- Christian Huitema > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
