On Aug 18, 2011, at 2:13 PM, Fred Baker wrote: > > On Aug 18, 2011, at 12:43 PM, George, Wesley wrote: > >> B. 7.4 ND cache priming and refresh >> WEG] might be worth thinking about situations where DHCPv6 is in use and >> whether that can be leveraged to achieve something similar to this, i.e. >> watch the DHCPv6 messages go past and pre-populate the ND cache accordingly. > > If they go through your device, that makes sense. > http://tools.ietf.org/html/draft-ietf-savi-dhcp would be an example. Any LAN > that has two routers has a problem, though, as only one of them is likely to > be/see the unicast DHCP responses.
Also I mostly thought about this in the reverse context, e.g. a large number of hosts keeping the router's address in their cache. it is possible to that this scenario is in fact invalid, which would make the draft simpler.
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
