pretty Easy privacy (pEp): Privacy by Default
draft-birk-pep-03

Document Type Active Internet-Draft (individual)
Last updated 2019-03-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         H. Marques
Internet-Draft                                            pEp Foundation
Intended status: Standards Track                            B. Hoeneisen
Expires: September 8, 2019                                       Ucom.ch
                                                          March 07, 2019

             pretty Easy privacy (pEp): Privacy by Default
                           draft-birk-pep-03

Abstract

   The pretty Easy privacy (pEp) protocols describe a set of conventions
   for the automation of operations traditionally seen as barriers to
   the use and deployment of secure end-to-end interpersonal messaging.
   These include, but are not limited to, key management, key discovery,
   and private key handling (including peer-to-peer synchronization of
   private keys and other user data across devices). pEp also introduces
   means to verify communication peers and proposes a trust-rating
   system to denote secure types of communications and signal the
   privacy level available on a per-user and per-message level.
   Significantly, the pEp protocols build on already available security
   formats and message transports (e.g., PGP/MIME), and are written with
   the intent to be interoperable with already widely-deployed systems
   in order to facilitate and ease adoption and implementation.  This
   document outlines the general design choices and principles of pEp.

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 September 8, 2019.

Marques & Hoeneisen     Expires September 8, 2019               [Page 1]
Internet-Draft          pretty Easy privacy (pEp)             March 2019

Copyright Notice

   Copyright (c) 2019 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
   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Relationship to other pEp documents . . . . . . . . . . .   5
   2.  Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Protocol's Core Design Principles . . . . . . . . . . . . . .   6
     3.1.  Privacy by Default  . . . . . . . . . . . . . . . . . . .   6
     3.2.  Data Minimization . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Interoperability  . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Peer-to-Peer (P2P)  . . . . . . . . . . . . . . . . . . .   7
     3.5.  User Experience (UX)  . . . . . . . . . . . . . . . . . .   7
   4.  Specific Elements in pEp  . . . . . . . . . . . . . . . . . .   8
     4.1.  pEp identity system . . . . . . . . . . . . . . . . . . .   8
     4.2.  Identifiers . . . . . . . . . . . . . . . . . . . . . . .   8
       4.2.1.  Key . . . . . . . . . . . . . . . . . . . . . . . . .   8
       4.2.2.  User  . . . . . . . . . . . . . . . . . . . . . . . .   8
       4.2.3.  Identity  . . . . . . . . . . . . . . . . . . . . . .   9
       4.2.4.  Address . . . . . . . . . . . . . . . . . . . . . . .   9
     4.3.  Example: Difference between pEp and OpenPGP . . . . . . .   9
   5.  Key Management  . . . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Key Generation  . . . . . . . . . . . . . . . . . . . . .  10
     5.2.  Private Keys  . . . . . . . . . . . . . . . . . . . . . .  10
       5.2.1.  Storage . . . . . . . . . . . . . . . . . . . . . . .  10
       5.2.2.  Passphrase  . . . . . . . . . . . . . . . . . . . . .  11
       5.2.3.  Private Key Export / Import . . . . . . . . . . . . .  11
     5.3.  Public Key Distribution . . . . . . . . . . . . . . . . .  11
     5.4.  Key Reset . . . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Trust Management  . . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  Privacy Status  . . . . . . . . . . . . . . . . . . . . .  15
Show full document text