Re: [DNSOP] Call for Adoption: draft-hardaker-dnsop-nsec3-guidance
Tony Finch <dot@dotat.at> Tue, 11 May 2021 21:34 UTC
Return-Path: <fanf2@hermes.cam.ac.uk>
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 A63533A2743 for <dnsop@ietfa.amsl.com>; Tue, 11 May 2021 14:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Ju-zh7sPe9c0 for <dnsop@ietfa.amsl.com>; Tue, 11 May 2021 14:33:59 -0700 (PDT)
Received: from ppsw-43.csi.cam.ac.uk (ppsw-43.csi.cam.ac.uk [131.111.8.143]) (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 EDD2E3A2742 for <dnsop@ietf.org>; Tue, 11 May 2021 14:33:58 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from [90.251.241.247] (port=50695 helo=milebook.lan) by ppsw-43.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpsa (PLAIN:fanf2) (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1lga0e-000xqc-pN (Exim 4.94.2) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 11 May 2021 22:33:44 +0100
Date: Tue, 11 May 2021 22:33:44 +0100
From: Tony Finch <dot@dotat.at>
To: Wes Hardaker <wjhns1@hardakers.net>
cc: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>, DNSOP Working Group <dnsop@ietf.org>
In-Reply-To: <yblwns5ckje.fsf@w7.hardakers.net>
Message-ID: <d72220fe-8a6b-d8e6-8b3-1749faddb4fb@dotat.at>
References: <bfaa3ab3-3d96-dcec-a175-5803de03d852@NLnetLabs.nl> <eb62e04b-2511-ac14-b2e1-c29eab64acfc@nic.cz> <yblwns5ckje.fsf@w7.hardakers.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-612234672-1620768824=:6671"
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/HvDNtwsweW6goD1A6XpstcTGPkU>
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: Tue, 11 May 2021 21:34:04 -0000
Wes Hardaker <wjhns1@hardakers.net> wrote: > Vladimír Čunát <vladimir.cunat+ietf@nic.cz> writes: > > > 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"? The draft is operational advice, so I think the relevant advice here is that if you are signing your zone with sloooow NSEC3 parameters, make sure your secondaries are willing to serve such a zone first. Tony. -- f.anthony.n.finch <dot@dotat.at> https://dotat.at/ Fair Isle: Cyclonic becoming northeast, 4 to 6. Moderate or rough. Rain, fog patches. Moderate or good, occasionally very poor.
- [DNSOP] Call for Adoption: draft-hardaker-dnsop-n… Benno Overeinder
- Re: [DNSOP] [Ext] Call for Adoption: draft-hardak… Paul Hoffman
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Tony Finch
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Daniel Migault
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Vladimír Čunát
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Peter van Dijk
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Olafur Gudmundsson
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Brian Dickson
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Paul Wouters
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Paul Wouters
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Matthijs Mekking
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Roy Arends
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Wes Hardaker
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Wes Hardaker
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Tony Finch
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Vladimír Čunát
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Wes Hardaker
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Puneet Sood
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Loganaden Velvindron
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Benno Overeinder
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Tony Finch
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Wes Hardaker
- Re: [DNSOP] Call for Adoption: draft-hardaker-dns… Wes Hardaker