host-identifier with IPv6

Sten Carlsen sten at
Wed Mar 4 01:18:45 UTC 2009

The way I hear all this is not a question of how to set up a large
network now and not about starting to walk around with a hand scanner
tomorrow. It is rather a question of having EXISTING large installations
and large databases with the mac-address as the only common (semi-)fixed
parameter. The large amount of pain, again as I hear it, is in changing
all of that existing data to use a new identifier, even one you can not
ask a user with a broken PC to give you.

Another question that has not been raised yet (maybe because it is not
an issue): How will these well discussed issues be influenced by the
massive virtualisation of servers that can be expected in many places,
not just in data centers. If you boot/reload those regularly from a disk
file as I will assume happens when it changes role because there is more
need for it in another application just now, will it retain its DUID,
load one from the disk file or make a new one each time?

Eustace, Glen wrote:
>> To me, the idea of tracking every mac address of every device on a
>> network by walking around with a keyboard or a bar-code scanner and
>> entering them all into a database is the very definition of "pain and
>> suffering." DHCP's whole raison-d'être is to save you, the network
>> administrator, the effort of walking around doing a manual process on
>> each machine.
>> So why is it that you have chosen this model - what is the value that
>> it adds, and why is it that there is no better solution that involves
>> less work?
> The big difference between an ISP and a corporate/educational institution, as far as I can see, is we have obligations with respect to the users and computers on our networks.
> For a large proportion of the devices on our network, we own them.  They are an asset and hence will be recorded, somewhere.  We have license agreements that apply to computers that we own. We have license agreements that are enforced by source IP address. We have large numbers of communal equipment e.g. laboratories that must provide a consistent known software environment for our students.  Basically we have to manage all the computers rather than an ISP that usually just provides network access.
> We operate some of our student networks in the same way as an ISP, in these I don't really care about a computers identity.  All addressing is dynamic.  All of our management issues, workflow etc pertains to our 'managed' networks.
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at

Best regards

Sten Carlsen

No improvements come from shouting:


More information about the dhcp-users mailing list