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 22:10 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsSxl-00038m-3R; Tue, 12 Jul 2005 18:10:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsSxi-00038Q-Ga for dhcwg@megatron.ietf.org; Tue, 12 Jul 2005 18:10:46 -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 SAA23563 for <dhcwg@ietf.org>; Tue, 12 Jul 2005 18:10:43 -0400 (EDT)
Received: from kaboom.isc.org ([204.152.187.72]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsTPz-0007P5-Pc for dhcwg@ietf.org; Tue, 12 Jul 2005 18:40:00 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200) id 6B2CCB2467; Tue, 12 Jul 2005 15:10:24 -0700 (PDT)
Date: Tue, 12 Jul 2005 15:10:24 -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: <20050712221024.GF27743@isc.org>
References: <1120944721.12354.64.camel@localhost.localdomain> <8737CA55-609B-44D9-80AF-DCF4494A1C56@nominum.com>
Mime-Version: 1.0
In-Reply-To: <8737CA55-609B-44D9-80AF-DCF4494A1C56@nominum.com>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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="===============1222108794=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
On Tue, Jul 12, 2005 at 03:31:58PM -0500, Ted Lemon wrote: > I don't agree with the changed text about the order in which updates > should be done. The draft should specify one or the other. I Actually, it's funny you should say that. I harbor the opposite opinion. I was thinking that it shouldn't limit the implementor to start at 6.3.1 vs 6.3.2, because I think it would be useful in some environs to start straight at 6.3.3 and let prereq failures lead you back to 6.3.2 if necessary. Deleting the first paragraph of 6.3 would read the way I wanted it to, jump straight into 'you MAY use other implementations'. Since the first step the document outlines is the query, I think most under-educated implementors would follow it. -- 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
- [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-… Ralph Droms
- Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-d… Ralph Droms
- Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-d… Ted Lemon
- Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-d… David W. Hankins
- Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-d… David W. Hankins
- Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-d… Ted Lemon
- Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-d… David W. Hankins
- Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-d… David W. Hankins