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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-01-09
Stream (None)
Intended RFC status (None)
Formats plain text 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                                            V. Birk
Internet-Draft                                                H. Marques
Intended status: Standards Track                                Shelburn
Expires: July 13, 2018                                    pEp Foundation
                                                              S. Koechli
                                                            pEp Security
                                                        January 09, 2018

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

Abstract

   Building on already available security formats and message transports
   (like PGP/MIME for email), and with the intention to stay
   interoperable to systems widespreadly deployed, pretty Easy privacy
   (pEp) describes protocols to automatize operations (key management,
   key discovery, private key handling including peer-to-peer
   synchronization of private keys and other user data across devices)
   that have been seen to be barriers to deployment of end-to-end secure
   interpersonal messaging. pEp also introduces "Trustwords" (instead of
   fingerprints) 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.  In this
   document, the general design choices and principles of pEp are
   outlined.

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 July 13, 2018.

Birk, et al.              Expires July 13, 2018                 [Page 1]
Internet-Draftpretty Easy privacy (pEp): Privacy by Default January 2018

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
   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
   2.  Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Protocol's core design principles . . . . . . . . . . . . . .   4
     3.1.  Compatibility . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Peer-to-Peer (P2P)  . . . . . . . . . . . . . . . . . . .   4
     3.3.  User Experience (UX)  . . . . . . . . . . . . . . . . . .   5
   4.  Identities in pEp . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Key Management  . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Private Keys  . . . . . . . . . . . . . . . . . . . . . .   9
     5.2.  Key Distribution  . . . . . . . . . . . . . . . . . . . .  10
     5.3.  Passphrases . . . . . . . . . . . . . . . . . . . . . . .  11
   6.  Privacy Status  . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Options in pEp  . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Option "Passive Mode" . . . . . . . . . . . . . . . . . .  12
     7.2.  Option "Disable Protection" . . . . . . . . . . . . . . .  12
       7.2.1.  For all communications  . . . . . . . . . . . . . . .  12
       7.2.2.  For some communications . . . . . . . . . . . . . . .  12
     7.3.  Option "Extra Keys" . . . . . . . . . . . . . . . . . . .  12
     7.4.  Option "Blacklist Keys" . . . . . . . . . . . . . . . . .  13
     7.5.  Establishing trust between peers  . . . . . . . . . . . .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   9.  Implementation Status . . . . . . . . . . . . . . . . . . . .  13
     9.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .  13
     9.2.  Reference implementation of pEp's core  . . . . . . . . .  14
     9.3.  Abstract Crypto API examples  . . . . . . . . . . . . . .  15
       9.3.1.  Encrypting a message  . . . . . . . . . . . . . . . .  15
       9.3.2.  Decrypting a message  . . . . . . . . . . . . . . . .  16
Show full document text