IETF Logo Mail Archive

Re: Scope for self-destructing email?

John C Klensin <john-ietf@jck.com> Tue, 15 August 2017 01:38 UTC

Return-Path: <john-ietf@jck.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 DEE66126B7E for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 18:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 hCJ42WCBEP7G for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 18:38:22 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A0D91321B6 for <ietf@ietf.org>; Mon, 14 Aug 2017 18:38:22 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dhQoH-000Aab-AW; Mon, 14 Aug 2017 21:38:21 -0400
Date: Mon, 14 Aug 2017 21:38:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: ietf@ietf.org
Subject: Re: Scope for self-destructing email?
Message-ID: <889C187443C99CC61539528A@PSB>
In-Reply-To: <a12ac1b5-f6a9-679c-23a2-61e715c43016@gmail.com>
References: <bc180881-4562-4b97-a625-51ef29770d9f@email.android.com> <6ce40fd4-3de7-b016-55f8-68b96df33333@alumni.stanford.edu> <a12ac1b5-f6a9-679c-23a2-61e715c43016@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0yNjv3Ial7O5E5MH6BScYFljUYo>
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: Tue, 15 Aug 2017 01:38:24 -0000


--On Tuesday, August 15, 2017 13:32 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> More seriously, how could you have any confidence at all that
>> unauthorized (or even "lawful intercept") copies of the
>> message would be deleted?
> 
> You can't. I have destroyed Message-ID:
> <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmai
> l.com>. Is that true? How do you know it's true?

Even if I had some way to verify that your statement about your
actions were true and that what you meant by "destroyed"
included any backup copies you might have kept as a side-effect
of other operations or procedures, there is no way that you can
guarantee that Google has destroyed it too.   Indeed, prior to
the recent change in Gmail policy, I one could infer that they
had not and would not until whatever information it was
contained were deemed of no relevance.

   john

v2.23.0 | Report a Bug | By Email