Re: [ietf-822] Expires header field

Keith Moore <moore@network-heretics.com> Fri, 02 December 2022 18:46 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09E30C14F692 for <ietf-822@ietfa.amsl.com>; Fri, 2 Dec 2022 10:46:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.595
X-Spam-Level:
X-Spam-Status: No, score=-2.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dh6Au-ctQLIl for <ietf-822@ietfa.amsl.com>; Fri, 2 Dec 2022 10:46:33 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07EA4C14CF02 for <ietf-822@ietf.org>; Fri, 2 Dec 2022 10:46:32 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id F3B863200033 for <ietf-822@ietf.org>; Fri, 2 Dec 2022 13:46:31 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 02 Dec 2022 13:46:32 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1670006791; x=1670093191; bh=r+993RrNAbLZM5kmblm+lGfBUapJ bsHKbp5j3mbvIUQ=; b=nhC/H5u0IIFuN+8u4qVl0xbIUfXB9MPirN633KUdQbOD 1BiXszmx/5P1dJ8hJXmeSo1jQ9T0dGyvwjNL71ytjluh2DGQkvBxiQOPTDFxEkma pMhMvJCrBrFDyJACD0ZEBSjF+uupfFke36cR0qKDIiMfV/kiiipHpWMo1csnRl8D Yohy7vBcazoD5hshyfn4sBvp7FpvJ6ePLcd2+a56vTp8ttvIBgFid7nPSGFpmSjf hBcniSjmPxMl+3bY9O8dkGn3OV/g7SsGgUZyC2d4bMV+7vdB96dYRwkNtB6OBKU4 9NbP4QJV2rs2P2ceDYVSkxWE7g7dC5O0YXCJ2mbKRw==
X-ME-Sender: <xms:B0iKY_Gzz1ZZvABSpdALgzvr7bUhjpJZImSLVB38iicIgYbFGZ-uXw> <xme:B0iKY8U_PLoip-6SNZW4CUJytbcypErSNxOIwxrSc4hPvOb9cXt-4IQOq0H_o342Q ML3oIyOcBMU7Q>
X-ME-Received: <xmr:B0iKYxJ97gNKn-blL9BwksbfS7lobYT4yYHgO7GgR9U1iD4OkYB2wokwQsFA3Ti260vjSnW16n98MJmtXiPZPS9uuQWjxovAj0I5mgooOhyNdFufAS507g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrtdekgdelfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptgfkffggfgfuvfhfhfgjsegrtderre dtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthifohhr khdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeehfeduvdeggfefve eiiefggeeludefjeduieetledugeefffelffevieffkeeiffenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqd hhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:B0iKY9HYZB6cd7YSNtBNF_wZQAnRSQNBaIcR47aYoJBrENnrmI3S5w> <xmx:B0iKY1Xbq-bXy-PL-slXJsCG_VdKlB4U6f8rHg9ow6flmmlhKIVaYA> <xmx:B0iKY4NdfQfVuCEw8eExTvBP1303_9zid7vUAW3C4nmqo-Fj_sR8Zw> <xmx:B0iKY9hLrm4mOrmzL1Pwt-qQvhvsX4ptCYgf4TAcGr_BcHzQgizbTg>
Feedback-ID: i5d8c41f0:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ietf-822@ietf.org>; Fri, 2 Dec 2022 13:46:31 -0500 (EST)
Content-Type: multipart/alternative; boundary="------------a0IJE9jt9gwFW0VKvjM8rEf4"
Message-ID: <cc0f5979-0449-24e1-7150-9306a5180aed@network-heretics.com>
Date: Fri, 02 Dec 2022 13:46:29 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
Content-Language: en-US
To: ietf-822@ietf.org
References: <CAL0qLwa+yJkczF3TqepSVEvjMABzc0HR9-LLS3ejAUPt2A83vQ@mail.gmail.com> <6a77f4ff-af76-70c3-65b9-04f702914002@dcrocker.net>
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <6a77f4ff-af76-70c3-65b9-04f702914002@dcrocker.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/RQ3KRKUVC-UEEEkolhNmL6VK_b8>
Subject: Re: [ietf-822] Expires header field
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2022 18:46:37 -0000

On 12/2/22 11:53, Dave Crocker wrote:

> The draft does not indicate in what way this specification is an 
> update or enhancement to the previous version.
>
> I suspect the change has more to do with use than semantics, and it is 
> explicitly no change in syntax.
>
> Consequently, it is probably less confusing to just limit the history 
> references to the history section.
>
> So for the Abstract, perhaps instead:
>
> The Expires message header field indicates when a message becomes 
> valueless and can be deleted safely.  Recipients have the option to 
> use this information, as guidance for further message disposition.
>
Or perhaps:

The Expires message header field indicates a date-time after which the 
author of the message believes that the message no longer has primary 
relevance to its intended recipient(s).   After that expiration 
date-time has passed, an MUA may present the message in such a way as to 
reflect the message's decreased relevance.   This field SHOULD NOT be 
interpreted by intermediate systems (such as relaying MTAs or delivery 
agents), and SHOULD NOT be used to trigger automatic deletion of the 
message.

(though maybe it's better to avoid normative language in the abstract 
and instead place it elsewhere in the document)

>> 1.  Introduction
>>
>>     The date and time of expiration can be used by the mailbox provider
>>     or the MUA to indicate to the user that certain messages could be
> which provider?  which MUA?  And what is the basis for having an 
> originating system (mailbox provider) decide when a message expires?
>
> I suspect what is meant is:
>
> The data and time of expiration can be added by an author, to indicate 
> when a message is considered no longer useful.
>
I interpreted "mailbox provider" to mean "recipient's mailbox provider" 
rather than an originating system.   But since we interpreted this 
differently, it appears that additional clarification is needed.

I'd prefer that this document align itself with established terminology, 
when applicable, in preference to inventing new terminology.

Keith