IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 15 November 2023 08:53 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 EC71EC17C89D for <sml@ietfa.amsl.com>; Wed, 15 Nov 2023 00:53:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 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, 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 3tt1I3W7HHVS for <sml@ietfa.amsl.com>; Wed, 15 Nov 2023 00:53:28 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 A5BB1C17C892 for <sml@ietf.org>; Wed, 15 Nov 2023 00:53:27 -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 90BD720B44 for <sml@ietf.org>; Wed, 15 Nov 2023 08:53:25 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 5C7E6A1BC0; Wed, 15 Nov 2023 09:53:23 +0100 (CET)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 594CBA1BB0 for <sml@ietf.org>; Wed, 15 Nov 2023 09:53:23 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: sml@ietf.org
In-reply-to: <9bf7c20a-3493-b6ee-d257-a65c2ccc7ff3@isode.com>
References: <9bf7c20a-3493-b6ee-d257-a65c2ccc7ff3@isode.com>
Comments: In-reply-to Alexey Melnikov <alexey.melnikov@isode.com> message dated "Mon, 13 Nov 2023 13:31:52 +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:53:23 +0100
Message-ID: <4053254.1700038403@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/HDeVfcZTUSyGwe8F-rpJuV4r-d8>
Subject: Re: [Sml] Adoption call: draft-happel-structured-email-use-cases-00 (Structured Email: 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: Wed, 15 Nov 2023 08:53:30 -0000

Alexey Melnikov <alexey.melnikov@isode.com> wrote:
    > Based on informal feedback received during the SML WG meeting in Prague, I am
    > initiating adoption call on draft-happel-structured-email-use-cases-00
    > (https://datatracker.ietf.org/doc/draft-happel-structured-email-use-cases/). The
    > adoption call will last for 2 weeks and will end on November 28th 2023.

This document is a good base for the WG, and we should adopt.
I don't know if there is a reason to publish this.

Surely a *MAJOR* existing use case is confirming an email is controlled by
the user. I guess that's 5.3.
Why are a few examples in "Existing Use cases", when almost all the rest are
also existing?

Under 5.4, Sign-Up, of course we have Mailing lists subscriptions, and it
would sure be nice if they could be clearly filed away for the MUA to show to
the user when they "un5ubscribe" to the list.  That use case could quite
reasonably be expanded.

I'd sure like examples for all the existing use cases.
If we had good examples then this document would be useful.
As is, there is too much offloading to JsonSchema, I think.

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

v2.23.0 | Report a Bug | By Email