On Mon, 17 Aug 2015, Steven Barth wrote:
At first glance all 3 behaviors seem sensible, while 2 and 3 look more
preferable.
However I do not particularly remember all the implications. In any case I'm
thinking of adding "Routers which seize to be elected DHCP
servers SHOULD - when applicable - invalidate remaining existing
bindings in order to trigger client reconfiguration."
as a generic recommendation.
Yes, I think this makes the most sense as well. The only other way of
solving this would be for all routers capable of becoming HNCP Designated
Router for the Common Link would keep all kinds of state between them (for
instance DHCP leases), and while this would be nice, I see this as a huge
complication that is probably not worth doing?
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
