Internet-Draft submission

idnits 2.16.02 

/a/www/www6s/staging/draft-brezorubio-wg-oblivion-00.txt:

  Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
  Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed before draft submission.

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Running in submission checking mode -- *not* checking nits according to
  https://www.ietf.org/id-info/checklist .
  ----------------------------------------------------------------------------


     No nits found.

Network Working Group                                           F. Brezo
Internet-Draft                                                  Y. Rubio
Intended status: Informational                                   i3visio
Expires: June 6, 2019                                  December 03, 2018


            A Method for Deactivation and Deletion Policies
                    draft-brezorubio-wg-oblivion-00

Abstract

   The existing methods for opting out or asking for users data stored
   by a service are far from being standard.  This fact makes the
   process of deactivating or deleting an account from a website
   difficult to find since each platform provides the link in a
   different way.  This document defines a standard ("oblivion.txt") to
   help organizations to describe the steps to follow by a user for
   deactivating or deleting an account from their websites as well as
   shipping the personal data linked to its users in a secure and
   standard way.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 6, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect



Brezo & Rubio             Expires June 6, 2019                  [Page 1]
Internet-Draft                     I-D                     December 2018


   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

1.1.  Motivation and Previous Work

   Many of the standard interaction of end users with online services
   involve creating and managing personal accounts.  Even when the
   creation of these accounts may seem easy to control, generally, the
   deletion and deactivation of an account does not fulfill with any
   type of standards making each experience look differently.  Regarding
   this issue, there has been efforts to list the procedures followed by
   different platforms to conduct this task.  For example, the project
   JustDelete.me shows a list of direct links to deletion URLs on
   different platforms.  However, this process is mainly curated by
   contributors, which is an approach that does not scale well.

   Similarly, the processes of requesting all the personal data stored
   by a service or even the management of the consents collected by it
   usually involve manual interactions withnon-standarized systems.
   These processes, enforced by law in many countries, are no longer
   easy to identify by the end user, hindering the exercise of rights
   inherent to the citizens.

   In this document, we define a machine-readable and extensible way of
   communicating how users can interact with a service to deactivate
   their accounts or fully deleting them.  This standard is thought to
   assist companies on providing a transparent and reachable way of
   giving access to their opt-out procedures so as to give back to the
   users the right to keep control of their own digital footprint.

1.2.  Terminology

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
   and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].

2.  The Specification

   This standard defines a text file to be placed in a known location
   that provides information for users and applications to assist them
   in the process of finding the tools to delete or remove accounts and
   services.




Brezo & Rubio             Expires June 6, 2019                  [Page 2]