IETF Logo Mail Archive

Re: [ietf-smtp] Registration policies for draft-freed-smtp-limits and elsewhere

John Levine <johnl@taugh.com> Mon, 07 August 2023 19:35 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 112A4C13AE4B for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Aug 2023 12:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.159
X-Spam-Level:
X-Spam-Status: No, score=-4.159 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=iecc.com header.b="VIdDYJi+"; dkim=pass (2048-bit key) header.d=taugh.com header.b="PLL3u2YB"
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 j3RP_KW7e76L for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Aug 2023 12:35:14 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35F19C137375 for <ietf-smtp@ietf.org>; Mon, 7 Aug 2023 12:35:13 -0700 (PDT)
Received: (qmail 92131 invoked from network); 7 Aug 2023 19:35:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=167e0.64d1476f.k2308; bh=9EzfLpe9D4zoZRboHH4wQ5J6mkanMj8+2OkD30E/80s=; b=VIdDYJi+KSEiAiTBfywWEF0UBocwd8jwEW7IeV+1ACNDsyWRehmvICPx4eu2yMQGy4e8YjYjh1DozJYhzSZWcCH2Y+QUgKjDurYAgkuLZ8Vd5v21KluMxTqD76inqE6YkOW+ItV9FBQaiUNDAO3xHt5GREwCv3tCh1qVMojzX3fbgE1nYtZdhVdcVZq0BRy9PLpHLJkZTI2H43xO0vAgRCFNXeP01LFYfpnVzxRg/SoXt7GPcOCQNsJky8WwIGs3PYTusXyGkSWfv7JJSpdQxzHPTz1lQPYlZLN956PSaagQOfRxejsK8e9EgvSltcvv2D0jpmsvX1XZ7g/RGPymtA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=167e0.64d1476f.k2308; bh=9EzfLpe9D4zoZRboHH4wQ5J6mkanMj8+2OkD30E/80s=; b=PLL3u2YBKzgVXlzJMY/t98j8MfEGyPyKz+CICEMENR9BK+CCB+QW6FPAT/lMZvyA5Lip5ShroEwLH8xvapGhd2HepFAEI6ewYGnNWJVDgStzBnFLgEzQ32jc/wHON02QSa8H4k9ZcqFM2N8HHVNs51lbjxexmzS3rkJ2/B8KQiss+LxKTg7+m1LXCE7NS7unnq46nwtD8TGPnTVnQ7p5VZCXFEom1fWDp37dyyLcTbCqXcDV8SuCcA7Rawawg42kOvkTc+BOdqnsFeitg1HcDlQacLCYtkhm4FGL97W6VxZ/bBSJaMIGrlVSR/EYo4p2G9Yi/dh5u6Rmj6VNraJwyA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 07 Aug 2023 19:35:11 -0000
Received: by ary.qy (Postfix, from userid 501) id EF3EDFF945E9; Mon, 7 Aug 2023 15:35:10 -0400 (EDT)
Date: Mon, 07 Aug 2023 15:35:10 -0400
Message-Id: <20230807193510.EF3EDFF945E9@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: john-ietf@jck.com
In-Reply-To: <F3021D9E1ADC0C4845954283@PSB>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/rIp3bwST3-hfn3UENp-365YH3Tg>
Subject: Re: [ietf-smtp] Registration policies for draft-freed-smtp-limits and elsewhere
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Aug 2023 19:35:19 -0000

It appears that John C Klensin  <john-ietf@jck.com> said:
>As implicitly threatened above, I have just posted
>draft-klensin-iana-consid-hybrid-01, "Hybrid IANA Registration
>Policy".  ....

I looked at it and honestly, if we want to chage RFC 8126, we should
simplify the registration rules, not add yet more complication.

There are basically two kinds of regstry, small ones where we might
run out of code points, and big ones where we won't.  (Small could
be under 256 available, big is over 50,000.  I can't think of any
in between.)

For small ones, we apply traditional quality control, expert review up
to standards action. For the large ones, it's FCFS. We can certainly
encourage registrants in large ones to provide detailed specifications
and offer help to do so, but even if they don't, register it anyway. 

R's,
John

v2.23.0 | Report a Bug | By Email