pretty Easy privacy (pEp): Privacy by Default
draft-birk-pep-02
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Expired Internet-Draft (individual) | |
Last updated | 2018-12-28 (latest revision 2018-06-26) | ||
Stream | (None) | ||
Intended RFC status | (None) | ||
Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
Additional URLs |
|
||
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) |
https://www.ietf.org/archive/id/draft-birk-pep-02.txt
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 relies on "Trustwords" (as a word mapping of 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.
Authors
Volker Birk
(volker.birk@pep.foundation)
HernĂ¢ni Marques
(hernani.marques@pep.foundation)
Shelburn
(shelburn@pep.foundation)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)