[bind10-dev] DHCP and BIND10

[christof]

> I know we often get abused by embedded systems users, as the DHCP
> package has gained a lot of bloat.  We want to be able to provide a
> solution here, but we may just write a separate "minimal" piece of
> software rather than try and make one piece of software scale to
> both ends of the spectrum.  But then we do double the maintenance,
> and probably the smaller daemon will suffer from slow feature creep
> as people want just "one more thing" from the big server's camp.
> 

do one daemon with hooks for everything. The hooks could be simple returns
if not overridden.

How about a state machine where DHCP at BIND10 provides the minimal necessary
protocol flow by default, but has customizable entry/exit-actions for
states and transitions?

So the default server would be lean. 
If I wants persistent storage for leases, i can compile in the backend for
disk writes and select "commit_to_disk(Lease)" as an entry_action to the
appropriate states. If i want a mail generated for certain ACK-Packets
(don't laugh, i actually use DHCP for address assignment even if the client
does not have an in-band DHCP client), i would just add a
send_ACK_email(address, lease) function...
(and the user would be responsible for choosing the right tool to get the
needed performance. The SOHO dhcp server might get away with calling a
shell script to update a web-page with addresses on each ACK. For an
enterprise you would choose -and compile in- the native async DDNS module)

Implementation-wise the overhead should be in the order of a table lookup.

Christof