[Medup] Fwd: New Version Notification for draft-pep-keysync-03.txt
"Hernâni Marques (p≡p foundation)" <hernani.marques@pep.foundation> Tue, 06 June 2023 13:38 UTC
Return-Path: <hernani.marques@pep.foundation>
X-Original-To: medup@ietfa.amsl.com
Delivered-To: medup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A386FC151093 for <medup@ietfa.amsl.com>; Tue, 6 Jun 2023 06:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.695
X-Spam-Level:
X-Spam-Status: No, score=-1.695 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=pep.foundation header.b="JcTucDXT"; dkim=neutral reason="invalid (public key: not available)" header.d=pep.foundation header.b="JcTucDXT"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q1CBA5DTtp7O for <medup@ietfa.amsl.com>; Tue, 6 Jun 2023 06:38:24 -0700 (PDT)
Received: from pibit.ch (dragon.pibit.ch [185.203.114.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44620C15155E for <medup@ietf.org>; Tue, 6 Jun 2023 06:38:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by dragon.pibit.ch (Postfix) with ESMTP id 565E62140334 for <medup@ietf.org>; Tue, 6 Jun 2023 15:38:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pep.foundation; s=default; t=1686058700; bh=7pOLYg/pC8LwiPp5Uz2tWyPzdX2UfNFgaOvCxZ01bEc=; h=Date:Subject:References:From:To:In-Reply-To:From; b=JcTucDXTCfPhOZQbgHPGp5wgtIqcGcuFgO7hI27Qdgc/vNYMvJs2ezKWxa4lvg0H1 VRUlVX6wcS40D939D0FCwdtNuPOHTOsURSMjJilp7c9GGN6mHq63t3lrh87ZSD9Hhv nSvLX9h9WEPbajZeMfhGR6bnhxpImk34nA/V9d30Kuek9BWKjd4EL/DtHwd/Grrjx7 5RTrA26Epn3Gn9uF2Vzz8a6pY/+89ARryEh5CjbOu1b0zqrWgA8HDfPZSL2CVcLnVe EwXdM9czuCNRDjnb2rsnAG5Rtkgi7q9W2oIOD+UbfyQTXNbNwnZ13+xLljQp9pRbJU VX0yjjsQebzFA==
Received: from pibit.ch ([127.0.0.1]) by localhost (dragon.pibit.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VFLC_2GhGhYD for <medup@ietf.org>; Tue, 6 Jun 2023 15:38:20 +0200 (CEST)
Received: from [192.168.100.252] (212-51-151-254.fiber7.init7.net [212.51.151.254]) by dragon.pibit.ch (Postfix) with ESMTPSA id 320FB21402F7 for <medup@ietf.org>; Tue, 6 Jun 2023 15:38:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pep.foundation; s=default; t=1686058700; bh=7pOLYg/pC8LwiPp5Uz2tWyPzdX2UfNFgaOvCxZ01bEc=; h=Date:Subject:References:From:To:In-Reply-To:From; b=JcTucDXTCfPhOZQbgHPGp5wgtIqcGcuFgO7hI27Qdgc/vNYMvJs2ezKWxa4lvg0H1 VRUlVX6wcS40D939D0FCwdtNuPOHTOsURSMjJilp7c9GGN6mHq63t3lrh87ZSD9Hhv nSvLX9h9WEPbajZeMfhGR6bnhxpImk34nA/V9d30Kuek9BWKjd4EL/DtHwd/Grrjx7 5RTrA26Epn3Gn9uF2Vzz8a6pY/+89ARryEh5CjbOu1b0zqrWgA8HDfPZSL2CVcLnVe EwXdM9czuCNRDjnb2rsnAG5Rtkgi7q9W2oIOD+UbfyQTXNbNwnZ13+xLljQp9pRbJU VX0yjjsQebzFA==
Message-ID: <d4fd89db-acd0-c0c6-6a25-14621bff6339@pep.foundation>
Date: Tue, 06 Jun 2023 15:38:19 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.2
References: <168605856606.33764.12125858681380601778@ietfa.amsl.com>
Content-Language: en-US
From: "Hernâni Marques (p≡p foundation)" <hernani.marques@pep.foundation>
To: medup@ietf.org
X-Pep-Version: 2.1
In-Reply-To: <168605856606.33764.12125858681380601778@ietfa.amsl.com>
X-Forwarded-Message-Id: <168605856606.33764.12125858681380601778@ietfa.amsl.com>
Content-Type: multipart/mixed; boundary="7b7b379a4d842ded488e6aef483bad7f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/medup/87dDm5Ysz_4biobfciesyOENR5g>
Subject: [Medup] Fwd: New Version Notification for draft-pep-keysync-03.txt
X-BeenThere: medup@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Missing Elements for Decentralized and Usable Privacy <medup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/medup>, <mailto:medup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/medup/>
List-Post: <mailto:medup@ietf.org>
List-Help: <mailto:medup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/medup>, <mailto:medup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jun 2023 13:38:28 -0000
Dear folks New revision (03) of the KeySnyc draft just published. Greets --hernani -------- Forwarded Message -------- Subject: New Version Notification for draft-pep-keysync-03.txt Date: Tue, 06 Jun 2023 06:36:06 -0700 From: internet-drafts@ietf.org To: Bernie Hoeneisen <bernie.hoeneisen@pep.foundation>, Hernani Marques <hernani.marques@pep.foundation>, Volker Birk <volker.birk@pep.foundation> A new version of I-D, draft-pep-keysync-03.txt has been successfully submitted by Bernie Hoeneisen and posted to the IETF repository. Name: draft-pep-keysync Revision: 03 Title: pretty Easy privacy (pEp): Key Synchronization Protocol (KeySync) Document date: 2023-06-06 Group: Individual Submission Pages: 74 URL: https://www.ietf.org/archive/id/draft-pep-keysync-03.txt Status: https://datatracker.ietf.org/doc/draft-pep-keysync/ Htmlized: https://datatracker.ietf.org/doc/html/draft-pep-keysync Diff: https://author-tools.ietf.org/iddiff?url2=draft-pep-keysync-03 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 insecure. The pEp KeySync protocol is designed to facilitate this personal key synchronization in a user-friendly manner. The IETF Secretariat
- [Medup] Fwd: New Version Notification for draft-p… Hernâni Marques (p≡p foundation)