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

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

Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C92124184; Thu, 7 Mar 2019 05:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4WpfRMqpQoWZ; Thu, 7 Mar 2019 05:54:00 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA0612008F; Thu, 7 Mar 2019 05:54:00 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.86_2) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1h1tTC-00057W-5y; Thu, 07 Mar 2019 14:53:58 +0100
Date: Thu, 7 Mar 2019 14:53:58 +0100 (CET)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: IETF DISPATCH list <dispatch@ietf.org>, IETF SEC DISPATCH list <secdispatch@ietf.org>, IETF SAAG list <saag@ietf.org>
Message-ID: <alpine.DEB.2.20.1903071444220.27152@softronics.hoeneisen.ch>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Y9j7oLp-WNoT1iNzTxntHquthVY>
Subject: [dispatch] New Version Notification for draft-birk-pep-03.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2019 13:54:03 -0000

Please be informed that an update of 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 (Missing Elements for Decentralized and Usable Privacy) discussions.

Discussion of this Internet-Draft and other pEp related matters is 
taking place on the new MEDUP mailing list (medup@ietf.org) from now on.
To subscribe: https://www.ietf.org/mailman/listinfo/medup

Looking forward to all your comments and feedback on the new MEDUP mailing 
list!

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