RE: [Dhcwg] Re: Change to 'seconds' field in DHCP message header

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Mon, 27 August 2001 13:47 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18257; Mon, 27 Aug 2001 09:47:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20190; Mon, 27 Aug 2001 09:46:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20161 for <dhcwg@ns.ietf.org>; Mon, 27 Aug 2001 09:46:42 -0400 (EDT)
Received: from imr1.ericy.com (imr1.ericy.com [208.237.135.240]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18188 for <dhcwg@ietf.org>; Mon, 27 Aug 2001 09:45:22 -0400 (EDT)
Received: from mr6.exu.ericsson.se (mr6u3.ericy.com [208.237.135.123]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id f7RDkgp18047 for <dhcwg@ietf.org>; Mon, 27 Aug 2001 08:46:42 -0500 (CDT)
Received: from eamrcnt747.exu.ericsson.se (eamrcnt747.exu.ericsson.se [138.85.133.37]) by mr6.exu.ericsson.se (8.11.3/8.11.3) with SMTP id f7RDkga20407 for <dhcwg@ietf.org>; Mon, 27 Aug 2001 08:46:42 -0500 (CDT)
Received: FROM eamrcnt760.exu.ericsson.se BY eamrcnt747.exu.ericsson.se ; Mon Aug 27 08:46:41 2001 -0500
Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <P4MPZMF0>; Mon, 27 Aug 2001 08:46:41 -0500
Message-ID: <66F66129A77AD411B76200508B65AC697B349C@eambunt705.ena-east.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: dhcwg@ietf.org
Subject: RE: [Dhcwg] Re: Change to 'seconds' field in DHCP message header
Date: Mon, 27 Aug 2001 08:46:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C12EFE.B3217610"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

I supported the change to 1/10th of a second (would even support a change to 1 second as mentioned previously).

I agree with Ralph. I don't see the need to waste the additional bytes.

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Monday, August 27, 2001 9:12 AM
To: dhcwg@ietf.org
Subject: [Dhcwg] Re: Change to 'seconds' field in DHCP message header


(Please note that this message has been sent to the new dhc WG mailing list, dhcwg@ietf.org.  The current mailing lists, dhcp-v4@bucknell.edu and dhcp-v6@bucknell.edu, will be taken off line tomorrow, Aug 28, around 4PM.  I will arrange for e-mail to the old lists to be forwarded to dhcwg@ietf.org for a couple of months.  I will also save the archives from the old lists and make them available on line as soon as possible. - RD)

Another alternative for greater range would be to define the units of the data value to be tenths of a second.  My intuition is that tenths of a second should be sufficiently precise...

Can anyone give us the benefit of experience with the 'secs' field in DHCPv4?  There hasn't been any interest in defining a new option with greater range or precision than the current 0-255 seconds measured in seconds.  Has the range or precision in DHCPv4 been inadequate in any specific instance?

- Ralph

At 10:44 PM 8/26/2001 -0400, you wrote:

>> I think 16-bits is enough (with the counter maxing out). If an attempt goes
>> on that long, no server is probably available and the relays (or servers)
>> will likely long have taken alternative actions (which probably failed as
>> well). So, I see little need to make this more than 16-bits.
>
>That's a pretty set of suppositions, but you may well be wrong.   Why
>not make sure that it works if you are?
>
>                               _MelloN_


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