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

David Dong via RT <iana-matrix@iana.org> Tue, 06 February 2024 03:33 UTC

Return-Path: <iana-shared@icann.org>
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 24091C14F6BC; Mon, 5 Feb 2024 19:33:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=no 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 I2MnnbHqWZnp; Mon, 5 Feb 2024 19:33:20 -0800 (PST)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (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 1242EC14F5EF; Mon, 5 Feb 2024 19:33:20 -0800 (PST)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id D7885E0341; Tue, 6 Feb 2024 03:33:19 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id D4F1460EA6; Tue, 6 Feb 2024 03:33:19 +0000 (UTC)
RT-Owner: david.dong
From: David Dong via RT <iana-matrix@iana.org>
Reply-To: iana-matrix@iana.org
In-Reply-To: <5224472B-7B3E-4741-AA16-9BC3AD43564D@amsl.com>
References: <RT-Ticket-1358110@icann.org> <RT-Ticket-1286986@icann.org> <169935484754.32250.8675663484311010341@ietfa.amsl.com> <rt-5.0.3-1053161-1700263317-1761.1286986-37-0@icann.org> <5224472B-7B3E-4741-AA16-9BC3AD43564D@amsl.com>
Message-ID: <rt-5.0.3-481603-1707190399-1698.1358110-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1358110
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: david.dong@iana.org
To: arusso@amsl.com
CC: superuser@gmail.com, rfc-editor@rfc-editor.org, john-ietf@jck.com, iana@iana.org, auth48archive@rfc-editor.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Tue, 06 Feb 2024 03:33:19 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/K7vERymZUKP0leIIJ2q_lcBto8k>
Subject: [auth48] [IANA #1358110] [IANA] Re: AUTH48: RFC-to-be 9422 <draft-freed-smtp-limits-07>
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
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: Tue, 06 Feb 2024 03:33:24 -0000

Hi Alice,

These changes are complete; please see:

https://www.iana.org/assignments/mail-parameters/

Best regards,

David Dong
IANA Services Sr. Specialist

On Mon Feb 05 19:22:25 2024, arusso@amsl.com wrote:
> 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