Watching performance on a DHCP Server

Olaf van der Spek olafvdspek at
Mon Feb 11 22:57:11 UTC 2008

On Feb 11, 2008 11:49 PM, Blake Hudson <blake at> wrote:
> I also happen to be of the notion that the implementation of a protocol
> should be an exercise left open to the programmer, the API and
> interoperatibility should be defined more strictly in the RFC. The spec
> does say that the lease needs to be committed to persistent storage
> before being offered to a client. How persistent is magnetic media? Is
> battery backed up RAM in my RAID controller persistent enough? what
> about RAM in a battery backed up system?

If you can live with the 'or else', you could drop such a 'should' (IMO).

> This requirement seems like it would make most DHCP servers (windows,
> appliance routers, almost anything running on ATA disks) non-conforming
> to the spec. Just something for discussion, the specs leave very little
> open to interpretation on this one.

Some consumer routers don't store leases at all, they start with a
clean slate after a reset.

I think it's possible to adhere to this requirement and still achieve
good performance.

More information about the dhcp-users mailing list