Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt
Stig Venaas <Stig.Venaas@uninett.no> Wed, 11 August 2004 10:40 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 GAA19318; Wed, 11 Aug 2004 06:40:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BuqV3-000751-FA; Wed, 11 Aug 2004 06:38:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BuqTj-0006tp-FQ for dhcwg@megatron.ietf.org; Wed, 11 Aug 2004 06:37:07 -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 GAA19161 for <dhcwg@ietf.org>; Wed, 11 Aug 2004 06:37:04 -0400 (EDT)
Received: from tyholt.uninett.no ([158.38.60.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuqYS-0003HZ-MR for dhcwg@ietf.org; Wed, 11 Aug 2004 06:42:01 -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 i7BAaN2M015866; Wed, 11 Aug 2004 12:36:23 +0200
Received: (from venaas@localhost) by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i7BAaMSL005402; Wed, 11 Aug 2004 12:36:22 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Wed, 11 Aug 2004 12:36:22 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Joe Quanaim <jdq@lucent.com>
Subject: Re: [dhcwg] comments on draft-ietf-dhc-lifetime-01.txt
Message-ID: <20040811103622.GF5086@sverresborg.uninett.no>
References: <y7vhdrl56ol.wl@ocean.jinmei.org> <200408030929.31655.jdq@lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200408030929.31655.jdq@lucent.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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 Tue, Aug 03, 2004 at 09:33:29AM -0400, Joe Quanaim wrote: > > JINMEI Tatuya / ???????????? wrote: > [...] > > 2. the usage of the lifetime option for other exchanges than > > Info-req/Reply exchanges. > > > > I'm even not 100% sure if the lifetime can be used for the other > > types of exchanges. Probably it can according to the draft, but > > then I'll have several questions on how to use it. > > > > For example, the draft says: > > > > Before making the request it MUST wait for a random amount of time > > between 0 and INF_MAX_DELAY. INF_MAX_DELAY is defined in [RFC 3315]. > > > > Is this also applies to the other cases even if INF_MAX_DELAY is a > > dedicated parameter for Info-req? If so, is it really valid? > > Isn't this duplicating rfc 3315? Removing it would prevent any subsequent > updates to rfc 3315 from conflicing with this statement. So what you're saying is that should say 1 sec, rather than INF_MAX_DELAY? Or are you saying that shouldn't specify random delay at all? At first I didn't see the need for random delay since there is one prior to the first information request according to rfc 3315, but as someone said it might be required. If for instance the client checks for expired lifetime every second or less often. > > Also, how does the client exactly react to the expiration event for > > the other cases? For example, consider the following scenario: > > > > - the client performs Solicit->Advertise->Request->Reply exchanges, > > and gets an IPv6 address allocated, a DNS server address X, and an > > associated lifetime T. > > - before the timeout "T1" for the allocated address passes, lifetime > > T expires. In this case, should the client restart the entire > > session from Solicit? Or should the client send a renew message? > > If so, the renew message also tries to update the allocated > > address even if it's too early? Or should the client even start > > Information-request/Reply exchanges just to update the DNS address > > information? > > Using this option in a stateful transaction makes things more complicated. > The lifetime option can expire between t1, t2, or the valid lifetime of an > address. As Jinmei Tatuya notes, what should the client be expected to do? > Restart the message exchange; just do an information-request; etc. > > Any negotiated value for t1, t2, or valid lifetime of an address could take > precedence over the lifetime option. This essentially makes the option > stateless only, but it simplifies the resulting changes to a client > implementation. I'm happy with this. If anyone got other opinions, please speak up. I'll mail text suggestion soon, > Joe Quanaim. Thanks, 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