For terminal clients and workstations without a hard disk, BOOTP was the perfect solution to obtain an IP address on the network and thus bind the operating system. The fact that the assignment of the address by the communication protocol could be solved simultaneously with the boot process was practical and simple for desktop computers, which began to be used in networks with more manageable sizes. As a result, it was problematic, for example, for the administrator to manually configure the BOOTP server's network information tables.
However, as networks grew and computers acquired autonomy, and thanks to the development of more mobile portable devices, not being able to automate the configuration process was seen as a negative factor. The desire for a new protocol was evident. With the Dynamic Host Configuration Protocol (DHCP) a successor was found in 1993 (final specification in RFC 2131). DHCP is largely based on the boot protocol structure, supplemented, however, with different additional configuration options and offers the ability to assign reusable network addresses to connection-seeking clients . Additionally, addressing information assignment with DHCP also works during current system operation: with BOOTP, no reboot is required.
These are the most important differences between both protocols:
| BOOTP | DHCP |
Automatic configuration | IP address assignment requires manual configuration of address tables | Supports automatic assignment and automatic obtaining of IP addresses (also manual configuration) |
Temporary IP addresses | It's not possible | Possible for a limited period of time |
Mobile device support | IP configuration and access to network information is not possible | Supports the mobility of network clients |
Error index | High error rate due to manual configuration | Virtually immune to errors thanks to automatic configuration of network components |
System Requirements | None | Requires hard drive to store and forward information |
Thanks to various optimizations, DHCP quickly became the standard protocol for IP management in networks, whereas today the BOOTP protocol has only historical value . Since DHCP supports the boot protocol, DHCP servers, in principle, can also respond to all kinds of requests made by a BOOTP client.