RE: [dhcwg] Computation of T1, T2, and lease expiration time

"Bernie Volz" <volz@cisco.com> Mon, 05 April 2004 22:09 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15176 for <dhcwg-archive@odin.ietf.org>; Mon, 5 Apr 2004 18:09:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAcHB-0000fU-HZ for dhcwg-archive@odin.ietf.org; Mon, 05 Apr 2004 18:09:05 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i35M95Cj002543 for dhcwg-archive@odin.ietf.org; Mon, 5 Apr 2004 18:09:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAcHB-0000ed-7V for dhcwg-web-archive@optimus.ietf.org; Mon, 05 Apr 2004 18:09:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15000 for <dhcwg-web-archive@ietf.org>; Mon, 5 Apr 2004 18:09:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BAcH8-0003vh-00 for dhcwg-web-archive@ietf.org; Mon, 05 Apr 2004 18:09:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BAc0O-0001FY-00 for dhcwg-web-archive@ietf.org; Mon, 05 Apr 2004 17:51:45 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BAbWf-0005p5-00 for dhcwg-web-archive@ietf.org; Mon, 05 Apr 2004 17:21:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAbWf-0000Li-BA; Mon, 05 Apr 2004 17:21:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAbWB-0000A8-Ih for dhcwg@optimus.ietf.org; Mon, 05 Apr 2004 17:20:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10152 for <dhcwg@ietf.org>; Mon, 5 Apr 2004 17:20:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BAbW9-0005mj-00 for dhcwg@ietf.org; Mon, 05 Apr 2004 17:20:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BAbEI-0003lX-00 for dhcwg@ietf.org; Mon, 05 Apr 2004 17:02:03 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BAb26-0001Ln-00 for dhcwg@ietf.org; Mon, 05 Apr 2004 16:49:26 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 05 Apr 2004 12:57:34 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i35KmrUe029445; Mon, 5 Apr 2004 13:48:54 -0700 (PDT)
Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHJ39835; Mon, 5 Apr 2004 16:48:52 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: "'Kevin A. Noll'" <kevin.noll@perfectorder.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Computation of T1, T2, and lease expiration time
Date: Mon, 05 Apr 2004 16:48:51 -0400
Organization: Cisco
Message-ID: <004501c41b4f$67260dd0$d0412ca1@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <PPEKLDPHBHOIHMHKFGLLOELECPAA.kevin.noll@perfectorder.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I think the text you refer to is:

   The client records the lease expiration time as the sum of
   the time at which the original request was sent and the duration of
   the lease from the DHCPACK message.

And, the question is what does "original request" refer to - the
DISCOVER or REQUEST?

To be completely safe, using the DISCOVER would be best (since that will
result in the shortest lease / T1 / T2 times for the client). But, I
think practially speaking that REQUEST is OK.

But, any client and server need to be prepared for some grace period for
leases as there is no requirement that the client and server have
synchronized clocks and their individual clocks may run fast or slow.

Perhaps this would be item to include in a future revision of
draft-ietf-dhc-implementation-01.txt?

- Bernie

-----Original Message-----
From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On Behalf Of
Kevin A. Noll
Sent: Monday, April 05, 2004 3:01 PM
To: dhcwg@ietf.org
Subject: [dhcwg] Computation of T1, T2, and lease expiration time



Paragraph 2 of Section 4.4.1 of RFC2131 implies that T1, 
T2, and the lease expiration time are all computed relative 
to the time that the client sends the DHCPDISCOVER.

Is this correct, or should these values be computed relative 
to the time that the client acquires the lease (i.e. when it receives
the DHCPACK)?

In a perfect world, the former would make sense because the time to get
from DISCOVER to ACK should be just a couple of 
seconds at most. 

In a not so perfect world, the latter would make sense. For example, if
the network or DHCP server is not performing very well, it may take many
seconds and several retries to actually get from DISCOVER to ACK. If
this happens and the DISCOVER time 
is the reference, then there could be a considerable discrepency 
between the client's and server's notion of when the lease 
should expire.

Am I correct, or did I miss another section of the document that
clarifies this?

--kan--
--
Kevin A. Noll, KD4WOZ
CCIE 10948, CCDP
Perfect Order, Inc.		
Kevin.Noll@perfectorder.com
717-796-1936


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg