Re: [dhcwg] Attempt at text for draft-ietf-dhc-lifetime-02

Stig Venaas <Stig.Venaas@uninett.no> Tue, 31 August 2004 12:26 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 IAA12220; Tue, 31 Aug 2004 08:26:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C27ee-0004Dw-CU; Tue, 31 Aug 2004 08:22:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C27Xp-0003Na-W1 for dhcwg@megatron.ietf.org; Tue, 31 Aug 2004 08:15:26 -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 IAA11742 for <dhcwg@ietf.org>; Tue, 31 Aug 2004 08:15:25 -0400 (EDT)
Received: from tyholt.uninett.no ([158.38.60.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C27Zn-0001is-EE for dhcwg@ietf.org; Tue, 31 Aug 2004 08:17:28 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b]) by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i7VCE3OK022210; Tue, 31 Aug 2004 14:14:03 +0200
Received: (from venaas@localhost) by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i7VCE14Z012362; Tue, 31 Aug 2004 14:14:01 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Tue, 31 Aug 2004 14:14:01 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Joe Quanaim <jdq@lucent.com>
Subject: Re: [dhcwg] Attempt at text for draft-ietf-dhc-lifetime-02
Message-ID: <20040831121401.GN2203@sverresborg.uninett.no>
References: <20040825151559.GJ5677@sverresborg.uninett.no> <200408270854.10485.jdq@lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200408270854.10485.jdq@lucent.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: dhcwg@ietf.org
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

On Fri, Aug 27, 2004 at 08:54:09AM -0400, Joe Quanaim wrote:
> 
> Stig Venaas wrote:
> > |  A client MUST also use the default refresh time IRT_DEFAULT if it
> > |  receives the option with value less than 600.
> >
> > Do you agree with a minimum like this? It should make it harder to
> > do bad things, and I don't see a use for <10 minutes. If <600,
> > would you rather use 600 than IRT_DEFAULT?
> 
> I think a minimum is a good idea, but it probably should not be reset to 24 
> hours.  That's probably not what an admin intended by setting the value that 
> low.

I agree sort of. For the protocol, I like the idea of totally ignoring
option with invalid value though, which means using the default. The
server implementation should perhaps give the administrator a warning,
or send 600 rather than the configured value.

We could also do what you suggest though. Other opinions?

> Also, are 0 or 0xffffffff a special case like elsewhere in dhcpv6?  I am not 
> sure it's necessary; I am just bringing up the point.

I think it infinity could potentially be useful, but 0xffffffff is in
practice infinity anyway.

If we leave it out now, we can still add it later if we want.

Stig

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