Ted Hardie <ted.ietf@xxxxxxxxx> wrote:
> The first is providing a facility that declares a particular message to be
> automatically overcome by events at a particular time, leaving it completely
> up to the recipient how to process the message based on that metadata. There
> are simple message types (today's weather, lunch availability, etc.) that
> could be thus set to be marked OBE when no longer relevant. Some
> clients
This is an interesting idea. For those of us who deal with many emails,
(particularly upon return from vacation), not having to deal with lunch plans
that have expired would in fact be nice.
Some of us still deal with cron job output. An hourly job that fails all
weekend generates a lot of email, and often only the most recent failure is
at all useful to know about. That's a job for good-old-Usenet Supercedes:,
but that's one email overcoming another, and the whole thing needs
some cryptographic support. Note that a merkle hash (a la s/key) would
probably suffice.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature