A few more concerns in addition to those I expressed earlier:
- Most MUAs and most other programs that print email messages (say for
use as evidence in court cases) typically won't display or print
Expires: header fields because that field has heretofore not been
regarded as significant. The reason I'm aware of this is that I've
sometimes had to explain to courts why a message that's been printed out
is not an accurate representation of the message that was actually sent,
because the program that printed out the message tried to be too clever,
say by converting the original date timezone to a different format.
And sometimes the precise timestamps matter.
- messages that expire before likely delivery, or only a very short time
after likely delivery. Especially
On 11/29/22 09:28, The IESG wrote:
The IESG has received a request from an individual submitter to consider the
following document: - 'Updated Use of the Expires Message Header Field'
<draft-billon-expires-06.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2022-12-27. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.
Abstract
This document allows broader use of the Expires message header field
for mail messages. Message creators can then indicate when a message
sent becomes valueless and can safely be deleted, while recipients
would use the information to delete or ignore these valueless
messages.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-billon-expires/
No IPR declarations have been submitted directly on this I-D.
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
