Re: [Emailcore] Two extra issues

Alexey Melnikov <aamelnikov@fastmail.fm> Fri, 18 December 2020 17:45 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: emailcore@ietfa.amsl.com
Delivered-To: emailcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB763A0B18 for <emailcore@ietfa.amsl.com>; Fri, 18 Dec 2020 09:45:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=rJwwNhYL; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=UVLV9ArK
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 YKGdIil6tzri for <emailcore@ietfa.amsl.com>; Fri, 18 Dec 2020 09:45:43 -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 8AEC43A0957 for <emailcore@ietf.org>; Fri, 18 Dec 2020 09:45:43 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 960BE9E2; Fri, 18 Dec 2020 12:45:42 -0500 (EST)
Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Fri, 18 Dec 2020 12:45:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=4lzy+8Aw+RjSRDGZjiazJTIFN3HAUTk t8YJ4XQiFCvw=; b=rJwwNhYLOLxvFYXzoTgpUqZuE4RQmrLvaGxiI8VXXP/XWiv jY1F/qYovdGyq9uyA+8jInOuDSlGNmiugmi7+BitfthVFyAc2Al35pafVbBaNcvh T2EepT+gochpcfVpEUazAi+Vqt9gNZJ/Sqxoa2zPnTnYuMbYBXaULgrLjTEXrrPR MClJoK30AoDpSepnO3F6OEjYVJbLHcREVAXyWLOcI8ybB8qeQ9UaHmqxVVWN912E jzW1imNMDXoT5W74jTTUz3n2ZLSjlfcZg8paUVkU4OsrvUAOnfpMQKb4IuRZdfBE 1s4fous2F2+lZMDXCFyqIc23jTYIRn2YHeMKU8Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=4lzy+8 Aw+RjSRDGZjiazJTIFN3HAUTkt8YJ4XQiFCvw=; b=UVLV9ArKkcQyZbNUF48bsx sWtnvV4z1heOvFs8+/SiujkR/a/MTSJ6rKUZvrcF3fAq2ROJGEv5hgdyVQ/qO0cL saOKX7pz3lbgOcWP/t+Q36jWWk1gmTz7n7q+3KsPdFmxF4c5SVYG+6LATIJ6bcPN Src0Ux3civV+LUx8dGiSYaqlm1s9PKHe81F4uY5rrPg4RKaipwDNhkzNdpNq6gX+ UEhAqYtlwtMzW1jZhzEf+H5/yEXlkTaISJhCSbbcRIBzqPBe/10xFyXpHfwmH2hk +PNf9jArUbABOtsr/tLaZsDK/5kGLjGmqGEkvn5sQRsf9EXiR5ub6oOPziHGrTQw ==
X-ME-Sender: <xms:xercX0aHLQNVhcr3invzXWnWZSP9I5spOULNfovUK9dxLrDZSwV1jQ> <xme:xercX_aYafLKdlGoct_X6jp2_7PfyzrUD38IR7EcVLR1EbMk4EPlWQlU_gexrP1Ej A41ELox6L74PTGAuA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeliedguddtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreertdenucfhrhhomhepfdetlhgvgigvhicuofgvlhhnihhkohhvfdcuoegrrghm vghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmheqnecuggftrfgrthhtvghrnheplefftd fghfevueduiefhffejlefgtdduhfdvtedtheeftedthfeghfefiefggeffnecuffhomhgr ihhnpehivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmh
X-ME-Proxy: <xmx:xercX-98i2S9l0BdqvYYrZI8GQ3HObMm6IbeOvlHU0Mk1xbuwmlanw> <xmx:xercX-pX2tRGzB2ycJY5f18Tvd0nuM_ljeg1ZDET0yWMb9L7VnxMqg> <xmx:xercX_pu7_8_eXwucMwPg8IPNOvehfYCJVc-k3FOiSHZ2D9xUum1bQ> <xmx:xurcX5G07yopH1Fljn3Y4yTqbwcV67ixaOebZ-qVK-M3R1B74uJQ7w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id EC0B16F60065; Fri, 18 Dec 2020 12:45:08 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.1-61-gb52c239-fm-20201210.001-gb52c2396
Mime-Version: 1.0
Message-Id: <6c4c5b51-69df-49be-b7b0-9a35f76c0e78@www.fastmail.com>
In-Reply-To: <9ABCA62E3E54C4356D09E1EE@PSB>
References: <9ABCA62E3E54C4356D09E1EE@PSB>
Date: Fri, 18 Dec 2020 17:43:21 +0000
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: John C Klensin <john-ietf@jck.com>, emailcore@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/-AkS4ReKzDuWHlY5K6it27Azj18>
Subject: Re: [Emailcore] Two extra issues
X-BeenThere: emailcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emailcore>, <mailto:emailcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore/>
List-Post: <mailto:emailcore@ietf.org>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emailcore>, <mailto:emailcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Dec 2020 17:45:46 -0000

Hi John,

On Thu, Dec 17, 2020, at 5:02 AM, John C Klensin wrote:
> Hi.
> 
> As mentioned in my note about ticket #2 sent about an hour ago,
> two additional issues came to my attention (or I was reminded
> about them) while looking at that issue and looking through the
> document.  
> 
> I've put them into the working version of what will become
> draft-ietf-emailcore-rfc5321bis-01 as:
> 
>        ----
> 
>  G.12.  Extension Keywords Starting in 'X-'
> 
>    Section 2.2.2 contains a discussion of SMTP keywords starting
> in "X".
>    Given general experience with such things and RFC 6648, is
> there any
>    reason to not deprecate that practice entirely and remove
> that text?
>    If we do so, should Section 4.1.5 be dropped or rewritten to
> make
>    clear this is an obsolete practice?

New ticket: <https://trac.ietf.org/trac/emailcore/ticket/42>
 
>  G.13.  Deprecating HELO
> 
>    RFC 5321 (and 2821 before it) very carefully circle around
> the status
>    of HELO, even recommending its use as a fallback when EHLO is
> sent
>    and a "command not recognized" response is received.  We are
> just a
>    few months short of 20 years; is it time to deprecate the
> thing and
>    clean out some or all of that text?  And, given a recent
> (4Q2020)
>    discussion on the EMAILCORE list, should EHLO be explicitly
> bound to
>    SMTP over TCP with the older transports allowed only with
> HELO?
>    While those questions may seem independent, separating them
> is fairly
>    hard given the way the text is now constructed.

New ticket: <https://trac.ietf.org/trac/emailcore/ticket/43>

> Two more things...
> 
> (1) I think I've figured out how to overlay the ticket numbers
> from https://trac.ietf.org/trac/emailcore/report/1 onto the
> relevant lists in 5321bis where they are applicable, so the
> request for someone to build a table for me is withdrawn -- they
> will be in the next version.
> 
> (2) I await guidance from the WG Chairs as to when to post a new
> version.  My personal preference would be to wait until we have
> at least a few more tickets resolved, but up to them (and the
> WG).

I agree, you should wait until a few more issues are resolved.

Best Regards,
Alexey