DHCP Lease Renewal Process

The DHCP client renews its IP configuration data prior to the expiration of the lease time. If the lease period expires and the DHCP client has not yet renewed its IP configuration
data, then the DHCP client loses the IP configuration data and begins the DHCP lease generation process again.
The lease renewal process is the result of the lease period value. The lease period value ensures that DHCP maintains the IP address information and that clients regularly update
or renew their IP address configuration data. Having DHCP maintain this information means that you can manage IP addressing from the DHCP server.
The client must renew its IP configuration data before the lease period expires. At specific intervals, a DHCP client attempts to renew its lease to ensure that it has up-to-date
configuration information.
At any time during the lease period, the DHCP client can send a DHCPRELEASE packet to the DHCP server to release the IP address configuration data and to cancel any remaining
lease.
A DHCP client automatically attempts to renew its lease as soon as 50 percent of the lease duration has expired. The DHCP client will also attempt to renew its IP address lease each
time that the computer restarts. To attempt a lease renewal, the DHCP client sends a DHCPREQUEST packet directly to the DHCP server from which the client obtained the lease.
If the DHCP server is available, it renews the lease and sends the client a DHCPACK packet with the new lease duration and any updated configuration parameters. The client
updates its configuration when it receives the acknowledgment. If the DHCP server is unavailable, the client continues to use its current configuration parameters.

If the DHCP client fails to renew its lease the first time, then the DHCP client broadcasts a DHCPDISCOVER packet to update its address lease when 87.5 percent of the current
lease duration expires. At this stage, the DHCP client accepts a lease that any DHCP server has issued.

Allocation of network addresses

DHCP supports three mechanisms for IP address allocation. In "automatic allocation", DHCP assigns a permanent IP address to a client. In "dynamic allocation", DHCP assigns
an IP address to a client for a limited period of time (or until the client explicitly relinquishes the address). In "manual allocation", a client's IP address is assigned by the
network administrator, and DHCP is used simply to convey the assigned address to the client. A particular network will use one or more of these mechanisms, depending on
the policies of the network administrator.
Dynamic allocation is the only one of the three mechanisms that allows automatic reuse of an address that is no longer needed by the client to which it was assigned. Thus,
dynamic allocation is particularly useful for assigning an address to a client that will be connected to the network only temporarily or for sharing a limited pool of IP addresses
among a group of clients that do not need permanent IPaddresses. Dynamic allocation may also be a good choice for assigning an IP address to a new client being permanently
connected to a network where IP addresses are sufficiently scarce that it is important to reclaim them when old clients are retired.
The basic mechanism for the dynamic allocation of network addresses is simple: a client requests the use of an address for some period of time (which is called a lease). The
allocation mechanism guarantees not to reallocate that address within the requested time and attempts to return the same network address each time the client requests an
address.

Manual allocation allows DHCP to be used to eliminate the error-prone process of manually configuring hosts with IP addresses in environments where (for whatever reasons) it
is desirable to manage IPaddress assignment outside of the DHCP mechanisms.
Automatic allocation allows DHCP to give a host a permanent network address but still do it automatically, without human interference.
As a consistency check, the allocating server should test the reused address before allocating the address, e.g., with an ICMP echo request, and the client should test the newly
received address, e.g., with ARP.

Louie dave Mortilla,Nicholas Punzalan,Pol

9/18/2018
Angelo Ramos