Markus, Steven,
When we assign a v4 prefix to a common link, we elect a designated DHCPv4
server. As Markus has explained to me, this is done to avoid sharing
state between multiple DHCPv4 servers on a single link, which makes sense.
What default routes should be announced to v4 clients? Just the one
through the node serving as DHCPv4 server (and count on Redirects to
optimise routing), snoop on the routing protocol and choose the best
default router according to the routing protocol, or announce all the
routers on the local link and trust the host to choose wisely?
(On a related note, do you think that it is wise to snoop on the routing
protocol and build something similar to the example in RFC 4191 Section 3.6?)
What happens when a new router appears on the link, a new election is
called, and the new router becomes the designated DHCPv4 server -- won't
address collisions occur? Perhaps DHCPv4 service should be "sticky", in
the sense that a new election isn't called if the previously elected
server is still alive.
(With stateful DHCPv6, we could perhaps do something with RECONFIGURE,
although I'm not sure if RECONFIGURE is able to force the client to choose
a different server.)
-- Juliusz
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
