Re: [DNSOP] Call for Adoption: draft-hardaker-dnsop-nsec3-guidance

Peter van Dijk <peter.van.dijk@powerdns.com> Mon, 10 May 2021 19:06 UTC

Return-Path: <peter.van.dijk@powerdns.com>
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 55DF43A277C for <dnsop@ietfa.amsl.com>; Mon, 10 May 2021 12:06:33 -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 rmrL_O9kmWLq for <dnsop@ietfa.amsl.com>; Mon, 10 May 2021 12:06:28 -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 B46D33A2779 for <dnsop@ietf.org>; Mon, 10 May 2021 12:06:28 -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 76BDF6A0D4; Mon, 10 May 2021 21:06:23 +0200 (CEST)
Received: from plato ([84.81.54.175]) by imap.open-xchange.com with ESMTPSA id OKo+HC+EmWB6GgAA3c6Kzw (envelope-from <peter.van.dijk@powerdns.com>); Mon, 10 May 2021 21:06:23 +0200
Message-ID: <37c86b6baaf412f2dd73618795a8b92c383b5c01.camel@powerdns.com>
From: Peter van Dijk <peter.van.dijk@powerdns.com>
To: DNSOP Working Group <dnsop@ietf.org>
Date: Mon, 10 May 2021 21:06:23 +0200
In-Reply-To: <bfaa3ab3-3d96-dcec-a175-5803de03d852@NLnetLabs.nl>
References: <bfaa3ab3-3d96-dcec-a175-5803de03d852@NLnetLabs.nl>
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/dnsop/0orouP8eNBJGoojcn5wlT2YGzMU>
Subject: Re: [DNSOP] Call for Adoption: draft-hardaker-dnsop-nsec3-guidance
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: Mon, 10 May 2021 19:06:34 -0000

On Mon, 2021-05-10 at 10:55 +0200, Benno Overeinder wrote:
> The draft is available here: 
> https://datatracker.ietf.org/doc/draft-hardaker-dnsop-nsec3-guidance/.
> 
> Please review this draft to see if you think it is suitable for adoption 
> by DNSOP, and comments to the list, clearly stating your view.
> 
> Please also indicate if you are willing to contribute text, review, etc.

I support adoption of this draft, and am willing to review and
contribute text (in fact, I have already done so at small scale).

I think the draft really deserves some text on when not to use NSEC3 at
all (i.e. when to pick NSEC instead) and I would be happy to contribute
that too, if nobody beats me to it.

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