pretty Easy privacy (pEp): Key Synchronization Protocol (KeySync)
draft-hoeneisen-pep-keysync-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bernie Hoeneisen , Hernâni Marques , Kelly Bristol | ||
| Last updated | 2019-10-31 | ||
| Replaces | draft-birk-pep-keysync | ||
| Replaced by | draft-pep-keysync | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-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:
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 unsecure. The pEp KeySync protocol is designed to facilitate this personal key synchronization in a user-friendly manner.
Authors
Bernie Hoeneisen
Hernâni Marques
Kelly Bristol
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)