Re: [DNSOP] DNSOPWorking Group Last Call for draft-ietf-dnsop-nsec3-guidance

Wes Hardaker <wjhns1@hardakers.net> Thu, 24 March 2022 22:50 UTC

Return-Path: <wjhns1@hardakers.net>
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 6BA373A0D6F; Thu, 24 Mar 2022 15:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 JUTrPBSzNBOx; Thu, 24 Mar 2022 15:50:43 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (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 016313A0DBE; Thu, 24 Mar 2022 15:50:42 -0700 (PDT)
Received: from localhost (unknown [10.0.0.3]) by mail.hardakers.net (Postfix) with ESMTPA id 6B2B021045; Thu, 24 Mar 2022 15:50:41 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: dnsop <dnsop@ietf.org>, dnsop-chairs <dnsop-chairs@ietf.org>
References: <CADyWQ+HOLf7=hyiJeW5sDAarG7a+tEEBrGvF+FnrjrEqfw9LeA@mail.gmail.com>
Date: Thu, 24 Mar 2022 15:50:41 -0700
In-Reply-To: <CADyWQ+HOLf7=hyiJeW5sDAarG7a+tEEBrGvF+FnrjrEqfw9LeA@mail.gmail.com> (Tim Wicinski's message of "Wed, 23 Mar 2022 19:45:46 -0400")
Message-ID: <yblo81vhsn2.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/WRqxX7fucyqS9tCz5UIySO7i6ew>
Subject: Re: [DNSOP] DNSOPWorking Group Last Call for draft-ietf-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: Thu, 24 Mar 2022 22:50:46 -0000

Tim Wicinski <tjw.ietf@gmail.com> writes:

> With the authors feeling there are no outstanding changes and most people are happy with the current
> version.  So this means it's time:

Note that two small changes have been introduced since -06 were
published, which were just wording related changes.  Here are the diffs:


<    zone owners about good values to select.  Recent in academic studies
<    have shown that NSEC3 hashing provides only provides moderate
<    protection [GPUNSEC3][ZONEENUM].
---
>    zone owners about good values to select.  Recent academic studies
>    have shown that NSEC3 hashing provides only moderate protection
>    [GPUNSEC3][ZONEENUM].

and


<    iteration counts greater than 0, which will likely resulting in
<    returning a SERVFAIL to the client when no processed responses are
---
>    iteration counts greater than 0, which will likely result in
>    returning a SERVFAIL to the client when no acceptable responses are

-- 
Wes Hardaker
USC/ISI