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

Keith Moore <moore@network-heretics.com> Thu, 26 December 2019 22:03 UTC

Return-Path: <moore@network-heretics.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 344D21200EF for <ietf-smtp@ietfa.amsl.com>; Thu, 26 Dec 2019 14:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 nlw4GkswOvAv for <ietf-smtp@ietfa.amsl.com>; Thu, 26 Dec 2019 14:03:40 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB0641200B6 for <ietf-smtp@ietf.org>; Thu, 26 Dec 2019 14:03:40 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 5D5C221B74; Thu, 26 Dec 2019 17:03:38 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 26 Dec 2019 17:03:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=154QdlY1B3o6QbCI3iE50qJHvmDy3ualEYagDuIJq Eo=; b=UN5J0LShNnx4DeZhSdINOt1koZoFL9cWHTVGKzXnIkDMbZFtPMCUHGAXl lhHSp2w+lk+0MMvEIgiZbB92QtxXTTvmWLa6j5W5+fUqNcuAtGwtBxkVP96DC1b8 hRP27PUDTELmVamxPtp1q7PRTA6Q5seqxQ45lZ1TVJualmpYA6FVyTgWp7Dx4XUU zQfdOEynm6w1wPw7+i+ee918EYPIzz1b/vWl8zmAn4OOQ8NWlm4avANUWsPYmbyO Zhz4w1As7f2ta7yS/X4oum1EhxQ6C6/B7oxlkR0B1MVUeuiG4xC4sMOBBKW4HKyw VyMl8njrAOIN+R8v4EYIX0x5JTo9w==
X-ME-Sender: <xms:OC4FXk8iN0biJTEGUpbJBj9-SbYSO_x-Gu4stP6hP4JU3csYnOOrVA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvddviedgudehhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrd duheenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgv rhgvthhitghsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:OC4FXg-LRTKjbTPNv8AJqL0KBHgNbWe8R1XTRcgry23JkRSlmZxeJw> <xmx:OC4FXlCcCtiYv6YXMYhlsNzvmrHxjBhcCMbzosgXTEwTGxrB_Oy8NA> <xmx:OC4FXox3sw1HicXuvAF0iI-ZuPZ_l_gOsZJxFs9HquOQJuDP59qhng> <xmx:Oi4FXgKbejPMKT9uKeIPBHePu9MIZpu5vEjjeoYpZeEIJ3G0KNpUXA>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 583D130607B4; Thu, 26 Dec 2019 17:03:36 -0500 (EST)
To: John C Klensin <john-ietf@jck.com>, ietf-smtp@ietf.org
References: <FCDE38AEA7DDB9BB0FB206F9@PSB> <0cbf23be-dbfc-f78f-8e63-d92d6e34fbf0@network-heretics.com> <37C195CAA3295DE832711B38@PSB>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <434a885c-3709-b90b-40cd-4c45ba339666@network-heretics.com>
Date: Thu, 26 Dec 2019 17:03:34 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <37C195CAA3295DE832711B38@PSB>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/btLcrImGaePIdOuTCdkh5rJ76jc>
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 22:03:43 -0000

On 12/26/19 4:30 PM, John C Klensin wrote:

> 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.

As sympathetic as I am to the privacy issue, I'd have a difficult time 
supporting a general requirement to encrypt all mail relaying because of 
backward compatibility issues with hosts that don't have TLS support yet 
(including IIoT-related concerns).

I also think that any SMTP upgrade will quite naturally have a long 
tail, so imposing any global requirement (even if it earned broad 
support) without breaking mail that people need to continue to have 
delivered, would be quite a technical challenge.

To me it seems that all of this should be out-of-scope for 5321bis, or 
that the only mention of this in 5321bis should be to declare such 
things out-of-scope.   Requiring hop-by-hop encryption would be the most 
disruptive change in the history of SMTP, I think, far more so than EHLO.

Keith