The encyclopedia · Software & IT · Technical decision · 1993-1997
DHCP let a host broadcast, be answered, and lease an IP so a new device joins any network
DHCP's Discover/Offer/Request/Ack exchange plus a bounded lease auto-configured a host and reused addresses.
IETF
the move
Once every machine needed an IP, subnet mask and router, the naive way was static configuration: an administrator wrote them down by hand. That did not scale, and after a laptop left one network and joined another it broke.
DHCP turns setup into a conversation the host starts. It sends a broadcast, a server answers with an offer, the host asks for it, and the server acknowledges it for a set period. Because it is built on BOOTP relay agents, it could be rolled out without replacing every router.
Because the address is a lease rather than a gift, it expires and returns to the pool. So addresses are reused, networks stay manageable, and plugging in a device just works.
why it works
- A broadcast means a host with zero knowledge of the network can still reach a server, so no pre-configuration is needed.
- The finite lease means abandoned addresses (laptops that left, cables unplugged) are reclaimed automatically.
- Leaning on existing BOOTP relay agents let DHCP deploy incrementally instead of requiring a network-wide switch.
- The renew and rebind timers give a client graceful transitions on one network rather than hard failures.
what transfers
Make setup a conversation the device itself starts, and give the scarce resource a limited lease so the system recovers without an operator.
what came after
DHCP was finalized in RFC 2131 in March 1997 and became the standard way every home, office and ISP hands out addresses. Later work added IPv6 (DHCPv6) and options for boot servers, DNS and time. Its security gaps led to DHCP snooping and option-82 on managed switches.
references
spotted an error? The archive wants to know.