Re: address selection and DHCPv6

[Ralph Droms <rdroms at cisco.com>]

There is an operational issue - anecdotal, perhaps not of interest - that
I've heard of.  It's related to Alain's observation of who runs routers and
who runs the DHCP server.

Anyway, the issue is that, in the case of router misconfiguration, it may be
the case that hosts unexpectedly take on new addresses, that may take 2
hours to flush from their interfaces.  DHCP would avoid that particular
problem.  Note that I'm not claiming DHCP is less prone to
misconfiguration...

- Ralph


On 10/26/06 6:16 PM, "Durand, Alain" <Alain_Durand at cable.comcast.com> wrote:

> I've been thinking some more about Bernie's point. In theory it should not,
> but in pratical operation, it does matter where the config information is
> coming from.
> The ops people in charge of routers are not the same as the one in charge of
> servers (DHCP included) ... and the last thing I'd like to see hapening is the
> source address selected by a server to change if one team changes a lifetime
> without noticing the other...
> 
>    - Alain.
> 
> 
> ----- Original Message -----
> From: Bernie Volz (volz) <volz at cisco.com>
> To: Manfredi, Albert E <albert.e.manfredi at boeing.com>; Durand, Alain
> Cc: ipv6 at ietf.org <ipv6 at ietf.org>
> Sent: Thu Oct 26 16:03:26 2006
> Subject: RE: address selection and DHCPv6
> 
> I would think that how an address is assigned shouldn't enter into this.
> I can't see that it matters.
> 
> What really matters is the lifetimes associated with the address. The
> longest lifetime address is probably the best to use since it is the
> most stable. [Ignoring privacy and other related issues.]
> 
> Perhaps this gets at what you want anyway, since manually assigned
> addresses would presumable have the longest lifetime?
> 
> - Bernie 
> 
> -----Original Message-----
> From: Manfredi, Albert E [mailto:albert.e.manfredi at boeing.com]
> Sent: Thursday, October 26, 2006 3:06 PM
> To: Durand, Alain
> Cc: ipv6 at ietf.org
> Subject: RE: address selection and DHCPv6
> 
> Except that from what others have said, that might not be the desired
> goal. Perhaps for privacy or other reasons, a most stable address choice
> might not be optimal.
> 
> I originally thought that would be the best choice, but ...
> 
> Bert
> 
> 
>> -----Original Message-----
>> From: Durand, Alain [mailto:Alain_Durand at cable.comcast.com]
>> Sent: Thursday, October 26, 2006 2:00 PM
>> To: Bernie Volz (volz); James Carlson; Vlad Yasevich
>> Cc: ipv6 at ietf.org
>> Subject: RE: address selection and DHCPv6
>> 
>> The question is not to get an absolutely stable address,
>> but to make sure that in case multiple addresses are defined,
>> the one with the highest likelyhood of stability is selected.
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6 at ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6 at ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------