Re: [dhcwg] Minutes from meeting in SLC, 12/10

Ted Lemon <mellon@nominum.com> Tue, 08 January 2002 03:49 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 WAA06126 for <dhcwg-archive@odin.ietf.org>; Mon, 7 Jan 2002 22:49:23 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id WAA03607 for dhcwg-archive@odin.ietf.org; Mon, 7 Jan 2002 22:49:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA03538; Mon, 7 Jan 2002 22:43:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA03517 for <dhcwg@ns.ietf.org>; Mon, 7 Jan 2002 22:43:51 -0500 (EST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06077 for <dhcwg@ietf.org>; Mon, 7 Jan 2002 22:43:47 -0500 (EST)
Received: from green.bisbee.fugue.com (tnt14b-67.focal-chi.corecomm.net [216.214.204.67]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id g083fOS12248; Mon, 7 Jan 2002 19:41:24 -0800 (PST)
Received: from dechen (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id g083iDV00828; Mon, 7 Jan 2002 22:44:13 -0500 (EST)
Date: Mon, 07 Jan 2002 22:44:12 -0500
Subject: Re: [dhcwg] Minutes from meeting in SLC, 12/10
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v475)
Cc: dhcwg@ietf.org, Steve Gonczi <steve@relicore.com>, 'Thomas Narten' <narten@us.ibm.com>
To: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
From: Ted Lemon <mellon@nominum.com>
In-Reply-To: <66F66129A77AD411B76200508B65AC69B4CD28@EAMBUNT705>
Message-Id: <FB16DE20-03E9-11D6-912A-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.475)
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

My only recollection as to why there might have been a reason to make this 
optional was that it was unknown at the time whether all clients actually 
put real values in the secs field of the DHCP packet.   I think it's fine 
to make support for this in agents that implement load balancing mandatory 
anyway, though - all of the major clients of which I am aware do correctly 
support the secs field.


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