[Medup] New Version Notification for draft-birk-pep-03.txt

Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Thu, 07 March 2019 13:44 UTC

Date: Thu, 07 Mar 2019 14:44:19 +0100
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
To: medup@ietf.org
Message-ID: <alpine.DEB.2.20.1903071436080.27152@softronics.hoeneisen.ch>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/medup/7CJ-5pnS7OASwASYAyrkz487yRM>
Subject: [Medup] New Version Notification for draft-birk-pep-03.txt
Precedence: list

Dear MEDUP list

Please be informed that the Internet-Draft draft-birk-pep-03 has just been 
published (see also below). It describes in general how pEp (pretty Easy 
privacy) works and it serves as a starting point for the MEDUP 
discussions.

Discussion of this Internet-Draft is taking place on this mailing 
list (medup@ietf.org).

Looking forward to all your comments, expression of support and 
other feedback!

All the best,
  Bernie

---------- Forwarded message ----------
Date: Thu, 7 Mar 2019 14:15:11
From: internet-drafts@ietf.org
Subject: New Version Notification for draft-birk-pep-03.txt


A new version of I-D, draft-birk-pep-03.txt
has been successfully submitted by Hernani Marques and posted to the
IETF repository.

Name:		draft-birk-pep
Revision:	03
Title:		pretty Easy privacy (pEp): Privacy by Default
Document date:	2019-03-07
Group:		Individual Submission
Pages:		31
URL:            https://www.ietf.org/internet-drafts/draft-birk-pep-03.txt
Status:         https://datatracker.ietf.org/doc/draft-birk-pep/
Htmlized:       https://tools.ietf.org/html/draft-birk-pep-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-birk-pep
Diff:           https://www.ietf.org/rfcdiff?url2=draft-birk-pep-03

Abstract:
    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 (including peer-to-peer synchronization of
    private keys and other user data across devices). pEp also introduces
    means 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.
    Significantly, the pEp protocols build on already available security
    formats and message transports (e.g., PGP/MIME), and are written with
    the intent to be interoperable with already widely-deployed systems
    in order to facilitate and ease adoption and implementation.  This
    document outlines the general design choices and principles of pEp.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

[Medup] New Version Notification for draft-birk-p… Bernie Hoeneisen