> > Like I said, if there's a bunch of routers announcing their presence > > and you want a DHCP option to provide guidance to a host as to which > > one to choose, that would be fine. But pointing to a potentially non- > > existing address in the hopes that there will magically be a router > > residing at that address would a serious regression in robustness. > > > It really isn't a serious regression in robustness in the real world. > It really is functioning today. Most DHCP servers are not used to > shoot users in the head, despite your claims to the contrary.
This to me is one of the least credible claims of the RA/SLAAC crowd. On the one hand we have carriers around the world with millions and millions of customers getting default routes and other config through DHCPv4 every day. And most of the time it actually works very well! On the other hand we have RA/SLAAC with a vastly smaller customer base, vastly less real life testing - but which is still claimed to be so much better that DHCPv6 is not *allowed* to get a default route option. The mind boggles. Steinar Haug, Nethelp consulting, sth...@nethelp.no
