Depends on what the DHCPv6 server is configured to do. AAC and DHCPv6 can assign addresses on the same prefix, but I would suspect that in most deployments there is little reason to do that. Instead, DHCPv6 would likely assign addresses on prefixes that are not AAC.
More likley is that you have a unique local prefix that you allow AAC for. But, for a global unicast address you need to go to DHCPv6. The DHCPv6 server would *NOT* likely assign another unique local address for that client. Just because a prefix is advertised as AAC or not, does not imply ANYTHING about what DHCPv6 would do for that prefix. Though in practice there is little reason to use both AAC and DHCPv6 on that single prefix. Though there may be good reason to do AAC on some prefixes and DHCPv6 on others if multiple prefixes are active. - Bernie > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of da Silva, Ron > Sent: Friday, May 27, 2005 9:31 AM > To: Iljitsch van Beijnum > Cc: dhcwg@ietf.org; IETF IPv6 Mailing List > Subject: [dhcwg] Re: purpose of m/o bit > > > To me, assuming the current specs, the following would make sense: > > One of the permutations missing in your algorithm is if a device is > configured for always-full-DHCPv6 on an interface AND it receives RA > with AAC set...I presume in that case the device would get multiple > addresses, right? > > -ron > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
