IETF Logo Mail Archive

Re: [Last-Call] [Ext] Last Call: <draft-ietf-dnsop-dnssec-bcp-03.txt> (DNS Security Extensions (DNSSEC)) to Best Current Practice

Paul Hoffman <paul.hoffman@icann.org> Fri, 23 September 2022 16:44 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168E9C14F74B; Fri, 23 Sep 2022 09:44:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eaTfTDXynqh9; Fri, 23 Sep 2022 09:44:39 -0700 (PDT)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (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 8C670C14F72A; Fri, 23 Sep 2022 09:44:39 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa5.dc.icann.org (8.17.1.5/8.17.1.5) with ESMTPS id 28NGiYcN006894 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 23 Sep 2022 16:44:35 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.29; Fri, 23 Sep 2022 09:44:34 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.0986.029; Fri, 23 Sep 2022 09:44:34 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: tom petch <daedulus@btconnect.com>
CC: "last-call@ietf.org" <last-call@ietf.org>, dnsop <dnsop@ietf.org>, "dnsop-chairs@ietf.org" <dnsop-chairs@ietf.org>, "draft-ietf-dnsop-dnssec-bcp@ietf.org" <draft-ietf-dnsop-dnssec-bcp@ietf.org>
Thread-Topic: [Ext] Last Call: <draft-ietf-dnsop-dnssec-bcp-03.txt> (DNS Security Extensions (DNSSEC)) to Best Current Practice
Thread-Index: AQHYz2vCxfZwwPnJ+Uy8a+p2GLLzhg==
Date: Fri, 23 Sep 2022 16:44:34 +0000
Message-ID: <5341E64B-2F67-4262-AB20-CABC5D241EE6@icann.org>
References: <166376520467.13223.15550799018842632600@ietfa.amsl.com> <632DE01D.3000701@btconnect.com>
In-Reply-To: <632DE01D.3000701@btconnect.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: multipart/signed; boundary="Apple-Mail=_579824E9-6AAC-4C6E-BF16-EA335B156034"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.528,FMLib:17.11.122.1 definitions=2022-09-23_06,2022-09-22_02,2022-06-22_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/YgssSL4TuuCIizAy77Ejhf11VB0>
Subject: Re: [Last-Call] [Ext] Last Call: <draft-ietf-dnsop-dnssec-bcp-03.txt> (DNS Security Extensions (DNSSEC)) to Best Current Practice
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Sep 2022 16:44:40 -0000

On Sep 23, 2022, at 9:34 AM, tom petch <daedulus@btconnect.com> wrote:
> Going into the IANA registry by name, as I usually do, I think that from Section 6
> DNSSEC Algorithm numbers
> DNSSEC NSEC3 parameters
> are groups and not registries whereas
> DNSSEC DS RRtype
> I have yet to find (but have not yet used the URL)

Thanks for the comment. I don't know if there is a strict rule about what is an IANA "registry" verus a "group". I do note that all three that are listed are top-level URLs, so I would guess that they would all be considered the same type of IANA thing.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email