[Sml] Re: Structured Email and AI Agents
John Levine <johnl@taugh.com> Thu, 28 August 2025 22:08 UTC
Return-Path: <johnl@iecc.com>
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 857B25A4AE29 for <sml@mail2.ietf.org>; Thu, 28 Aug 2025 15:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.384
X-Spam-Level:
X-Spam-Status: No, score=-4.384 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, HEADER_FROM_DIFFERENT_DOMAINS=0.017, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="hGCivlGn"; dkim=pass (2048-bit key) header.d=taugh.com header.b="U+NPifb9"
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 z83CI1NLqSzL for <sml@mail2.ietf.org>; Thu, 28 Aug 2025 15:08:02 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 36B4C5A4AE24 for <sml@ietf.org>; Thu, 28 Aug 2025 15:08:02 -0700 (PDT)
Received: (qmail 32988 invoked from network); 28 Aug 2025 22:08:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=80d068b0d341.k2508; t=1756418871; x=1756764471; bh=UaBKJAqU9uOViZmwHy78Yn0tm7PoFAzp1z35UG1ZLic=; b=hGCivlGn8jJCRjQXMieHh0T8x0KksrXoHGVlDr1pe4c75gSkjYf3FfsxXynnW3lgDXKC8U6NqoOh4b8CRr0Oql0hJPWZgw6RY3eMrE3/Y1j3tj8HiL1RGPAhp9r6lHIaiA8X71gfJTNYFNf97EX9f9wUGiXWliVfoLmVZ7UKc4/JuAi2+Ecs1Y0Wb+/nh+um3ATOPvfm2E4yYwzUdgIP3fhymxmWmHoV/NZYu+DsKWFk186kVkJlDF5ZaWan/a+crMTNvruN5IrK7vt5vE5AZefhNcjmsNYJhP9a1lX/ZyMvUwITT1g/W888+b2HQRmfhSgJ+P1IO3wPWCJXPYLmcQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=80d068b0d341.k2508; bh=UaBKJAqU9uOViZmwHy78Yn0tm7PoFAzp1z35UG1ZLic=; b=U+NPifb9Ee8mCekNH8Ljbay/eU8yJDGEgiXNekZGVvCdgTjFiPy9e6M+dL8vVphtNnF8qnQU4Hnb1WHPEE5AtW3gkiI64wfLJQep346tEutksQBX4X6WZwS8A36nYWb1Blfroi2RbreS3zlaR0x2O7aJPjDsIalWEYjRXTnhVoduK17o1dIagIiDNW9VmVaMot7Ir2+PE5ipeM5gw8Mm6gFZtFhRYzwqgScIW7x+OvG3htcCFdESC043hrajpEAgPxTmf9trHyaIF8P0d2qj846YMgRM0B9qqirl0EUByOAneuvsqTZBBS65f6amHZBcgLgUYnmOdllXHZrhPwapKA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 28 Aug 2025 22:08:01 -0000
Received: by ary.qy (Postfix, from userid 501) id E3E97DA25183; Thu, 28 Aug 2025 18:08:00 -0400 (EDT)
Date: Thu, 28 Aug 2025 18:08:00 -0400
Message-Id: <20250828220800.E3E97DA25183@ary.qy>
From: John Levine <johnl@taugh.com>
To: sml@ietf.org
In-Reply-To: <8438.1756415514@obiwan.sandelman.ca>
Organization: Taughannock Networks
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> <8438.1756415514@obiwan.sandelman.ca>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: 4ARRRNOFRZR2Y4PQWV4G6RUGE23JHPRT
X-Message-ID-Hash: 4ARRRNOFRZR2Y4PQWV4G6RUGE23JHPRT
X-MailFrom: johnl@iecc.com
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: mcr+ietf@sandelman.ca
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/GMrbT3SDxCX9a3LG-8zTS_J7-9o>
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>
It appears that Michael Richardson <mcr+ietf@sandelman.ca> said: >-=-=-=-=-=- >Yes we can use Sender: >It contains an email address. Does it need to be valid? I think so. This goes down the rabbit hole of what's a valid address but in the usual sense that you can reply to it, yes. Part of the point is that you have the option of replying to the From or the Sender. >I'm concerned that it might then be used for other kinds of validation, and >we can't just put what we need there. At the moment I haven't seen Sender used for any validation although I have seen suggestions that DMARC should somehow use it. But I doubt that will happen. >So, yes, we could use it. >I don't agree that the *target* can be indicated with Content-Type. In this example it's a calendar invite, and we have a format and content type for that. More generally I'd think it depends whether you plan to have an SML thing intended for machine parsing or natural language that you expect an AI assistant to figure out or maybe something else. (Wave hands vigorously here.) > 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? I would expect to use something else to decide how to process it. As I'm sure you know we have decades of experience here with both formatted content types and hacks like procmail. It's not clear to me that there is anything useful to say about mail that is supposed to be handled automatically but that you can't describe well enough that a content type or procmail pattern could route it. R's, John
- [Sml] Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents John Levine
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents John R Levine
- [Sml] Re: Structured Email and AI Agents Michael Richardson
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents Michael Richardson
- [Sml] Re: Structured Email and AI Agents John Levine
- [Sml] Re: Structured Email and AI Agents Ben Bucksch
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents John R Levine
- [Sml] Re: Structured Email and AI Agents Michael Richardson
- [Sml] Re: Structured Email and AI Agents Steffen Nurpmeso
- [Sml] Re: Structured Email and AI Agents John Levine
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents Arnt Gulbrandsen
- [Sml] Re: Structured Email and AI Agents Michael Richardson
- [Sml] Re: Structured Email and AI Agents Michael Richardson