[dhcwg] TTL on service addresses
Ralph Droms <rdroms@cisco.com> Fri, 08 November 2002 16:45 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26690 for <dhcwg-archive@odin.ietf.org>; Fri, 8 Nov 2002 11:45:31 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA8GlZR09476 for dhcwg-archive@odin.ietf.org; Fri, 8 Nov 2002 11:47:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8GlYv09473 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 11:47:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26643 for <dhcwg-web-archive@ietf.org>; Fri, 8 Nov 2002 11:45:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Ghuv09189; Fri, 8 Nov 2002 11:43:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Gfav08980 for <dhcwg@optimus.ietf.org>; Fri, 8 Nov 2002 11:41:36 -0500
Received: from funnel.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26304 for <dhcwg@ietf.org>; Fri, 8 Nov 2002 11:39:02 -0500 (EST)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-126.cisco.com [161.44.149.126]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id LAA12075 for <dhcwg@ietf.org>; Fri, 8 Nov 2002 11:41:32 -0500 (EST)
Message-Id: <4.3.2.7.2.20021108112530.03d7f810@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 08 Nov 2002 11:41:17 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] TTL on service addresses
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
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@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] TTL on service addresses Ralph Droms
- Re: [dhcwg] TTL on service addresses Ted Lemon
- RE: [dhcwg] TTL on service addresses Vijayabhaskar A K
- RE: [dhcwg] TTL on service addresses Bernie Volz (EUD)