Re: Scope for self-destructing email?

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 17 August 2017 01:24 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 061BA132391 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 18:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KCJiW_qQzwsW for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 18:24:28 -0700 (PDT)
Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3C5A126BF0 for <ietf@ietf.org>; Wed, 16 Aug 2017 18:24:28 -0700 (PDT)
Received: by mail-pg0-x22b.google.com with SMTP id t80so4451233pgb.5 for <ietf@ietf.org>; Wed, 16 Aug 2017 18:24:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ObVYgHMPz3WR8VTFtfo7oxuFReLd4DSW0GIkGvYRaX8=; b=mVmht3zh/zjjB1SsRMIYem/9sTuK13F1Wypztr5rpvkgB+AjY148GZP4fFdUkPEY4i xD/GAtecoHoJwsaplCUXdSNOuNJxK061t7+2b611H+LrL4KLrikAK+TF7/H0Klb9f3xh aDtolyqeJZSL9nudq9Yz989bAGwlK2cXF71XVZVsd19gJQCb0wO+fj6CuGcV4i31/DzK 9Vo1FmFQQCgvX4EPoJm/GDBjheyg4RkXb5gDelbxKIBd3if7uQCd0rgQ6pAVQApCft9y JsnCv4+eQpsA27r6QqIij90rV/0/zoBGFnegE5XHLWeu+bUdzcQyYMsKozpHnltb2tjx QHiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=ObVYgHMPz3WR8VTFtfo7oxuFReLd4DSW0GIkGvYRaX8=; b=odYrKG9GNL//OZ6hSLd6Pv7Ip9cPq4SiPKX/wcE/6RIuJ1Cm6djhQLNOTq3k/Lxuxm f+PScnJOO0fVCo1LygFV6fuOrrq/02d3QDFLl1Ef0fTtOUooOxBGGU1U2wfGMqeivArz fEVx70yHVOxtQVO7NJfD2AzSYtEI2jiaE/u/LrpiI6JCndTewyAJiZWaOSbS7rsgvAEG CXbPkVfnvVaraOOI44QLSPo7zq/ygcKjg2LuHnPkNanf0yEEP2D99BIKy8tj3LJJZmlQ ikIzoTYuUgpqWLlCinJXumBIsSJQlHlLCNaiFawxbO+Pajqc2+jHFKhUZ4YCLoidL0E5 BV2A==
X-Gm-Message-State: AHYfb5i2bt5qTMpqKtN65JjNxBAJw+ISMTp9QCxtyCkRjNp2ygrz83uG i6JGjXvZt5UgBA==
X-Received: by 10.84.231.9 with SMTP id f9mr3816523plk.257.1502933068215; Wed, 16 Aug 2017 18:24:28 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u12sm3566719pgq.24.2017.08.16.18.24.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Aug 2017 18:24:27 -0700 (PDT)
Subject: Re: Scope for self-destructing email?
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Cc: vaibhavsinghacads@gmail.com
References: <20170816225637.4431.qmail@ary.lan>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com>
Date: Thu, 17 Aug 2017 13:24:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170816225637.4431.qmail@ary.lan>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L5u8U7wLdBxs4_Wbf5Vx16EF1yw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Aug 2017 01:24:31 -0000

On 17/08/2017 10:56, John Levine wrote:
> In article <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> you write:
>> This seems to work for me. Any problems which could come up with having a
>> central authority for this feature?
> 
> Many.  What if I tell the central authority that I implement
> self-destructive e-mail but I'm lying?  How could the central
> authority tell?  I'm pretty sure I can pass whatever audits they make
> since they have no way to tell what data I'm hiding in places they
> can't see.
> 
>> 4.) A really boiled down version of ephemeral mails could just mark the
>> mail "outdated" if the information provided in the mail is not expected to
>> hold good after some time, instead of actually expunging the mail.
> 
> As others have said, that feature has come and gone many times in the past.  In
> netnews, which is similar in some ways to mail, there's an Expires: header which
> works reasonably well, typically used to mark messages that stop being interesting
> after some point like weather forecasts or event reminders.  There's no guarantee
> that anyone will follow the advice, and you certainly can't use it to force stuff
> to disappear, but it's been occasionally useful.

I thought of changing the title to "Scope for self-destructing web pages?"

After I heard an early internal presentation of the design of the World-Wide Web
from my CERN colleague Tim Berners-Lee, probably in 1993, I asked him why he didn't
make an expiry date a mandatory feature of every HTML document. Being a man of some
foresight, he explained exactly why it wouldn't work in practice, despite being
a wonderful idea in theory.

And yes, according to RFC 1866 (and for all I know, more recent definitions
of HTML) you can include things like
    <META HTTP-EQUIV="Expires" CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">
and the server may then include "Expires: Tue, 04 Dec 1993 21:29:02 GMT"
in the reply to an HTTP GET.

Only, have you noticed any web pages expiring recently? Maybe there are
browsers that annoy their users by not displaying expired pages?

Bits don't expire.

    Brian