Re: [dhcwg] TTL on service addresses
Ted Lemon <Ted.Lemon@nominum.com> Fri, 08 November 2002 17:15 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 MAA29068 for <dhcwg-archive@odin.ietf.org>; Fri, 8 Nov 2002 12:15:18 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA8HHLS12381 for dhcwg-archive@odin.ietf.org; Fri, 8 Nov 2002 12:17:21 -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 gA8HHLv12378 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 12:17:21 -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 MAA28978 for <dhcwg-web-archive@ietf.org>; Fri, 8 Nov 2002 12:14:47 -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 gA8HEtv12242; Fri, 8 Nov 2002 12:14:55 -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 gA8HBxv11781 for <dhcwg@optimus.ietf.org>; Fri, 8 Nov 2002 12:11:59 -0500
Received: from toccata.fugue.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28542 for <dhcwg@ietf.org>; Fri, 8 Nov 2002 12:09:25 -0500 (EST)
Received: from nominum.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id gA8H7Z203900; Fri, 8 Nov 2002 11:07:35 -0600 (CST)
Date: Fri, 08 Nov 2002 11:11:48 -0600
Subject: Re: [dhcwg] TTL on service addresses
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v546)
Cc: dhcwg@ietf.org
To: Ralph Droms <rdroms@cisco.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <4.3.2.7.2.20021108112530.03d7f810@funnel.cisco.com>
Message-Id: <2A7B85D7-F33D-11D6-9BDA-00039367340A@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Why not just have the server set the renewal time on the packet to the shortest TTL in the packet? Why does the client even need to know this, since what it's going to have to do to refresh the information is to renew the lease anyway. And if we do it this way, does it need to be a protocol issue? _______________________________________________ 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)