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

Amanda Baber <amanda.baber@iana.org> Fri, 23 September 2022 19:25 UTC

Return-Path: <amanda.baber@iana.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 DB488C15256A; Fri, 23 Sep 2022 12:25:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 darBKtXOcl0x; Fri, 23 Sep 2022 12:25:49 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 235F5C1522CE; Fri, 23 Sep 2022 12:25:49 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa2.lax.icann.org (8.17.1.5/8.17.1.5) with ESMTPS id 28NJPiil008120 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 23 Sep 2022 19:25:45 GMT
Received: from MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) 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 12:25:43 -0700
Received: from MBX112-W2-CO-2.pexch112.icann.org ([10.226.41.130]) by MBX112-W2-CO-2.pexch112.icann.org ([10.226.41.130]) with mapi id 15.02.0986.029; Fri, 23 Sep 2022 12:25:43 -0700
From: Amanda Baber <amanda.baber@iana.org>
To: Paul Hoffman <paul.hoffman@icann.org>, 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>, Sabrina Tanamal <sabrina.tanamal@iana.org>
Thread-Topic: [Last-Call] [Ext] Last Call: <draft-ietf-dnsop-dnssec-bcp-03.txt> (DNS Security Extensions (DNSSEC)) to Best Current Practice
Thread-Index: AQHYz4JFZ81s7e+OBkSajMnM5UOM1A==
Date: Fri, 23 Sep 2022 19:25:43 +0000
Message-ID: <484D4C8A-486C-44F3-9E76-1E983C383349@iana.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.63.22070801
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <8D16547595854542A3E38EC702DADD62@pexch112.icann.org>
Content-Transfer-Encoding: base64
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_08,2022-09-22_02,2022-06-22_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/Wry3zeyi-XlTHKDGD3HFQ1dob6c>
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 19:25:53 -0000

Hi,

IANA uses the term "registry group" to refer to top-level registries and "registry" to describe a set of registrations (as opposed to a set of sets). There are logistical reasons for this, but the use of the term "registry" in particular matches the usage in ICANN's MoU with the IETF (and our MoU-mandated performance reports).

I should add that we still use the term "sub-registry," but only to refer to, e.g., a registry of sub-TLVs for a TLV.

So "Domain Name System Security (DNSSEC) NextSECure3 (NSEC3) Parameters" (as it's listed at https://www.iana.org/protocols and https://www.iana.org/assignments/dnssec-nsec3-parameters) is a registry group that includes the DNSSEC NSEC3 Flags, DNSSEC NSEC3PARAM Flags, and DNSSEC NSEC3 Hash Algorithms registries, while "DNSSEC Delegation Signer (DS) Resource Record (RR) Type Digest Algorithms" is the name of a registry group that consists solely of a registry called "Digest Algorithms."

We'll address this in more detail in 8126bis. RFC 8126, which mostly uses the word "grouping" -- "group" was recommended by the RFC Editor -- mentions this issue, but doesn't include instructions.

Thanks,

Amanda Baber
IANA Operations Manager

On 9/23/22, 9:44 AM, "last-call on behalf of Paul Hoffman" <last-call-bounces@ietf.org on behalf of paul.hoffman@icann.org> wrote:

    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