Subject: [dhcwg] Meaning of NAK in RENEWING and REBINDING state?

From: "Kevin A. Noll" <[email-masked]>
Date: Sun, 04 Jan 2004 21:34:05 -0500

Reading through my last question to the WG I had to ask another question...

What exactly is the meaning of a NAK sent to a client that is attempting
to renew or rebind?

Based on the state machine diagram, it would seem that a NAK in response
to a renew or rebind would mean that the client's lease is being revoked
prior to the lease period.

Is this correct?

If it is, then what is the proper way for a server to respond to a renew
or rebind if it wants to allow the client to use its current lease, but
not extend the lease?

Section 4.4.5 of 2131 seems to say that the server should return T1 and T2
in an ACK based upon how long it wishes the client to continue using the
lease. It seems, though, that using this method it would be possible to get
into a situation where T1 and T2 are adjusted such that the client must
attempt renewal at smaller and smaller intervals up until the lease expires.

e.g. if the original lease is 60sec...
 - the client attempts renewal at 30secs
 - the server doesn't wish to extend the lease, but also doesn't want to
revoke
the lease, so it returns T1=15secs, T2=7secs
 - the client attempts renewal again at 15 secs
 - server sets T1=7secs, T2=4secs
 - client renews at 7 secs
 - server sets T1=3secs, T2=1sec
 - client renews at 3 secs
 - server sets T1=1sec, T2=0sec
 - client renews at 1sec
 - lease expires

Is this correct interpretation or did I miss a clarification in another
section?

--kan--
--
Kevin A. Noll, KD4WOZ
CCIE 10948, CCDP
Perfect Order, Inc.
[email-masked]
717-796-1936

_______________________________________________
dhcwg mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/dhcwg