IETF Logo Mail Archive

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

Bill Woodcock <woody@pch.net> Fri, 22 May 2020 21:59 UTC

Return-Path: <woody@pch.net>
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 654B73A0BEA for <dnsop@ietfa.amsl.com>; Fri, 22 May 2020 14:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ba9dyT5vTVRr for <dnsop@ietfa.amsl.com>; Fri, 22 May 2020 14:59:21 -0700 (PDT)
Received: from mail.pch.net (keriomail.pch.net [206.220.231.84]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19A293A0BE5 for <dnsop@ietf.org>; Fri, 22 May 2020 14:59:20 -0700 (PDT)
X-Footer: cGNoLm5ldA==
Received: from [10.19.48.14] ([69.166.14.2]) by mail.pch.net (Kerio Connect 9.2.7 patch 3) with ESMTPS (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)) for dnsop@ietf.org; Fri, 22 May 2020 14:59:15 -0700
From: Bill Woodcock <woody@pch.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_B9E4D03D-2683-48E6-AB67-F47BE1E75872"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Fri, 22 May 2020 23:59:11 +0200
References: <CAKr6gn0Fqk0qNCs5wbptN+rWRBQgBKom4iiudW0V1Xrj3fmE7Q@mail.gmail.com> <2487238.otjEU5M4pH@linux-9daj>
To: dnsop WG <dnsop@ietf.org>
In-Reply-To: <2487238.otjEU5M4pH@linux-9daj>
Message-Id: <51096CAB-97BC-496D-8322-40BEB0F7334E@pch.net>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vz4Vv4TC09aLpis-q4reSWbvK8M>
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 21:59:23 -0000


> On May 22, 2020, at 3:38 AM, Paul Vixie <paul@redbarn.org> wrote:
> 
> On Friday, 22 May 2020 00:55:34 UTC George Michaelson wrote:
>> My Colleague George Kuo asked me for definitions of public DNS
>> service. not "public DNS" but the trigram "public DNS service"
>> 
>> Colloquially we understand this reasonably well. It is in the space of
>> what Google, quad9, CloudFlare and others do. The various clean DNS
>> feeds people subscribe to, it is the functional role of a recursive,
>> but to the public, yet somehow not the bad one of an open DNS resolver
>> being abused to do DDoS: its the conscious service offering of a
>> recursive/cache/forwarder in the public view, a declared intent.
> 
> 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.

                                -Bill

v2.31.3 | Report a Bug | By Email | System Status