On 2009/11/10, at 10:58, Ralph Droms wrote:
In the discussion of IPv6 address selection , Dave Thaler asked me
to comment on this bullet from slide 10:
* DHCP option
- Hard to kick policy reconfigure by a server.
Not wanting to contribute to yet another iteration of the RA-vs-DHCP
debate, I'm responding through the mailing list. DHCPv6 has an
explicit mechanism, required by RFC 3315, in which a server can
asynchronously trigger a DHCPv6 message exchange from the client.
I know there is RECONFIGURE message of DHCPv6,
but it requires secured channel to use it.
So, I described "Hard" here.
Hard means that it cannot be used everywhere the
DHCP is used nwo.
Thanks.
Suresh commented that the router might be a better source of updates
in some circumstances, when the selection policy is modified by
changes in the routing infrastructure as propagated by routing
protocols. I haven't thought about that scenario and can't comment...
- Ralph
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
