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

Pete Resnick <resnick@episteme.net> Fri, 12 February 2021 00:35 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 96DA53A0EF0 for <ietf-smtp@ietfa.amsl.com>; Thu, 11 Feb 2021 16:35:20 -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 CxItQyv81mnW for <ietf-smtp@ietfa.amsl.com>; Thu, 11 Feb 2021 16:35:19 -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 26FD23A0EEF for <ietf-smtp@ietf.org>; Thu, 11 Feb 2021 16:35:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id D75D3D561849; Thu, 11 Feb 2021 18:35:17 -0600 (CST)
Received: from episteme.net ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCLkGpJGLX0d; Thu, 11 Feb 2021 18:35:17 -0600 (CST)
Received: from [172.16.1.16] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id F37C7D561838; Thu, 11 Feb 2021 18:35:16 -0600 (CST)
From: Pete Resnick <resnick@episteme.net>
To: John Levine <johnl@taugh.com>
Cc: ietf-smtp@ietf.org, dcrocker@bbiw.net
Date: Thu, 11 Feb 2021 18:35:16 -0600
X-Mailer: MailMate (1.14r5757)
Message-ID: <6D7EBCFD-C4C1-4623-BB95-4F6114A93C3B@episteme.net>
In-Reply-To: <20210204234602.6DB4D6D63596@ary.local>
References: <20210204234602.6DB4D6D63596@ary.local>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/TBOEhH8pD-Hd_5bBDbmpgd9sXzI>
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 00:35:21 -0000

On 4 Feb 2021, at 17:46, John Levine wrote:

> In article <ac72f2cc-7244-23d1-3615-a8f4e5f7388c@dcrocker.net> you 
> write:
>> This draft was prompted by discussion in the emailcore wg, but is
>> outside the scope of the wg charter.  So the spec is being pursued as
>> AD-sponsored.
>
> This short draft fills in a long standing gap in the specs.  MTAs have 
> been
> adding Delivered-To headers for over 20 years but the header has never 
> been
> registered with IANA and there's never been a spec saying what it 
> does.

Documenting an existing header field is always a good thing, but a 
couple of questions:

Is there any functional or semantic difference between an MDA adding 
Delivered-To: and an MDA adding a Received: with a 'for' clause 
containing the same address? Is it somehow conveying the semantic 
difference between an MTA and an MDA? It seems like Received: could have 
been used, and it can carry more info. (And perhaps the right question 
to ask before all that is: Why did folks start adding a Delivered-To: 
instead of just adding a Received: field with a 'for' clause?)

Also, does adding the Return-Path: happen before or after adding the 
Delivered-To:? The spec seems to indicate before, but it doesn't mention 
Return-Path: at all.

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