> As it is today, to use DHCPv6 the way I want, I must first have my host > get an IP (the wrong one), figure out what DUID it used, and reconfigure > my server to give it the one I want it to have. With RA, I don't assign > the address, but to know what it is, I just look up its MAC address and > I'm done. With DHCPv4, I look up its MAC address, add it to my server > configuration and I'm done. > > I don't really care if it's a MAC address per se, but I don't want to > have to deal with DUID change because of OS reinstallation, change of > client software, dual-boot, removal & re-adding of the connection > definition, etc. I can think of reasons why it might be nice to have > different DUIDs for different OS's, so I don't object to the option, but > in most cases the current spec hurts (me) more than it helps.
I'm amazed at how the DUID was supposed to be "better than" (more stable than) a MAC address - and therefore the MAC address wouldn't be needed), but ends up being worse in too many cases. Steinar Haug, Nethelp consulting, [email protected] -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
