Re: [ietf-smtp] New Version Notification for draft-crocker-email-deliveredto-00.txt

Pete Resnick <resnick@episteme.net> Fri, 12 February 2021 17:03 UTC

Return-Path: <resnick@episteme.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 DAB663A17C8 for <ietf-smtp@ietfa.amsl.com>; Fri, 12 Feb 2021 09:03:56 -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 ah-Nw3FZKzpm for <ietf-smtp@ietfa.amsl.com>; Fri, 12 Feb 2021 09:03:54 -0800 (PST)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CF643A17CD for <ietf-smtp@ietf.org>; Fri, 12 Feb 2021 09:03:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 86BBCD581664; Fri, 12 Feb 2021 11:03:53 -0600 (CST)
Received: from episteme.net ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ju2uJ8XefAAw; Fri, 12 Feb 2021 11:03:52 -0600 (CST)
Received: from [172.16.1.16] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 6D966D58165A; Fri, 12 Feb 2021 11:03:52 -0600 (CST)
From: Pete Resnick <resnick@episteme.net>
To: dcrocker@bbiw.net
Cc: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
Date: Fri, 12 Feb 2021 11:03:51 -0600
X-Mailer: MailMate (1.14r5757)
Message-ID: <2F7AAE37-2D9D-4CFD-9FC1-8E174BA13693@episteme.net>
In-Reply-To: <a6e19810-4fe4-3b2a-8c79-0f9397b77c9f@dcrocker.net>
References: <20210204234602.6DB4D6D63596@ary.local> <6D7EBCFD-C4C1-4623-BB95-4F6114A93C3B@episteme.net> <a6e19810-4fe4-3b2a-8c79-0f9397b77c9f@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/eiGxe3QuBt6TP4HZU4O9t3Z1oZI>
Subject: Re: [ietf-smtp] New Version Notification for draft-crocker-email-deliveredto-00.txt
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: Fri, 12 Feb 2021 17:03:57 -0000

On 11 Feb 2021, at 20:48, Dave Crocker wrote:

> On 2/11/2021 4:35 PM, Pete Resnick wrote:
>> Also, does adding the Return-Path: happen before or after adding the 
>> Delivered-To:? The spec seems to indicate [after], but it doesn't 
>> mention Return-Path: at all.
>
>
> One is specified in 821 & 822, ff.  The other is specified in this new 
> draft.  Neither is jointly specified.
>
> I haven't noticed anything in the new draft that even mentions them 
> jointly.  Indeed, Received: is only cited in the new draft in the 
> Security Considerations section.
>
> If there is anything in it that produced the 'seems to indicate' 
> impression, I'd like to know what it is, so I can fix it.  Even if 
> they are added by the same process, I would not expect there to be any 
> order dependency.

The examples show Delivered-To: next to the last Received: field, which 
implies that Return-Path: is going to get pre-pended after the 
Delivered-To: field. If in practice they can appear in either order 
(which seems perfectly plausible), that seems like a reasonable thing to 
mention. If in practice they always appear in a particular order (which 
also seems plausible) and some entity later reading the message relies 
on that order (which doesn't seem like a great idea, but weirder things 
have happened), that seems like an important thing to say. Either way, 
setting expectations seems good.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best