Dynamic Host Configuration Protocol

Dynamic Host Configuration Protocol
Name	Dynamic Host Configuration Protocol
Developer	Internet Engineering Task Force
Introduced	October 1993
Based on	Bootstrap Protocol
Osi layer	Application layer
Port	67, 68 (UDP)
Rfc	RFC 2131, RFC 2132

Dynamic Host Configuration Protocol. It is a standardized network management protocol used on Internet Protocol networks for automatically assigning IP addresses and other communication parameters to devices. The protocol, developed under the auspices of the Internet Engineering Task Force, eliminates the need for manual configuration by a network administrator. A DHCP server dynamically distributes network configuration parameters, such as IPv4 addresses, for interfaces and services.

Overview

The protocol was originally defined in October 1993 through RFC 1531, building upon the earlier Bootstrap Protocol. Its primary purpose is to reduce the configuration burden on system administrators in large networks like those at Massachusetts Institute of Technology or corporate environments. A client device, such as a computer or smartphone, requests and receives configuration information upon joining a network, allowing for efficient use of a limited pool of IP addresses. This automation is a cornerstone of modern Internet connectivity, from home Wi-Fi networks to large-scale enterprise deployments by companies like Cisco Systems.

Operation

The process, often called DORA, involves four key messages exchanged between a client and server: Discover, Offer, Request, and Acknowledgment. The transaction begins when a client, like a device running Microsoft Windows or Android (operating system), broadcasts a DHCPDISCOVER message. A DHCP server, which may be software on a Linux distribution or a dedicated appliance from Juniper Networks, responds with a DHCPOFFER containing an available IP address. The client then sends a DHCPREQUEST to accept the offer, and the server finalizes the process with a DHCPACK, committing the IP address lease. This entire exchange uses User Datagram Protocol ports 67 and 68.

Security

The original specification lacked robust security mechanisms, making it vulnerable to attacks like IP address spoofing or rogue servers. In response, RFC 3118 introduced authentication options for DHCP messages. Common threats include a malicious actor deploying a rogue DHCP server to provide false configuration, potentially redirecting traffic through a compromised gateway in an attack similar to a man-in-the-middle attack. To mitigate risks, network administrators often implement security features on network switches from vendors like Aruba Networks, utilizing techniques such as DHCP snooping to filter unauthorized messages.

DHCP options

These are variable-length fields that carry additional configuration parameters beyond the basic IP address and subnet mask. Defined in documents like RFC 2132, options are numbered and provide critical information such as the address of Domain Name System servers, the IP address of a default router, or the name of a boot image for Preboot Execution Environment clients. Option 66, for instance, specifies a Trivial File Transfer Protocol server, while Option 150 is used for more complex Cisco Systems IP Phone deployments. The list of options is maintained by the Internet Assigned Numbers Authority.

DHCPv6

This is the version of the protocol for IPv6 networks, standardized in RFC 8415. While IPv6 supports Stateless Address Autoconfiguration, DHCPv6 is used for stateful address assignment and providing other configuration parameters not available via Router Advertisements. It operates using User Datagram Protocol ports 546 and 547 and can be deployed in networks managed by organizations like Comcast or Deutsche Telekom. DHCPv6 supports options analogous to its IPv4 counterpart, such as providing the addresses of DNS servers, crucial for the functioning of the modern Internet.

Related protocols

Several protocols interact with or complement its functionality. The Bootstrap Protocol was its direct predecessor. For IP address management and tracking, the Internet Protocol Address Management framework is often used. In the context of Internet Service Providers like Verizon, the Point-to-Point Protocol may use it to assign addresses. Furthermore, protocols like the Extensible Authentication Protocol can be integrated for secure network access control in architectures defined by the Institute of Electrical and Electronics Engineers in standards like IEEE 802.1X.

Category:Internet protocols Category:Application layer protocols Category:Internet Standards