Re: [dhcwg] DDNS-DHCP [6]: Relationship between DNS TTL and DHCP lease length

Robert Elz <kre@munnari.OZ.AU> Fri, 20 June 2003 09:47 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 FAA23238 for <dhcwg-archive@odin.ietf.org>; Fri, 20 Jun 2003 05:47:32 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5K9l6d28446 for dhcwg-archive@odin.ietf.org; Fri, 20 Jun 2003 05:47:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TIU5-0007Oj-Vp for dhcwg-web-archive@optimus.ietf.org; Fri, 20 Jun 2003 05:47:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23199 for <dhcwg-web-archive@ietf.org>; Fri, 20 Jun 2003 05:47:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TIRj-00019E-00 for dhcwg-web-archive@ietf.org; Fri, 20 Jun 2003 05:44:39 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19TIRj-00019B-00 for dhcwg-web-archive@ietf.org; Fri, 20 Jun 2003 05:44:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TIU0-0007NT-Th; Fri, 20 Jun 2003 05:47:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TITi-0007Go-Ai for dhcwg@optimus.ietf.org; Fri, 20 Jun 2003 05:46:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23193 for <dhcwg@ietf.org>; Fri, 20 Jun 2003 05:46:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TIRL-000197-00 for dhcwg@ietf.org; Fri, 20 Jun 2003 05:44:15 -0400
Received: from ratree.psu.ac.th ([202.12.73.3]) by ietf-mx with esmtp (Exim 4.12) id 19TIRK-00018j-00 for dhcwg@ietf.org; Fri, 20 Jun 2003 05:44:14 -0400
Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98]) by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h5K9jCr11939; Fri, 20 Jun 2003 16:45:18 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h5K9iFH25906; Fri, 20 Jun 2003 16:44:15 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
cc: dhcwg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: [dhcwg] DDNS-DHCP [6]: Relationship between DNS TTL and DHCP lease length
In-Reply-To: <200306200103.h5K13rWl030720@sandelman.ottawa.on.ca>
References: <200306200103.h5K13rWl030720@sandelman.ottawa.on.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 20 Jun 2003 16:44:14 +0700
Message-ID: <15427.1056102254@munnari.OZ.AU>
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>

    Date:        Thu, 19 Jun 2003 21:03:52 -0400
    From:        Michael Richardson <mcr@sandelman.ottawa.on.ca>
    Message-ID:  <200306200103.h5K13rWl030720@sandelman.ottawa.on.ca>

First, Mark's summary looked fine to me.

But ...

  | As such, what I really want is a dynamic update operation which actually
  | says "install this record with TTL=XXX, deleting the record after YYY"
  | (Clearly, XXX < YYY, and some may argue YYY:=XXX. I'm undecided)

The XXX & YYY relationship isn't important here but XXX << YYY (in the
mathematical << sense, not "shift left") if this were to have any hope
of working.

But yes, that's what almost everyone wanted when dynamic update was
being defined - and a lot of effort was spend attempting to find
something which would actually work like that.   Unfortunately,
nothing reliable could be found, so that is not what exists.

You can try and dream up a protocol to allow this to work, but
first please go and review all the archives from when dynamic
update was being designed, and then again since then whenever anyone
has suggested it since - it is not nearly as simple to make work
properly as it seems it should be - and if it can't be guaranteed
to work, then the host has to deal with it other ways anyway.

  | I have really no problem sending a new update every couple of minutes.
  | In fact, I'd prefer to do this.

Unfortunately, by itself, that doesn't help - that was the original
plan for this (you need to investigate the way the whole DNS works,
including the primary/secondary relationship, and servers that crash at
inconvenient times, to see the problems).

kre


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