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

John C Klensin <john-ietf@jck.com> Fri, 04 August 2023 22:13 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 B932AC15153F for <ietf-smtp@ietfa.amsl.com>; Fri, 4 Aug 2023 15:13:30 -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 AWrsjqNDdA0t for <ietf-smtp@ietfa.amsl.com>; Fri, 4 Aug 2023 15:13:26 -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 6C718C151065 for <ietf-smtp@ietf.org>; Fri, 4 Aug 2023 15:12:43 -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 1qS32I-0002HX-4X; Fri, 04 Aug 2023 18:12:42 -0400
Date: Fri, 04 Aug 2023 18:12:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
Message-ID: <84D8053BB2F713C3B696534A@PSB>
In-Reply-To: <20230804211051.253DEFF7148A@ary.qy>
References: <20230804211051.253DEFF7148A@ary.qy>
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/ietf-smtp/spI9-IMQNpyriiKLtVPdM1b_Sig>
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: Fri, 04 Aug 2023 22:13:30 -0000

Ack.  And thanks.

And, fwiw, I'd prefer to see it handled in 8126bis and that
level of detail torn out of 5321bis.  If we are seeing multiple
places where that model is useful, SMTP is really not the best
place for the description.

   john


--On Friday, August 4, 2023 17:10 -0400 John Levine
<johnl@taugh.com> wrote:

> It appears that John C Klensin  <john-ietf@jck.com> said:
>> requirements for those registries.  So, unless we want LIMITs
>> and its parameters to be unique among extensions, either I
>> need to write some tricky text, or we need to create a
>> normative reference to 5321bis (holding up publication of
>> this), or the either long-promised revision to 8126 or the
>> long-threatened update to it to include just that option (an
>> I-D I started on two weeks ago when I noticed the "need to do
>> something about this" note in 5321bis).   Thoughts?
> 
> I'd rather wait for 5321bis and then handle it normally.  Think
> if it as another nudge to get 5321bis out the door.
> 
> I've implemented it as a plugin in my mail server (the obscure
> but respectable mailfront.)  As you might expect, it wasn't
> hard.
> 
> R's,
> John