> -----Original Message----- > From: Christian Huitema [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 22, 2006 12:22 AM > To: Fred Baker; Thomas Narten > Cc: Durand, Alain; Bob Hinden; IPv6 Mailing List > Subject: RE: Proposed M&O bits text for RFC2461bis > >> 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.
The problem with the above solution is that is assume that all hosts on the same link should be configured with the same policy, Either all DHCP or all stateless autoconf. If on a link I have a number of servers and a number of client PCs, I may want to let the PC use stateless autoconf and force the servers to use DHCP. > > 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? I agree. See my previous mail. - Alain. -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
