Re: [DNSOP] definitions of "public DNS Service"

Paul Vixie <paul@redbarn.org> Mon, 25 May 2020 15:34 UTC

Return-Path: <paul@redbarn.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 234093A0DAE for <dnsop@ietfa.amsl.com>; Mon, 25 May 2020 08:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 U2oIGPothcjK for <dnsop@ietfa.amsl.com>; Mon, 25 May 2020 08:34:48 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB1B43A0D90 for <dnsop@ietf.org>; Mon, 25 May 2020 08:34:41 -0700 (PDT)
Received: from linux-9daj.localnet (vixp1.redbarn.org [24.104.150.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 465FFB074A; Mon, 25 May 2020 15:34:39 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: Tony Finch <dot@dotat.at>, dnsop@ietf.org
Cc: dnsop WG <dnsop@ietf.org>, George Kuo <george@apnic.net>, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
Date: Mon, 25 May 2020 15:34:38 +0000
Message-ID: <3261748.qd5D8ZHc2X@linux-9daj>
Organization: none
In-Reply-To: <189033692.11260.1590397577578@appsuite-gw1.open-xchange.com>
References: <CAKr6gn0Fqk0qNCs5wbptN+rWRBQgBKom4iiudW0V1Xrj3fmE7Q@mail.gmail.com> <alpine.DEB.2.20.2005221744110.25154@grey.csi.cam.ac.uk> <189033692.11260.1590397577578@appsuite-gw1.open-xchange.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/NQmwMXtxpiAB6REiGENcBaX2CCg>
Subject: Re: [DNSOP] definitions of "public DNS Service"
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 25 May 2020 15:34:58 -0000

On Monday, 25 May 2020 09:06:17 UTC Vittorio Bertola wrote:
> > Il 22/05/2020 18:59 Tony Finch <dot@dotat.at> ha scritto:
> > 
> > I think despite what Paul H. said this is already covered in RFC 8499:
> >    Open resolver:  A full-service resolver that accepts and processes
> >    
> >       queries from any (or nearly any) client.  This is sometimes also
> >       called a "public resolver", although the term "public resolver" is
> >       used more with open resolvers that are meant to be open, as
> >       compared to the vast majority of open resolvers that are probably
> >       misconfigured to be open.  Open resolvers are discussed in
> >       [RFC5358].
> 
> I think this definition is good - perhaps what we need is just to agree to
> use "open resolver" instead of "public resolver".
> 
> If you wanted to convey the nuance that it's not just open, but open on
> purpose and meant to attract users from the entire Internet, you could add
> "global": "open global resolver".
> 
> Or, as an alternative, you could use the term "platform", which is
> increasingly being used to identify Internet-wide global companies that
> provide multiple consumer services. "Platform resolver" would also convey
> the idea that these resolvers are going to be distributed and ubiquitously
> available. "Cloud resolver" could have a similar meaning.

not that it will matter, but i find those names unprovocative and descriptive.

> But, as for any terminological bikeshedding effort, you cannot force others
> to use the "most correct" term, so it's possibly just a waste of time.

i don't think we'll be able to improve on dagon's "more correct" suggestion:

> I suggest: "distant resolver outside of the user's policy oversight".

-- 
Paul