IETF Logo Mail Archive

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

Ted Lemon <mellon@nominum.com> Tue, 03 August 2004 06:00 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 CAA04499; Tue, 3 Aug 2004 02:00:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrsFd-0006DA-7F; Tue, 03 Aug 2004 01:54:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Brs5o-0002C5-BY for dhcwg@megatron.ietf.org; Tue, 03 Aug 2004 01:44:08 -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 BAA03432 for <dhcwg@ietf.org>; Tue, 3 Aug 2004 01:44:07 -0400 (EDT)
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Brs8n-0003qX-R5 for dhcwg@ietf.org; Tue, 03 Aug 2004 01:47:15 -0400
Received: from [66.93.162.248] (0127bhost249.starwoodbroadband.com [12.105.247.249]) by toccata.fugue.com (Postfix) with ESMTP id A10C91B29C3; Tue, 3 Aug 2004 00:42:46 -0500 (CDT)
In-Reply-To: <20040803033357.GA20506@sverresborg.uninett.no>
References: <y7vhdrl56ol.wl@ocean.jinmei.org> <20040803033357.GA20506@sverresborg.uninett.no>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <FED44CCF-E50F-11D8-982E-000A95D9C74C@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@nominum.com>
Subject: Re: [dhcwg] Re: comments on draft-ietf-dhc-lifetime-01.txt
Date: Mon, 02 Aug 2004 22:43:07 -0700
To: Stig Venaas <Stig.Venaas@uninett.no>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
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
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

I think that we should specify what a client should do when it isn't 
given a lifetime option, rather than leaving it to the implementor.   I 
would pick a number - say an hour - and recommend that as a default 
value when no lifetime has been given.   I would require that this be 
configurable on the client.   We should make sure that there isn't some 
corner case where a network administrator that wants a really long 
lifetime doesn't get hosed by the default value, but I don't think it's 
okay to just leave it unstated.

Sorry for not saying this sooner - I was dithering over whether to make 
a point of it, and when Jinmei Tatuya stepped in with his observations, 
that gave me a good excuse to kibbitz.   :')


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

v2.30.2 | Report a Bug | By Email | System Status