Questions regarding infinite leases and T1/T2 timers

"Michael J. Lewis" <hosmjl@chevron.com> Tue, 12 March 1996 20:11 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18902; 12 Mar 96 15:11 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18898; 12 Mar 96 15:11 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa11460; 12 Mar 96 15:11 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu; (5.65v3.0/1.1.8.2/29Aug94-0956AM) id AA02465; Tue, 12 Mar 1996 14:50:32 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4) id AA12042; Tue, 12 Mar 1996 14:35:44 -0500
Received: from portal.chevron.com by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA04948; Tue, 12 Mar 1996 14:35:38 -0500
Received: by portal.chevron.com id AA12909 (InterLock SMTP Gateway 3.0 for dhcp-v4@bucknell.edu); Tue, 12 Mar 1996 11:35:25 -0800
Received: by portal.chevron.com (Protected-side Proxy Mail Agent-1); Tue, 12 Mar 1996 11:35:25 -0800
Message-Id: <3145D282.7D7B@chevron.com>
Date: Tue, 12 Mar 1996 13:37:38 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Michael J. Lewis" <hosmjl@chevron.com>
Organization: Chevron
X-Mailer: Mozilla 2.0 (Win95; I)
Mime-Version: 1.0
To: dhcp-v4@bucknell.edu
Subject: Questions regarding infinite leases and T1/T2 timers
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I've just finished looking at a vendor DHCP server that for a 
manual entry (map an IP address to a specific MAC address), returns an 
infinite lease and values for T1 and T2 that map to the appropriate 
values for the normal lease on the subnet.  My client sees the infinite 
lease and proceeds to ignore the T1/T2 values, thereby failing to renew 
the lease and pick up any changed configuration parameters.

This unexpected scenario has raised two questions regarding the DHCP 
protocol specifications.

	1.  Should the server provide T1/T2 times on an infinite lease?
		(Or is it possible to have an infinite lease that 
		requires a client to go through the renewal process?)
	2.  If such options are included in a REQUEST packet, can the
		client ignore them?

I looked through the draft DHCP specifications but there is very little 
regarding infinite leases and whether the timers apply.  It would seem 
that one or both of the implementations are in error here but I did not 
want to call either vendor until I had some consensus as to what meets 
the specifications.

Thanks for your help.