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

John C Klensin <john-ietf@jck.com> Thu, 26 December 2019 21:30 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 792AC1200EC for <ietf-smtp@ietfa.amsl.com>; Thu, 26 Dec 2019 13:30:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 UaPvwP-MWE_E for <ietf-smtp@ietfa.amsl.com>; Thu, 26 Dec 2019 13:30:34 -0800 (PST)
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 095E51200B6 for <ietf-smtp@ietf.org>; Thu, 26 Dec 2019 13:30:34 -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 1ikaiG-000GLa-L9; Thu, 26 Dec 2019 16:30:32 -0500
Date: Thu, 26 Dec 2019 16:30:25 -0500
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>, ietf-smtp@ietf.org
Message-ID: <37C195CAA3295DE832711B38@PSB>
In-Reply-To: <0cbf23be-dbfc-f78f-8e63-d92d6e34fbf0@network-heretics.com>
References: <FCDE38AEA7DDB9BB0FB206F9@PSB> <0cbf23be-dbfc-f78f-8e63-d92d6e34fbf0@network-heretics.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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/aCisAXd5InSm6yXV6iaJ-q_V_gE>
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: Thu, 26 Dec 2019 21:30:35 -0000


--On Thursday, December 26, 2019 14:23 -0500 Keith Moore
<moore@network-heretics.com> wrote:

> John,
> 
> Just to clarify my point-of-view, I don't see the recent spam
> discussions as resulting in significant new text in
> RFC5231bis. What I imagine for RFC5321bis is at most some very
> slight tweaking of the wording.    As far as I can tell it
> was just a coincidence that the issue with the IETF MTA
> cropped up at about the same time you started to ask about
> 5321bis.

Keith,

I don't either.  But I don't see it as useful to revise 5321
without some consensus, however rough, about whether or not
something should be said about those issues.  I note in that
regard that there are advantages and uses for originator
authentication that have little or nothing to do with anti-spam
activities.   I also interpret some recent work and statements
within the IETF as leading toward prohibiting email that is not
encrypted hop-by-hop on the grounds of privacy protection not
anti-spam efforts.  If a WG comes together and treats those
issues as out of scope, it would be fine with me.  I just don't
think we should either be ignoring the issue or assuming that
everyone agrees with those who have spoken up most loudly in
recent weeks.

   john