Re: [DNSOP] [Ext] Benjamin Kaduk's No Objection on draft-ietf-dnsop-terminology-bis-13: (with COMMENT)

Paul Hoffman <paul.hoffman@icann.org> Tue, 28 August 2018 18:17 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20878130E14; Tue, 28 Aug 2018 11:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 LAqh4wOOrncd; Tue, 28 Aug 2018 11:17:15 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89C5D130E07; Tue, 28 Aug 2018 11:17:15 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 28 Aug 2018 11:17:13 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Tue, 28 Aug 2018 11:17:13 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: The IESG <iesg@ietf.org>, "draft-ietf-dnsop-terminology-bis@ietf.org" <draft-ietf-dnsop-terminology-bis@ietf.org>, "suzworldwide@gmail.com" <suzworldwide@gmail.com>, "dnsop-chairs@ietf.org" <dnsop-chairs@ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [Ext] Benjamin Kaduk's No Objection on draft-ietf-dnsop-terminology-bis-13: (with COMMENT)
Thread-Index: AQHUPlmW64fhiiUClkGz9CdLQXvA+aTV70AA
Date: Tue, 28 Aug 2018 18:17:12 +0000
Message-ID: <B433A884-808D-4F3C-9210-E911D88ECE70@icann.org>
References: <153541075520.29995.11362089145955536527.idtracker@ietfa.amsl.com>
In-Reply-To: <153541075520.29995.11362089145955536527.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B35468DE2DA933409BF76EDC5535604D@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/7UCukfBNsdi3MEXeu7ObeBCCYTg>
Subject: Re: [DNSOP] [Ext] Benjamin Kaduk's No Objection on draft-ietf-dnsop-terminology-bis-13: (with COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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, 28 Aug 2018 18:17:17 -0000

On Aug 27, 2018, at 3:59 PM, Benjamin Kaduk <kaduk@mit.edu>; wrote:
> First off, thank you all for the effort that went into this document -- it's
> quite helpful to have a central resource to refer to.
> 
> I agree with Mirja about further clarity for the 2308 updates being nice, and
> about the "primary master" definition's clarification.  (The latter seems like
> it would meet a DISCUSS criterion, as internal inconsistency makes it difficult
> to have a clear specification.  But it would be absurd to apply it here when
> the fix is clear.)

We'll fix it based on what Warren tells us comes out of the telechat. This is edge-case-y enough where we need more specific input from the IESG. 

> I appreciate that "privacy of names" and "privacy of data associated with
> names" are called out as potential facets of a naming system to consider, but I
> would like to understand better why they are not given more treatment in this
> document.  The surrounding text seems to imply that they are not needed to
> describe the DNS and that a pure lexicon need not explore the privacy
> considerations of the terms being defined; is this correct, and was there much
> discussion on this question?

There was no discussion of this at all. The description you are referring to was added in the -04 draft in January 2017, and was unchanged since. 

> In a similar vein, it was a little surprising to only see the facets be
> expounded upon for the global DNS and not the other related naming systems,
> though it's unclear that there would be much non-overlap for the other systems
> considered.

The document is about definitions that apply mostly to the global DNS. The facet list was added in hopes that other documents that describe other naming systems can use the facets (or maybe additional ones) to help compare those naming systems with the global DNS.

> In Section 6:
> 
> I'm a little confused about the interaction between "stealth server"
> and "hidden master" -- if a hidden master is a stealth server, it is "like
> a slave" and would thus be expected to get its configuration from yet
> another master?  But this doesn't jibe with being listed as the MNAME.
> I accept that DNS terminology is a complicated area and there may not
> be a right answer, of course.

There might not be *one* right answer. Note that this definition appeared in an RFC very late in the development of the DNS, even though the functionality had been widely used for over a decade.

> The "privacy-enabling DNS server" definition seems too narrowly scoped to
> particular existing technologies as opposed to describing the properties
> provided (or mentioning the possibility for future protocols to be
> included).  

It is a quote from an existing RFC, and we tried to rely on such quotes over our own definitions.

> Is a DNS-over-HTTP server "privacy-enabling"?

Assuming you mean DNS-over-HTTPS, it probably will be in the future.

>  How about
> DNS-over-QUIC?

Some of us are hoping that that will not exist other than as DNS-over-HTTPS-over-QUIC (DoHQ).

> Section 8
> 
> Interesting to see the term "Opt-Out zone" used but not defined in this
> document.  (No action needed, and I do see the definition of "Opt-Out".)

RFC 5155 does define it as "Opt-Out zone:  a zone with at least one Opt-Out NSEC3 RR.", but the term is not commonly used.

> Finally, I am somewhat sympathetic to the indications that this document may
> (also) be appropriate as Informational; I look forward to seeing how that
> discussion unfolds.

So are the authors. :-)

--Paul Hoffman