stateless-autoconfig is entirely not sufficient for site admins to use
in a 'renumbering' event. There are many items passed out in DHCP
responses which are used by the end systems and not included in
stateless-autoconfig. Existing practices account for these items via
DHCP in a mostly centralized manner, without these items site-admins
will be left with no option but to manually touch each device...
Take a moderately large enterprise of 50k systems in a global setting,
how long will it take to touch each of the 50k devices and change even
the basics: dns-server, wins-servers, domainname (assume you can not
'trust' the system owner/user to get this right, and assume you have
limited helpdesk-staff).