IETF Logo Mail Archive

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

Joe Quanaim <jdq@lucent.com> Mon, 23 August 2004 18:21 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 OAA28374; Mon, 23 Aug 2004 14:21:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BzJ6x-0001ZS-RS; Mon, 23 Aug 2004 14:00:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BzIqx-0007X3-Fv for dhcwg@megatron.ietf.org; Mon, 23 Aug 2004 13:43:31 -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 NAA25486 for <dhcwg@ietf.org>; Mon, 23 Aug 2004 13:43:25 -0400 (EDT)
Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzIrD-0001bW-47 for dhcwg@ietf.org; Mon, 23 Aug 2004 13:43:48 -0400
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id i7NHgfY1022199; Mon, 23 Aug 2004 12:42:42 -0500 (CDT)
Received: from kraken.mh.lucent.com by homail.ho.lucent.com (8.11.7+Sun/EMS-1.5 sol2) id i7NHgfU06769; Mon, 23 Aug 2004 13:42:41 -0400 (EDT)
From: Joe Quanaim <jdq@lucent.com>
To: Stig Venaas <Stig.Venaas@uninett.no>
Subject: Re: [dhcwg] behavior on lifetime expiration (Re: comments on draft-ietf-dhc-lifetime-01.txt)
Date: Mon, 23 Aug 2004 13:42:39 -0400
User-Agent: KMail/1.5.4
References: <y7vhdrl56ol.wl@ocean.jinmei.org> <200408231045.02340.jdq@lucent.com> <20040823151021.GE1105@sverresborg.uninett.no>
In-Reply-To: <20040823151021.GE1105@sverresborg.uninett.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200408231342.39913.jdq@lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org, tjc@ecs.soton.ac.uk
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jdq@lucent.com
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

Stig Venaas wrote:
> I feel strongly that it should only tell the client when it should
> try to update the info (like t1 I guess). But the client should
> keep the info while it keeps trying to update the info. As I
> understand the DHCP spec, it will keep retransmitting the
> Information-Request indefinitely if necessary, which means that
> the config data also might be kept indefinitely.

I agree with this sentiment.  If a client must remove configured information 
when the lifetime option expires, the client is punished.  A client that did 
not implement the lifetime option could continue to use configured 
information.  The option expiration is not necessarily indicative of a change 
in the network.

It sounds like all that is needed is a new name for this option.

Joe.


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

v2.23.0 | Report a Bug | By Email