RE: [dhcwg] TTL on service addresses

"Vijayabhaskar A K" <> Sun, 10 November 2002 12:02 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id HAA14950 for <>; Sun, 10 Nov 2002 07:02:28 -0500 (EST)
Received: (from mailnull@localhost) by (8.11.6/8.11.6) id gAAC4Ue00544 for; Sun, 10 Nov 2002 07:04:30 -0500
Received: from ( []) by (8.11.6/8.11.6) with ESMTP id gAAC4Uv00541 for <>; Sun, 10 Nov 2002 07:04:30 -0500
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id HAA14934 for <>; Sun, 10 Nov 2002 07:01:57 -0500 (EST)
Received: from (localhost.localdomain []) by (8.11.6/8.11.6) with ESMTP id gAAC2Hv00460; Sun, 10 Nov 2002 07:02:17 -0500
Received: from ( []) by (8.11.6/8.11.6) with ESMTP id gAAC0Wv00397 for <>; Sun, 10 Nov 2002 07:00:32 -0500
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id GAA14850 for <>; Sun, 10 Nov 2002 06:58:00 -0500 (EST)
Received: from ( []) by (Postfix) with ESMTP id 0DA858050E0; Sun, 10 Nov 2002 07:00:30 -0500 (EST)
Received: from nt4147 ( []) by with SMTP (8.8.6 (PHNE_17135)/8.8.6 SMKit7.02) id RAA29053; Sun, 10 Nov 2002 17:23:46 +0530 (IST)
From: Vijayabhaskar A K <>
To: 'Ralph Droms' <>,
Subject: RE: [dhcwg] TTL on service addresses
Date: Sun, 10 Nov 2002 17:30:08 +0530
Message-ID: <000001c288b0$b82aceb0$2f290a0f@nt4147>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <>, <>
List-Id: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


The service addresses are not likely to change frequently.
So, i feel that there is no meaning of having TTL for these
addresses and renewing them once in a while.

Already, we have a mechanism called "reconfiguration", through
which this can be accomplished. Inclusion of TTL will unnecessarily
complicate the client, as it needs to keep track of another timer,
along with the one for IAs.

I think, we can keep the option part as it is, thus, whatever
the service addresses it receive, its going to be valid for
infinite, and server will notify the change, if any, using the
reconfigure-init in course of time

~ Vijay

-----Original Message-----
From: []On Behalf Of
Ralph Droms
Sent: Friday, November 08, 2002 10:11 PM
Subject: [dhcwg] TTL on service addresses

At the last WG meeting, we talked about how to add lifetime information to
addresses for services (for example, DNS server addresses).

So, what are the requirements?  Basically, we want to be able to inform the
client the time over which it can expect the service address to be
useful.  The client can then re-contact the server to confirm the continued
validity of those addresses or find out about new service addresses.

Question - is it useful to have a separate lifetime for each service or can
we make a simplification about lifetime information that applies to all of
the services configured on the client?

Are there other requirements?

- Ralph

dhcwg mailing list

dhcwg mailing list