Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt

Joe Quanaim <jdq@lucent.com> Thu, 12 August 2004 14:38 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 KAA05873; Thu, 12 Aug 2004 10:38: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 1BvGbs-0000Ny-61; Thu, 12 Aug 2004 10:31:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BvGYQ-00085L-86 for dhcwg@megatron.ietf.org; Thu, 12 Aug 2004 10:27:42 -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 KAA05231 for <dhcwg@ietf.org>; Thu, 12 Aug 2004 10:27:40 -0400 (EDT)
Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvGdN-0004va-Cz for dhcwg@ietf.org; Thu, 12 Aug 2004 10:32:50 -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 i7CEOLLG006713; Thu, 12 Aug 2004 09:24:21 -0500 (CDT)
Received: from kraken.mh.lucent.com by homail.ho.lucent.com (8.11.7+Sun/EMS-1.5 sol2) id i7CEOKx03603; Thu, 12 Aug 2004 10:24:20 -0400 (EDT)
From: Joe Quanaim <jdq@lucent.com>
To: Bernie Volz <volz@cisco.com>, 'Stig Venaas' <Stig.Venaas@uninett.no>
Subject: Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt
Date: Thu, 12 Aug 2004 10:18:57 -0400
User-Agent: KMail/1.5.4
References: <000001c48073$af492fa0$d0412ca1@amer.cisco.com>
In-Reply-To: <000001c48073$af492fa0$d0412ca1@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200408121018.57077.jdq@lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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

Bernie Volz wrote:
> I do think you should remove that last paragraph:
>
> >    The lifetime option is mainly intended for Stateless DHCP service as
> >    specified in [RFC 3736].  If the client receives IA Address options
> >    containing lifetimes, the lifetime option should be ignored.  The
> >    client should get updated configuration data from the server when it
> >    renews the addresses.

I would prefer leaving the paragraph.

> It confuses the issue.
>
> Perhaps something like:
>
>   The primary motivation for the lifetime option is for situations where
>   no lifetime (or renewal time) is communicated to the client, such as for
>   Stateless DHCP service as specified in [RFC 3736]. However, it applies
>   to both stateful and stateless DHCP clients and is an upper bound for
>   when a client should initiate renewal of at least its non-address based
>   configuration parameters - a stateful client MAY renew its addresses at
>   the same time and SHOULD always get updated configuration data from the
>   server when it renews any addresses.
>
>   One difference between Stateful and Stateless clients with regards
>   to this option is that a Stateful client that does not receive this
>   option MUST NOT apply the default lifetime.
>

As noted, the motivation of the lifetime option is to ensure stateless clients 
receive current configuration information.  As such, I think keeping it out 
of stateful configuration is the simplest approach.  As we have discussed, 
stateful configuration already has several variables to manipulate client 
behavior.  I do not see much gain in adding another.

Still, it's not that complex a change.  If I am outvoted, so be it.

Joe Quanaim.


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