Skip to main content

pretty Easy privacy (pEp): Key Synchronization Protocol

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Bernie Hoeneisen , Hernâni Marques
Last updated 2019-07-07
Replaced by draft-hoeneisen-pep-keysync
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-hoeneisen-pep-keysync
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Modern users of messaging systems usually have multiple devices, and often desire to send and receive encrypted messages on some or all of their devices. Using encryption on multiple devices often results in situations where messages cannot be decrypted on the device used to read the message due to a missing private key. This document specifies a protocol for secure peer-to-peer synchronization of private keys across devices belonging to the same user (pEp Key Synchronization Protocol). 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.


Bernie Hoeneisen
Hernâni Marques

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)