<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-chuang-agent-attribution-header-fields-01" category="exp" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="Agent Attribution">Agent Attribution Header Fields</title>
    <seriesInfo name="Internet-Draft" value="draft-chuang-agent-attribution-header-fields-01"/>
    <author fullname="Weihaw Chuang">
      <organization>Google, Inc.</organization>
      <address>
        <email>weihaw@google.com</email>
      </address>
    </author>
    <author fullname="Emil Gustafsson">
      <organization/>
      <address>
        <email>emil@emailer.se</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <workgroup>Independent Stream</workgroup>
    <keyword>Agent</keyword>
    <keyword>Attribution</keyword>
    <keyword>Identity</keyword>
    <abstract>
      <?line 35?>

<t>When human users communicate with autonomous computer agent users, the human users should be able to identify that communication as coming from agent users and know which humans are responsible for the agent users.  This document specifies email header fields that an email sender can use to transmit agent user attribution information to email receivers.  The first header field is human readable and specifies the agent's responsible humans' email address.  The second header field is machine readable and specified in JSON attribution information.</t>
    </abstract>
  </front>
  <middle>
    <?line 39?>

<section anchor="introduction">
      <name><strong>Introduction</strong></name>
      <t>Recent autonomous computer agent users have gained the capability to communicate with human users through such means such as emails (<xref target="RFC5322"/>).  Human users should be able to identify that communication as coming from computer agents.  They should also be able to identify which humans are responsible for the agent, that is the human owner of the agent.   For example when the agent misbehaves and sends unwanted email, the recipient may want to communicate with the responsible human to stop the behavior.  This document specifies email header fields (<xref target="RFC5322"/>) that an email sender can use to transmit agent user attribution information to email receivers.  The first header field Agent-of specifies the agent's responsible human's email address, and is human and machine readable.  The second header field Agent-attribution is specified in JSON attribution information, and is meant to be machine readable only.</t>
      <section anchor="terminology-and-definitions">
        <name><strong>Terminology and Definitions</strong></name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <xref target="RFC2119"/>.</t>
      </section>
    </section>
    <section anchor="header-fields">
      <name><strong>Header Fields</strong></name>
      <t>This specification defines two header field-names (<xref target="RFC5322"/>) agent-of and agent-attribution.</t>
      <t>When the agent-of header field is attached to an email, it defines that a computer agent sent the message.   The field value is an address-list (<xref target="RFC5322"/>) of the responsible humans of the agent  that sent an email.  This is meant to be human and machine readable.</t>
      <artwork><![CDATA[
agent-of        =   "Agent-of:" address-list CRLF
]]></artwork>
      <t>With this header field, the responsible human information here is simplified for readability.  If there are multiple responsible humans of an agent, multiple addresses may be specified or an email address alias may be used to represent many users that control that agent.  In other scenarios, when an agent triggers the creation of another agent, the responsible human information MUST be propagated so that it is always available to the newly created agent if it is to use this header field.  This identity MUST provide the means to communicate via SMTP (<xref target="RFC5321"/>) with the responsible human or humans of the agent.  It does not have to be their primary email address, and can be an alias or mailing list (<xref target="RFC5321"/>).</t>
      <t>Alternatively when the sender wishes to represent a more complex responsibility relationship, they can use the agent-attribution header field.   The field value is a base64string (<xref target="RFC4648"/>) of JSON (<xref target="RFC8259"/>).  The JSON key-value of attributes about the identity of the responsible humans that allows arbitrary definition of  responsibility and delegation relationship of computer agents.  We expect that there will be an IANA registry for these values as well as future updates to this document to represent those relationships.  It is meant to be only machine readable.  When the agent-attribution header field is attached to an email, it also defines that a computer agent sent the message.</t>
      <artwork><![CDATA[
agent-attribution        =   "Agent-attribution:" base64string CRLF
]]></artwork>
      <t>If both header fields are present in a message, the receiver SHOULD take a union of the sender identities of both header fields.</t>
      <section anchor="authentication">
        <name><strong>Authentication</strong></name>
        <t>Senders MUST sign these header fields with DKIM (<xref target="RFC6376"/>).  Receivers that use these headers MUST DKIM authenticate them, i.e the signature passes and the agent header fields in this document are covered by the header hash.  If DKIM2 (<eref target="https://datatracker.ietf.org/doc/html/draft-ietf-dkim-dkim2-spec">draft-ietf-dkim-dkim2-spec</eref>) authentication is available, then DKIM2 results SHOULD be used for authentication instead of DKIM with the same coverage requirement.  To prevent spoofing of the responsible humans, receivers that use those identities MUST check for DMARC relaxed (<xref target="RFC9989"/>) alignment of human identifiers with a passing DKIM or DKIM2 signature domain.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name><strong>Security Considerations</strong></name>
      <t>These headers MUST be DKIM authenticated before they can be used as defined in <xref target="authentication"/>.  Similarly the responsible humans' email addresses domains MUST be DKIM aligned as defined in <xref target="authentication"/>.  Presence of this header field does not infer any trustworthiness.  It is simply a claim by the sender that the creator of the email is an agent and a second claim of who are the responsible humans of an agent.  The third claim is that this provides a means of communicating with the responsible humans of an agent.  Receivers MUST make their own judgement of the utility of this information.   Agent-of header field says nothing about the authentication requirements of the agent or the From header field as this is solely about agent attribution as opposed to agent identity.  Agent-attribution header field is not yet defined but could be used both for agent attribution and identity.</t>
    </section>
    <section anchor="iana-considerations">
      <name><strong>IANA Considerations</strong></name>
      <t>This document has no IANA actions yet.</t>
      <t>--</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="RFC5322">
        <front>
          <title>Internet Message Format</title>
          <author fullname="P. Resnick" initials="P." role="editor" surname="Resnick"/>
          <date month="October" year="2008"/>
          <abstract>
            <t>This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="5322"/>
        <seriesInfo name="DOI" value="10.17487/RFC5322"/>
      </reference>
      <reference anchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC5321">
        <front>
          <title>Simple Mail Transfer Protocol</title>
          <author fullname="J. Klensin" initials="J." surname="Klensin"/>
          <date month="October" year="2008"/>
          <abstract>
            <t>This document is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. Although SMTP was designed as a mail transport and delivery protocol, this specification also contains information that is important to its use as a "mail submission" protocol for "split-UA" (User Agent) mail reading systems and mobile environments. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="5321"/>
        <seriesInfo name="DOI" value="10.17487/RFC5321"/>
      </reference>
      <reference anchor="RFC4648">
        <front>
          <title>The Base16, Base32, and Base64 Data Encodings</title>
          <author fullname="S. Josefsson" initials="S." surname="Josefsson"/>
          <date month="October" year="2006"/>
          <abstract>
            <t>This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="4648"/>
        <seriesInfo name="DOI" value="10.17487/RFC4648"/>
      </reference>
      <reference anchor="RFC8259">
        <front>
          <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
          <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
          <date month="December" year="2017"/>
          <abstract>
            <t>JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
            <t>This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
          </abstract>
        </front>
        <seriesInfo name="STD" value="90"/>
        <seriesInfo name="RFC" value="8259"/>
        <seriesInfo name="DOI" value="10.17487/RFC8259"/>
      </reference>
      <reference anchor="RFC6376">
        <front>
          <title>DomainKeys Identified Mail (DKIM) Signatures</title>
          <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
          <author fullname="T. Hansen" initials="T." role="editor" surname="Hansen"/>
          <author fullname="M. Kucherawy" initials="M." role="editor" surname="Kucherawy"/>
          <date month="September" year="2011"/>
          <abstract>
            <t>DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature.</t>
            <t>This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="STD" value="76"/>
        <seriesInfo name="RFC" value="6376"/>
        <seriesInfo name="DOI" value="10.17487/RFC6376"/>
      </reference>
      <reference anchor="RFC9989">
        <front>
          <title>Domain-Based Message Authentication, Reporting, and Conformance (DMARC)</title>
          <author fullname="T. Herr" initials="T." role="editor" surname="Herr"/>
          <author fullname="J. Levine" initials="J." role="editor" surname="Levine"/>
          <date month="May" year="2026"/>
          <abstract>
            <t>This document describes the Domain-based Message Authentication, Reporting, and Conformance (DMARC) protocol.</t>
            <t>DMARC permits the owner of an email's Author Domain to enable validation of the domain's use to indicate the Domain Owner's or Public Suffix Operator's message handling preference regarding failed validation and to request reports about the use of the domain name. Mail-receiving organizations can use this information when evaluating handling choices for incoming mail.</t>
            <t>This document obsoletes RFCs 7489 and 9091.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9989"/>
        <seriesInfo name="DOI" value="10.17487/RFC9989"/>
      </reference>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA8VYa2/bOBb9rl/BTT/0gchp0063MbDAGEkzzW4e3SRFsVjs
B1qiLW4kUUNKcT1F+tvn3EtKlmSn0wEW2ACJFYu8z3PPvWQcx1Gt61xNxWyp
ylrM6trqeVNrU4oPSqbKilOt8tRFcj636n7HuiiRtVoau54K9aWKotQkpSwg
MbVyUcdJ1shyGUvaFsvNtjhj8fGCxccvX0WumRfaObyr1xX2n72/PY3Kppgr
O41SKJlGiSmdKl3jpqK2jYpgz+toZezd0pqmwpYyVZXCH5h4U1sliyjSleXV
rj58+fLo5aGI7tQae9KpiETs/eGHnkv494yE6HodyabOjPWLI4GfRZPn3sPP
SmdyJY7ZRf/S2KUs9W+SxEzFL8Ysc7UPu5IJv1aF1PlUrHjjz0t+PUlMwS8T
05Q14rhD0/tC5+IX+CAXziE3fWEK737mZ2UnTg1FRVFpbAFz7hG+SJeL3n9x
HAs5d7WVSR1FnzNViqwpZCkap6yDjKJoSk3pFStdZwKRMKUpTMPvqqYGOjiv
fsO+qDM1kOAy0+SpmCuoyZWojdAc1cUaS2Xd00B4kyxWI5ILa4q+ZCHLVNyV
ZiVWmU4yrwPfWiWschVAoUk+fGMTejsnQtxm2gmAsinoW1epRANzzkdPeBQK
j0JvFcz37xwhyYrE+0PmI1SlK3TdUyF6mBZdfPGM5V6MVYlCwIMxMFNbVw8U
C1jo4wbIphwr8nhja+fVUzfw2AfiaVAk0xQvWzVOoVrSLT2FTDJdqt2asKIU
f7+5unzMK8j2uCl0muYK8HoiXrw4A9ZM2iS04sWLKLqGxwjPH+BFZPJeiaWE
NSl7mMhKznWOoqPgbcGvj6w6Q8EvM+EawKFQhAZ+lCGvTjz7+vUv16fHP70+
PHx4eA67P/yvgDn0JYR73cqUuTM7Bf84dPe9Edr1CsqsSmg0i80q6BWn2Ka+
yKKCiBXV7wb+oNK5ogj76iEsO9GUK1nWCDcHyRcs4KkrzVskrMT7ndH3S0fQ
o5WuNhW/ZXXa2D9Zc8NE/d9KkPtAjAD/YNU9dcOq2+cwd4VM/4xL7TuFORu3
R5L0w1XZ6aZK4PQBgFuFbsp8zfUbPaGivVUWmDa5Wa55+4la6FKTOEc1TJai
UQrqlE7sXXy6ud3b95/i8oqfr9//89PZ9fsTer75MDs/7x7aFTcfrj6dn2ye
NjuPry4u3l+e+M0Xs3/teR/2rj7enl1dzs73yOd6ACOqGe+aBoZtZRUhGcWZ
KpcgLD5OHk2Hr14dPTxMAj8NJhnv3Ca8ochTcp+SvjKD1MTUgLdQKlu0kNFb
sw1H+fOgHmntmIqxAzki8jMd4vcFoN3ZwrUwJk9Hf0gw7HL4iojAg5rk3su8
USy9bKEZ5xpoH3kQqGS7mwxIRngbWGVrYlvfI7x9B/dIw7dv36IuEOHnb/jd
a+tuujc09/j6/JR3IZKef6i2ehHcf4SS+gSQKcuxcBoU6UuJmNYbxp0Gzpyx
v1hIACuavNZEp7sDQx56iu4WBquVY/5EIDZlC1Udk4Vl6A9adkvBXpx9q4Bm
5zm4XHc9jjsR9dY8QCHw/hn6AZksHPqstNqAfZj+W/PAknq59ELQV+Evh4Md
8Du7RvNHIeSCh6mVNZVcSio5NDjfoLhHyXwl1/i4h5dt0yOxpVrla69bhRoR
ehE2YQ3z+TipHbbC9O3VQ/c9vgmgp1SMOtS9luLm4vZjD+SvCOTf6VzIzQ68
U3BRfwbZRKD8hOLhjSXawhJdSLveRf3Uo6jvlyHFUECLaGwY1R+ZhpqY5ajp
kofxfL1p36HlrbTLlBuCQ4rCAKPEB7n6snHKz0xW5Zwyl+mKM7ve9M2Ohvod
ZBT4nSQi5tKpt29wSCBHgg9v3r55FziE21L4+t3hT0d+1iJJ/AYdJPbCCHtB
N40kc9N4Eusy/TgheeznuVnR4DTXGAGQgrTrV7R1HAzKSKpytfQo7seGlm/P
cJ8VHV9VUnt1nhFWOs9DUs9mlzOIWSKVUB7mNYSWvXPUhlYKi/G5aOoGe5uK
zqzOl0O/jw1SirOlUwPznMfgiF2pee8aKEZd5rH0frfd8Mj6p3vOgNT7erfZ
vfcWND9AVI/mwcNzQ3P+YDwkUm6DhfYuWwu64ZUHOxHmi1reIRSYcwMsegUV
gEaDndmlCRUpvk7FEzrv00o/Fzy049Js8DUNETcs13mKcnpZBkQM7WcKOvnH
2UVbJW9f//Wtr5Lrdir1QQ+F2kkIknlvzyheVCBxE1/XpFky4irJbYigv2ng
Q2t2DlWJgRHAxXztDxx+RyZd5rsjWXAonv3bX+hoVS/i9E4X/Ocwpnb3n2dZ
XVduenAAzEu6ULhTdkIrJ8YuD6DtIKuL/OBxCc+fi2HgGbFtT+Fkl8EQgAG9
17Upb9soleRYROlqOEP55ih27cBhpvNuI0gQ+GujrSo8/98awtu9P7gYsyCU
PspN+5ujRT+JVNM9vHEeUXrJHVt5cjG7Puaa/wK7AyyOjt4d8WSZI5+cGpoY
fTv2R0hNSvxFDKeaDGO3SCRHZgOF1KC6MYeGAfhGJY0lWjwm85Fd2Z/zx4hD
RLdAR4flBTWfrq+0cecBfMGHeB6/R/XzgJDe6AJ5tPn6kSiOLjCUC/aP7aHQ
/JjGj8wYifKZGw0Zm/6OQYcoDiMXXxDirFMTwboNB/PkuCZCzKUu2hIJlNJ2
Cj/lmO587r0JM/jSz84wuz35eVFYu8qMP9U8Ooi3AkJPhXW23a9dqx9PYUJy
zI9hb+8SA0h5fBQaK9rQEke/IEr1049ZleK/TbpULT5JHmg97/o3jW6D26LN
uXqQAUcjI42iZNpmGBjVb68wR8eScF1ySvcxA8HSBSuQOpPTYOWlhzT02hSN
aFVlwgQe5tMwjEzEjhP5uJ8SgNaq7rCIZXTv6u+VuDS4yTAvbWunA3urrb1G
oxFjV4X2CRu0DM1+HJF84+bIigldy0XR71wf8tTRFwAA

-->

</rfc>
