Help with DHCPv6 client-identifiers

[Rudy Zijlstra]

On 11/20/2011 04:39 PM, Ralph Droms (rdroms) wrote:
> Depends on what is meant by 'identify the unit'.  The DHCP provisioning system may use a different identifier than other parts of the provisioning system ... likely for historical reasons.
>
> - Ralph
>
>
> On Nov 20, 2011, at 10:18 AM, "Ted Lemon"<Ted.Lemon at nominum.com>  wrote:
>
>> On Nov 20, 2011, at 9:08 AM, "Rudy Zijlstra"<rudy at grumpydevil.homelinux.org>  wrote:
>>> It is what is used to identify the unit, so it can be provisioned with the correct service level. A unit that does not supply the MAC address does not pass compliance testing.
>> If the statement you just made were true, then it would be the case that the device does not send a DUID, right?
>>
The DUID is there.. and i do not care whether the DHCP server uses as 
hash or key in its internal storage. The unit identifier is the 
MAC-Address. As that is known beforehand, is printed on the outside of 
the box as well as outside of the unt, and does not change.

The DUID is not known beforehand, and thus cannot be used to identify 
the unit in the Operator workflow, nor for any policy decision in the 
DHCP server such as what config file to provide to the unit.