pretty Easy privacy (pEp): Key Synchronization Protocol (KeySync)
draft-pep-keysync-02

Document Type Expired Internet-Draft (individual)
Authors Volker Birk  , Bernie Hoeneisen  , Kelly Bristol 
Last updated 2021-01-14 (latest revision 2020-07-13)
Replaces draft-hoeneisen-pep-keysync
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-pep-keysync-02.txt

Abstract

This document describes the pEp KeySync protocol, which is designed to perform secure peer-to-peer synchronization of private keys across devices belonging to the same user. Modern users of messaging systems typically have multiple devices for communicating, and attempting to use encryption on all of these devices often leads to situations where messages cannot be decrypted on a given device due to missing private key data. Current approaches to resolve key synchronicity issues are cumbersome and potentially insecure. The pEp KeySync protocol is designed to facilitate this personal key synchronization in a user-friendly manner.

Authors

Volker Birk (volker.birk@pep.foundation)
Bernie Hoeneisen (bernie.hoeneisen@pep.foundation)
Kelly Bristol (kelly.bristol@pep.foundation)

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