Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-resolution-09.txt>

"David W. Hankins" <David_Hankins@isc.org> Tue, 12 July 2005 21:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsSKo-0005Ab-Hw; Tue, 12 Jul 2005 17:30:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsSKm-00059c-BK for dhcwg@megatron.ietf.org; Tue, 12 Jul 2005 17:30:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13793 for <dhcwg@ietf.org>; Tue, 12 Jul 2005 17:30:29 -0400 (EDT)
Received: from kaboom.isc.org ([204.152.187.72]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsSms-0003jJ-SL for dhcwg@ietf.org; Tue, 12 Jul 2005 17:59:35 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200) id 1B8ACB2467; Tue, 12 Jul 2005 14:30:02 -0700 (PDT)
Date: Tue, 12 Jul 2005 14:30:02 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-resolution-09.txt>
Message-ID: <20050712213002.GE27743@isc.org>
References: <1120944721.12354.64.camel@localhost.localdomain>
Mime-Version: 1.0
In-Reply-To: <1120944721.12354.64.camel@localhost.localdomain>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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>
Content-Type: multipart/mixed; boundary="===============0790671465=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

I would like to see section 6.3.4, when describing the policy for
'replacement' of fqdn's by the latest dhcp speaker claiming to have
that name, to state there must be a prerequisite for the over-riding
update...although implementations might do this update without a prereq,
I think the document should be consistent about suggesting DHCP servers
only touch names that either have DHCID's on them, or don't exist at all.

eg:

    ... If the configured policy allows
   replacement of existing records, the updater submits a query that
   deletes all RRs for the FQDN and adds the A and/or AAAA and DHCID RRs
   that represent the IP address and client identity of the new client.

becomes:

    ... If the configured policy allows
    replacement of existing records, the updater submits a query which
    contains:

	o A prerequisite that a DHCID RR of any value exist for this FQDN.
	o The deletion of all RRs for the FQDN.
	o The addition of the A and/or AAAA RR
	o The addition of the new DHCID RR.



Or something like that.

-- 
David W. Hankins		"If you don't do it right the first time,
Software Engineer			you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg