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

Paul Vixie <paul@redbarn.org> Sat, 23 May 2020 02:46 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 0387A3A0EE8 for <dnsop@ietfa.amsl.com>; Fri, 22 May 2020 19:46:54 -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=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 rV0xJAi1Q6VC for <dnsop@ietfa.amsl.com>; Fri, 22 May 2020 19:46:52 -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 6655E3A0E2E for <dnsop@ietf.org>; Fri, 22 May 2020 19:46:52 -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 8B87EB074A; Sat, 23 May 2020 02:46:51 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: dnsop WG <dnsop@ietf.org>
Cc: Bill Woodcock <woody@pch.net>
Date: Sat, 23 May 2020 02:46:50 +0000
Message-ID: <16919731.mxCJBW68yc@linux-9daj>
Organization: none
In-Reply-To: <51096CAB-97BC-496D-8322-40BEB0F7334E@pch.net>
References: <CAKr6gn0Fqk0qNCs5wbptN+rWRBQgBKom4iiudW0V1Xrj3fmE7Q@mail.gmail.com> <2487238.otjEU5M4pH@linux-9daj> <51096CAB-97BC-496D-8322-40BEB0F7334E@pch.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/aexZYYMvQVtWpNG_MNEYNES3WRI>
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: Sat, 23 May 2020 02:46:54 -0000

On Friday, 22 May 2020 21:59:11 UTC Bill Woodcock wrote:
> > On May 22, 2020, at 3:38 AM, Paul Vixie <paul@redbarn.org> wrote:
> > ...
> > 
> > these services aren't public in any way, and should not be described as
> > public. they are operated privately for private purposes
> 
> True of Google and Cloudflare, not true of Quad9.
> 
> > a county park is public. anycast RDNS is a business.
> 
> Again, true of Google and Cloudflare, but not true of Quad9.

there may be a distinction, but not a difference. ibm and pch and the other 
backers of quad9, and the security industry partners who participate, have 
solid personal reasons, just as google and cloudflare and opendns do, for 
running an open recursive name service. open recursion is novel concept, only 
25 years or so old, and the internet functioned fine without it, and as shown 
by the PiHole project and others, the internet can still function fine without 
it. as much as the interested parties have bent the narrative toward their 
interests, open recursion remains a private service run for private reasons, 
and the name "public" would be misleading in the extreme.

-- 
Paul