RE: address selection and DHCPv6
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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
--------------------------------------------------------------------




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.