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

Tony Finch <dot@dotat.at> Fri, 22 May 2020 16:59 UTC

Return-Path: <dot@dotat.at>
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 7578E3A0C4E for <dnsop@ietfa.amsl.com>; Fri, 22 May 2020 09:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 64_uqmSZn1Fh for <dnsop@ietfa.amsl.com>; Fri, 22 May 2020 09:59:25 -0700 (PDT)
Received: from ppsw-40.csi.cam.ac.uk (ppsw-40.csi.cam.ac.uk [131.111.8.140]) (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 C3A313A0C24 for <dnsop@ietf.org>; Fri, 22 May 2020 09:59:25 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:43790) by ppsw-40.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.138]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1jcB0x-000oW0-l1 (Exim 4.92.3) (return-path <dot@dotat.at>); Fri, 22 May 2020 17:59:19 +0100
Date: Fri, 22 May 2020 17:59:19 +0100
From: Tony Finch <dot@dotat.at>
To: George Michaelson <ggm@algebras.org>
cc: Paul Vixie <paul@redbarn.org>, Andrew Campling <andrew.campling@419.consulting>, dnsop WG <dnsop@ietf.org>, George Kuo <george@apnic.net>
In-Reply-To: <LO2P265MB0573E5674E005493793C6294C2B40@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <alpine.DEB.2.20.2005221744110.25154@grey.csi.cam.ac.uk>
References: <CAKr6gn0Fqk0qNCs5wbptN+rWRBQgBKom4iiudW0V1Xrj3fmE7Q@mail.gmail.com> <2487238.otjEU5M4pH@linux-9daj> <LO2P265MB0573E5674E005493793C6294C2B40@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/5EY3qrsro0Z2LiWA7KaCTma8aKU>
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: Fri, 22 May 2020 16:59:28 -0000

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].

Paul V. is right that "public" is not a good term in this context.
IIRC it was introduced as part of a product name to make it sound less
monopolistic. And just "DNS" is unhelpfully unclear about whether it's a
recursive or authoritative service.

Tony (whose random .sig seems to be trolling).
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
public services of the highest quality