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

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Sat, 04 September 2004 03:45 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 XAA05974; Fri, 3 Sep 2004 23:45:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3RJd-000824-BS; Fri, 03 Sep 2004 23:34:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3RJ8-0007qp-S8 for dhcwg@megatron.ietf.org; Fri, 03 Sep 2004 23:33:43 -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 XAA05417 for <dhcwg@ietf.org>; Fri, 3 Sep 2004 23:33:39 -0400 (EDT)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3RLq-0007rs-UG for dhcwg@ietf.org; Fri, 03 Sep 2004 23:36:32 -0400
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:545c:249b:d371:bb2c]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 4CEAA15263; Sat, 4 Sep 2004 12:33:35 +0900 (JST)
Date: Sat, 04 Sep 2004 12:33:37 +0900
Message-ID: <y7vzn461ze6.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: Stig Venaas <Stig.Venaas@uninett.no>
Subject: Re: [dhcwg] behavior on lifetime expiration (Re: comments on draft-ietf-dhc-lifetime-01.txt)
In-Reply-To: <20040903083450.GA22060@sverresborg.uninett.no>
References: <y7vhdrl56ol.wl@ocean.jinmei.org> <20040803033357.GA20506@sverresborg.uninett.no> <y7veklyqkbx.wl@ocean.jinmei.org> <A9C62C40-F510-11D8-AE27-000A95D9C74C@nominum.com> <y7vfz6cenvy.wl@ocean.jinmei.org> <6C20AA0D-F5DF-11D8-8541-000A95D9C74C@nominum.com> <y7vy8jv70uo.wl@ocean.jinmei.org> <20040901123029.GI15000@sverresborg.uninett.no> <y7vy8ju59e7.wl@ocean.jinmei.org> <20040903083450.GA22060@sverresborg.uninett.no>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: dhcwg@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>
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, 3 Sep 2004 10:34:50 +0200, 
>>>>> Stig Venaas <Stig.Venaas@uninett.no> said:

> So how about something like this:

> When a client receives a Reply to an Information-Request that
> contains configuration information (i.e., does not contain a
> Status Code option), it SHOULD install that new configuration
> information after removing any previously received configuration
> information.  There may be reasons not to always do this.  One
> example might be when client has indication that it has moved to
> a new link.  How a client copes with movement is outside the scope
> of this document.

> I'm not not sure if it should be "SHOULD" or "should" there. At
> least I don't see this as part of the protocol. In my opinion
> the idea is just to give a general recommendation or some guidance
> to implementors.

The proposed text basically looks fine.  But I'd be a bit more
specific that the above description means if the new configuration
information does not have any update on a particular instance of the
old information (e.g., DNS server list) the client will simply remove
the old information.

As for "SHOULD" vs "should", I don't have a strong opinion.  If you
prefer "should", please just go for it.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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