Re: [Sml] Adoption call: draft-happel-structured-email-00 (Structured Email)

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 15 November 2023 08:47 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 3F58BC15198B for <sml@ietfa.amsl.com>; Wed, 15 Nov 2023 00:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 EMJgoOJ2lwQw for <sml@ietfa.amsl.com>; Wed, 15 Nov 2023 00:47:56 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (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 38C8FC151549 for <sml@ietf.org>; Wed, 15 Nov 2023 00:47:55 -0800 (PST)
Received: from dyas.sandelman.ca (dynamic-046-114-177-123.46.114.pool.telefonica.de [46.114.177.123]) by relay.sandelman.ca (Postfix) with ESMTPS id 2040120B44 for <sml@ietf.org>; Wed, 15 Nov 2023 08:47:53 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id B9445A1BC0; Wed, 15 Nov 2023 09:46:50 +0100 (CET)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id B60FCA1BB0 for <sml@ietf.org>; Wed, 15 Nov 2023 09:46:50 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: sml@ietf.org
In-reply-to: <65823367-5c9c-2985-b21e-a45fbaca39c3@isode.com>
References: <65823367-5c9c-2985-b21e-a45fbaca39c3@isode.com>
Comments: In-reply-to Alexey Melnikov <alexey.melnikov@isode.com> message dated "Mon, 13 Nov 2023 13:41:03 +0000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 15 Nov 2023 09:46:50 +0100
Message-ID: <4053108.1700038010@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/Lke0KRfjo0wNYXSySzvPLjUF-S4>
Subject: Re: [Sml] Adoption call: draft-happel-structured-email-00 (Structured Email)
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: Wed, 15 Nov 2023 08:47:58 -0000

I have read draft-happel-structured-email-00.
I believe that the document is a good base for starting work.

I like that the links to issues have been spread into the document, thank you.
(You might want to use the venue attribute if you are doing kramdown, which
you seem to be using, and the bullet points in a blank line between them)

I'm not pleased with the partial representation idea, although I could
tolerate it as a transition mechanism.

I believe that there are a few classes of systems that ought to be processing
structured emails which are not MUAs.  tripit is one such system.

The Updates: section is too weak, security-wise.
I don't think RFC4021 is anywhere sufficient in security statements.

My preference would be a TOFU/pinned mechanism of SMIME signatures.
(that is: you can Updates: an email if it's signed with the same signer as
the email it updates)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*