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 22:14 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 EAB6EC1524A3; Fri, 23 Sep 2022 15:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 agNEFh21PnYF; Fri, 23 Sep 2022 15:14:21 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.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 7C6C1C14F74E; Fri, 23 Sep 2022 15:14:21 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa4.dc.icann.org (8.17.1.5/8.17.1.5) with ESMTPS id 28NMEFZH004920 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 23 Sep 2022 22:14:15 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) 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 15:14:14 -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 15:14:14 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Amanda Baber <amanda.baber@iana.org>
CC: tom petch <daedulus@btconnect.com>, "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+OBkSajMnM5UOM1K3uCfOA
Date: Fri, 23 Sep 2022 22:14:14 +0000
Message-ID: <FE34047E-6AAD-4E1A-AD14-3FDB39B627EB@icann.org>
References: <484D4C8A-486C-44F3-9E76-1E983C383349@iana.org>
In-Reply-To: <484D4C8A-486C-44F3-9E76-1E983C383349@iana.org>
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=_9BD9C305-986E-4B5F-9DD3-EC954F08FBDB"; 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_10,2022-09-22_02,2022-06-22_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/q4C0DZ1WOpxBgkfv72IFI4wvCis>
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 22:14:22 -0000

On Sep 23, 2022, at 12:25 PM, Amanda Baber <amanda.baber@iana.org> wrote:
> 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).

Excellent, thanks!

--Paul Hoffman

v2.23.0 | Report a Bug | By Email