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

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Wed, 11 August 2004 14:22 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 KAA07947; Wed, 11 Aug 2004 10:22:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ButxB-0006qr-HD; Wed, 11 Aug 2004 10:19:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Butq1-0003zE-S7 for dhcwg@megatron.ietf.org; Wed, 11 Aug 2004 10:12:21 -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 KAA06859 for <dhcwg@ietf.org>; Wed, 11 Aug 2004 10:12:19 -0400 (EDT)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Butum-0008NF-6V for dhcwg@ietf.org; Wed, 11 Aug 2004 10:17:17 -0400
Received: from ocean.jinmei.org (unknown [2001:200:0:4819:99b8:98fa:2262:6c66]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 7F87B1525D; Wed, 11 Aug 2004 23:12:17 +0900 (JST)
Date: Wed, 11 Aug 2004 23:12:16 +0900
Message-ID: <y7v4qn9u5kv.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt
In-Reply-To: <000201c4797e$2a5f37e0$46828182@amer.cisco.com>
References: <200408030929.31655.jdq@lucent.com> <000201c4797e$2a5f37e0$46828182@amer.cisco.com>
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: de4f315c9369b71d7dd5909b42224370
Cc: venaas@uninett.no, tjc@ecs.soton.ac.uk, jdq@lucent.com, 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 Tue, 3 Aug 2004 13:20:22 -0400, 
>>>>> "Bernie Volz" <volz@cisco.com> said:

> I too would recommend that this option only be used with stateless
> (Information-Request/Reply). It does not apply to stateful - in stateful,
> even if there are no T1/T2 times (i.e., no IA_NA option), the client will
> need to do something when it no longer has addresses so it will get new
> information from the server.

I tend to agree.  In addition to the above points, I'd like to point
out that in the stateful exchanges the server can initiate update by
Reconfigure - at least in theory.

					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