<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.birk-pep" target="https://datatracker.ietf.org/doc/html/draft-birk-pep-01">
   <front>
      <title>pretty Easy privacy (pEp): Privacy by Default</title>
      <author initials="V." surname="Birk" fullname="Volker Birk">
         <organization>pEp Foundation</organization>
      </author>
      <author initials="H." surname="Marques" fullname="Hernâni Marques">
         <organization>pEp Foundation</organization>
      </author>
      <author initials="S." surname="Shelburn" fullname="S. Shelburn">
         <organization>pEp Foundation</organization>
      </author>
      <author initials="S." surname="Koechli" fullname="Sandro Koechli">
         <organization>pEp Security</organization>
      </author>
      <date month="January" day="9" year="2018" />
      <abstract>
	 <t>   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 &quot;Trustwords&quot; (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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-birk-pep-01" />
   
</reference>
