Help with DHCPv6 client-identifiers

[Rudy Zijlstra]

On 11/20/2011 04:29 PM, Ted Lemon wrote:
> On Nov 20, 2011, at 5:31 AM, "Simon Hobson"<dhcp1 at thehobsons.co.uk>  wrote:
>
>> And your suggestion for a unique*, invariant**, deterministic***, and always available**** identifier is ?
>> * Yes, some manufacturers have cocked it up, but it's mostly unique.
>> ** The majority of devices where this is being called for don't change their hardware address frequently (or at all).
>> *** MAC addresses survive OS re-installs, "reset to factory default" operations, etc.
>> **** Any device with an ethernet like interface will have one.
>>
>> I think everyone complaining that hardware address isn't supplied by a DHCPv6 client would be happy if the client always supplied a unique, invariant, and determinable ID. Unfortunately, that was not included in the IPv6/DHCPv6 specs.
> Yes, it is in the spec.   Read the spec.   For heaven's sake, the whole *point* of the DUID was to come up with something that was more reliably unique than the MAC address.
Unfortunately, it is also reliably unpredictable