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

John C Klensin <john-ietf@jck.com> Thu, 26 December 2019 19:09 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 EDF6F1208DF; Thu, 26 Dec 2019 11:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 SnrMWyJKAe30; Thu, 26 Dec 2019 11:09:10 -0800 (PST)
Received: from bsa2.jck.com (ns.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 51DD6120884; Thu, 26 Dec 2019 11:09:10 -0800 (PST)
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 1ikYVQ-000GCa-DV; Thu, 26 Dec 2019 14:09:08 -0500
Date: Thu, 26 Dec 2019 14:09:01 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf-smtp@ietf.org
cc: art-ads@ietf.org
Message-ID: <FCDE38AEA7DDB9BB0FB206F9@PSB>
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/5FpGUB0ZlJ9xfMxg_NN5qBsuJFg>
Subject: [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: Thu, 26 Dec 2019 19:09:12 -0000

Hi.

My impression is that discussions are now either going around in
circles or have deteriorated into a couple of people repeating
themselves in attempts to convince, or at least explain to,
others.  I wouldn't presume to try to stop those discussions,
but want to see if we can move forward.

That impression may be wholly incorrect but I think it is, or
should be, clear to everyone that we've significantly departed
from the fairly narrow questions of whether it is appropriate
for IETF servers to reject any mail session opening attempt that
uses an IP address literal in the EHLO command and what 5421
actually says (and was intended to say) about acceptance or
rejection of address literals.

In the hope that it will help us make progress, at least toward
getting some focus on getting a WG put together and/or clarity
from the ADs about how (or if) they would like to move forward,
I've worked up a new draft of rfc5321bis that adds a appendix
(G) about outstanding issues identified in the last several
weeks to the appendix about issue identified in errata (H.1 in
the -02 version, formerly G.1 in the -01 one).  It does _not_
propose solutions, only identifies topics that need discussion
about whether or not we should deal with them and, if so, where.
I will probably post that version tomorrow or over the weekend.
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

thanks,
   john