Re: Choosing length of lease
Mike Carney - SunSoft Internet Engineering <mwc@atlantic.east.sun.com> Sat, 09 November 1996 17:03 UTC
Received: from cnri by ietf.org id aa01554; 9 Nov 96 12:03 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa10930;
9 Nov 96 12:03 EST
Received: from reef.bucknell.edu by mail.bucknell.edu;
(5.65v3.2/1.1.8.2/17Jul96-0109PM)
id AA26581; Sat, 9 Nov 1996 11:56:41 -0500
Date: Sat, 9 Nov 1996 11:56:41 -0500
Message-Id: <Roam 0.9.4.847557492.27966.mwc@atlantic.east>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Mike Carney - SunSoft Internet Engineering <mwc@atlantic.east.sun.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Choosing length of lease
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Hi John, Typically, we use (and we tell customers) the lease which meets the following criteria: 1) Long enough so that if the underlying hardware, etc upon which the DHCP service runs goes on the blink, the hardware, etc will be fixed before leases start expiring. 2) Given #1, the shortest possible lease which meets this requirement, so that any changes to DHCP parameters are picked up on a timely basis (such as renumbering networks, new services) and expired IP addresses are recycled rapidly (they are in short supply). The typical answer runs from 6hours (Sun's internal) to 2 days (for a certain customer). Both numbers arrived at using #1 and #2. Mike
- Choosing length of lease John M. Wobus
- Re: Choosing length of lease Mike Carney - SunSoft Internet Engineering
- Re: Choosing length of lease Michael J. Lewis
- Re: Choosing length of lease Mark Sirota
- Re: Choosing length of lease Michael J. Lewis
- RE: Choosing length of lease Hibbs, R Barr (rbhibbs)