Re: [ietf-smtp] Possible cont4ibution to moving forward with RFC5321bis SMTP

Alessandro Vesely <vesely@tana.it> Fri, 27 December 2019 12:34 UTC

Return-Path: <vesely@tana.it>
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 3FF2712006B for <ietf-smtp@ietfa.amsl.com>; Fri, 27 Dec 2019 04:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkOzQZDb9BOu for <ietf-smtp@ietfa.amsl.com>; Fri, 27 Dec 2019 04:34:52 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 667C212004F for <ietf-smtp@ietf.org>; Fri, 27 Dec 2019 04:34:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1577450088; bh=LU/Ak+bQ0z2jgviRNXHR5fDK6c5jhSfunp9cT1mwPOk=; l=1172; h=To:Cc:References:From:Date:In-Reply-To; b=DCMNA0/cgbtg6i+E4IRbk0fvqMiL50Mq4R4SAwc9uU8PsTlrZaxs3JUHLws+iGavK SIO7dBsfDZA4R2jkcrBD1g3obDy+bYHUn/PcsJ3fjcEueNfWokbMblKLuO5l78Mg5Y qCHXFh4ngz3tZ4zMw4uSTC2xd6eo4JFB+dSViswrouq/QLul/qtUbKYTkWl0a
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.2, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC07E.000000005E05FA68.000061E3; Fri, 27 Dec 2019 13:34:48 +0100
To: John C Klensin <john-ietf@jck.com>
Cc: ietf-smtp@ietf.org
References: <FCDE38AEA7DDB9BB0FB206F9@PSB>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <0605ee67-86eb-3e27-26b0-7a1c16a37bee@tana.it>
Date: Fri, 27 Dec 2019 13:34:47 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0
MIME-Version: 1.0
In-Reply-To: <FCDE38AEA7DDB9BB0FB206F9@PSB>
Content-Type: text/plain; charset="us-ascii"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/VKK7uwceW6f1hXXWnIUgADG-lsk>
Subject: Re: [ietf-smtp] Possible cont4ibution to moving forward with RFC5321bis SMTP
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
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, 27 Dec 2019 12:34:54 -0000

On Thu 26/Dec/2019 20:09:01 +0100 John C Klensin wrote:
> If anyone has more or less broad issues that should be
> identified in that section that have not come up either in
> errata or recent discussions, mentioning them RSN so I can add
> them to the list would be helpful.  The list so far is:
> 
>    Appendix G.  Other Outstanding Issues
>      G.1.  IP address literals
>      G.2.  Meaning of "MTA" and Related Terminology
>      G.3.  Originator, or Originating System, Authentication


I have a couple of topics that I think it's worth discussing:

    G.4.  Reshape Section 3.9 so that ancillary specs can define:
          G.4.1 Mailing lists, including newsletters, and,
          G.4.2 Email address portability, by forwarding.

    G.5.  Clarify where the protocol stands with respect to
          * submission on port 587
          * submission on port 465
          * TLS relay on a port different from 25 (whenever)

I take the occasion to recall that I have copied some annotations from YAM to:
https://hyp.is/QQqD1iW3Eeq0pQfOL0z_1Q/tools.ietf.org/html/draft-klensin-rfc5321bis-00
(See https://web.hypothes.is/start/)

Further annotating rfc5321bis-00 can help staying focused, IMHO.


Best
Ale
--