Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt
Stig Venaas <Stig.Venaas@uninett.no> Thu, 12 August 2004 13:35 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 JAA01265; Thu, 12 Aug 2004 09:35:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BvFW2-0005gP-3z; Thu, 12 Aug 2004 09:21:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BvFOO-0003uy-UV for dhcwg@megatron.ietf.org; Thu, 12 Aug 2004 09:13:17 -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 JAA29915 for <dhcwg@ietf.org>; Thu, 12 Aug 2004 09:13:15 -0400 (EDT)
Received: from tyholt.uninett.no ([158.38.60.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvFTM-0003Zj-MC for dhcwg@ietf.org; Thu, 12 Aug 2004 09:18:25 -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 i7CDAY2M016961; Thu, 12 Aug 2004 15:10:34 +0200
Received: (from venaas@localhost) by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i7CDAYUx009117; Thu, 12 Aug 2004 15:10:34 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Thu, 12 Aug 2004 15:10:34 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt
Message-ID: <20040812131034.GI8177@sverresborg.uninett.no>
References: <200408120831.02326.jdq@lucent.com> <002601c48069$f73b3330$6401a8c0@amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <002601c48069$f73b3330$6401a8c0@amer.cisco.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: dhcwg@ietf.org, tjc@ecs.soton.ac.uk, jdq@lucent.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 Thu, Aug 12, 2004 at 08:43:27AM -0400, Bernie Volz wrote: > If a server sets the T1/T2 times to infinity, it gets what it asked for - > the configuration is static FOREVER. This is one reason it would be an > extremely bad idea to ever use these values. We added them for clarity in > the RFC, though never really figured they would be used in practice. > > The no address issue is an interested one. > > On a SOLICIT, the server is ONLY to return the Status Message response with > NoAddrAvail status. It is *NOT* supposed to return any configuration > information!!! > > Though it is always possible that a subsequent REQUEST or RENEW/REBIND would > result in no addresses. However, in those cases the IA_NA is still returned > with T1 and T2 times and those would, IMHO, apply. (In these cases, the > NoAddrAvail status is embedded *INSIDE* the IA_* options so these options > are still returned.) > > I suppose there is the case when a SOLICIT/REQUEST/RENEW/REBIND for an IA_NA > and IA_TA results in no addresses for a IA_NA and one or more addresses for > a IA_TA, in which case no T1/T2 times are provided - thought the IA_TA does > have lifetimes. > > But, all of this gets very messy fairly quickly. > > So, perhaps the easiest thing to do is to *ALWAYS* allow the LIFETIME option > - for stateful and stateless. A client *SHOULD* renew (etc) its information > whenver the shortest time expires - LIFETIME, T1, or lifetime on an address > (and the client needs a replacement address). If the client is stateful, is > uses RENEW (whether the client includes on or more IA_NAs if no T1 time has > expired is a matter of local policy - though it would seem reasonable for me > if it did since there's no harm in doing so). If a client is stateless, it > uses INFORMATION-REQUEST. > > This also makes server implementations easier since the T1/T2 times and > "other-configuration-parameters" lifetime can be configured independently > and a server need not assure that no T1 time is greater than > "other-configuration-parameters". This is more in line with my original idea for lifetime. I've started improving the draft, and I now have these paragraphs: The lifetime option specifies a lifetime for all configuration data contained in other options in an advertise or reply message that have no associated lifetime. If any of the options have an associated lifetime of their own which is shorter than the lifetime option value, then that should take precedence. Or in other words, the lifetime option specifies an upper bound for how long the client should wait before attempting to renew the data. If there are options with a shorter lifetime or the client has other reasons for requesting data from the DHCP server, then it should also update the data covered by the lifetime option. I think this should pretty much cover what you say and is in line with my own thinking. After that I have the paragraph: The lifetime option is mainly intended for Stateless DHCP service as specified in [RFC 3736]. If the client receives IA Address options containing lifetimes, the lifetime option should be ignored. The client should get updated configuration data from the server when it renews the addresses. Personally I'm happy to remove that again. I guess we should try to come to some consensus before I do more writing. Stig _______________________________________________ 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