Re: [Dhcwg] Re: Change to 'seconds' field in DHCP message header
Ted Lemon <mellon@nominum.com> Tue, 28 August 2001 02:56 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 WAA09227; Mon, 27 Aug 2001 22:56:06 -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 WAA17875; Mon, 27 Aug 2001 22:55:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA17848 for <dhcwg@ns.ietf.org>; Mon, 27 Aug 2001 22:55:11 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09167 for <dhcwg@ietf.org>; Mon, 27 Aug 2001 22:53:50 -0400 (EDT)
Received: from grosse.bisbee.fugue.com (user-2inic6l.dialup.mindspring.com [165.121.48.213]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id f7S2nLf10452; Mon, 27 Aug 2001 19:49:22 -0700 (PDT)
Received: from grosse.bisbee.fugue.com (localhost [127.0.0.1]) by grosse.bisbee.fugue.com (8.11.3/8.6.11) with ESMTP id f7S2smT00572; Mon, 27 Aug 2001 22:54:48 -0400 (EDT)
Message-Id: <200108280254.f7S2smT00572@grosse.bisbee.fugue.com>
To: Ralph Droms <rdroms@cisco.com>
cc: dhcwg@ietf.org
Subject: Re: [Dhcwg] Re: Change to 'seconds' field in DHCP message header
In-Reply-To: Message from Ralph Droms <rdroms@cisco.com> of "Mon, 27 Aug 2001 22:29:05 EDT." <4.3.2.7.2.20010827222005.038fa050@funnel.cisco.com>
Date: Mon, 27 Aug 2001 22:54:48 -0400
From: Ted Lemon <mellon@nominum.com>
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 will not respond to any further questions about this. Promises, promises. :'} I'm sorry for all the mistakes in the previous couple of messages - I'm working from what I remember seeing a while back, when we had decided to call the message milliseconds and represent it in milliseconds, so I apparently didn't read your writeup very carefully. :'( > Are you referring to the granularity of the 'secs' field? How > would you make it more fine-grained if the units for the fields > are defined as "seconds" in the spec? I'm referring to timeout computations. And if timeout computations are more fine-grained, then it would make sense for the secs field to be more fine-grained as well. Otherwise the implementor has to answer the question "if the difference between the last transmission time and the current transmission time is less than one half the granularity, do I specify an interval of zero or one?" I would rather not force the implementor to make this decision, because s/he will get it wrong, probably even if it is carefully specified in the draft. I don't know many junior geeks who have taken courses in numerical methods. _MelloN_ _______________________________________________ dhcwg mailing list dhcwg@ietf.org http://www1.ietf.org/mailman/listinfo/dhcwg
- [Dhcwg] Re: Change to 'seconds' field in DHCP mes… Ralph Droms
- RE: [Dhcwg] Re: Change to 'seconds' field in DHCP… Bernie Volz (EUD)
- [dhcwg] RE: Change to 'seconds' field in DHCP mes… Ralph Droms
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ted Lemon
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ralph Droms
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ted Lemon
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ted Lemon
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ralph Droms
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ralph Droms
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ted Lemon
- [dhcwg] Changes to remove "client-link-local-addr… Ralph Droms
- Re: [dhcwg] Changes to remove "client-link-local-… Ted Lemon
- Re: [dhcwg] Changes to remove "client-link-local-… Ralph Droms
- Re: [dhcwg] Changes to remove "client-link-local-… Ted Lemon
- Re: Re[2]: [dhcwg] Lease database storage in DHCP… Thomas Narten
- Re: [dhcwg] Assigning DHCPv6 option codes Thomas Narten
- Re: [dhcwg] dhcpv6-24: randomization delay before… Thomas Narten
- Re: [dhcwg] dhcpv6-24: randomization delay before… Thomas Narten
- Re: [dhcwg] dhcpv6-24: movement detection and Con… Thomas Narten
- Re: [dhcwg] dhcpv6-24: use of anycast Thomas Narten
- Re: [dhcwg] dhcpv6-24: use of anycast Thomas Narten
- Re: [dhcwg] dhcpv6-24: vendor-specific issues Thomas Narten
- Re: [dhcwg] status of draft-ietf-dhc-agent-subnet… Thomas Narten
- Re: [dhcwg] status of draft-ietf-dhc-agent-subnet… Thomas Narten
- Re: [dhcwg] DHC WG charter Thomas Narten
- Re: [dhcwg] DHC WG charter Thomas Narten
- RE: [dhcwg] DHC WG charter Ralph Droms
- Re: [dhcwg] DHC WG charter Thomas Narten
- Re: [dhcwg] DHC WG charter Ralph Droms
- Re: [dhcwg] Agenda items for IETF-59, Seoul Naiming Shen
- Re: [dhcwg] *DRAFT* minutes from WG meeting in Se… Naiming Shen
- Re: [dhcwg] dhc wg last call on "DHCP Relay Agent… Thomas Narten