Re: [dns-privacy] [Fwd: New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-00.txt]

Paul Wouters <paul@nohats.ca> Fri, 29 May 2020 15:25 UTC

Return-Path: <paul@nohats.ca>
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 E9A373A0433 for <dns-privacy@ietfa.amsl.com>; Fri, 29 May 2020 08:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 Hntchyo_C_VB for <dns-privacy@ietfa.amsl.com>; Fri, 29 May 2020 08:25:43 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 6B0F43A0C40 for <dns-privacy@ietf.org>; Fri, 29 May 2020 08:25:43 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 49YT0j1FDTzDkT; Fri, 29 May 2020 17:25:41 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1590765941; bh=aNDnKJQjrXg9naW6eXrpnEcf4+cC2H3hPy37OZaQ76k=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=oGqM7kC+M71WJu9fqcrf/SOgMQRxWXy+YUorFpO+4/xBrPHBSY4rFu2InjoUxQ5Qk GnZj/KQwQLRkCv6fTviaOEUueLaDZ27vlSs+/N2jNhztruyV37Qo65OYnP6BgsU5XZ vy1/mGq5GuSYiv5qIRauMpiOxoVA+VOhmxI4ICoc=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id bU8LyUhvK-Ti; Fri, 29 May 2020 17:25:39 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 29 May 2020 17:25:39 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 1A4376020EE7; Fri, 29 May 2020 11:25:38 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 1644A66B7C; Fri, 29 May 2020 11:25:38 -0400 (EDT)
Date: Fri, 29 May 2020 11:25:38 -0400
From: Paul Wouters <paul@nohats.ca>
To: Peter van Dijk <peter.van.dijk@powerdns.com>
cc: dns-privacy@ietf.org
In-Reply-To: <10319d748a2ecc2c4e8cad7b8fb545a1f65ff925.camel@powerdns.com>
Message-ID: <alpine.LRH.2.21.2005291115060.31882@bofh.nohats.ca>
References: <158987990316.29446.4343920282978207647@ietfa.amsl.com> <a15e2d1df86820f2483516662d3712d8a60161cd.camel@powerdns.com> <alpine.LRH.2.21.2005191134560.13722@bofh.nohats.ca> <ec6bc9248179a9ab56ea490f82b14c7e90ffe819.camel@powerdns.com> <alpine.LRH.2.21.2005241222410.4172@bofh.nohats.ca> <77f7a9c38c6bd0a059679a7ab3027b4da9005512.camel@powerdns.com> <alpine.LRH.2.21.2005241710490.10453@bofh.nohats.ca> <5653e4dd2ab6daa648387808a3ac04e088bbc89b.camel@powerdns.com> <CAHbrMsDKQqfnoty+cRa5bJ=zVkONYTbFf-=8hzAj0E7pWeFXug@mail.gmail.com> <a8f44365b9b3a079753f8286cc19fbb241996bf5.camel@powerdns.com> <CAHbrMsAhKB9=nPfnmYzT-tu8-XMYNwyyuYM3T9106iWNzPpDAQ@mail.gmail.com> <alpine.LRH.2.21.2005272118320.18445@bofh.nohats.ca> <10319d748a2ecc2c4e8cad7b8fb545a1f65ff925.camel@powerdns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/fCMn2wwlg5iISFD25-pKNk0SmLM>
Subject: Re: [dns-privacy] [Fwd: New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-00.txt]
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, 29 May 2020 15:25:45 -0000

On Fri, 29 May 2020, Peter van Dijk wrote:

> On Wed, 2020-05-27 at 21:27 -0400, Paul Wouters wrote:
>> It would make everything a LOT cleaner and we got no bogus
>> DNSKEY records to ignore in our DNSSEC validation path.
>
> What bogus DNSKEY records?

It really all depends on what registry systems you want to support. We
have some combo's:

- Takes any DS    --> give our DS with DoT info embedded
- Takes DS, but verifies it is a real DNSKEY at the child --> we create bogus DNSKEY matching our DS request
- Takes any CDS   --> Put our info in zone as CDS 
- Takes CDS, but verifies it is a real DNSKEY at the child --> we create bogus DNSKEY matching our CDS request
- Takes DNSKEY, only does syntax checks ---> we dont need to publish anything
- Takes DNSKEY, verifies it lives in child --->  we create bogus DNSKEY
- Takes DNSKEY, but verifies it is a supported algorithm --> we have to convince them to support our pseudo alg
- Takes any CDNSKEY  ---> we only need to publish as CDNSKEY, not DNSKEY
- Takes CDNSKEY but verifies it lives in child as DNSKEY ---> we need to publish CDNSKEY and bogus DNSKEY

When I say bogus I mean "not a DNSKEY used for DNSSEC validation of DNS data"

Paul