[auth48] [IANA] Re: AUTH48: RFC-to-be 9422 <draft-freed-smtp-limits-07>

Alice Russo <arusso@amsl.com> Mon, 05 February 2024 19:22 UTC

Return-Path: <arusso@amsl.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18F15C14F61A; Mon, 5 Feb 2024 11:22:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, 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 WDZY5vLD0e80; Mon, 5 Feb 2024 11:22:22 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 94D84C14F60F; Mon, 5 Feb 2024 11:22:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7CB61424B426; Mon, 5 Feb 2024 11:22:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pWPFkjNyuq9Y; Mon, 5 Feb 2024 11:22:22 -0800 (PST)
Received: from smtpclient.apple (c-76-146-133-47.hsd1.wa.comcast.net [76.146.133.47]) by c8a.amsl.com (Postfix) with ESMTPSA id 40382424CD01; Mon, 5 Feb 2024 11:22:22 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <rt-5.0.3-1053161-1700263317-1761.1286986-37-0@icann.org>
Date: Mon, 05 Feb 2024 11:22:21 -0800
Cc: John C Klensin <john-ietf@jck.com>, "Murray S. Kucherawy" <superuser@gmail.com>, auth48archive <auth48archive@rfc-editor.org>, rfc-editor@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5224472B-7B3E-4741-AA16-9BC3AD43564D@amsl.com>
References: <RT-Ticket-1286986@icann.org> <169935484754.32250.8675663484311010341@ietfa.amsl.com> <rt-5.0.3-1053161-1700263317-1761.1286986-37-0@icann.org>
To: iana@iana.org
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/P94AybXY82XQNjO1H_MniEVjsSE>
Subject: [auth48] [IANA] Re: AUTH48: RFC-to-be 9422 <draft-freed-smtp-limits-07>
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Feb 2024 19:22:27 -0000

Greetings, IANA,

Please update https://www.iana.org/assignments/mail-parameters
under "SMTP Server Limits" as follows to match the edited document (https://www.rfc-editor.org/authors/rfc9422.txt).

OLD:
> Name: MAILMAX
> Value syntax: %x31-39 0*5DIGIT ; 0 not allowed, 6 digit maximum
NEW:
Value syntax: %x31-39 0*5DIGIT ; "0" not allowed, six-digit maximum

OLD:
> Name: RCPTMAX
> Value syntax: %x31-39 0*5DIGIT ; 0 not allowed, 6 digit maximum
NEW:
Value syntax: %x31-39 0*5DIGIT ; "0" not allowed, six-digit maximum

OLD:
> Name: RCPTDOMAINMAX
> Value syntax: %x31-39 0*5DIGIT ; 0 not allowed, 6 digit maximum
NEW:
Value syntax: %x31-39 0*5DIGIT ; "0" not allowed, six-digit maximum

Thank you.
RFC Editor/ar


> On Nov 17, 2023, at 3:21 PM, Sabrina Tanamal via RT <drafts-approval@iana.org> wrote:
> 
[...]

> ACTION 2:
> 
> We've created the following registry and placed it in the "MAIL Parameters" registry group:
> 
> SMTP Server Limits
> Registration Procedure(s): Specification Required
> Expert(s): Unassigned
> Reference: [RFC-freed-smtp-limits-07]
> 
> Name: MAILMAX
> Value syntax: %x31-39 0*5DIGIT ; 0 not allowed, 6 digit maximum
> Description: MAILMAX specifies the maximum number of transactions (MAIL FROM commands) the server will accept in a single session. The count includes all MAIL FROM commands, regardless of whether they succeed or fail.
> Restrictions: None.
> Security Considerations: See [RFC-freed-smtp-limits-07, Section 6]
> Reference: [RFC-freed-smtp-limits-07]
> 
> Name: RCPTMAX
> Value syntax: %x31-39 0*5DIGIT ; 0 not allowed, 6 digit maximum
> Description: RCPTMAX specifies the maximum number of RCPT TO commands the server will accept in a single transaction. It is not a limit on the actual number of recipients the message ends up being sent to; a single RCPT TO command may produce multiple recipients or, in the event of an error, none.
> Restrictions: None.
> Security Considerations: See [RFC-freed-smtp-limits-07, Section 6]
> Reference: [RFC-freed-smtp-limits-07]
> 
> Name: RCPTDOMAINMAX
> Value syntax: %x31-39 0*5DIGIT ; 0 not allowed, 6 digit maximum
> Description: RCPTDOMAINMAX specifies the maximum number of different domains that can appear in a recipient (RCPT TO) address within a single session. This limit is imposed by some servers that bind to a specific internal delivery mechanism on receipt of the first RCPT TO command.
> Restrictions: None.
> Security Considerations: See [RFC-freed-smtp-limits-07, Section 6]
> Reference: [RFC-freed-smtp-limits-07]
> 
> Please see
> https://www.iana.org/assignments/mail-parameters