[Sml] Re: I-D Action: draft-ietf-sml-structured-email-05.txt

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Tue, 21 October 2025 12:55 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: sml@mail2.ietf.org
Delivered-To: sml@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 1C42A797A1E2 for <sml@mail2.ietf.org>; Tue, 21 Oct 2025 05:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eVxqD7HhwdUH for <sml@mail2.ietf.org>; Tue, 21 Oct 2025 05:55:49 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id AD14079794C7 for <sml@ietf.org>; Tue, 21 Oct 2025 05:55:11 -0700 (PDT)
Authentication-Results: stabil.gulbrandsen.priv.no; dmarc=none (p=none dis=none) header.from=gulbrandsen.priv.no
Authentication-Results: stabil.gulbrandsen.priv.no; spf=pass smtp.mailfrom=gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1761051309; bh=swacDeeRefsq7GhhrClgRHRfhNp8kjuHM+5beRi8FK0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=CUSSZkXeDGVgd06bzmviBKUKzvn3YOs1bfPaf8KBWaD3iQYk7TTXTOVnbjSvmjzi8 GcfC96ulkrN+P9dfaXKqIkhminIXeDa3InwCqXJQ+kXjp6cLLOLuUQtlXAkS24DSES JO0JXrFVoC+gKYBaZKerNzv3kc6jrH5T6swc2oz4=
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 4727FC0025; Tue, 21 Oct 2025 13:55:09 +0100 (IST)
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1761051307-17206-17201/9/12529; Tue, 21 Oct 2025 12:55:07 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Robert Stepanek <rsto@fastmailteam.com>
In-Reply-To: <6723b743-4e82-4bed-aff1-41097cc091b4@app.fastmail.com> (Robert Stepanek's message of "Tue, 21 Oct 2025 12:13:00 +0200")
References: <176103414421.2272208.11805811026223550404@dt-datatracker-84f8f646b-tg6mn> <87ecqw39o9.fsf@libertango.gulbrandsen.priv.no> <6723b743-4e82-4bed-aff1-41097cc091b4@app.fastmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.1
Date: Tue, 21 Oct 2025 14:55:08 +0200
Message-Id: <877bwoza6r.fsf@libertango.gulbrandsen.priv.no>
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Message-ID-Hash: RM7YVBOCV2SWLZHARG2BT4WSQKT3XMKV
X-Message-ID-Hash: RM7YVBOCV2SWLZHARG2BT4WSQKT3XMKV
X-MailFrom: arnt@gulbrandsen.priv.no
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: sml@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sml] Re: I-D Action: draft-ietf-sml-structured-email-05.txt
List-Id: Structured Email <sml.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/lTbauTfUO8uXALoi0gm6LCq-2zA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sml>
List-Help: <mailto:sml-request@ietf.org?subject=help>
List-Owner: <mailto:sml-owner@ietf.org>
List-Post: <mailto:sml@ietf.org>
List-Subscribe: <mailto:sml-join@ietf.org>
List-Unsubscribe: <mailto:sml-leave@ietf.org>

Robert Stepanek <rsto=40fastmailteam.com@dmarc.ietf.org> writes:
> On Tue, Oct 21, 2025, at 11:07 AM, Arnt Gulbrandsen wrote: 
> 
>  Being understandable by the users is an important part of 
>  user-friendliness. Users cannot be expected to care about the 
>  technical differences between e.g. structured data encoded 
>  using  JSON-LD and a calendar invitation encoded using 
>  vCalendar. 
> 
> Nit: I think you mean iCalendar (RFC 5545), not vCalendar? 

You tell me ;) Pick any.

I think the most appropriate format is the one for which the 
largest number of mail readers would display an "accept 
invitation" button, but any calendar format is appropriate, 
precisely because the format shouldn't matter to user.

The key is that users shouldn't have to care about the format in 
the message. There ought to be only two classes: Messages that 
cause buttons to be displayed and ones that don't. A message that 
contains "add ticket to wallet" has a different MIME structure 
from one that contains "add event to calendar", and WE all know 
about MIME structures, content types and JSON-LD. But users 
shouldn't (IMO) notice any difference in MUA behaviour due to that 
MIME structure difference.

Arnt