Persistent DUID (DHCP Unique Identifier) for Server

Ted Lemon Ted.Lemon at nominum.com
Fri Nov 25 20:04:19 UTC 2011


On Nov 25, 2011, at 7:05 AM, Simon Hobson wrote:
To the letter of the spec, that still doesn't fit the "cannot be changed" requirement. Most devices have some flash, if only to hold the MAC address, and whilst nominally static, such flash can usually be changed.

If the official identifier is burned in ROM, or is effectively unchangeable even though stored in flash, it should be okay to use even if you can falsify a different address on the wire.   What you can't use is the address that's in the kernel that can be changed, for instance, because you can't know whether it was changed before you got to it.   So to use DUID-LL, your primary responsibility is to a good process, I think.

Of course, there are also manufacturers that do not actually ensure that their addresses are unique.   When you block out the enterprise ID, it's not *that* many devices.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20111125/6797c80e/attachment.html>


More information about the dhcp-users mailing list