Re: [ietf-smtp] draft-freed-smtp-limits

John C Klensin <john-ietf@jck.com> Mon, 07 August 2023 03:33 UTC

Return-Path: <john-ietf@jck.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 7BD30C151083 for <ietf-smtp@ietfa.amsl.com>; Sun, 6 Aug 2023 20:33:42 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 BkeHlB8njILD for <ietf-smtp@ietfa.amsl.com>; Sun, 6 Aug 2023 20:33:40 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.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 490BDC15106B for <ietf-smtp@ietf.org>; Sun, 6 Aug 2023 20:33:40 -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 1qSqzy-000FZS-SP; Sun, 06 Aug 2023 23:33:38 -0400
Date: Sun, 06 Aug 2023 23:33:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, ietf-smtp@ietf.org
Message-ID: <9ADBF8895968610C15C5AA9D@PSB>
In-Reply-To: <9df5aee0-603c-5e69-5042-3a058259e40f@dcrocker.net>
References: <E5D603318655781DAC56BADD@PSB> <BF128F7A-C3E8-4F57-9DC9-E11C997326ED@isdg.net> <63EBB19B3823FADBE6671A65@PSB> <CAL0qLwbmaHbSdcEZ4zm65rwat24i-gByFEgiKAn8FYfU6oqgbQ@mail.gmail.com> <A760A7077C05E42B5200A81B@PSB> <CAL0qLwaztOZBMWyMkP7ho6UZMLda+AQb6WLf5Ajb3EM_amSe2w@mail.gmail.com> <9df5aee0-603c-5e69-5042-3a058259e40f@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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/ietf-smtp/_IjsrEg1o96y0WAE611YX3Ym1Qk>
Subject: Re: [ietf-smtp] draft-freed-smtp-limits
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 03:33:42 -0000

--On Sunday, August 6, 2023 18:36 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

>> If this is a model that we think might be useful for other
>> future  registries to follow
> 
> 
> I think that having two registries confuses tasks and meaning,
> and makes it more effort to get registered and ambiguous to
> use.

While 5321bis (through -19) allows for the possibility of two
registries (following some of the provisional/permanent splits)
there is nothing in that draft that requires anything more than
a single registry with a flag that indicates which option was
chosen.
>...

> Making registration effort higher makes it more likely people
> won't bother to register.

And that was exactly what drove the formation of the hybrid
model.  

> The confusion of goals is thinking that there is benefit in
> conflating registration with quality control.  There isn't.
> (Well, almost never and certainly not in this case.)

It isn't "quality control".  It could be (and, back when
"Standards Track or..." was first specified for those
registries, was), about genuine interest on the part of would-be
registrants for getting input and suggestions from the
community.  I've just looked through a number of early media
type registrations from long ago; many of them would have been
much worse -- requiring new keywords, registrations, and
documents somewhere-- had they not gone through the
standardization process.

>...

   john