Re: [DNSOP] More input for draft-ietf-dnsop-dnssec-bcp?

Peter Thomassen <peter@desec.io> Tue, 26 April 2022 22:54 UTC

Return-Path: <peter@desec.io>
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 D3DB7C13A8C6 for <dnsop@ietfa.amsl.com>; Tue, 26 Apr 2022 15:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.753
X-Spam-Level:
X-Spam-Status: No, score=-3.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-1.857, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=a4a.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jQvL4PRBIpHK for <dnsop@ietfa.amsl.com>; Tue, 26 Apr 2022 15:54:13 -0700 (PDT)
Received: from mail.a4a.de (mail.a4a.de [IPv6:2a01:4f8:10a:1d5c:8000::8]) (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 DCEDCC1843F6 for <dnsop@ietf.org>; Tue, 26 Apr 2022 15:53:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=a4a.de; s=20170825; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=mFfyKpGuS/gVPpnIqlQSkedor90zUSPxTUi/hwFgFog=; b=vngbsl+U29o1GDeFZFdB9RtUPf hceDCezCMfq4H9E2newRKvCuCcKhWFtOWEAcY+1+zWb7g0QdBiZTPAmZTeFgxtd+RP/++EDuRjiSJ R2qJltlLoiwDBODCDG+pkGQOk6SfVulsVUpAG80jyePdA0OISHQ4rMxFoWbVIq9A05fqydNMaL16Y 1Pj3BKgLzYSKniCZCDzSIcZUwLrCxD9f5EtzdsUs04dscU0rchiFb7/kB9sUgI0bjcgKdboz1d8RH ipgKeYdnUiaILaKSxzRTUJpUp8N0ylEab71swuFE/HLAI5S2dgPPV1z382OX/G5qE0xc+1sc6JPQh AgIaYSmA==;
Received: from 2603-9001-0e08-d96f-3639-29c8-2f55-9aff.inf6.spectrum.com ([2603:9001:e08:d96f:3639:29c8:2f55:9aff]) by mail.a4a.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from <peter@desec.io>) id 1njU47-0003qk-Ju for dnsop@ietf.org; Wed, 27 Apr 2022 00:53:51 +0200
Message-ID: <d82ca1ff-db2f-773c-dee2-345d85cc059d@desec.io>
Date: Wed, 27 Apr 2022 00:53:47 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0
Content-Language: en-US
To: dnsop@ietf.org
References: <02759DA4-45AF-4021-BBD1-B8733CD85CE1@icann.org>
From: Peter Thomassen <peter@desec.io>
In-Reply-To: <02759DA4-45AF-4021-BBD1-B8733CD85CE1@icann.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wH1U3B0B1LRdbOHN6Y7LtAgRMek>
Subject: Re: [DNSOP] More input for draft-ietf-dnsop-dnssec-bcp?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.34
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, 26 Apr 2022 22:54:17 -0000

Hi,

On 4/25/22 23:50, Paul Hoffman wrote:
> Greetings. I posted the -01 about ten days ago, and have not heard anything since then. The chairs indicated that they wanted this fast-tracked, so I'll nudge here for more input, either on the WG mailing list on in the repo (https://github.com/paulehoffman/draft-hoffman-dnssec). If nothing big comes up, I'll ask for WG Last Call.

I like the idea of collecting state-of-the-art DNSSEC recommendations in some central place.

However, I noticed that three of the RFCs listed in the draft are from 202x, and likely more will have to be added in the future. That made me wonder:

How do we update this collection?

Do we issue a new BCP with a new RFC number every time that seems reasonable? When would that be / how many new relevant RFCs would have to get published before that happens?

Have we considered other ways of doing this, e.g. moving all the RFCs listed to a to-be-erected "IANA DNSSEC BCP registry", which can be updated more easily?

~Peter

-- 
https://desec.io/