Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt
JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Tue, 17 August 2004 08:51 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 EAA01609; Tue, 17 Aug 2004 04:51:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwze2-0006E0-VO; Tue, 17 Aug 2004 04:48:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwzal-0005NI-J4 for dhcwg@megatron.ietf.org; Tue, 17 Aug 2004 04:45:16 -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 EAA01320 for <dhcwg@ietf.org>; Tue, 17 Aug 2004 04:45:13 -0400 (EDT)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bwzgi-0007gq-Jv for dhcwg@ietf.org; Tue, 17 Aug 2004 04:51:26 -0400
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:fd13:3c53:7410:a99a]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 141771525D; Tue, 17 Aug 2004 17:45:06 +0900 (JST)
Date: Tue, 17 Aug 2004 17:45:05 +0900
Message-ID: <y7v4qn22lwu.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: jdq@lucent.com
Subject: Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt
In-Reply-To: <200408121018.57077.jdq@lucent.com>
References: <000001c48073$af492fa0$d0412ca1@amer.cisco.com> <200408121018.57077.jdq@lucent.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: d185fa790257f526fedfd5d01ed9c976
Cc: dhcwg@ietf.org, tjc@ecs.soton.ac.uk, Bernie Volz <volz@cisco.com>, 'Stig Venaas' <Stig.Venaas@uninett.no>
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 Thu, 12 Aug 2004 10:18:57 -0400, >>>>> Joe Quanaim <jdq@lucent.com> said: >> The primary motivation for the lifetime option is for situations where >> no lifetime (or renewal time) is communicated to the client, such as for >> Stateless DHCP service as specified in [RFC 3736]. However, it applies >> to both stateful and stateless DHCP clients and is an upper bound for >> when a client should initiate renewal of at least its non-address based >> configuration parameters - a stateful client MAY renew its addresses at >> the same time and SHOULD always get updated configuration data from the >> server when it renews any addresses. >> >> One difference between Stateful and Stateless clients with regards >> to this option is that a Stateful client that does not receive this >> option MUST NOT apply the default lifetime. > As noted, the motivation of the lifetime option is to ensure stateless clients > receive current configuration information. As such, I think keeping it out > of stateful configuration is the simplest approach. As we have discussed, > stateful configuration already has several variables to manipulate client > behavior. I do not see much gain in adding another. It's not a strong opinion, but I'd also still prefer to restrict the use of the lifetime option to the stateless case. The reasons are: - even if it might be true that the client can use stateful exchanges without having addresses or infinite T1/T2 timers for other configurations only, it should be a very minor case (I'm pretty sure that everyone agrees on this - whether still want to allow such usage or not). In my understanding, the sense of RFC3315 is that "if you can get an address, you may get other information. If you cannot get an address, then give up any possible information." In fact, Section 18.1.8 says [...] If the client receives no addresses in any of the IAs, it may either try another server (perhaps restarting the DHCP server discovery process) or use the Information-request message to obtain other configuration information only. but the RFC does not (explicitly) allow the client to continue to use other information configuration than addresses. What you are going to achieve in the scenario of the lifetime option with the stateful case seems to contradict the original sense, IMO. - recalling that we rejected the idea of multiple lifetime options for multiple configuration parameters, it's odd to me that we are now going to have T1/T2 as well as the lifetime option (I was happy with rejecting the idea of multiple lifetimes, BTW). If we applied the same logic, we could simply use an appropriate T1 value to implement controlled update of the other configuration information. Again, it's true that stateful exchanges can provide no finite timers, but, as I said in the above bullet, it's very minor or even almost-unexpected use case in my understanding. - as I pointed out in my first message, we'll have to define all the details, most of which are boring corner cases (but the implementors would be unhappy if we didn't define those). I know some of you are now trying to address those, and trying to minimize the complexity of the specification. However, right now I'm not sure if it really makes sense, considering the usage case of stateful+lifetime is minor. I admit this is a tradeoff issue, and perhaps we need to end up discussing details to make a clear consensus. - one thing I'm concerned about which is related to the above point: there is already a non-address IA that has a notion of timeout: IA_PD. So, we'll probably have to consider the combination of IA_PD and the lifetime option. Moreover, the lifetime option document may need to be generic enough to prepare for any future stateful resources that has a notion of timeout. > Still, it's not that complex a change. If I am outvoted, so be it. Same here. Though I'm still skeptical about the benefit of the use case of stateful+lifetime, considering the possible complexity, I can live with that if the specification is crystal clear about all the details. 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
- [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt JINMEI Tatuya / 神明達哉
- [dhcwg] Re: comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- Re: [dhcwg] Re: comments on draft-ietf-dhc-lifeti… Ted Lemon
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Joe Quanaim
- Re: [dhcwg] Re: comments on draft-ietf-dhc-lifeti… Stig Venaas
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Ted Lemon
- RE: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Bernie Volz
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Joe Quanaim
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Joe Quanaim
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- RE: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Bernie Volz
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Joe Quanaim
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- RE: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Bernie Volz
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Joe Quanaim
- RE: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Bernie Volz
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- RE: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Bernie Volz
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- RE: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Bernie Volz
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Joe Quanaim
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- RE: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Bernie Volz
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… JINMEI Tatuya / 神明達哉
- [dhcwg] behavior on lifetime expiration (Re: comm… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] behavior on lifetime expiration (Re: … Ted Lemon
- Re: [dhcwg] behavior on lifetime expiration (Re: … Joe Quanaim
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas
- Re: [dhcwg] behavior on lifetime expiration (Re: … Tim Chown
- Re: [dhcwg] behavior on lifetime expiration (Re: … Joe Quanaim
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas
- Re: [dhcwg] behavior on lifetime expiration (Re: … JINMEI Tatuya / 神明達哉
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas
- Re: [dhcwg] behavior on lifetime expiration (Re: … Joe Quanaim
- Re: [dhcwg] behavior on lifetime expiration (Re: … Ted Lemon
- RE: [dhcwg] behavior on lifetime expiration (Re: … Bernie Volz
- RE: [dhcwg] behavior on lifetime expiration (Re: … Bernie Volz
- Re: [dhcwg] behavior on lifetime expiration (Re: … Robert Elz
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Robert Elz
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas
- Re: [dhcwg] behavior on lifetime expiration (Re: … Robert Elz
- Re: [dhcwg] behavior on lifetime expiration (Re: … Joe Quanaim
- Re: [dhcwg] behavior on lifetime expiration (Re: … Ted Lemon
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Stig Venaas
- Re: [dhcwg] behavior on lifetime expiration (Re: … JINMEI Tatuya / 神明達哉
- Re: [dhcwg] behavior on lifetime expiration (Re: … JINMEI Tatuya / 神明達哉
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… Ted Lemon
- Re: [dhcwg] dhc-lifetime-01: dropping omitted opt… Ted Lemon
- Re: [dhcwg] behavior on lifetime expiration (Re: … Ted Lemon
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas
- Re: [dhcwg] comments on draft-ietf-dhc-lifetime-0… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] behavior on lifetime expiration (Re: … JINMEI Tatuya / 神明達哉
- Re: [dhcwg] behavior on lifetime expiration (Re: … Ted Lemon
- Re: [dhcwg] behavior on lifetime expiration (Re: … Robert Elz
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas
- Re: [dhcwg] behavior on lifetime expiration (Re: … JINMEI Tatuya / 神明達哉
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas
- Re: [dhcwg] behavior on lifetime expiration (Re: … Joe Quanaim
- Re: [dhcwg] behavior on lifetime expiration (Re: … Stig Venaas