I was referring to RFC 3203 (defines DHCPFORCERENEW message), which is the
trigger that signals a host (through its DHCP client) to send a DHCPREQUEST
message to the server. As far as I know, this feature is not widely
implemented in clients or servers.
Once the client sends the DHCPREQUEST message, all the required DHCP
functions are part of RFCC 2131 and are widely implemented:
* Host sends DHCPREQUEST, as though the host is requesting a lease extension
* Server responds with DHCPNAK
* Host removes current IP address from interface
* Host sends DHCPDISCOVER
* Server responds with DHCPOFFER containing new IP address
* Host sends DHCPREQUEST for new IP address
* Server responds with DHCPACK, completing assignment of new IP address
I don't imply that "not widely implemented" is a reason not to include
DHCPFORCERENEW in the PANA spec (if that is what you had intended).
- Ralph
On 10/10/06 5:40 AM, "Alper Yegin" <alper.yegin at yegin.org> wrote:
Ralph,
DHCPv4 reconfiguration is, as far as I know, not implemented anywhere, so
a
requirement for DHCPv4 reconfiguration is another inter-protocol
entanglement.
Can you clarify what part of re-configuration process you are referring to
as not implemented? Is it the host's ability to request another IP address,
DHCP server's ability to hand out another IP address, or something else?
Alper
