Re: [Gen-art] Genart Last Call review of draft-freed-smtp-limits-06

John C Klensin <john@jck.com> Sun, 17 September 2023 22:06 UTC

Return-Path: <john@jck.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F25DC151099 for <gen-art@ietfa.amsl.com>; Sun, 17 Sep 2023 15:06:51 -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 0F2gmhepsgQZ for <gen-art@ietfa.amsl.com>; Sun, 17 Sep 2023 15:06:46 -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 2D700C14CE33 for <gen-art@ietf.org>; Sun, 17 Sep 2023 15:06:45 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1qhzuc-0000HX-KF; Sun, 17 Sep 2023 18:06:42 -0400
Date: Sun, 17 Sep 2023 18:06:37 -0400
From: John C Klensin <john@jck.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
cc: General Area Review Team <gen-art@ietf.org>
Message-ID: <97CB0F7D9973F9AFB7444D98@PSB>
In-Reply-To: <CAL0qLwYGHGT=+Oh2_FF0m7gkJwgMQVyn9OdJh7GNYtSmRuNT+Q@mail.gmail.com>
References: <b245ea64-3685-cc78-5dad-41539a92591a@alum.mit.edu> <CAL0qLwYGHGT=+Oh2_FF0m7gkJwgMQVyn9OdJh7GNYtSmRuNT+Q@mail.gmail.com>
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@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/4lAVFBo8ytz5ueR0kC5p_FJYnkg>
Subject: Re: [Gen-art] Genart Last Call review of draft-freed-smtp-limits-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Sep 2023 22:06:51 -0000

Murray, Paul,

Please stand by for half-written note...   I should be able to
finish and post the next couple of hours.

  john


--On Sunday, September 17, 2023 14:53 -0700 "Murray S.
Kucherawy" <superuser@gmail.com> wrote:

> On Fri, Sep 15, 2023 at 9:49 AM Paul Kyzivat
> <pkyzivat@alum.mit.edu> wrote:
> 
>> 
>> Section 7.2 seems to conflate two things:
>> 
>> - the information that must be provided in a specification
>>    document that registers new limits
>> 
>> - the information that is to included in the registry itself
>> 
>> ISTM that the registry itself should contain the limit name
>> and a reference to the specification document. It might also
>> contain the value syntax, or at least an indication if a
>> value is allowed.
>> 
>> The descriptions of semantics, restrictions, and security
>> considerations don't lend themselves to inclusion in the
>> registry, but should be clearly spelled out in the
>> specification.
>> 
> 
> This is an interesting observation.  I suppose I overlooked it
> because by now I'm used to both types of registries.  A good
> example of this style is the media types registry, where some
> of the details (e.g., option names) that you might normally
> expect to find in the specification document only are actually
> also required to be present in the registry.  That model of
> registry has been around for a pretty long time and we seem to
> be fine with it.  But most other newer registries are just a
> table of the reserved name and a reference to the specifying
> document, with all of the details typically stored in the
> latter, with maybe a "status" column included.
> 
> I'd be inclined to split the difference, and say either the
> registry has to contain the limit value's syntax, or a
> reference to the defining document where such can be found.
> We allow this in the media types registry for security
> considerations, for example.
> 
> 
>> Also, the request for the new registry should probably
>> include its exact name ("SMTP Server Limits"?), and that it
>> should be included within the "MAIL Parameters" protocol
>> registry.
>> 
> 
> I agree, precision here is never a bad thing.
> 
> -MSK