Re: [dhcwg] behavior on lifetime expiration (Re: comments ondraft-ietf-dhc-lifetime-01.txt)

Ted Lemon <mellon@fugue.com> Fri, 27 August 2004 18:45 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24051; Fri, 27 Aug 2004 14:45:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C0lf2-0000SK-Ov; Fri, 27 Aug 2004 14:41:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C0lWm-0006YE-7B for dhcwg@megatron.ietf.org; Fri, 27 Aug 2004 14:32:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22073 for <dhcwg@ietf.org>; Fri, 27 Aug 2004 14:32:42 -0400 (EDT)
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0lXx-0007no-5m for dhcwg@ietf.org; Fri, 27 Aug 2004 14:33:58 -0400
Received: from [10.222.34.118] (m815f36d0.tmodns.net [208.54.95.129]) by toccata.fugue.com (Postfix) with ESMTP id 932E51B2003 for <dhcwg@ietf.org>; Fri, 27 Aug 2004 13:31:49 -0500 (CDT)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <200408270928.58762.jdq@lucent.com>
References: <20040827062321.GA15052@sverresborg.uninett.no> <29651.1093585502@munnari.OZ.AU> <77.1093589569@munnari.OZ.AU> <200408270928.58762.jdq@lucent.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <7B6727F5-F857-11D8-A7B9-000A95D9C74C@fugue.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] behavior on lifetime expiration (Re: comments ondraft-ietf-dhc-lifetime-01.txt)
Date: Fri, 27 Aug 2004 13:32:42 -0500
To: dhcwg@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: 7bit

On Aug 27, 2004, at 8:29 AM, Joe Quanaim wrote:
> For the example involving dns and this option, I read the draft as 
> such: when
> the option expires, don't dismiss the configured dns data.  Request new
> information.  When new information is received, replace the existing 
> data
> with the newly obtained.  This prevents the client from being left 
> without
> dns while making an attempt to be current.  Also, if a server returns 
> an
> empty set of dns servers, that is what the client should use.  It 
> doesn't
> make much sense, but misconfigured dhcp servers aren't something a 
> client
> should be programmed to handle.

I agree that this is what the client should do.   If this isn't clear 
to kre from reading it, then perhaps we need to make it clearer, but I 
certainly agree that this is the behavior that we want to specify.


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