Scope for self-destructing email?

vaibhav singh <vaibhavsinghacads@gmail.com> Mon, 14 August 2017 19:01 UTC

Return-Path: <vaibhavsinghacads@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 94DFC1323F9 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 X66hfmK1FmW1 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:01:54 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 D06BF132399 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:01:53 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id m34so111005iti.1 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:01:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=u3uVuTOZp2F/GwKNTXF2NIe9F9ThEI799mGNQM7L5eA=; b=NFV8a3ZNhjX3C3N01+YQid3g9tzZ5tPrdrbp4QnfSNtnYXrjeev+wSsv8DcFqVQCkr 5zYed3qxG9L5ZhvQ7JbfDTxPzb4tFU7hRdjapwOn9me60K2slQqmWCntMf7pQwlwWsjZ KYhOKNQIEEYkyc8rS6C3i90nRm1AzFswyM0WGYMp+4BSj2KYgTpAe2oQcBL9xyTJIj8h UgCTd2TjyBEQYHOgf8Tltok0RwfGlS4oDb/BqxvjUoFBJcZU7IVLdxJJnpevlP15Of/u nbjMUjnMoaelL9b939uszVbWZFht+3/BGkFgEOtXfOITYZtYN89wTKw/p3luvzzxytgZ qTDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=u3uVuTOZp2F/GwKNTXF2NIe9F9ThEI799mGNQM7L5eA=; b=I9BVGj+5ZANAeTmXiZDcQy7daXJgDhrNSuX6yqhga8j9plWTBB9cVqX4JkHIG66dHn ZBN9Xd6KKK5ypxx5nZxMOuC7ZRJUaRXdGjx3O/oP/Qid4XYP6G1odqCFiAgk3Pr3rZHe z3mGk7iGGWp0dVfjnNyselZ+wliqbGlAdm7BLyYVJ6JysN0MNlIuw9UetNnKKGWYFinK xnGp/l03S+fWmeZmCu+5WZvKHfUjqENRhIiz/yBM29YWL3mhqXh8v5Ik2u5pWTtLcYuU G8c/63nmEcnU4ynBY7iv6k2Ev8RRO+pKpNyez6uSbseNKfRliaZIyARWfyZL3aO5XZtp xZfA==
X-Gm-Message-State: AHYfb5glUCyNbawxuV0Ue6stjjsm++O7bSOFcgb7GsJDZglWc3XiQ8uG nBEcBl/vl0wxlHqJgvW3n1gSj+629zHz
X-Received: by 10.36.243.77 with SMTP id t13mr15794iti.50.1502737312948; Mon, 14 Aug 2017 12:01:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.208 with HTTP; Mon, 14 Aug 2017 12:01:52 -0700 (PDT)
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Tue, 15 Aug 2017 00:31:52 +0530
Message-ID: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
Subject: Scope for self-destructing email?
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045fb318baa61d0556bb4bd4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vDgc5yI8hkkITEC9i_eAiRpWLPQ>
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:01:56 -0000

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.

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.

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).

I would also like to know about things (working groups, internet drafts
etc) which are being done to enforce GDPR to
email and Instant Messaging especially.

-- 

Regards,
Vaibhav Singh