Re: [DNSOP] comments on draft-ietf-dnsop-dns-terminology-03
Casey Deccio <casey@deccio.net> Tue, 14 July 2015 16:26 UTC
Return-Path: <casey@deccio.net>
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 65A141A21AD for <dnsop@ietfa.amsl.com>; Tue, 14 Jul 2015 09:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 dLuWFGXEpRB9 for <dnsop@ietfa.amsl.com>; Tue, 14 Jul 2015 09:26:01 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::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 BE4091A1BC8 for <dnsop@ietf.org>; Tue, 14 Jul 2015 09:26:00 -0700 (PDT)
Received: by iecuq6 with SMTP id uq6so15032892iec.2 for <dnsop@ietf.org>; Tue, 14 Jul 2015 09:26:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=deccio.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XZBEMZXncdBNHmH2o/ftWJW3YwDNH16I3yI2NxwwKIg=; b=bD6ywmBT/hDf2NkirwDmCtdf3/0O37x23v9FRBxPhjgHCbrctxyw114C2yVKWFBljB 7kS50IOVYgygktHsY5tJqJPC8kr7YfB1p+in2q9Y1h8F1gyDx3pA5URq+Z0mdzHX2MmN GTRyizS7zqF7FiVKtrl2rOCRMeii/vFlwWj7s=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XZBEMZXncdBNHmH2o/ftWJW3YwDNH16I3yI2NxwwKIg=; b=Jg2BXtBpty5BA19VfiN6P43m/t+prALLaQ0H8o3XtjPfKkxn+JpKpYuETzwfFuIvah liGiSSN7HwGDWz1Avmqw4Fo9cMExwQRzPkjRbf1QwcHhMsJ2pMDZowFrHhMmic/VnD+w pvhYZGUfu8QLKQPbMKt1RWME6YHUgXy61IqNoJ4CcK3AIMkqXxKSPA/70omphjFHHHA4 mME7s1rDjSLvL1yWI+2uKx4DSn7TynwAICYxgGOP/DOTRcRvbC6xoL0MnCMq8nKMTuEc g/FitIeUYGPqUfEC5T2bckdXOu37rxGBFWnpZ7sKX8pfffxTVvWpZGyQvh5gytoLraPd 7vRQ==
X-Gm-Message-State: ALoCoQlIOv0T5mvLWK+gTdgXVkIuhKLI3SOcZfr/OL0JLAAJpnedloGmP0nDLkFzI+sX4zfIT2iR
MIME-Version: 1.0
X-Received: by 10.50.72.98 with SMTP id c2mr4577563igv.72.1436891160155; Tue, 14 Jul 2015 09:26:00 -0700 (PDT)
Received: by 10.50.240.17 with HTTP; Tue, 14 Jul 2015 09:26:00 -0700 (PDT)
In-Reply-To: <83A64168-3510-4E0B-AA23-54547C05990B@vpnc.org>
References: <CAEKtLiQWPM6yJZZASQ5k1bzsbHc3jv5FRsJ6ifgUdj9TRLCmRg@mail.gmail.com> <83A64168-3510-4E0B-AA23-54547C05990B@vpnc.org>
Date: Tue, 14 Jul 2015 12:26:00 -0400
Message-ID: <CAEKtLiSb1at+8oipBmK3K69k4jcvBuVKHQ-=sTjvuy-YGFqsLg@mail.gmail.com>
From: Casey Deccio <casey@deccio.net>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="047d7bdc0fb62eb581051ad84bbd"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/MMlGo0udm2vq6NTbJBoflD5yNLE>
Cc: dnsop WG <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: Tue, 14 Jul 2015 16:26:03 -0000
On Tue, Jul 14, 2015 at 12:00 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote: > On 13 Jul 2015, at 14:20, Casey Deccio wrote: > > 1. (stylistic) There are a number of definitions that quote terminology >> and >> then parenthetically state "quoted from". It seems more intuitive, >> precise, and consistent to mark quoted text using quotation marks instead, >> as in other definitions. Some examples (there are probably more): >> - Canonical name >> - CNAME >> - NODATA >> - Resolver >> > > Yes, the document does not use a consistent style to say what is quoted. I > did this to make it more readable. In specific, I think using quotation > marks will make it less readable. If there are specific places where the > style makes it unclear what is quoted, we should correct that, but trying > to be completely consistent will make some parts harder to read. I'm not sure how adding quotation marks makes things less readable. If we're saying that we're quoting text, I'd really like to know what the text is that we're quoting. If we're paraphrasing, no quotation marks are necessary. This is a fairly standard practice. > > 3. The current text for referral is incomprehensible. I suggest the > following: > > A response "generated using local data" which contains no answer but rather > includes "name servers which have zones which are closer ancestors to the > name than the server sending the reply" (RFC 1034, sections 4.1 and > 4.3.1). These name servers take the form of NS records in the authority > section of the response and come from the "NS RRs marking cuts along the > bottom of a zone" when "a match would take us out of the authoritative > data" (RFC 1034, section 4.3.2). Referrals are only associated with > non-recursive (i.e., iterative) queries (RFC 1034 section 4.3.1). In > general, a referral is a way for a server to send an answer saying that the > server does not know the answer, but knows where the resolver should direct > its query should be directed in order to eventually get an answer. > > Historically, many authoritative servers answered with a referral to the > root zone when queried for a name for which they were not authoritative, > but this practice has declined. > > See also Glue Records. > > This is still contentious, and I think it really should be deferred to the > -bis document for longer discussion and hopefully consensus. > Could you help me understand which parts of the (reworded) paragraph are contentious? Independent of the current intended definitions for "referral", the current text really is unreadable and (in my opinion) unsuitable for an initial document. 4. In the definition of RRset, the bit about TTLs needing to be the same >> seems out of place for this terminology document. That is an operational >> requirement. >> > > Disagree. To some people, TTLs are operational, to others they are part of > the master file format. For the latter, this sameness applies to the > definition. What I am saying is that whether the TTLs are the same (correct) or the TTLs are different (incorrect), it doesn't change the definition of RRset, which is the set of RRs with the same name/class/type. Therefore the requirement that the TTL be the same is not a useful statement for the definitions doc, whether it's operational or standards-based. Regards, Casey
- [DNSOP] comments on draft-ietf-dnsop-dns-terminol… Casey Deccio
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Chris Thompson
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Casey Deccio
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Tony Finch
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Tim Wicinski
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Casey Deccio
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… John Dickinson
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… John Dickinson
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Stephane Bortzmeyer
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Andrew Sullivan
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Andrew Sullivan
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Paul Hoffman
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Tim Wicinski
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Shane Kerr
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Sara Dickinson
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Warren Kumari
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Andrew Sullivan
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Suzanne Woolf
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Jim Reid
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… Warren Kumari
- Re: [DNSOP] comments on draft-ietf-dnsop-dns-term… joel jaeggli