Re: [dns-privacy] Call for adoption: draft-vandijk-dprive-ds-dot-signal-and-pin

Peter van Dijk <peter.van.dijk@powerdns.com> Fri, 25 September 2020 20:06 UTC

Return-Path: <peter.van.dijk@powerdns.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 C41AB3A08BA for <dns-privacy@ietfa.amsl.com>; Fri, 25 Sep 2020 13:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.398, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 4drS4Of_-8di for <dns-privacy@ietfa.amsl.com>; Fri, 25 Sep 2020 13:06:28 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 64B163A08B9 for <dns-privacy@ietf.org>; Fri, 25 Sep 2020 13:06:28 -0700 (PDT)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx4.open-xchange.com (Postfix) with ESMTPS id 8DDF26A241; Fri, 25 Sep 2020 22:06:26 +0200 (CEST)
Received: from plato (84-81-54-175.fixed.kpn.net [84.81.54.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 618083C039B; Fri, 25 Sep 2020 22:06:26 +0200 (CEST)
Message-ID: <09a50aec9b8527d43e475bd83b242cde39370c9e.camel@powerdns.com>
From: Peter van Dijk <peter.van.dijk@powerdns.com>
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Date: Fri, 25 Sep 2020 22:06:25 +0200
In-Reply-To: <alpine.LRH.2.23.451.2008112138490.99493@bofh.nohats.ca>
References: <4b3271ee-e796-3102-1ead-d1f9a3137514@innovationslab.net> <alpine.LRH.2.23.451.2008112138490.99493@bofh.nohats.ca>
Organization: PowerDNS.COM B.V.
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5-1.1
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/cZUUokFYL06R_dA57nPrKuHYqEY>
Subject: Re: [dns-privacy] Call for adoption: draft-vandijk-dprive-ds-dot-signal-and-pin
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: Fri, 25 Sep 2020 20:06:30 -0000

Hi Paul,

On Tue, 2020-08-11 at 21:43 -0400, Paul Wouters wrote:
> I am against adoption for two reasons. The draft as it currently is,
> requires that domain name owners and nameserver hosting administrators
> synchronise their nameserver TLS keys. This is impossible to do at
> scale.

For various reasons, also unrelated to this draft, I hope that syncing
problem gets solved some day!

> Second, this method introduces a possible national MITM by the TLD being
> able to put in TLD wide DS records that might be published against the
> wishes of the childen within the TLD. A protection mechanism via the child
> confirming the parent record with a CDS record would address this concern.

I saw no appetite for that from other WG participants, which is why
this has not made it to the text, but I'm still not opposed to it.

> I truly wish the idea would work. And I still believe a DNSKEY bit on
> the DNSKEY to signal encrypted DNS availability would be worth pursuing.

As I said before, if this is the contribution that makes some other
draft work, I'll also be happy :)

Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/