Re: [Sml] SML BoF / pEp Use Cases

Hans-Joerg Happel <happel@audriga.com> Sat, 25 March 2023 07:53 UTC

Return-Path: <happel@audriga.com>
X-Original-To: sml@ietfa.amsl.com
Delivered-To: sml@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1CEEC14CE29 for <sml@ietfa.amsl.com>; Sat, 25 Mar 2023 00:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 8Kv6Xen55z6s for <sml@ietfa.amsl.com>; Sat, 25 Mar 2023 00:53:16 -0700 (PDT)
Received: from mail.audriga.com (mail.audriga.com [176.221.42.35]) (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 7E2B7C14CF15 for <sml@ietf.org>; Sat, 25 Mar 2023 00:53:16 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.audriga.com (Postfix) with ESMTP id 034C5A29B; Sat, 25 Mar 2023 08:53:14 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mail.audriga.com
Received: from mail.audriga.com ([127.0.0.1]) by localhost (mail.audriga.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9I8hkvOde_T; Sat, 25 Mar 2023 08:53:11 +0100 (CET)
Received: from [31.133.129.99] (dhcp-8163.meeting.ietf.org [31.133.129.99]) (Authenticated sender: happel@audriga.com) by mail.audriga.com (Postfix) with ESMTPSA id 64408A18B; Sat, 25 Mar 2023 08:53:10 +0100 (CET)
Message-ID: <92ca44a7-6c2a-984e-9f5b-b3f6b073d662@audriga.com>
Date: Sat, 25 Mar 2023 16:53:06 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
Content-Language: en-US
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>, sml@ietf.org
Cc: "Hernâni Marques (p≡p foundation)" <hernani.marques@pep.foundation>
References: <alpine.DEB.2.22.394.2303241708210.665520@softronics.hoeneisen.ch>
From: Hans-Joerg Happel <happel@audriga.com>
In-Reply-To: <alpine.DEB.2.22.394.2303241708210.665520@softronics.hoeneisen.ch>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/RwRU_fM3tz0dXaqh2jyokHAE1tw>
Subject: Re: [Sml] SML BoF / pEp Use Cases
X-BeenThere: sml@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Structured Email <sml.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sml>, <mailto:sml-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sml/>
List-Post: <mailto:sml@ietf.org>
List-Help: <mailto:sml-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sml>, <mailto:sml-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Mar 2023 07:53:20 -0000

Hi Bernie,

thanks for pointing to pEp!

I did not yet have time to dig too deeply into the documents you 
reference, but the things you mention could certainly be use cases of 
structured email.

Would you like to present some slides at the BoF on Tuesday?

Thanks and best,
Hans-Joerg

ps.: I esp. tried to grasp the details of key sychronization (2), but 
failed to find at which of the process steps (email) messages are used 
by now. In particular, how do you "address" the different devices in 
case they are all using the same email account?

Beyond that: are there implementations of (1-3) already, and how do they 
work by now

On 25.03.23 01:11, Bernie Hoeneisen wrote:
> Dear SML List,
>
> As I understand SML (Structured Email), in pEp [1] we have some Use 
> Cases that may fit into SML. In the following a short description:
>
> 1) Process Attached PGP Key
>
> One Use case may be, where a (PGP) key is attached to an email. By 
> default the attached Key shall not be shown to the User (as this leads 
> to bad UX). The Key shall rather be automatically processed by the 
> client as described in 
> https://datatracker.ietf.org/doc/html/draft-pep-email
>
>
> 2) Private Key Synchronization
>
> https://datatracker.ietf.org/doc/html/draft-pep-keysync specifies a 
> protocol to securely set up a trusted channel to exchange private key 
> information among clients belonging the same users in a decentralized 
> manner. The messages for setting up the trusted channel and exchanging 
> keys over said channel need to be processed automatically and shall 
> not be shown to the user.
>
> 3) Key Reset
>
> https://datatracker.ietf.org/doc/html/draft-pep-keyreset specifies a 
> protocol to reset (revoke/replace) Keys. This protocol contains means 
> for distributing such information to be automatically processed by the 
> clients.
>
> Looking forward to your feedback on whether or not these Use Cases are 
> in scope of SML.
>
> cheers,
>  Bernie, pEp Foundation
>
> [1] https://pep.foundation/pEp-software/
>
> -- 
>
> http://ucom.ch/
> Modern Telephony Solutions and Tech Consulting for Internet Technology
>