[kea-dev] DUID-EN

Tomek Mrugalski tomasz at isc.org
Fri May 15 18:56:03 UTC 2015


On 15.05.2015 17:42, Templin, Fred L wrote:
>> Technically, it's not supported, but you can trivially add support for
>> it. Start kea6 and stop it. It will store its generated DUID in
>> ${install-dir}/var/kea/kea-dhcp6-serverid. This is the server DUID in
>> hex form. Feel free to generate your own DUID and put it there. I'm not
>> sure what your deployment model is, but you can even deploy kea with
>> this file, so it will use whatever DUID you want from its first start.
> 
> It sounds like something I could do, but seems a bit cumbersome. ISC dhcp
> has a configuration file option for enabling DUID-EN, so there is no need to
> carry along an ancillary serverid file.
> 
>> This possibility is (somewhat briefly) discussed in Kea User's Guide,
>> section 8.4. Would that work for you?
> 
> OK, but it seems like just one more configuration file to keep track of
> and increases the chance of misconfigurations. It would be far simpler
> if there were a configuration option that could be added to the main
> kea config file.
I see your point. Personally, I don't consider DUID a configuration
parameter in its classical sense. This is something that is supposed to
be generated once and kept as is for the lifetime of the server. At
least that's what was envisioned by RFC3315. I understand that there may
be specific needs that warrant tweaking server's DUID, but in my opinion
they are sufficiently uncommon that it is ok to make its edits cumbersome.

On the other hand, I would afraid that if we expose a configuration
parameter, people may get confused and think that setting their DUID by
hand is required.

Anyway, if those arguments doesn't convince you, please submit a ticket.
I honestly admit that it likely won't be implemented in the next couple
months, simply because we have lots of tickets planned already and this
is not a common feature and there is a workaround that is relatively
easy to apply. Nevertheless, hopefully we'll get round to this ticket
one day.

Tomek



More information about the kea-dev mailing list