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

Vladimír Čunát <vladimir.cunat+ietf@nic.cz> Thu, 13 May 2021 08:04 UTC

Return-Path: <vladimir.cunat+ietf@nic.cz>
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 544053A2E76 for <dnsop@ietfa.amsl.com>; Thu, 13 May 2021 01:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 lVMSJgwTOfBG for <dnsop@ietfa.amsl.com>; Thu, 13 May 2021 01:04:10 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 674C83A2E74 for <dnsop@ietf.org>; Thu, 13 May 2021 01:04:09 -0700 (PDT)
Received: from [IPv6:2a02:768:2d1c:226::a2e] (unknown [IPv6:2a02:768:2d1c:226::a2e]) by mail.nic.cz (Postfix) with ESMTPSA id 83C62140AE7; Thu, 13 May 2021 10:04:05 +0200 (CEST)
To: DNSOP Working Group <dnsop@ietf.org>, Wes Hardaker <wjhns1@hardakers.net>
References: <bfaa3ab3-3d96-dcec-a175-5803de03d852@NLnetLabs.nl> <eb62e04b-2511-ac14-b2e1-c29eab64acfc@nic.cz> <yblwns5ckje.fsf@w7.hardakers.net>
From: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>
Message-ID: <e5f83f8a-6cf7-426c-706d-e2b04d166927@nic.cz>
Date: Thu, 13 May 2021 10:04:05 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <yblwns5ckje.fsf@w7.hardakers.net>
Content-Type: multipart/alternative; boundary="------------72D50D18F55ECDE500DBA770"
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.102.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-3prt8sYYETMmgTmxHDuM7rSEYY>
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: Thu, 13 May 2021 08:04:14 -0000

On 11/05/2021 18.17, Wes Hardaker wrote:
>> I'd also expect something on limits accepted by secondaries.  And some
>> details are probably up to further discussion (e.g. particular numbers
>> and SERVFAIL), but I don't think such details would block adoption.
> That's certainly an interesting thing to think about, but it starts to
> get in between the relationship of primaries and secondaries.  Is that
> something that should be "standardized"?

I'm not really a good person to ask about these relationships. Anyway, 
if some values were to get standardized to cause SERVFAIL in validators, 
I would expect also secondaries to refuse them, though perhaps that's 
more of an advice or setting expectations (contrary to the validator 
part which I consider an incompatible change in protocol).  Naturally, 
signers should be at least as strict, too, e.g. refuse to go in the 
range that gets standardized to cause a downgrade.