Re: [DNSOP] comments on draft-ietf-dnsop-dns-terminology-03

"Paul Hoffman" <paul.hoffman@vpnc.org> Thu, 16 July 2015 02:15 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BBF61B2FFD for <dnsop@ietfa.amsl.com>; Wed, 15 Jul 2015 19:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FTjDT312FmUE for <dnsop@ietfa.amsl.com>; Wed, 15 Jul 2015 19:15:31 -0700 (PDT)
Received: from hoffman.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ADE01B2FA2 for <dnsop@ietf.org>; Wed, 15 Jul 2015 19:15:31 -0700 (PDT)
Received: from [10.32.60.122] (142-254-17-100.dsl.dynamic.fusionbroadband.com [142.254.17.100]) (authenticated bits=0) by hoffman.proper.com (8.15.1/8.14.9) with ESMTPSA id t6G2FQf2019142 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Jul 2015 19:15:27 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 142-254-17-100.dsl.dynamic.fusionbroadband.com [142.254.17.100] claimed to be [10.32.60.122]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, Casey Deccio <casey@deccio.net>
Date: Wed, 15 Jul 2015 19:15:26 -0700
Message-ID: <F9A99D9D-2A3E-4433-A219-2C27AFC009B3@vpnc.org>
In-Reply-To: <20150716003359.GD13926@mx2.yitter.info>
References: <CAEKtLiQWPM6yJZZASQ5k1bzsbHc3jv5FRsJ6ifgUdj9TRLCmRg@mail.gmail.com> <83A64168-3510-4E0B-AA23-54547C05990B@vpnc.org> <alpine.LSU.2.00.1507141719130.32296@hermes-1.csi.cam.ac.uk> <55A543CD.6010008@gmail.com> <CAEKtLiRQVgQRnm51gSb0e9zhmQ7vYVJXdPBQsSLXqHo_hiAKyw@mail.gmail.com> <20150716003359.GD13926@mx2.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/GiZyUwqmuN-GZ6nwFHDDJ5FmNGs>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] comments on draft-ietf-dnsop-dns-terminology-03
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2015 02:15:32 -0000

On 15 Jul 2015, at 17:33, Andrew Sullivan wrote:

> Hi,
>
> On Tue, Jul 14, 2015 at 03:43:12PM -0400, Casey Deccio wrote:
>> I am also concerned about the apparent urgency to get the initial 
>> document
>> out with points that admittedly remain contentious and/or where there 
>> isn't
>> WG consensus.  I don't think it needs perfection, but it seems 
>> unnecessary
>> to get the document published without further explicitly identifying 
>> and
>> considering the standing issues.  We've haven't had this document
>> before--I'm not sure what the rush is now.
>
> Just on this issue, and speaking only for myself (but as one of the
> people behind this document), my view is that this WG has historically
> been one of the places where documents go to die, and I am unwilling
> to go through the exercise of proving again how great an enemy of the
> good the perfect can be.  I'd be much more inclined to remove the
> contentious definitions and publish that document than to try to get
> things perfect.
>
> I agree and acknowledge that there remain some definitions in there
> that are contentious.

Not only do you agree and acknowledge that, *so does the document*. 
Based on the contention and lack of consensus for some of the 
definitions, the Introduction now says:

During the development of this document, it became clear that some 
DNS-related terms are interpreted quite differently by different DNS 
experts. Further, some terms that are defined in early DNS RFCs now have 
definitions that are generally agreed to that are different from the 
original definitions. Therefore, the authors intend to follow this 
document with a substantial revision in the not-distant future. That 
revision will probably have more in-depth discussion of some terms as 
well as new terms; it will also update some of the RFCs with new 
definitions.

If there is something more that can be said in the document, by all 
means let us know.

--Paul Hoffman