Re: [ietf-smtp] Email standard revision

Dave Crocker <dhc@dcrocker.net> Tue, 18 February 2020 15:20 UTC

Return-Path: <dhc@dcrocker.net>
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 A1332120130 for <ietf-smtp@ietfa.amsl.com>; Tue, 18 Feb 2020 07:20:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.818
X-Spam-Level:
X-Spam-Status: No, score=-1.818 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_NEUTRAL=0.779, URIBL_BLOCKED=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 lyJXKPAR8rvP for <ietf-smtp@ietfa.amsl.com>; Tue, 18 Feb 2020 07:20:36 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C96B012084F for <ietf-smtp@ietf.org>; Tue, 18 Feb 2020 07:20:36 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id DEF0922182 for <ietf-smtp@ietf.org>; Tue, 18 Feb 2020 10:20:35 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 18 Feb 2020 10:20:35 -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 :reply-to:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=s1ghkYoqo5TPFTGETnyzRTjr/GwrE HBDXwX4iq81dt0=; b=Lu4UMJ95rolSXH/LtuxL/hUxQzOFeqpwitfJl3XIsVIUU dcSnu90vqzkg8b63xCfm1Bh84XEGd2CUTy27hXRhER0f78dM0bA9aLE0ZyBrPclz 50qLqP0/zEGe0GWVITbsthxsAm8iF9p1OYvj1qk9kFuYupGNGp7a7QCoFo77AHJJ ss1T/yfz4YZNcqGQo9PykNjojovRB6mZJkoTebL5aVzAgnfbDH2gTjHAAx/yEdhv OfcpRl1Va/NOtKwshXOFDLfICmGHId65xjyJHGhK4B0+X3qRlb5LUjjI7PZwe6AL onUEPymhBF3yVbeWZXv7rxK887JbllyI5szSdQbJQ==
X-ME-Sender: <xms:wwBMXrL4kgjwO9yvDTsNHIa3fpA4DFahiDTTBcDZnPil8WFVAwdVPQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrjeekgdejhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhrhfkffgfgggjtgfgsehtje ertddtfeejnecuhfhrohhmpeffrghvvgcuvehrohgtkhgvrhcuoeguhhgtsegutghrohgt khgvrhdrnhgvtheqnecuffhomhgrihhnpegssghifidrnhgvthenucfkphephedtrddvvd eirdejrddvudegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepughhtgesuggtrhhotghkvghrrdhnvght
X-ME-Proxy: <xmx:wwBMXpvdBcBQKRh5rfofrVVXcaxwl7m-I70HB_tRorDs2u4VXF-HaA> <xmx:wwBMXgSrnJVgCoDiAffp-yYAyBkw2ezyh5Fx52hrLyVU_Hp0vlulDg> <xmx:wwBMXnOeS0KYA_uPQK3jMVoF31mkQGZRgd3nRR0MGyPXXmPIXrpCwA> <xmx:wwBMXrpsQYHqWGE1tB5Cp6lz6TeIYZy1s5Wr0nec6Y4_J4qc6y4x7Q>
Received: from [172.16.137.206] (unknown [50.226.7.214]) by mail.messagingengine.com (Postfix) with ESMTPA id 42D813280060 for <ietf-smtp@ietf.org>; Tue, 18 Feb 2020 10:20:35 -0500 (EST)
To: ietf-smtp@ietf.org
References: <CAOEezJTLEzpDUivS50xUvQtQbNNyJXVKk29Q=c4QRaxgRvTxBw@mail.gmail.com> <972BC556117E20BE16D62E29@PSB> <7c7bd9e2-ffc8-c307-898a-2c827c72695f@tana.it>
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: dcrocker@bbiw.net
Message-ID: <eb8a1c75-294b-6deb-3bb2-68ac723543d5@dcrocker.net>
Date: Tue, 18 Feb 2020 07:20:36 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <7c7bd9e2-ffc8-c307-898a-2c827c72695f@tana.it>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/jx3liYWb-03tBy-GioOqWvQVqXQ>
Subject: Re: [ietf-smtp] Email standard revision
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: Tue, 18 Feb 2020 15:20:39 -0000

Folks,

After some discussion with Barry, what seems to have been missing is a 
clear statement of needs and goals.  Many different approaches to 
revision are possible and reasonable.  So the reasons for choosing one 
needs to be clear.


Logic for a limited effort:


     The current, well-established, core specifications for email are at 
a lower standards level than what the (realistically) long-obsolete 
versions.  The goal is to (finally) establish the later versions as full 
standards (and, I assume, declare the earlier versions as obsolete.)

     Any substantive revision to the current specifications runs the 
risk -- actually the likelihood -- of resulting in the output being 
labeled at a /lower/ standards level than it current has, thereby 
exacerbating the original issue.

     Hence the revision effort needs to be constrained to altering only 
essential, /minor/ details.  A cleanup exercise, if you will.



Yes?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net