Re: [dhcwg] Re: one more comment about the lifetime option

Ralph Droms <rdroms@cisco.com> Tue, 03 August 2004 18:28 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 OAA29669; Tue, 3 Aug 2004 14:28:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs3p9-0002os-JJ; Tue, 03 Aug 2004 14:15:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs3Zp-0007fe-HI for dhcwg@megatron.ietf.org; Tue, 03 Aug 2004 13:59:53 -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 NAA27298 for <dhcwg@ietf.org>; Tue, 3 Aug 2004 13:59:52 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs3cw-0006Lr-1d for dhcwg@ietf.org; Tue, 03 Aug 2004 14:03:07 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 03 Aug 2004 13:59:21 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i73HxERW016513; Tue, 3 Aug 2004 13:59:14 -0400 (EDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-28.cisco.com [10.86.242.28]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AKO68233; Tue, 3 Aug 2004 13:59:13 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040803135851.02af6cb0@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 03 Aug 2004 13:59:10 -0400
To: "JINMEI Tatuya / ?$B?@L@C#:H" <jinmei@isl.rdc.toshiba.co.jp>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: one more comment about the lifetime option
In-Reply-To: <20040803171447.GA27805@sverresborg.uninett.no>
References: <y7vacxc5f3r.wl@ocean.jinmei.org> <y7vacxc5f3r.wl@ocean.jinmei.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 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

I agree with Stig - we've discussed this issue before and come to the 
conclusion that there is little extra overhead in delivering information 
that has not changed, so there should be a single lifetime - chosen to be 
the shortest lifetome of any of the client's parameters.

- Ralph

At 07:14 PM 8/3/2004 +0200, Stig Venaas wrote:
>On Wed, Aug 04, 2004 at 02:03:04AM +0900, JINMEI Tatuya / ?$B?@L@C#:H wrote:
> > I forgot to mention this one:
> >
> > Is it possible to specify different lifetimes for different instances
> > of stateless information?  For example, people may want to specify
> > different lifetimes for recursive DNS server addresses and for SIP
> > server addresses.
>
>We should keep this simple. If e.g. recursive server data needs to be
>updated more frequently than SIP data, I would simply say that lifetime
>should be the shortest. When you contact server to update DNS data, you
>can at the same time update other data like SIP server address.
>
>Note that the draft says:
>
>    If client has received a lifetime with this option, and contacts
>    server to receive new or update any existing data prior to its
>    expiration, it SHOULD also update data covered by this option.  If no
>    new lifetime is received, it MUST behave as if no value was ever
>    provided.
>
>In line with that SHOULD, there's no good reason to have multiple
>lifetimes.
>
>Stig
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg


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