IETF Logo Mail Archive

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

Stig Venaas <Stig.Venaas@uninett.no> Tue, 24 August 2004 10: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 GAA19908; Tue, 24 Aug 2004 06:00:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BzXi9-0003Q9-80; Tue, 24 Aug 2004 05:35:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BzXW4-0000n5-Mx for dhcwg@megatron.ietf.org; Tue, 24 Aug 2004 05:22:56 -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 FAA17566 for <dhcwg@ietf.org>; Tue, 24 Aug 2004 05:22:49 -0400 (EDT)
Received: from tyholt.uninett.no ([158.38.60.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzXWS-00048H-VA for dhcwg@ietf.org; Tue, 24 Aug 2004 05:23:22 -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 i7O9MA2M018296; Tue, 24 Aug 2004 11:22:10 +0200
Received: (from venaas@localhost) by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i7O9M9eW005707; Tue, 24 Aug 2004 11:22:09 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Tue, 24 Aug 2004 11:22:09 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Joe Quanaim <jdq@lucent.com>
Subject: Re: [dhcwg] behavior on lifetime expiration (Re: comments on draft-ietf-dhc-lifetime-01.txt)
Message-ID: <20040824092209.GA5677@sverresborg.uninett.no>
References: <y7vhdrl56ol.wl@ocean.jinmei.org> <200408231045.02340.jdq@lucent.com> <20040823151021.GE1105@sverresborg.uninett.no> <200408231342.39913.jdq@lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200408231342.39913.jdq@lucent.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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

On Mon, Aug 23, 2004 at 01:42:39PM -0400, Joe Quanaim wrote:
[...]
> It sounds like all that is needed is a new name for this option.

So let's try to find a new name. I think "update time option" is
one possibility. I don't like "update timer option" because this
is only a value to use for the timer, not the timer itself.

Another alternative is "refresh time option" perhaps?

I discussed it with a colleague, and we came up with alternatives
like "suggested refresh/update time option" or "refresh/update
within option". Not so sure about the last one, it tries to make
it clear that you might refresh/update before the specified time.

I think we should keep the name fairly short. We should have a
name that isn't misleading, but people will still have to read the
draft to understand exactly what it is.

Stig

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

v2.23.0 | Report a Bug | By Email