Re: [dns-privacy] New draft-ietf-dprive-unauth-to-authoritative and draft-pp-dprive-common-features

Peter van Dijk <peter.van.dijk@powerdns.com> Mon, 24 May 2021 20:21 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 2CA8C3A34E4 for <dns-privacy@ietfa.amsl.com>; Mon, 24 May 2021 13:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 1DoIQHgUXgEw for <dns-privacy@ietfa.amsl.com>; Mon, 24 May 2021 13:21:11 -0700 (PDT)
Received: from mx3.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 8BBB93A34E9 for <dprive@ietf.org>; Mon, 24 May 2021 13:21:11 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [84.81.54.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id D8F406A0D7; Mon, 24 May 2021 22:21:07 +0200 (CEST)
Received: from plato ([84.81.54.175]) by imap.open-xchange.com with ESMTPSA id kQMvNLMKrGCNfgAA3c6Kzw (envelope-from <peter.van.dijk@powerdns.com>); Mon, 24 May 2021 22:21:07 +0200
Message-ID: <770330e721a2192ce32f24403bb92fd9a1c2a181.camel@powerdns.com>
From: Peter van Dijk <peter.van.dijk@powerdns.com>
To: "dprive@ietf.org" <dprive@ietf.org>
Date: Mon, 24 May 2021 22:21:07 +0200
In-Reply-To: <B27C4F2E-D5AF-428B-BBD1-A57E7D676BD5@icann.org>
References: <B27C4F2E-D5AF-428B-BBD1-A57E7D676BD5@icann.org>
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/se6W_nv62oE0Tt4-3x_Yxp2V93o>
Subject: Re: [dns-privacy] New draft-ietf-dprive-unauth-to-authoritative and draft-pp-dprive-common-features
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: Mon, 24 May 2021 20:21:16 -0000

Hello DNSOP,

On Wed, 2021-05-19 at 16:58 +0000, Paul Hoffman wrote:
> Greetings again. Peter and I have revised draft-ietf-dprive-unauth-to-authoritative and draft-pp-dprive-common-features based on recent mailing list traffic. One major change is that we realized that we could move even more sections from unauth-to-authoritative to common-features because they would apply to the fully-authenticated use case. Please review them to see if you agree.
> 
> If people like the idea of us splitting out common features, it would be good if it too became a WG document, particularly to help focus the discussions on the unauthenticated and fully-authenticated use cases.
> 
> --Paul Hoffman and Peter van Dijk
> 
> https://www.ietf.org/archive/id/draft-pp-dprive-common-features-01.txt
> https://www.ietf.org/archive/id/draft-ietf-dprive-unauth-to-authoritative-01.txt

A friendly ping - we moved a bunch of text from our adopted draft to the 'common' draft, so that 'discovery' and 'security properties' can be discussed separately. We think this even makes sense if the adox draft does not get adopted today, because it (or some other draft with stronger security properties than our unauth draft) might get adopted in the future.

So, chairs, can you please think about adopting draft-pp-dprive-common-features even before the adox draft is adopted?

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