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

Keith Moore <moore@network-heretics.com> Thu, 02 January 2020 19:28 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 66CE8120120 for <ietf-smtp@ietfa.amsl.com>; Thu, 2 Jan 2020 11:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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 zZjd4ZCFEoZL for <ietf-smtp@ietfa.amsl.com>; Thu, 2 Jan 2020 11:28:14 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38E36120113 for <ietf-smtp@ietf.org>; Thu, 2 Jan 2020 11:28:14 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id A12019A2; Thu, 2 Jan 2020 14:28:13 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 02 Jan 2020 14:28:13 -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=aWwY/bmAARZPxMqIH6zoXNMn5rB40hpx+fmhAQeqI Zk=; b=VuE8/18kx8LZeWECQ0WX36fRNJ6e98qgAas54uro2AXszM/5UKSPrh25y IJJ/pptO+UMROIUVCYybeZueQVzN+FZcEGEsW4u3uFwGhHawZIa5FapChOdiujR6 kUDPoxFPjeDKYac9w3Zew2uuxV1aVPRSQHOMc4hG/oTrfOVPZlvcP6uS9kv8pzuz 8g/SqaEhT1XYOFXUP1NTKB08x1XPAVRwtytVRHkDb7eIOJwScXk541evrSm6guqW KC9Pjq7Ho68/V37Rr4kQcc7SQqLr9iI1GpmakqldDay3T1Zm1XWhEXi4dG8j/XnI 9i3D+HeSrpzhwOuF/gSZPzHDsUsuA==
X-ME-Sender: <xms:TEQOXjachnWsbaifSyxtCX23q7qAB7AgKLPqoDOvE4BlkaD_z0BIhA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdeguddguddviecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrd duheenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgv rhgvthhitghsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:TEQOXoUoYU0hoJ4HOJ2o1buKol7ptUWrNf6h8klvXOcdTleR9VtO1A> <xmx:TEQOXjFez1JJ1T4r0UfgwNHfCk-mmgKuCYVmJju2d9O9nVEeDv1Cxw> <xmx:TEQOXqYrAX27bQvgnbmDfsIfXMR6uDOEhUeF1reyxGuH7x1CfsElaw> <xmx:TUQOXpg6-URO3i1yJJN2rpLl05njXSyf6pIG3y_p94R07J5GkUlsMQ>
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 DD3D13060741; Thu, 2 Jan 2020 14:28:11 -0500 (EST)
To: ietf-smtp@ietf.org
References: <20200101175510.8549A11E2905@ary.qy> <D441E0BE-1F32-4329-9296-A5026540E8D0@dukhovni.org> <994e7a23-9e80-4751-6067-8863ad0ee72f@network-heretics.com> <2Iq+URBKeODeFANB@highwayman.com> <5E0E04AA.5070408@isdg.net> <986919d8-613b-7e13-c39b-0f7f978ca763@network-heretics.com> <B7644591809D5C3CBB682F56@JcK-HP5.jck.com> <65a41f13-6a8f-95ef-2a6f-744a4604c546@dcrocker.net>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <0fc9f066-ecd2-5e8e-e795-c778bc4847e8@network-heretics.com>
Date: Thu, 02 Jan 2020 14:28:11 -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: <65a41f13-6a8f-95ef-2a6f-744a4604c546@dcrocker.net>
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/A7kx_UNO6_j5Rc0MxNwBMYsCsKs>
Subject: Re: [ietf-smtp] Possible contribution 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, 02 Jan 2020 19:28:15 -0000

On 1/2/20 1:23 PM, Dave Crocker wrote:

> On 1/2/2020 10:17 AM, John C Klensin wrote:
>> That even includes such questions as
>> whether RFC 974 was the right solution to that problem and
>> remains the right solution in a world in which the DNS is being
>
> Where is there indication that this mechanism has been having 
> operational problems?
>
> Where is the discussion of an alternative?
>
> Failing to obtain some history covering both of these questions, 
> pursuing this topic doesn't seem likely to be productive, though it 
> could be wonderfully expensive in time and frustration.

Some of us remember these things and the references are potentially 
useful to those who do.    Are we constrained to only talk about what 
we're sure everyone already knows?   I certainly don't want us to have 
to revisit the entire history of email in this discussion (and to have 
to repeat that discussion every few years), but I assume that people 
seriously involved in email are motivated to do that anyway.   So I 
don't think it's wrong to refer to history, and I think that sometimes 
it provides valuable context.

I doubt that much, if any, historical discussion should be in the 
5321bis spec(s).   If someone really feels motivated there could be an 
informational document but I wouldn't want it to be a work item for a WG.

Keith