<?xml version="1.0" encoding="utf-8"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" docName="draft-backer-sml-action-requests-00" ipr="trust200902" submissionType="IETF" consensus="true" xml:lang="en">
<front>
<title abbrev="SML Action Requests">Structured Action Requests and Shared Status in Email</title>
<seriesInfo name="Internet-Draft" value="draft-backer-sml-action-requests-00"/>
<author initials="A." surname="Bäcker" fullname="Alex Bäcker" asciiSurname="Baecker" asciiFullname="Alex Baecker"><organization>ab Inventio</organization><address><email>alex@abinventio.com</email></address></author>
<date year="2026" month="November" day="18"/>
<area>Applications and Real-Time</area><workgroup>Structured Email</workgroup>
<keyword>structured email</keyword><keyword>action request</keyword><keyword>task</keyword>
<abstract><t>Much email asks the recipient to do something: approve, send, sign, pay, decide. Email has no interoperable way to say who owns such a request, when it is due, or whether it is done, so senders track requests by hand and requests are dropped. This document defines a Structured Email (SML) profile for action requests: a machine-readable action object, carried as JSON-LD using the schema.org Action vocabulary and optionally mirrored as an iCalendar VTODO, plus status-update messages that supersede earlier ones, so that every participant's mail client in every administrative domain can show one current status. It works with no shared server between organizations, and it degrades to readable text in clients that do not implement it.</t></abstract>
</front>
<middle>
<section><name>Introduction</name>
<t>Closed platforms (project trackers, CRMs, workplace suites) track tasks with owners, due dates and status, but only among users of the same platform. Email crosses organizational boundaries but carries no task semantics. iCalendar VTODO over iMIP <xref target="RFC5546"/><xref target="RFC6047"/> can exchange tasks by email but is rarely used for this, has no follow-up semantics, and is not visible in mail views. The SML core specification <xref target="I-D.ietf-sml-structured-email"/> defines how to embed JSON-LD in email and how one message supersedes another, and leaves structured replies to future work (its Section 5.2). This document is such a profile for the most common structured reply: a status change on a requested action.</t>
<t>Goals:</t>
<ol><li>A sender designates the owner(s), outcome and due time of a request in a way any compliant client can display and track.</li><li>Status (acknowledged, in progress, blocked, delegated, completed, declined, cancelled) travels back by email, structured or as plain text, and every participant converges on the latest status.</li><li>Clients and automated agents can follow up politely and stop when the action is done, within limits the recipient can see.</li><li>Non-compliant clients show the same information as text.</li></ol>
<t>Non-goals: defining how an agent decides when to follow up, or how free-text replies are interpreted. Those are implementation choices; this document defines only the data and the message flow they act on.</t>
</section>
<section><name>Conventions and Terminology</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in BCP 14 <xref target="RFC2119"/><xref target="RFC8174"/> when, and only when, they appear in all capitals.</t>
<ul><li>Action request: an email message that carries an action object with status "requested".</li><li>Requester: the party asking for the action.</li><li>Owner: a party the requester designates as responsible for the action. Recipients become owners by the requester's designation; they need not act to accept ownership.</li><li>Participant: the requester, the owners, and any other listed party.</li><li>Status update: an email message carrying a newer version of an action object for an existing action.</li><li>Agent: software acting for a requester or owner (in a client, a server, or a service with delegated mailbox access).</li></ul>
</section>
<section><name>The Action Object</name>
<t>The action object is a JSON-LD node of type schema:Action (or a subtype) with the following properties.</t>
<table><thead><tr><th>Property</th><th>Req.</th><th>Meaning</th></tr></thead><tbody>
<tr><td>identifier</td><td>MUST</td><td>Globally unique action id, a "urn:uuid:" URN or a URI in the requester's domain. Never reused.</td></tr>
<tr><td>sml:version</td><td>MUST</td><td>Integer starting at 1, incremented on every change.</td></tr>
<tr><td>participant</td><td>MUST</td><td>The requester (schema:Person with email). Other participants MAY be listed.</td></tr>
<tr><td>agent</td><td>MUST</td><td>One or more owners (schema:Person with email), each with a role: responsible, contributor or approver, and a per-owner status.</td></tr>
<tr><td>description</td><td>MUST</td><td>The requested outcome in plain language.</td></tr>
<tr><td>endTime</td><td>SHOULD</td><td>Due time, RFC 3339 with offset.</td></tr>
<tr><td>sml:priority</td><td>MAY</td><td>Integer 0-9 with the meaning of the iCalendar PRIORITY property <xref target="RFC5545"/>: 1 is highest, 9 lowest, 0 undefined. See Section 3.1.</td></tr>
<tr><td>actionStatus</td><td>MUST</td><td>schema.org status (see Section 4) for generic consumers.</td></tr>
<tr><td>sml:status</td><td>MUST</td><td>Fine-grained status from Section 4.</td></tr>
<tr><td>sml:statusReason</td><td>MAY</td><td>Text, for blocked, declined or delegated.</td></tr>
<tr><td>sml:blockingParty</td><td>MAY</td><td>Person or text, for blocked.</td></tr>
<tr><td>sml:evidence</td><td>MAY</td><td>URL or cid: reference to the completion evidence (e.g., an attachment).</td></tr>
<tr><td>sml:followUpPolicy</td><td>MAY</td><td>Section 6.</td></tr>
<tr><td>sml:history</td><td>MAY</td><td>Ordered list of prior transitions: {status, time, actor, basis}. basis is one of "structured", "inferred" or "observed".</td></tr>
</tbody></table>
<t>The "sml:" prefix is a placeholder for the SML Email Vocabulary namespace, still TBD in the core specification.</t>
<section><name>Priority and Due Time</name>
<t>Priority and due time say different things. endTime says how urgent an action is. sml:priority says how important the requester considers it, relative to the requester's other open requests. A requester can therefore mark a request with a distant due time as more important than one due tomorrow. Clients MAY use priority to order or highlight requests. Because each requester sets priorities on their own scale, clients SHOULD NOT present priorities from different requesters as directly comparable. This document does not define how agents use priority.</t>
<t>Example (abbreviated):</t>
<sourcecode><![CDATA[
{
  "@context": "https://schema.org",
  "@type": "Action",
  "identifier": "urn:uuid:7c1e4f0a-2b8d-4c47-9f2e-1a2b3c4d5e6f",
  "sml:version": 1,
  "participant": {"@type": "Person",
                  "email": "requester@example.com"},
  "agent": [{"@type": "Person", "email": "owner@example.org",
             "sml:role": "responsible", "sml:status": "requested"}],
  "description": "Send the signed NDA",
  "endTime": "2026-12-03T17:00:00-08:00",
  "sml:priority": 2,
  "actionStatus": "PotentialActionStatus",
  "sml:status": "requested",
  "sml:followUpPolicy": {"initialDelay": "P2D", "cadence": "P2D",
    "maxFollowUps": 3, "quietPeriod": "P1D",
    "businessHoursOnly": true}
}
]]></sourcecode>
</section>
</section>
<section><name>Status Values and Transitions</name>
<table><thead><tr><th>sml:status</th><th>schema:actionStatus</th><th>Terminal</th><th>Who may set it</th></tr></thead><tbody>
<tr><td>requested</td><td>PotentialActionStatus</td><td>no</td><td>requester</td></tr>
<tr><td>acknowledged</td><td>ActiveActionStatus</td><td>no</td><td>owner</td></tr>
<tr><td>in-progress</td><td>ActiveActionStatus</td><td>no</td><td>owner</td></tr>
<tr><td>blocked</td><td>ActiveActionStatus</td><td>no</td><td>owner</td></tr>
<tr><td>delegated</td><td>ActiveActionStatus</td><td>no</td><td>owner (names the new owner)</td></tr>
<tr><td>completed</td><td>CompletedActionStatus</td><td>yes</td><td>owner; requester may confirm</td></tr>
<tr><td>declined</td><td>FailedActionStatus</td><td>yes</td><td>owner</td></tr>
<tr><td>cancelled</td><td>FailedActionStatus</td><td>yes</td><td>requester</td></tr>
</tbody></table>
<t>Permitted transitions: from requested to any status; among the non-terminal statuses freely; from any non-terminal status to a terminal status. A terminal status MAY be reopened only by the requester (back to requested, with a new version). Receivers MUST ignore transitions set by a party not allowed to set them (Section 8).</t>
<t>With several owners, each owner has a per-owner status and the aggregate status is: completed when all responsible owners are completed; declined or cancelled per the requester's update; otherwise the least advanced non-terminal status.</t>
</section>
<section><name>Message Structure</name>
<section><name>Action request</name>
<t>An action request is a Structured Email message <xref target="I-D.ietf-sml-structured-email"/> containing:</t>
<ol><li>A text/plain part and, OPTIONALLY, a text/html part. Both MUST include a human-readable status block, for example: "Action requested of Maria Lopez · Due 3 Dec 17:00 PT · Status: Requested". A non-compliant client then still shows the request.</li><li>An application/ld+json part carrying the action object, with Content-Purpose: Machine-readable as in the core specification.</li><li>OPTIONALLY, a text/calendar part with METHOD:REQUEST carrying an equivalent VTODO (Section 7).</li></ol>
<t>New header field (Section 10):</t>
<sourcecode><![CDATA[
Action-Id: <urn:uuid:7c1e4f0a-2b8d-4c47-9f2e-1a2b3c4d5e6f>
]]></sourcecode>
<t>Action-Id lets clients and agents correlate messages without parsing bodies. It MUST equal the action object's identifier.</t>
</section>
<section><name>Status update</name>
<t>A status update is a reply (In-Reply-To and References set as usual) that carries the full current action object with an incremented version, the same Action-Id, and a Supersedes header <xref target="RFC4021"/> naming the message whose action object it replaces. A compliant client MUST display only the highest-version action object per Action-Id and SHOULD render it as a single live item, not a new one. The text parts MUST restate the current status block.</t>
<t>Either an owner's client (or agent) or the requester's client (or agent) may send a status update. When the owner replies in free text only, the requester's agent MAY derive a status from the text and send a status update to all participants. Such an update MUST record basis "inferred" in sml:history, so that the owner can see and correct it. A future version may define simple reply words (for example DONE, BLOCKED, NEW DATE) that clients can recognize without natural-language processing, so that status can be updated without an automated agent.</t>
</section>
<section><name>State without a shared server</name>
<t>The current state of an action is the highest-version action object received for its Action-Id. Any participant can rebuild it from their own mailbox, so no server shared between organizations is needed.</t>
</section>
<section><name>Revision before acknowledgement</name>
<t>Until an owner's status is anything other than requested, the requester MAY revise the action (description, due time, owners) by sending a superseding action request with a higher version. Compliant clients replace the displayed request. After acknowledgement, changes to description or due time MUST be sent as an amendment: an action object with sml:amendment set to the proposed changes and sml:amendmentStatus "pending" until the owner accepts or rejects it. This protects owners from unilateral changes after they commit.</t>
</section>
</section>
<section><name>Follow-up Policy</name>
<t>sml:followUpPolicy states how the requester's client or agent will remind owners. It is visible to the owner, so recipients know what to expect.</t>
<table><thead><tr><th>Field</th><th>Meaning</th></tr></thead><tbody>
<tr><td>initialDelay</td><td>ISO 8601 duration before the first reminder.</td></tr>
<tr><td>cadence</td><td>Duration between reminders, or "relative" with an offsets list relative to endTime (e.g., ["-P3D","-P1D","PT0S"]).</td></tr>
<tr><td>maxFollowUps</td><td>Upper bound on reminders. Agents MUST NOT exceed it.</td></tr>
<tr><td>quietPeriod</td><td>No reminder within this duration after any status change by an owner.</td></tr>
<tr><td>businessHoursOnly</td><td>If true, reminders only in the owner's business hours when known.</td></tr>
<tr><td>escalation</td><td>{after: n, contact: email}. The contact is copied after n unanswered reminders. MUST be disclosed in the request.</td></tr>
<tr><td>channels</td><td>Permitted reminder channels. Default ["email"].</td></tr>
</tbody></table>
<t>Agents MUST stop reminding when the action reaches a terminal status, and SHOULD defer reminders while an owner's structured vacation notice <xref target="I-D.ietf-sml-structured-vacation-notices"/> is in effect. How an agent chooses timing and wording within these limits is out of scope.</t>
</section>
<section><name>iCalendar and JSCalendar Mapping</name>
<t>For calendar and task servers that implement iTIP/iMIP <xref target="RFC5546"/><xref target="RFC6047"/>, the action MAY also be sent as a VTODO <xref target="RFC5545"/> with METHOD:REQUEST, using the task extensions of <xref target="RFC10051"/> where noted. Field mapping:</t>
<table><thead><tr><th>Action object</th><th>VTODO</th></tr></thead><tbody>
<tr><td>identifier</td><td>UID</td></tr>
<tr><td>sml:version</td><td>SEQUENCE</td></tr>
<tr><td>participant (requester)</td><td>ORGANIZER</td></tr>
<tr><td>agent (owners)</td><td>ATTENDEE; ROLE=REQ-PARTICIPANT for responsible owners</td></tr>
<tr><td>description</td><td>SUMMARY</td></tr>
<tr><td>endTime</td><td>DUE</td></tr>
<tr><td>sml:priority</td><td>PRIORITY</td></tr>
<tr><td>sml:statusReason</td><td>COMMENT; REASON <xref target="RFC10051"/> where a registered reason URI applies</td></tr>
</tbody></table>
<t>Status mapping:</t>
<table><thead><tr><th>sml:status</th><th>VTODO STATUS</th><th>Owner's PARTSTAT</th><th>Notes</th></tr></thead><tbody>
<tr><td>requested</td><td>NEEDS-ACTION</td><td>NEEDS-ACTION</td><td></td></tr>
<tr><td>acknowledged</td><td>NEEDS-ACTION</td><td>ACCEPTED</td><td></td></tr>
<tr><td>in-progress</td><td>IN-PROCESS</td><td>IN-PROCESS</td><td>PERCENT-COMPLETE MAY be set</td></tr>
<tr><td>blocked</td><td>IN-PROCESS</td><td>IN-PROCESS</td><td>SUBSTATE:SUSPENDED <xref target="RFC10051"/></td></tr>
<tr><td>delegated</td><td>unchanged</td><td>DELEGATED</td><td>DELEGATED-TO names the new owner</td></tr>
<tr><td>completed</td><td>COMPLETED</td><td>COMPLETED</td><td></td></tr>
<tr><td>declined</td><td>CANCELLED</td><td>DECLINED</td><td></td></tr>
<tr><td>cancelled</td><td>CANCELLED</td><td>unchanged</td><td>set by the requester</td></tr>
</tbody></table>
<t>Status changes in this profile come from participants' messages, so senders SHOULD omit TASK-MODE <xref target="RFC10051"/> (its default, CLIENT, applies). The follow-up policy (Section 6) and amendments (Section 5.4) have no VTODO equivalent; they are omitted from the VTODO or carried in X- properties to be registered later. An iTIP REPLY from the owner's server MUST be treated as a structured status update.</t>
<t>For JMAP servers the same mapping applies to the JSCalendar Task object <xref target="RFC8984"/><xref target="I-D.ietf-jmap-tasks"/>, whose priority property uses the same 0-9 scale. A JMAP server can therefore store a received action request as an ordinary task in the owner's task list.</t>
</section>
<section><name>Security Considerations</name>
<ul><li>Authorization: a receiver MUST apply a status transition only if the sender is a participant allowed to set it (Section 4). It SHOULD require DMARC-aligned authentication of the sender's domain, or a valid signature over the action object (see <xref target="I-D.ietf-sml-trust"/>).</li><li>Spoofed completion: a forged "completed" silently drops a task. Clients SHOULD show the basis of the latest status and SHOULD let the requester confirm completions inferred from text.</li><li>Spam-like behavior: the follow-up policy is a ceiling, not a goal. Agents MUST respect maxFollowUps and businessHoursOnly, and owners' clients MAY let users reject an action, which ends all reminders.</li><li>Privacy: status updates go to all participants, so the requester should keep the participant list as small as the task allows. Agents that interpret free text with language models should process it locally or under data-processing agreements.</li></ul>
</section>
<section><name>Privacy Considerations</name>
<t>The action object reveals who owes what to whom and when. Forwarding a status update forwards this. Clients SHOULD warn before forwarding an action object outside the participant list.</t>
</section>
<section><name>IANA Considerations</name>
<ul><li>Register the header field "Action-Id" in the Permanent Message Header Field Names registry <xref target="RFC3864"/>: protocol mail, status standard, this document.</li><li>Register the vocabulary terms in Section 3 in the SML Email Vocabulary registry once that registry is created by the core specification.</li></ul>
</section>
<section><name>Implementation Status</name>
<t>A private prototype exists (ab Inventio, 2026). It implements the iCalendar VTODO / JSCalendar Task mapping of Section 7 and the status transitions of Section 4. It does not yet implement the JSON-LD action object of Section 3 or the superseding status updates of Section 5.2. The author is seeking server and client implementers for the full profile.</t>
</section>
</middle>
<back>
<references><name>References</name>
<references><name>Normative References</name><reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119"><front><title>Key words for use in RFCs to Indicate Requirement Levels</title><author/><date year="1997"/></front><seriesInfo name="RFC" value="2119"/></reference><reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174"><front><title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title><author/><date year="2017"/></front><seriesInfo name="RFC" value="8174"/></reference><reference anchor="RFC4021" target="https://www.rfc-editor.org/info/rfc4021"><front><title>Registration of Mail and MIME Header Fields</title><author/><date year="2005"/></front><seriesInfo name="RFC" value="4021"/></reference><reference anchor="RFC3864" target="https://www.rfc-editor.org/info/rfc3864"><front><title>Registration Procedures for Message Header Fields</title><author/><date year="2004"/></front><seriesInfo name="RFC" value="3864"/></reference><reference anchor="RFC5545" target="https://www.rfc-editor.org/info/rfc5545"><front><title>Internet Calendaring and Scheduling Core Object Specification (iCalendar)</title><author/><date year="2009"/></front><seriesInfo name="RFC" value="5545"/></reference><reference anchor="RFC5546" target="https://www.rfc-editor.org/info/rfc5546"><front><title>iCalendar Transport-Independent Interoperability Protocol (iTIP)</title><author/><date year="2009"/></front><seriesInfo name="RFC" value="5546"/></reference><reference anchor="RFC6047" target="https://www.rfc-editor.org/info/rfc6047"><front><title>iCalendar Message-Based Interoperability Protocol (iMIP)</title><author/><date year="2010"/></front><seriesInfo name="RFC" value="6047"/></reference><reference anchor="RFC8984" target="https://www.rfc-editor.org/info/rfc8984"><front><title>JSCalendar: A JSON Representation of Calendar Data</title><author/><date year="2021"/></front><seriesInfo name="RFC" value="8984"/></reference><reference anchor="I-D.ietf-sml-structured-email" target="https://datatracker.ietf.org/doc/draft-ietf-sml-structured-email/"><front><title>Structured Email</title><author/><date/></front><seriesInfo name="Internet-Draft" value="draft-ietf-sml-structured-email"/></reference></references>
<references><name>Informative References</name><reference anchor="RFC10051" target="https://www.rfc-editor.org/info/rfc10051"><front><title>Task Extensions to iCalendar</title><author/><date year="2026"/></front><seriesInfo name="RFC" value="10051"/></reference><reference anchor="I-D.ietf-sml-structured-vacation-notices" target="https://datatracker.ietf.org/doc/draft-ietf-sml-structured-vacation-notices/"><front><title>Structured vacation notices</title><author/><date/></front><seriesInfo name="Internet-Draft" value="draft-ietf-sml-structured-vacation-notices"/></reference><reference anchor="I-D.ietf-sml-trust" target="https://datatracker.ietf.org/doc/draft-ietf-sml-trust/"><front><title>Structured Email: Trust and Security Considerations</title><author/><date/></front><seriesInfo name="Internet-Draft" value="draft-ietf-sml-trust"/></reference><reference anchor="I-D.ietf-jmap-tasks" target="https://datatracker.ietf.org/doc/draft-ietf-jmap-tasks/"><front><title>JMAP for Tasks</title><author/><date/></front><seriesInfo name="Internet-Draft" value="draft-ietf-jmap-tasks"/></reference></references>
</references>
</back>
</rfc>
