IETF Logo Mail Archive

[Sml] Re: Structured Email and AI Agents

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 28 August 2025 21:11 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 A606B5A46224 for <sml@mail2.ietf.org>; Thu, 28 Aug 2025 14:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 Zupb-HQvMv4b for <sml@mail2.ietf.org>; Thu, 28 Aug 2025 14:11:57 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 209525A4621C for <sml@ietf.org>; Thu, 28 Aug 2025 14:11:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id AC1ED1800F for <sml@ietf.org>; Thu, 28 Aug 2025 17:11:56 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id zrgr80WqV6mg for <sml@ietf.org>; Thu, 28 Aug 2025 17:11:55 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1756415515; bh=uKJX2y65M7XSk6Fve1GLZWWcmpPtrIDfEgt007H89/8=; h=From:To:Subject:In-Reply-To:References:Date:From; b=RB1MQ5Wm1QLtKo8gUgaSkMB8jLFeniN1cjKAx7KnW2KfYXwxEY/nju8JWW+2BBS2j SMF72aR1HK8nQKhe9Z4e6e+JaVlwHlEMEk2Jj7Inps5PnLWeDkfuHN66NDHj273tnQ ROMuYzlJiN0RAL3RrF1FfOU/Z0hwScHSaMOVaYxImfkiRlzY0AfIJ2CrUu8xt8OHB8 LCUeNQp40gkDKD+giUQkRerrKBDHq38a1iSpvmGoG/5TJC9xBrCwMzVh8mhnglQBaZ GiDhIujWPgnHyWP5HwvHiea0T/X+cgRWa3XUdAWPuq2j6coXLkmCkZlbuR2H5Yd7Io dEgfKhAqTaLmA==
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:7cd8:6ff:fe54:5c1a]) by tuna.sandelman.ca (Postfix) with ESMTP id 0A1741800C for <sml@ietf.org>; Thu, 28 Aug 2025 17:11:55 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 04794220 for <sml@ietf.org>; Thu, 28 Aug 2025 17:11:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: sml@ietf.org
In-Reply-To: <20250827222825.430BCD9FDF65@ary.qy>
References: <DS4PPF69F41B22E72C08B1885D3E7B1571DC53EA@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM> <20250825192803.1CE42D96C6E8@ary.qy> <DS4PPF69F41B22E0E98B3B664276E8FFA9EC53EA@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM> <6ea763c2-925a-3f3f-9d52-a357256e55b7@taugh.com> <7158.1756238376@obiwan.sandelman.ca> <DS4PPF69F41B22E472E285B6EDA0A41573FC538A@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM> <27676.1756316868@obiwan.sandelman.ca> <20250827222825.430BCD9FDF65@ary.qy>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 28 Aug 2025 17:11:54 -0400
Message-ID: <8438.1756415514@obiwan.sandelman.ca>
Message-ID-Hash: MOHT74ME2ZNZWRJBGE666TS3O7PZM7DD
X-Message-ID-Hash: MOHT74ME2ZNZWRJBGE666TS3O7PZM7DD
X-MailFrom: mcr+ietf@sandelman.ca
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sml] Re: Structured Email and AI Agents
List-Id: Structured Email <sml.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/DJXD07PyjsYrKNp9BZhbpbxQA2c>
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>

Yes we can use Sender:
It contains an email address.  Does it need to be valid? I think so.
I'm concerned that it might then be used for other kinds of validation, and
we can't just put what we need there.

So, yes, we could use it.
I don't agree that the *target* can be indicated with Content-Type.

I don't think this example is at all correct:

  From: Boss Bob <bob.smith@company.com>
  Sender: Bob's assistant <alice.jones@company.com>
  Subject: whatever

I think it would be:
  From: Boss Bob <bob.smith@company.com>
  Sender: Company Travel Assistant <travel.assistant@company.com>
  Subject: whatever

Having the same email in Sender: would mean sorting (sieving) on what?
The word "assistant" in the other part?

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.46.0 | Report a Bug | By Email | System Status