Re: Scope for self-destructing email?
Matthias Merkel <moritz30@moritz30.de> Mon, 14 August 2017 19:14 UTC
Return-Path: <moritz30@moritz30.de>
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 ECEE813240D for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:14:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.08
X-Spam-Level: *
X-Spam-Status: No, score=1.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no 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 KlGI9_lqoGzk for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:14:30 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59364132408 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:14:30 -0700 (PDT)
Received: from [10.53.190.197] (x590feec5.dyn.telefonica.de [89.15.238.197]) by mx.zohomail.com with SMTPS id 1502738063227750.3543644352833; Mon, 14 Aug 2017 12:14:23 -0700 (PDT)
Date: Mon, 14 Aug 2017 21:13:54 +0200
Subject: Re: Scope for self-destructing email?
Message-ID: <b5b27ee1-430f-421d-800b-822e5b6bd45c@email.android.com>
X-Android-Message-ID: <b5b27ee1-430f-421d-800b-822e5b6bd45c@email.android.com>
In-Reply-To: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
From: Matthias Merkel <moritz30@moritz30.de>
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/41PXcgJgSyHm3TLVvPmtVjurWUU>
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: Mon, 14 Aug 2017 19:14:32 -0000
Another enhancement to this idea was a notification which will be sent from some (Exploding email RFC) compliant MUA, in case the receiver refuses to delete the email from the client. (I know Snapchat is a poor example here, but they apparently send notifications to the originator of the snap in case any receiver tries to capture the screenshot of the snap. This is, in theory, what we are trying to do here).With regards to this, me and my friends were thinking about the idea of a self-destructing email, wherein the sender will mark the mail to be destroyed (expunged from the server) once the receiver(s) have finished reading it/after a time period chosen by the sender.Hi,As some of you may already know, General Data Protection Regulation (GDPR), about to be enforced in the EU within months, and calls for strict regulations for Right to rectify communications, Right to be forgotten , Pseudonymisation and Data portability.I would also like to know about things (working groups, internet drafts etc) which are being done to enforce GDPR toemail and Instant Messaging especially.--Regards,Vaibhav Singh
- Scope for self-destructing email? vaibhav singh
- Re: Scope for self-destructing email? Matthias Merkel
- Re: Scope for self-destructing email? Dave Cridland
- Re: Scope for self-destructing email? Matthias Merkel
- Re: Scope for self-destructing email? Matthew Pounsett
- Re: Scope for self-destructing email? Warren Kumari
- Re: Scope for self-destructing email? Matthias Merkel
- Re: Scope for self-destructing email? Randy Presuhn
- Re: Scope for self-destructing email? Martin Rex
- Re: Scope for self-destructing email? Brian E Carpenter
- Re: Scope for self-destructing email? John C Klensin
- Re: Scope for self-destructing email? John Levine
- Re: Scope for self-destructing email? joel jaeggli
- RE: Scope for self-destructing email? Michel Py
- Re: Scope for self-destructing email? John Levine
- Re: Scope for self-destructing email? Theodore V Faber
- Re: Scope for self-destructing email? vaibhav singh
- Re: Scope for self-destructing email? Ted Hardie
- Re: Scope for self-destructing email? Matthias Merkel
- Re: Scope for self-destructing email? John C Klensin
- Re: Scope for self-destructing email? Matthias Merkel
- Re: Scope for self-destructing email? John C Klensin
- Re: Scope for self-destructing email? Warren Kumari
- Re: Scope for self-destructing email? Ted Hardie
- Re: Scope for self-destructing email? Brian E Carpenter
- Re: Scope for self-destructing email? Lyndon Nerenberg
- Re: Scope for self-destructing email? Phillip Hallam-Baker
- Re: Scope for self-destructing email? Deen, Glenn (NBCUniversal)
- Re: Scope for self-destructing email? Phillip Hallam-Baker
- Re: Scope for self-destructing email? Christian Huitema
- Re: Scope for self-destructing email? Gary E. Miller
- Re: Scope for self-destructing email? Michael Richardson
- Re: Scope for self-destructing email? John C Klensin
- Re: Scope for self-destructing email? Phillip Hallam-Baker
- Re: Scope for self-destructing email? John Levine
- Re: Scope for self-destructing email? ned+ietf
- Re: Scope for self-destructing email? Adam Roach
- Re: Scope for self-destructing email? Phillip Hallam-Baker
- Re: Scope for self-destructing email? Phillip Hallam-Baker
- Re: Scope for self-destructing email? John R Levine
- Re: Scope for self-destructing email? Toerless Eckert
- Re: Scope for self-destructing email? Lloyd Wood
- Email client APIs. features. amd siupport (was: R… John C Klensin
- Re: Email client APIs. features. amd siupport (wa… Toerless Eckert
- Re: Email client APIs. features. amd siupport (wa… Phillip Hallam-Baker