Re: [ietf-smtp] New Version Notification for draft-crocker-email-deliveredto-00.txt
John C Klensin <john-ietf@jck.com> Mon, 15 February 2021 01:43 UTC
Return-Path: <john-ietf@jck.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 79B6B3A0FD1 for <ietf-smtp@ietfa.amsl.com>; Sun, 14 Feb 2021 17:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[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 vxWatrROEMZL for <ietf-smtp@ietfa.amsl.com>; Sun, 14 Feb 2021 17:43:23 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF7A73A0FD0 for <ietf-smtp@ietf.org>; Sun, 14 Feb 2021 17:43:23 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1lBSuy-0001sX-F2; Sun, 14 Feb 2021 20:43:16 -0500
Date: Sun, 14 Feb 2021 20:43:10 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <resnick@episteme.net>, dcrocker@bbiw.net
cc: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
Message-ID: <9C405D5FE4831396FFF39DDD@PSB>
In-Reply-To: <54BC4A2C-9B44-4369-AB16-85716CD404E3@episteme.net>
References: <20210204234602.6DB4D6D63596@ary.local> <6D7EBCFD-C4C1-4623-BB95-4F6114A93C3B@episteme.net> <a6e19810-4fe4-3b2a-8c79-0f9397b77c9f@dcrocker.net> <2F7AAE37-2D9D-4CFD-9FC1-8E174BA13693@episteme.net> <b1a67354-2edb-8ffd-af6b-aa776219d9d4@dcrocker.net> <54BC4A2C-9B44-4369-AB16-85716CD404E3@episteme.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/VO04iET2PqRRLdo-PeXMoanflWw>
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: Mon, 15 Feb 2021 01:43:25 -0000
--On Sunday, February 14, 2021 14:23 -0600 Pete Resnick <resnick@episteme.net> wrote: > On 14 Feb 2021, at 10:09, Dave Crocker wrote: > >> On 2/12/2021 9:03 AM, Pete Resnick wrote: >>> 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. >> >> >> It's always dangerous to attempt at deriving normative >> requirements from examples, of course. >> >> The current text just says to add Delivered-To: to the top >> and it says what actor is to do this. I think that has all >> of what is required about the field itself. >> >> RFC 5321 (Section 4.1.1.4) has similar detail, in its 5th >> paragraph. >> >> Guessing at a requirement about the combination of the fields >> goes quite a bit beyond either of the specifications. >> >> One could imagine a usage document discussing this, but there >> does not seem to be a benefit in creating a constraint about >> their combination in this specification. > > To the contrary: I am perfectly happy if there is no defined > order or constraint on the order, but I do think it's worth > saying that they MAY appear in either order (i.e., no > implementation should ever act on the order that they happen > to appear in). I don't feel strongly about this, but I've run into several MUAs over the years that expected Return-to: to be the first/top header field and that would get more or less confused or irritated if it was not there. That is a plausible inference from, e.g., the use of "beginning of" in Section 4.4. Other inferences are also plausible, especially if one assumes that processing between "final delivery" and the MUA (which the IETF carefully avoided trying to specify for many years and for which, AFAIK, there are still no standards track specifications) could add header fields before the SMTP-specified trace ones... or if one were concerned about SMTP extensions providing for such "at the beginning" fields. So I would agree that whatever this document chooses to say should be clear. And, if this discussion calls for a revision or clarification of the meaning of "beginning of" in 5321bis, presumably everyone here knows where and how to generate a ticket [1]. john [1] While addressing some of the same paragraphs, this note is quite separate from the issue raised in a recent note to that list ( https://mailarchive.ietf.org/arch/msg/emailcore/8nQGWm2r08OyjsuVAaVaZqik7cI ). Relative to 5321/ 5321bis, the above is about the interpretation and implications of "beginning of" while that other message is about "beginning of <what>".
- [ietf-smtp] Fwd: New Version Notification for dra… Dave Crocker
- Re: [ietf-smtp] Fwd: New Version Notification for… John Levine
- Re: [ietf-smtp] Fwd: New Version Notification for… Alessandro Vesely
- Re: [ietf-smtp] Fwd: New Version Notification for… Dave Crocker
- Re: [ietf-smtp] Fwd: New Version Notification for… Alessandro Vesely
- Re: [ietf-smtp] Fwd: New Version Notification for… Dave Crocker
- Re: [ietf-smtp] Fwd: New Version Notification for… John Levine
- Re: [ietf-smtp] Fwd: New Version Notification for… Valdis Kl ē tnieks
- Re: [ietf-smtp] Fwd: New Version Notification for… Dave Crocker
- Re: [ietf-smtp] Fwd: New Version Notification for… Alessandro Vesely
- Re: [ietf-smtp] Fwd: New Version Notification for… John Levine
- Re: [ietf-smtp] Fwd: New Version Notification for… Dave Crocker
- Re: [ietf-smtp] New Version Notification for draf… Pete Resnick
- Re: [ietf-smtp] New Version Notification for draf… Pete Resnick
- Re: [ietf-smtp] New Version Notification for draf… John R Levine
- Re: [ietf-smtp] New Version Notification for draf… Sam Varshavchik
- Re: [ietf-smtp] New Version Notification for draf… Dave Crocker
- Re: [ietf-smtp] New Version Notification for draf… Pete Resnick
- Re: [ietf-smtp] New Version Notification for draf… John R Levine
- Re: [ietf-smtp] New Version Notification for draf… Dave Crocker
- Re: [ietf-smtp] New Version Notification for draf… Dave Crocker
- Re: [ietf-smtp] New Version Notification for draf… John R Levine
- Re: [ietf-smtp] New Version Notification for draf… Pete Resnick
- Re: [ietf-smtp] New Version Notification for draf… Dave Crocker
- Re: [ietf-smtp] New Version Notification for draf… Valdis Kl ē tnieks
- Re: [ietf-smtp] New Version Notification for draf… John R Levine
- Re: [ietf-smtp] what's not a trace field John R. Levine
- Re: [ietf-smtp] New Version Notification for draf… John Levine
- Re: [ietf-smtp] New Version Notification for draf… Pete Resnick
- Re: [ietf-smtp] New Version Notification for draf… Dave Crocker
- Re: [ietf-smtp] New Version Notification for draf… John C Klensin
- Re: [ietf-smtp] New Version Notification for draf… John R Levine
- Re: [ietf-smtp] New Version Notification for draf… John Levine
- Re: [ietf-smtp] New Version Notification for draf… Dave Crocker
- Re: [ietf-smtp] New Version Notification for draf… John C Klensin
- Re: [ietf-smtp] New Version Notification for draf… Dave Crocker
- Re: [ietf-smtp] New Version Notification for draf… John C Klensin
- Re: [ietf-smtp] what's not a trace field Alexey Melnikov
- Re: [ietf-smtp] return-path vs delivered-to, was … John Levine
- Re: [ietf-smtp] return-path vs delivered-to, was … Dave Crocker
- Re: [ietf-smtp] return-path vs delivered-to, was … John R Levine
- Re: [ietf-smtp] return-path vs delivered-to, was … Dave Crocker
- Re: [ietf-smtp] return-path vs delivered-to, was … John C Klensin
- Re: [ietf-smtp] return-path vs delivered-to, was … Dave Crocker
- Re: [ietf-smtp] what's not a trace field Dave Crocker
- Re: [ietf-smtp] what's not a trace field John R. Levine
- Re: [ietf-smtp] what's not a trace field Dave Crocker
- Re: [ietf-smtp] what's not a trace field John R. Levine
- Re: [ietf-smtp] what's not a trace field Dave Crocker
- Re: [ietf-smtp] what's not a trace field John R. Levine
- Re: [ietf-smtp] what's not a trace field Dave Crocker
- Re: [ietf-smtp] return-path vs delivered-to, was … Alexey Melnikov
- Re: [ietf-smtp] what's not a trace field Ned Freed
- Re: [ietf-smtp] what's not a trace field Kurt Andersen (b)
- Re: [ietf-smtp] what's not a trace field John R. Levine
- Re: [ietf-smtp] what's not a trace field Dave Crocker
- Re: [ietf-smtp] what's not a trace field John Levine
- Re: [ietf-smtp] what's not a trace field Dave Crocker
- Re: [ietf-smtp] what's not a trace field John R Levine
- Re: [ietf-smtp] what's not a trace field Dave Crocker
- Re: [ietf-smtp] what's not a trace field John R Levine
- Re: [ietf-smtp] what's not a trace field Dave Crocker
- Re: [ietf-smtp] what's not a trace field John C Klensin
- Re: [ietf-smtp] what's not a trace field Alessandro Vesely
- Re: [ietf-smtp] what's not a trace field Dave Crocker