<div><Resending the mail, as there is no response><br>Can someone please throw light on ISC's implementation.</div>
<div><br>regards</div>
<div>Ravi</div>
<div class="gmail_quote">On Thu, May 20, 2010 at 8:39 PM, ravi kumar <span dir="ltr"><<a href="mailto:ravikumar.lrk@gmail.com">ravikumar.lrk@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>I would like to know the behavior of Dhcp Failover implementation in INIT-REBOOT scenario. Is the following highlighted part taken care of in Failover implementation ? </div>
<div>Also, would like to know if anyone has come across any Client, that behaves in below specified manner : Request is sent during INIT-REBOOT, though Client doesnot have valid lease.</div>
<div> </div>
<div><Copy-Paste from Dhcp Failover draft [<a href="http://tools.ietf.org/html/draft-ietf-dhc-failover-12.txt" target="_blank"><strong>draft-ietf-dhc-failover-12.txt</strong></a>]></div>
<div> </div>
<div>One troublesome issue is that of the DHCP client responsibility when<br> sending in DHCPREQUEST/INIT-REBOOT requests. While the original DHCP<br> RFC was written to require a DHCP client to have time left to run on<br>
the lease for an IP address if the client is sending an INIT-REBOOT<br> request, it was sufficiently unclear that some client vendors didn't<br> realize this until recently. Since the INIT-REBOOT request was sent<br>
with the IP address in the dhcp-requested-address option and not in<br> the ciaddr (for perfectly good reasons), the similarity to the RENEW<br> and REBINDING case was lost on many people.<br><br> <font style="BACKGROUND-COLOR: #ffff00"> At present, the failover protocol does not assume that a client send-<br>
ing in an INIT-REBOOT request necessarily has a valid lease on the IP<br> address appearing in the dhcp-requested-address option in the INIT-<br> REBOOT request.<br></font><br> The implications of this are as follows: Assume that there is a DHCP<br>
client that gets a lease from one server while that server is unable<br> to communicate with its failover partner. Then, assume that after<br> that client reboots it is able only to communicate with the other<br> failover server. If the failover servers have not been able to com-<br>
municate with each other during this process, then the DHCP client<br> will get a new IP address instead of being able to continue to use<br> its existing IP address. This will affect no applications on the DHCP<br>
client, since it is rebooting. However, it will use up an additional<br> IP address in this marginal case.<br></div>
<div>regards</div>
<div>Ravi</div></blockquote></div><br>