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

John C Klensin <john-ietf@jck.com> Fri, 23 September 2022 21:16 UTC

Return-Path: <john-ietf@jck.com>
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 2B01EC152577; Fri, 23 Sep 2022 14:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 HWLfMyEOc_WS; Fri, 23 Sep 2022 14:16:11 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DD7CC1522BD; Fri, 23 Sep 2022 14:16:10 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1obq1l-000NB0-PE; Fri, 23 Sep 2022 17:16:05 -0400
Date: Fri, 23 Sep 2022 17:16:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Amanda Baber <amanda.baber@iana.org>, Paul Hoffman <paul.hoffman@icann.org>, tom petch <daedulus@btconnect.com>
cc: last-call@ietf.org, dnsop <dnsop@ietf.org>, dnsop-chairs@ietf.org, draft-ietf-dnsop-dnssec-bcp@ietf.org, Sabrina Tanamal <sabrina.tanamal@iana.org>
Message-ID: <22E949C1D2F3D4A7D1F0CA69@PSB>
In-Reply-To: <484D4C8A-486C-44F3-9E76-1E983C383349@iana.org>
References: <484D4C8A-486C-44F3-9E76-1E983C383349@iana.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/QcUf-SPagG6z5KTeBjb_jAHkYi8>
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 21:16:15 -0000


--On Friday, September 23, 2022 19:25 +0000 Amanda Baber
<amanda.baber@iana.org> wrote:

> 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.

Amanda,

In the hope of getting something else on which I'm working [1]
right, some questions about the above: 

If I look at a protocol assignments page, e.g.,
https://www.iana.org/assignments/mail-parameters/mail-parameters.xhtml
is "MAIL Parameters" the "top-level registry" aka "registry
group", despite the fact that some of the registries on that
page are associated with different protocols (even if they are
somehow mail-related and, as we have discussed, there are
mail-related registries elsewhere)?

Also some of what I assume are called "registries" ("SMTP
Service Extensions", "SMTP Service Extension Parameters", "Mail
Transmission Types", etc.) are subsidiary to other ones there.
Does that make a difference? 

And, is "SMTP Service Extension Parameters" properly a
sub-registry of "SMTP Service Extensions"?  And, forgive my
ignorance, but what is a "TLV" in this context?

thanks,
   john



[1] draft-ietf-emailcore-rfc5321bis