Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-terminology-02.txt
Paul Hoffman <paul.hoffman@vpnc.org> Fri, 05 June 2015 16:51 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 50AD51A8F51 for <dnsop@ietfa.amsl.com>; Fri, 5 Jun 2015 09:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.053
X-Spam-Level:
X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 ZU2UTQTDp5U6 for <dnsop@ietfa.amsl.com>; Fri, 5 Jun 2015 09:51:29 -0700 (PDT)
Received: from 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 400CF1A8F44 for <dnsop@ietf.org>; Fri, 5 Jun 2015 09:51:29 -0700 (PDT)
Received: from [10.121.3.93] (74-93-10-100-SFBA.hfc.comcastbusiness.net [74.93.10.100]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t55Gop6M012768 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2015 09:50:53 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 74-93-10-100-SFBA.hfc.comcastbusiness.net [74.93.10.100] claimed to be [10.121.3.93]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <alpine.LSU.2.00.1506050005550.30373@hermes-1.csi.cam.ac.uk>
Date: Fri, 05 Jun 2015 09:50:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <081EDE00-3FB4-4135-8CE7-149F73E4A74A@vpnc.org>
References: <20150526153132.306.56516.idtracker@ietfa.amsl.com> <alpine.LSU.2.00.1506050005550.30373@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/ccHahRE088dbnyrdRXO_oqcCWA4>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-terminology-02.txt
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: <http://www.ietf.org/mail-archive/web/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: Fri, 05 Jun 2015 16:51:30 -0000
Thanks again for the in-depth review. A few comments below. On Jun 4, 2015, at 5:35 PM, Tony Finch <dot@dotat.at> wrote: > I mentioned an alphabetical index in my previous comment - I expect that > will be easier to add during final editing. I want to mention it again > because one of the main questions a reader will have is, does this > glossary define the term I am looking for? An alphabetical index would > help a lot. The indexing tools for RFCs suck in many ways. We assume that if someone is looking at the RFC and wonders if a term in defined, they'll use the search function of their text editor or web browser. > "recursive mode" and "iterative mode". No-one uses those phrases. However, RFC 1034 uses those terms, and there was disagreement on what else to use. It would be great for the -bis of this document to have specific definitions for the terms people do use, but we doubt we can get this now, other than by through exhaustion. > The definition of "authoritative data" is still wrong. We have done the best we can with this, given that RFC 1034's definition is in dispute. > I am still unhappy about the description of referrals. (I found them > surprisingly slippery when I was writing my suggestions.) So are we. Again, we hope that we can get consensus for this and other slippery terms when we do the -bis. > Under SEP, "RRdata" should be "RDATA". Fully disagree. If we are quoting an RFC, we should not change the words, even the spelling. > Also, I think this sentence from > RFC 6781 section 3.2.3 is important because most key management tooling > implements it - "It is suggested that the SEP flag be set on keys that are > used as KSKs and not on keys that are used as ZSKs." That is good advice, but not really part of the definition of the definition of SEP, is it? > "child-centric resolver" - kill it. Done. And, in case anyone else is reading this far: we still want more review, although the WG finishes today. --Paul Hoffman
- [DNSOP] I-D Action: draft-ietf-dnsop-dns-terminol… internet-drafts
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Tony Finch
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Tony Finch
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… John Dickinson
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Joe Abley
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Joe Abley
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Tony Finch
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… John Dickinson
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Tony Finch
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Andrew Sullivan
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-term… Paul Hoffman