IETF Logo Mail Archive

Re: [dns-privacy] [Ext] next steps for draft-opportunistic-adotq

Jim Reid <jim@rfc1035.com> Wed, 24 March 2021 14:56 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0443A3A2E17 for <dns-privacy@ietfa.amsl.com>; Wed, 24 Mar 2021 07:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=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 et2xW-qicA3b for <dns-privacy@ietfa.amsl.com>; Wed, 24 Mar 2021 07:56:07 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 572B33A2E15 for <dns-privacy@ietf.org>; Wed, 24 Mar 2021 07:56:06 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id ACC882420C28; Wed, 24 Mar 2021 14:56:02 +0000 (UTC)
From: Jim Reid <jim@rfc1035.com>
Message-Id: <C6C1D17A-CE7B-4189-BC63-69FD2C5E9FD8@rfc1035.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D451FB4C-5895-44A5-875C-D16659572E50"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
Date: Wed, 24 Mar 2021 14:56:01 +0000
In-Reply-To: <A45C3DAA-C910-427A-9359-E38570D274D3@pch.net>
Cc: dns-privacy@ietf.org
To: Bill Woodcock <woody@pch.net>
References: <A68841F4-B7CC-4AAC-BC9F-0961ADF2C8FA@rfc1035.com> <DF40D081-1EA8-4E92-BB67-2966E32688DE@nohats.ca> <2E5B5290-CBBE-4F20-AD89-0BDCE3B2AA7F@pch.net> <DB196A4D-2720-4C9E-8A66-C314AB16BA0E@rfc1035.com> <A45C3DAA-C910-427A-9359-E38570D274D3@pch.net>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/uay_03mTCSaP96BAZoS3PVsPPbA>
Subject: Re: [dns-privacy] [Ext] next steps for draft-opportunistic-adotq
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2021 14:56:12 -0000


> On 24 Mar 2021, at 14:10, Bill Woodcock <woody@pch.net> wrote:
> 
> How many mqps are necessary to have a voice in your vision of multistakeholderism?

I don’t know.

I think/hope we have the same vision of multistakeholderism. If not, that’s a conversation for another time and place.

> Or, viewed from the other end of the spectrum, are you suggesting that only the two or three largest TLDs out of two thousand, count?

No, of course not. Any TLD or authoritiev server is welcome to do whatever it wants here. Even if I think it’s a bad idea. Which could very well be an incentive for others to deploy.

What I am saying is this WG needs to think more about the impacts* of Do[TH] on busy authoritative servers (not just TLDs). And maybe for busy recursive servers too. Some of us were talking about that just over an hour ago in the RIPE DNS WG:

https://www.ripe.net/participate/ripe/wg/active-wg/dns/remote-sessions/2021-03-24-ripe-dns-wg-hollenbeck-balanced-dns-information-protection-strategy.pdf

AFAICT the WG hasn’t yet considered any of the risk analysis issues identified in Scott’s presentation.

* Those impacts BTW go beyond query rates or TLS session management.

v2.23.0 | Report a Bug | By Email