Fwd: issues with ipv6 and DUID

[Steven Carr]

So if it doesn't support the -D flag then what else doesn't it support.
When it comes to IPv6 you really need to be on the bleeding edge as the
code to support it is still rapidly changing having features/bug fixed.

As for the DUID-LLT always changing, that is wrong, RFC3315 states:
*Clients and servers using this type of DUID MUST store the DUID-LLT in
stable storage, and MUST continue to use this DUID-LLT even if the network
interface used to generate the DUID-LLT is removed.  Clients and servers
that do not have any stable storage MUST NOT use this type of DUID.
*


On 5 April 2013 15:27, Cory Coager <ccoager at gmail.com> wrote:

> No, DUID-LL doesn't change, DUID-LLT always changes.  DUID-LLT is dynamic
> because the T stands for time.
>
>
>
> On Fri, Apr 5, 2013 at 9:41 AM, Steven Carr <sjcarr at gmail.com> wrote:
>
>>
>> I guess the bigger question is why does the DUID-LLT keep changing, if
>> I'm to read RFC3315 correctly it states that DUID-LLT is generated once and
>> then written to non-volatile storage for future use. So does the client
>> have non-volatile storage? if so is dhclient writing the value to a
>> non-volatile location?
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20130405/8db45071/attachment.html>