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

Tim Wicinski <tjw.ietf@gmail.com> Thu, 16 July 2015 02:52 UTC

Return-Path: <tjw.ietf@gmail.com>
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 BF0861B35D3 for <dnsop@ietfa.amsl.com>; Wed, 15 Jul 2015 19:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 x1hLem_Y-72G for <dnsop@ietfa.amsl.com>; Wed, 15 Jul 2015 19:52:04 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B76CD1B35D1 for <dnsop@ietf.org>; Wed, 15 Jul 2015 19:52:04 -0700 (PDT)
Received: by qkdv3 with SMTP id v3so42087096qkd.3 for <dnsop@ietf.org>; Wed, 15 Jul 2015 19:52:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=ii2eR06g+h8Hw5nqvOBnWpLxhWzb0wsHRprpzj925do=; b=hqArNLN9l7oiE/10GJk7dmutOR8hWuUD5AiKP3njT6S1dfVvUwzuUfxKIy7Ovyhaqk YsChlQ3+w/9Xaub2n9q+ViQaNhAXc0I2PK0Z8vuzSHpt6ruHugy3zGQBRqq0krA07NT1 +XvBNPz2cndDu8GmUOkqazwtCXginYXygiA5sUxZJFoW0YYxhnzQ2NrA210IT6D3dq0i oIalUHh8Z5wyaF0XA/O82swAjlci6XHPvv89POss6yUNC9QE3NELbup0o4gq8Pfqahbf RCaLAVVoPtyNgowluUUgMcuVRf+VWVvbeX71SO4Um1ugOOcMmL0idPKtXW73d39ETX1Z mtxw==
X-Received: by 10.140.39.17 with SMTP id u17mr13695679qgu.5.1437015124017; Wed, 15 Jul 2015 19:52:04 -0700 (PDT)
Received: from still.local (184-19-93-177.drr03.clbg.wv.frontiernet.net. [184.19.93.177]) by smtp.googlemail.com with ESMTPSA id 20sm3334317qkp.39.2015.07.15.19.52.02 for <dnsop@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Jul 2015 19:52:03 -0700 (PDT)
To: dnsop@ietf.org
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> <F9A99D9D-2A3E-4433-A219-2C27AFC009B3@vpnc.org>
From: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <55A71C52.40407@gmail.com>
Date: Wed, 15 Jul 2015 22:52:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:41.0) Gecko/20100101 Thunderbird/41.0a2
MIME-Version: 1.0
In-Reply-To: <F9A99D9D-2A3E-4433-A219-2C27AFC009B3@vpnc.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/iKGeCujOfb0TeJcKny9v8_KsuMs>
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:52:06 -0000


On 7/15/15 10:15 PM, Paul Hoffman wrote:

>
> 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
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


Also, the document took the approach early on of documenting what 
existing RFCs said in one place.  When it became clear that what the 
RFCs say may not be how people currently use the term, the consensus in 
the working group was to document the existing definition, and flag it 
as in disagreement.  Once this document was pushed out, *then* the 
revised draft could actually update old RFCs.

As chair, I also felt that once this draft is published (and all 
contention removed), it would become something that would be part of the 
document shepherding process - to make sure new RFCs actually used 
accurate terminology.  But that may be a pipe dream.

I do think the authors have done an impressive job considering the scope 
of the document and the depth and breath of comments.

tim