Re: [ietf-smtp] To trace field or not to trace field
Dave Crocker <dhc@dcrocker.net> Mon, 15 February 2021 18:15 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 59CD73A0E9E for <ietf-smtp@ietfa.amsl.com>; Mon, 15 Feb 2021 10:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.201
X-Spam-Level:
X-Spam-Status: No, score=-0.201 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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=dcrocker.net
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 sxtLxS26dtvU for <ietf-smtp@ietfa.amsl.com>; Mon, 15 Feb 2021 10:15:13 -0800 (PST)
Received: from black.elm.relay.mailchannels.net (black.elm.relay.mailchannels.net [23.83.212.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 894523A0E63 for <ietf-smtp@ietf.org>; Mon, 15 Feb 2021 10:15:11 -0800 (PST)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 3D35C7E34A2 for <ietf-smtp@ietf.org>; Mon, 15 Feb 2021 18:15:08 +0000 (UTC)
Received: from nl-srv-smtpout3.hostinger.io (100-96-27-118.trex.outbound.svc.cluster.local [100.96.27.118]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 7567C7E365E for <ietf-smtp@ietf.org>; Mon, 15 Feb 2021 18:15:07 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout3.hostinger.io ([UNAVAILABLE]. [145.14.159.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.27.118 (trex/6.1.1); Mon, 15 Feb 2021 18:15:08 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Wipe-Army: 26d2803744c70308_1613412907991_1018505875
X-MC-Loop-Signature: 1613412907991:3412149548
X-MC-Ingress-Time: 1613412907991
Received: from [192.168.0.109] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout3.hostinger.io (smtp.hostinger.com) with ESMTPSA id 4E47431C338C for <ietf-smtp@ietf.org>; Mon, 15 Feb 2021 18:15:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1613412905; bh=MbNW66K25nqs2dfknoYVMDsEZFPNG4vAnnr588fDk6g=; h=Reply-To:Subject:From:To:References:Date:In-Reply-To; b=kHjuaE0wjZDptCC/ldWuFIrvA02J3uX7rYnFAutwReEARdLUuAIWByixBUC4wFX+h Y1ltbxEo43e+YtcPQ4UfAQ93N0s995MVTD6INi+FRWgG5NgUazek7Rxp4+QEnNxOj7 /cHUK6OYpB6dxJmzguCKym8P5vCYeeqMAzeSEycGHPHgDiDH0393gPN8gVpV0Rppbg 8sF4d6mCxgZNtx/wBX+tio8Ii8iMRGdwxoacrgMO3iZWoLoVa56zDBrltxfHRdh6LQ gCatmcZBjVD9H+UUWQ/6vohFBf2TRx7WF9sybSz/kotacpwcUavXt7R5phxViisb2w XaEomGoAFVAaw==
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
To: ietf-smtp <ietf-smtp@ietf.org>
References: <0bc4b7fa-d461-6307-c28e-7d048e4a8b2d@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <cb80e267-9265-31b8-928e-9a9324732a72@dcrocker.net>
Date: Mon, 15 Feb 2021 10:15:03 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <0bc4b7fa-d461-6307-c28e-7d048e4a8b2d@dcrocker.net>
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/8_nSzT5RWhEA0-iucrt3GC_B8pQ>
Subject: Re: [ietf-smtp] To trace field or not to trace field
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 18:15:14 -0000
On 2/15/2021 10:02 AM, Dave Crocker wrote:
> Here is the revised text:
I've also revised the introductory text to the section showing an example:
<section title="Multi-hop Example">
<t>The Delivered-To: header field can indicate a sequence of
deliveries, as demonstrated by this example, which has a message
traveling through a mailing list, on through an alias, and then reaching
final delivery...
I should note meta-point about specification writing...
The original draft had a single example header. Barry suggested making
it show a sequence. I've been impressed with the difference.
So my new meta-rule is that defining something that has relevance to a
sequence should include an example that demonstrates the sequence.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
- [ietf-smtp] To trace field or not to trace field Dave Crocker
- Re: [ietf-smtp] To trace field or not to trace fi… Dave Crocker
- Re: [ietf-smtp] To trace field or not to trace fi… Alexey Melnikov