<?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-feedback-id-header-00" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="feedback-id">Feedback-id Email Header Field</title>
    <seriesInfo name="Internet-Draft" value="draft-chuang-feedback-id-header-00"/>
    <author initials="W." surname="Chuang" fullname="Weihaw Chuang">
      <organization>Google, Inc.</organization>
      <address>
        <postal>
          <street>1600 Amphitheatre Parkway</street>
          <city>Mountain View</city>
          <region>California</region>
          <code>94043</code>
          <country>United States of America</country>
        </postal>
        <email>weihaw@google.com</email>
      </address>
    </author>
    <author initials="A." surname="Robinson" fullname="Allen Robinson">
      <organization>Google, Inc.</organization>
      <address>
        <postal>
          <street>20 Breithaupt Street, Kitchener, ON N2H 5G5</street>
          <city>Kitchener</city>
          <region>Ontario</region>
          <code>N2H 5G5</code>
          <country>Canada</country>
        </postal>
        <email>arobins@google.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <workgroup>Independent</workgroup>
    <keyword>Mailmaint</keyword>
    <abstract>
      <?line 43?>

<t>Large-volume email senders and Email Service Providers (ESPs) use Feedback Loops (FBLs) to identify campaigns in their traffic that generate a high volume of spam complaints from recipients and to detect abuse of their services. Traditional per-message complaint reports can expose individual recipient actions, creating privacy concerns. This document specifies the "Feedback-ID" email header field, which allows senders to embed structured campaign, customer, mail-type, and sender identifiers in outbound messages. Receiving mailbox providers authenticate this header field using DomainKeys Identified Mail (DKIM) and report aggregated spam complaint rates per identifier back to verified senders without disclosing individual recipient data.</t>
    </abstract>
  </front>
  <middle>
    <?line 47?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Large-volume email senders and Email Service Providers (ESPs) use Feedback Loops (FBLs) <xref target="RFC6449"/> to identify campaigns in their mail traffic that receive a high volume of spam complaints from recipients. FBLs are particularly useful to ESPs to detect abuse of their services by malicious or misconfigured senders and to remediate deliverability problems quickly.</t>
      <t>Traditional FBL implementations generate per-complaint messages using the Abuse Reporting Format (ARF) <xref target="RFC5965"/> (often routed to addresses advertised via <xref target="RFC9477"/>). However, per-message complaint reports can expose individual recipient actions to senders. To protect user privacy while still providing actionable abuse telemetry, mailbox providers (originally deployed by Gmail for its recipients via Postmaster Tools) can instead compute and report aggregated spam complaint statistics across campaigns.</t>
      <t>To enable aggregated FBL reporting, senders embed the "Feedback-ID" header field specified in this document, which consists of colon-separated parameters (called "Identifiers") that uniquely identify individual campaigns, customers, mail types, and the sender. Any Identifiers exhibiting an unusual spam rate that might cause deliverability issues can then be surfaced to verified domain owners in an FBL reporting dashboard or feed.</t>
    </section>
    <section anchor="terminology-and-definitions">
      <name>Terminology and Definitions</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>
      <t>Syntax definitions in this document use ABNF <xref target="RFC5234"/>. Email transport and message header formatting are defined in SMTP <xref target="RFC5321"/> and the Internet Message Format <xref target="RFC5322"/>. DomainKeys Identified Mail (DKIM) is defined in <xref target="RFC6376"/>, Sender Policy Framework (SPF) is defined in <xref target="RFC7208"/>, and DNS resource records (including PTR) are defined in <xref target="RFC1035"/>. Internet mail architecture terms such as Originator, Relay, Receiver, and Administrative Management Domain (ADMD) follow <xref target="RFC5598"/>.</t>
      <t>The term "Identifier" in this document refers to a colon-delimited parameter within the "Feedback-ID" header field that identifies a sender, campaign, customer, or mail category for aggregated complaint reporting.</t>
    </section>
    <section anchor="header-format">
      <name><strong>Header Format</strong></name>
      <t>Senders embed the "Feedback-ID" header field in outbound <xref target="RFC5322"/> messages to associate mail traffic with campaign, customer, mail-type, and sender Identifiers. Conceptually, the header field has the following format:</t>
      <artwork><![CDATA[
Feedback-ID: a:b:c:SenderId
]]></artwork>
      <t>The fields of this header are defined as follows:</t>
      <ul spacing="normal">
        <li>
          <t>"Feedback-ID": Name of the header field to be embedded in the message header section. Per <xref target="RFC5322"/>, header field names are case-insensitive.</t>
        </li>
        <li>
          <t>"a", "b", "c": OPTIONAL fields that MAY be used by the sender to embed up to three (3) Identifiers (for example, campaign/customer/other).</t>
        </li>
        <li>
          <t>"SenderId": REQUIRED unique Identifier (5 to 15 characters RECOMMENDED) chosen by the sender. It SHOULD remain consistent across the sender's mail stream.</t>
        </li>
      </ul>
      <section anchor="abnf-syntax">
        <name>ABNF Syntax</name>
        <t>The formal syntax of the "Feedback-ID" header field is specified using ABNF <xref target="RFC5234"/>, importing FWS and CRLF from <xref target="RFC5322"/>:</t>
        <artwork><![CDATA[
feedback-id-field = "Feedback-ID:" [FWS] feedback-id-value [FWS] CRLF

feedback-id-value = [ [ [opt-id] ":" ] [opt-id] ":" ] opt-id ":"
                    sender-id

opt-id            = 1*sender-id-char
sender-id         = 1*sender-id-char
                    ; 5*15sender-id-char RECOMMENDED
sender-id-char    = ALPHA / DIGIT / "-" / "_" / "." / "+" / "/" / "="
]]></artwork>
        <t>Each Identifier ("opt-id" and "sender-id") consists of alphanumeric characters, hyphens ("-"), underscores ("_"), periods ("."), and Base64 characters ("+", "/", and "=") to accommodate structured tokens and appended hashes. When fewer than three optional Identifiers are needed, senders MAY omit leading optional fields (for example, "b:c:SenderId" or "c:SenderId") or leave an intermediate optional field empty (for example, "a::c:SenderId").</t>
      </section>
      <section anchor="identifier-selection">
        <name>Identifier Selection</name>
        <t>When choosing Identifiers, the following operational requirements apply to ensure accurate aggregation:</t>
        <ul spacing="normal">
          <li>
            <t>Avoid Per-Message Unique Parameters: Senders SHOULD NOT use a parameter that is unique across every single message (for example, a unique "Message-ID" header field value <xref target="RFC5322"/>), because single-message Identifiers cannot accumulate aggregate volume.</t>
          </li>
          <li>
            <t>Avoid Cross-Field Repetition: For a given day's traffic, senders SHOULD ensure that Identifiers across different fields are not repeated, so that feedback data is not inadvertently aggregated across unrelated Identifiers.</t>
          </li>
          <li>
            <t>Namespace Scoping via Hashing: If there is concern about the uniqueness of the Identifier namespace, or if the sender prefers for data to be grouped between two Identifiers, a hash of one Identifier MAY be appended to the other.</t>
          </li>
        </ul>
      </section>
      <section anchor="illustrative-example">
        <name>Illustrative Example</name>
        <t>Below is a non-normative example illustrating the use of all four fields in a "Feedback-ID" header field:</t>
        <artwork><![CDATA[
Feedback-ID: CampaignIDX:CustomerID2:MailTypeID3:SenderId

]]></artwork>
        <ul spacing="normal">
          <li>
            <t>"CampaignIDX": Campaign Identifier specific to Customer 2 and unique across all customers (that is, no two customers share the same campaign ID).</t>
          </li>
          <li>
            <t>"CustomerID2": Unique customer Identifier.</t>
          </li>
          <li>
            <t>"MailTypeID3": Identifier for the type of mail (for example, a newsletter versus a product update), which can be either unique or common across customers based on how the sender wants to view the data.</t>
          </li>
          <li>
            <t>"SenderId": The sender's unique Identifier, which can be used for overall statistics.</t>
          </li>
        </ul>
        <t>In the case above, the receiving mailbox provider reports the spam complaint percentages for each of the four Identifiers independently whenever an Identifier exhibits an unusual spam rate and meets volume thresholds.</t>
      </section>
    </section>
    <section anchor="feedback-loop">
      <name><strong>Feedback Loop</strong></name>
      <t>An aggregated Feedback Loop (FBL) enables mailbox providers to report elevated spam complaint rates back to verified senders grouped by the Identifiers embedded in the "Feedback-ID" header field, without exposing individual complaining recipients.</t>
      <section anchor="authentication-and-infrastructure-requirements">
        <name>Authentication and Infrastructure Requirements</name>
        <t>To prevent spoofing of the "Feedback-ID" header field and unauthorized access to complaint data, participating senders and receivers apply the following authentication and sending infrastructure requirements:</t>
        <ul spacing="normal">
          <li>
            <t>DKIM Signing: Outbound traffic MUST be signed with DKIM <xref target="RFC6376"/> by a domain owned or controlled by the sender after the "Feedback-ID" header field has been added to the message, such that "Feedback-ID" is covered by the DKIM-Signature "h=" tag.</t>
          </li>
          <li>
            <t>Single Verified Header: Senders SHOULD ensure that their outbound traffic carries only one such verified "Feedback-ID" header field per message.</t>
          </li>
          <li>
            <t>Domain Verification for Reporting Access: The DKIM signing domain ("d=") SHOULD be registered and verified with the receiving mailbox provider's postmaster or feedback reporting service so that the sender can securely access the resulting FBL data.</t>
          </li>
          <li>
            <t>SPF and Reverse DNS Alignment: Senders MUST publish the IP addresses from which they send mail in the SPF records <xref target="RFC7208"/> of their signing domains. In addition, sending IP addresses MUST have valid DNS PTR records <xref target="RFC1035"/> that resolve to a valid hostname, which SHOULD preferably be one of the DKIM signing domains.</t>
          </li>
        </ul>
      </section>
      <section anchor="data-aggregation-and-reporting">
        <name>Data Aggregation and Reporting</name>
        <t>Receiving mailbox providers generate and report aggregated FBL statistics according to the following rules:</t>
        <ul spacing="normal">
          <li>
            <t>Right-to-Left Field Evaluation: Aggregate data MUST be generated for up to the first four (4) colon-separated (":") fields of the "Feedback-ID" header field value, starting from the right side. Any additional colon-separated fields to the left of those four rightmost fields are ignored.</t>
          </li>
          <li>
            <t>Empty Field Handling: If the rightmost field ("SenderId") is empty, receivers MUST NOT generate FBL data for the message. If any other field among the evaluated fields is empty, aggregate data is still generated for the remaining non-empty fields.</t>
          </li>
          <li>
            <t>Independent Per-Identifier Aggregation: FBL data is aggregated on each Identifier independently. This also allows senders to include fewer than three optional Identifiers when fewer dimensions are needed.</t>
          </li>
          <li>
            <t>Volume and Spam-Rate Thresholds: For a given day's traffic, FBL reports are generated only if a given Identifier is present in a minimum volume of messages as well as in distinct user spam reports, and exhibits an unusual spam rate that might cause deliverability issues, subject to receiver local policy.</t>
          </li>
          <li>
            <t>Recipient Scope: FBL data reported by a mailbox provider pertains only to recipients hosted within that provider's Administrative Management Domain (ADMD) <xref target="RFC5598"/>.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="security-considerations">
      <name><strong>Security Considerations</strong></name>
      <t>An unauthenticated "Feedback-ID" header field could be forged by an adversary to inject spam complaints into another sender's Feedback Loop (FBL) reports, corrupting deliverability telemetry or masking abuse across tenants. To prevent spoofing, senders MUST add the "Feedback-ID" header field prior to signing the message with DKIM <xref target="RFC6376"/> and MUST include "Feedback-ID" in the DKIM-Signature "h=" signed header fields list. Receivers MUST ignore unverified "Feedback-ID" header fields when attributing FBL statistics and MUST restrict access to FBL reports to domain owners that have verified control of the corresponding DKIM signing domain.</t>
      <t>If a message contains multiple "Feedback-ID" header fields, ambiguity can arise when different actors along a relay path insert their own headers. Senders SHOULD ensure that outbound messages contain only one verified "Feedback-ID" header field, and signers MAY oversign the "Feedback-ID" header field name in the DKIM-Signature "h=" tag as described in <xref target="RFC6376"/> Section 8.15 to prevent downstream insertion of additional "Feedback-ID" header fields.</t>
      <t>As described in <xref target="RFC6376"/> Section 8.6, DKIM signatures do not bind a message to the SMTP envelope recipient, leaving signed messages potentially susceptible to DKIM replay attacks. If a signed message carrying a "Feedback-ID" header field is captured and replayed at scale by an attacker, resulting recipient complaints could be attributed to the signed Identifiers.</t>
      <t>Traditional per-message feedback mechanisms such as <xref target="RFC5965"/> can disclose individual recipient complaint actions to the sender. Aggregating FBL statistics per Identifier and enforcing minimum daily message-volume and distinct-user spam-report thresholds before generating a report prevents senders from inferring the actions of individual recipients. To preserve this privacy property, senders SHOULD NOT place per-recipient or per-message unique values in "Feedback-ID", and receivers MUST enforce volume and distinct-reporter thresholds sufficient to prevent single-user re-identification. Additionally, because message header fields are visible to recipients, senders SHOULD use opaque tokens rather than confidential customer names or sensitive internal metadata in "Feedback-ID" Identifiers.</t>
    </section>
    <section anchor="iana-considerations">
      <name><strong>IANA Considerations</strong></name>
      <t>This document has no IANA actions yet. Note that the registration below for the "Feedback-ID" header field in the "Permanent Message Header Field Names" registry (<xref target="RFC3864"/>) is a draft placeholder and is not yet approved or ready for IANA action:</t>
      <artwork><![CDATA[
Header field name: Feedback-ID
Applicable protocol: mail
Status: informational
Author/Change controller: IETF
Specification document(s): This document
]]></artwork>
      <t>--</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <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="RFC5234">
          <front>
            <title>Augmented BNF for Syntax Specifications: ABNF</title>
            <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
            <author fullname="P. Overell" initials="P." surname="Overell"/>
            <date month="January" year="2008"/>
            <abstract>
              <t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="68"/>
          <seriesInfo name="RFC" value="5234"/>
          <seriesInfo name="DOI" value="10.17487/RFC5234"/>
        </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="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="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="RFC7208">
          <front>
            <title>Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1</title>
            <author fullname="S. Kitterman" initials="S." surname="Kitterman"/>
            <date month="April" year="2014"/>
            <abstract>
              <t>Email on the Internet can be forged in a number of ways. In particular, existing protocols place no restriction on what a sending host can use as the "MAIL FROM" of a message or the domain given on the SMTP HELO/EHLO commands. This document describes version 1 of the Sender Policy Framework (SPF) protocol, whereby ADministrative Management Domains (ADMDs) can explicitly authorize the hosts that are allowed to use their domain names, and a receiving host can check such authorization.</t>
              <t>This document obsoletes RFC 4408.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7208"/>
          <seriesInfo name="DOI" value="10.17487/RFC7208"/>
        </reference>
        <reference anchor="RFC1035">
          <front>
            <title>Domain names - implementation and specification</title>
            <author fullname="P. Mockapetris" initials="P." surname="Mockapetris"/>
            <date month="November" year="1987"/>
            <abstract>
              <t>This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="13"/>
          <seriesInfo name="RFC" value="1035"/>
          <seriesInfo name="DOI" value="10.17487/RFC1035"/>
        </reference>
        <reference anchor="RFC3864">
          <front>
            <title>Registration Procedures for Message Header Fields</title>
            <author fullname="G. Klyne" initials="G." surname="Klyne"/>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="J. Mogul" initials="J." surname="Mogul"/>
            <date month="September" year="2004"/>
            <abstract>
              <t>This specification defines registration procedures for the message header fields used by Internet mail, HTTP, Netnews and other applications. 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="90"/>
          <seriesInfo name="RFC" value="3864"/>
          <seriesInfo name="DOI" value="10.17487/RFC3864"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC6449">
          <front>
            <title>Complaint Feedback Loop Operational Recommendations</title>
            <author fullname="J. Falk" initials="J." role="editor" surname="Falk"/>
            <date month="November" year="2011"/>
            <abstract>
              <t>Complaint Feedback Loops similar to those described herein have existed for more than a decade, resulting in many de facto standards and best practices. This document is an attempt to codify, and thus clarify, the ways that both providers and consumers of these feedback mechanisms intend to use the feedback, describing some already common industry practices.</t>
              <t>This document is the result of cooperative efforts within the Messaging Anti-Abuse Working Group, a trade organization separate from the IETF. The original MAAWG document upon which this document is based was published in April, 2010. This document does not represent the consensus of the IETF; rather it is being published as an Informational RFC to make it widely available to the Internet community and simplify reference to this material from IETF work. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6449"/>
          <seriesInfo name="DOI" value="10.17487/RFC6449"/>
        </reference>
        <reference anchor="RFC5965">
          <front>
            <title>An Extensible Format for Email Feedback Reports</title>
            <author fullname="Y. Shafranovich" initials="Y." surname="Shafranovich"/>
            <author fullname="J. Levine" initials="J." surname="Levine"/>
            <author fullname="M. Kucherawy" initials="M." surname="Kucherawy"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>This document defines an extensible format and MIME type that may be used by mail operators to report feedback about received email to other parties. This format is intended as a machine-readable replacement for various existing report formats currently used in Internet email. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5965"/>
          <seriesInfo name="DOI" value="10.17487/RFC5965"/>
        </reference>
        <reference anchor="RFC9477">
          <front>
            <title>Complaint Feedback Loop Address Header</title>
            <author fullname="J. Benecke" initials="J." surname="Benecke"/>
            <date month="September" year="2023"/>
            <abstract>
              <t>This document describes a method that allows a Message Originator to specify a Complaint Feedback Loop (CFBL) address as a message header field. It also defines the rules for processing and forwarding such a complaint. The motivation for this arises out of the absence of a standardized and automated way to provide Mailbox Providers with an address for a CFBL. Currently, providing and maintaining such an address is a manual and time-consuming process for Message Originators and Mailbox Providers.</t>
              <t>The mechanism specified in this document is being published as an experiment to gather feedback and gauge the interest of implementers and deployers. This document is produced through the Independent RFC Stream and was not subject to the IETF's approval process.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9477"/>
          <seriesInfo name="DOI" value="10.17487/RFC9477"/>
        </reference>
        <reference anchor="RFC5598">
          <front>
            <title>Internet Mail Architecture</title>
            <author fullname="D. Crocker" initials="D." surname="Crocker"/>
            <date month="July" year="2009"/>
            <abstract>
              <t>Over its thirty-five-year history, Internet Mail has changed significantly in scale and complexity, as it has become a global infrastructure service. These changes have been evolutionary, rather than revolutionary, reflecting a strong desire to preserve both its installed base and its usefulness. To collaborate productively on this large and complex system, all participants need to work from a common view of it and use a common language to describe its components and the interactions among them. But the many differences in perspective currently make it difficult to know exactly what another participant means. To serve as the necessary common frame of reference, this document describes the enhanced Internet Mail architecture, reflecting the current service. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5598"/>
          <seriesInfo name="DOI" value="10.17487/RFC5598"/>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA7VbbXPbOJL+rl+B0344Oyt5HCfOTHSVulPseKIaJ/HZzsxd
bU1tQSRk4UIRXIK0RzeV+e37dDdAgrLjZKrudqs8tkQC/fr00w1kOp2OGtsU
ZqbOjMmXOvs0tbl6s9G2UG+Nzk2tzqwp8pFeLmtzO1Or/rFRphtz4+rtTNly
5Ua5y0q9wVJ5rVfNNFu3uryZJi9M17zi9PBw5NvlxnpvXdlsK7yyeHN9Nirb
zdLUs1GOdWejzJXelL71M9XUrRlh82ejO1d/uqldW+GVMjeVwY+yGY1sVfNj
vjk6PHx5eKRGn8wWD+czNVJT9Q76QCc8qdtm7Wr5dKTwP1tig18O1AmLyx+J
Fr8Yu9Z34XN51tU3M/WjczeFmWD/7IA/NWStmbrj5//jhr8+yNyGv/RNbUwz
U09fHB6q+aZa2wZWwIfqQtef7vSWn8psAyu+c23ZQEr1szV3/HltbmCimTrR
hV25urRaHnc5BHz5/PD5s/A3XiQ/fCxtY3J11cCCXrkVdjS1zfDWtFd2fqAu
3RK/ujJRd14Upuy++AZ9dc3Pfknho0P1ujbQVrdVA4no04n6yTbZ2pSmnqgP
79X7o7fq+MfjxATd9wP1P8AstXWJ7oM3o/YnutS5Ho1Gpas3urG3iKIRhWb/
13Q6VXoJGXWGqDnX9Y2Z3rqi3RhRS3mKqNorXcY0uDL1rc3gr9rdWv5u783V
hd9XrTdd1qhz5yp8c/b6HN80TlmKS7vaqkxvKm1vSg/jK/je1ohTvVrZDH/p
Rt2QtnCX0mptb9YqSAPf+UpvoNymKihyvVrVbgOTZLayhv4mEbFTbhqTNdCK
5MFrsocXqf2Buq51bhvYUReqQvZtjPf6xvQrY83K1Vgw06Uyv1UO69gyt9C2
xTvdjgo2wzJ+orIaIWyRFVVtb3UGJV2Zmbqk3dbWKyABdMAbvsLLK4tYhFRq
3GHM4nQc7C2QoFYEMhN1t7bZWumicHe+cwV0NACGnEKrzZq2xq/RqpAFOe82
FFC03pTgZMKmkdejIyytBA+4tlkiXnIVzACRL01moCzUoRWW7jeoFV1NcEHv
E9RBB+iWCowQoNdOHWHLT2br1SLuljPmqL3Tnxbv9lkesbLSNzcIa01pOnSw
qjlpq4HMioMLFrhFHvOy0Sp3SC0oo3Lrs8KxHA86DWCqDyTwNzbPC4P8+AuS
uald3rJD///y4Pff//3y7OTF8+cvP3/+WlLwHoPMqNkvfz4xDhTtDnwyqtI1
fNcWui62JOeqLUgOkvvrqaOWW0hV2My6FmAKEWFqV67sDYdgaiGsVZuNyS2F
SW4KiF3rpS2AaRRMy8JsvPpHa7NPxRbOSFMSsioLVQwljOYE6zGB8rUPkBiy
IewopeYs+iWHFn12xlin9uaXZ9H8xy9fHMP8e27VAOBROyn0ILDO8xoLYjmd
Q9zGenx+a3V47eXz77///Hn/QL11d+aW8uv/BDxo52A5gIUj67APoEbdwQlg
oDBId1sUIRdJN1lBw5jBY40hqwH6Jw9k7p6r7Y2FheF5EIXCbaEePPojBxpq
grKQOoFTUv3C+WajfQNZrp0rEMKkFqpcg6xnpVtC6m/JZk/OhAoZ7JvVzvs+
6CkCgGlBlX4FCoU6unLSBZiA330AHSBRRNpcMioB4YiqxKcgENOCzBWunHqD
/OCd6b+wJNstg8nw0XjRA+d4XzKyLe0/WgODdomcuLpTr8dkPwlpDVD2gsqk
hih2oOblViW7IHzWdmk5jmH1tmw9rct2rQV/IcMGWNBgMwqAnUwDoWyNRCKh
tlpiq7Ze6UwCvoPQnPFaubsyFAW8MLA9QNOvl07XOaU9MdgDRs1rU29sCdvd
bFmZU7OyJSeyh0uhGUinItbp1fjdx6vr8UT+q95/4N8v3/znx8Xlm1P6/ert
/Py8+yU+cfX2w8fz0/63/s2TD+/evXl/Ki+/m//3WOw5/nBxvfjwfn4+vud4
RkDovaSMhG+r2pCvNZ4wPqvtUoLl99//Bel+9PQpQBpqXm0BQ7/hkU61+wuT
7eev35+Fd4+Pnj3Hu6FOAMNLL8nRl9kuWBmfxMW1kV1EjKt31xdxvWdHT4FY
MVwWJHxpGvUurBVArnv4iDb/ehEmDfr95O0Xz75/8fnzBMWNycKFA9xv1Rll
A7Uaau/q4uzhN78/OvyB3uQ4eH+F4PGurVEfASkcAXu2zIqWkevi+nJ/V19Z
5enhs2OSvtORTajrDH2CYa4DlKtRPHxLxMirD4JqjQMgX5pCbyeBvxBCkyzz
HCFqieES5YUBSpiMvSYWQm04fXe6D08Qy4o14vjlD+x9CmLaME3/ByKrNqvA
zHTAEkrFjR1gCVMUqe+PIRdndcd4gJYBHyYPkjwXmELsPRnJEwzdLUwwv+Tu
kyexn+XoefIEof5nADbljmnk9VWZrOG9y5gEDOgMGeJPUNYEE9GXErWumpYK
2YSFHIi11sKtxZ0UbJJi6HVGf/zxxyhRCC3bbDnLZqL2IufvxeW8lhcK1HPc
NGKxjWzhaeXRE/RdA2OhJdObSKJ2HMwQxEbOY30yu8DgDVf3A3WBP1L7ToaL
UbMq3C7T3kwtzwgshfqBCKUJH5f0I4NQER2jhhxsQE+SqPXCCPqS1LcabUW/
N2t0rWrv2f6gTO1RyJnfNJG2Pki/i179zmHBej+IE40NWSL6hzKarKn2jmm7
p8cqW2tqTWmbBPJBQ9YgVuVQWqAGGmspE7Xh3A41XvgWk47+8X/1EpTUoOsN
J8VfBMUF8kMkUPTgIakCwZ2PpYVPqIfw0nuVYUIENxLUX6441E8uz8+EuKfO
jlGbDo1kn1cDIWZj9Tes9Gs6jpre6gJWlc9p+dHo/rev1N/o/65q8NmvaoyF
ft39U/6iP3i8sPs/sSbNv0bhyeR/r9TTJ90DU/LmqPvzsYce2ujf1PGTp8fD
B9OoGO18xSvPzy/eztV36nTx4+Ia/x1Px/Tz7/zzgH/+lX9+xz9fjQMKvNGo
L2lEjkW5sbCMbitQwZRI6qJa67LlKVMSvEjabQUKhmSBAPsThDwhLQqjoY/+
Th+hnbCO6iTE2hf8e42UfvE8TYI9SDshYQPbeTXm6YrOgPMbR4PCdCrQuE+0
Jz2pK54NMkCuqcv/hRjhytxRlq+ZIVJuQ0lpw9IEJ3QpETom70k4YYZDgVMF
op8CuXszIMsQFcYp0I6pao2Tv/fpAyxEzW0p5Cw2j8NlgUYViO3O2nqWLr4f
Ujlx3hUao9Das9pAD5kQJFpOdsqGq6jllL1rg161ZtbgyZJg/ISMpSc+Atu3
MrAKVZdGdLEmzG8dAh0YPo1k7aOA3UXXYcxUrLs9xWVGqRPqIKTAR6gMYEZ9
6FaRJkVfQIbG0fGVcRDgPmQJEqSwg/BbGmkpZPGuz03DAn1F6RrWf9MWqQVM
GE4cJDY4IYmnPDyn/tw0TKZnRD8g5A0KVok2YwtUDiyhj7Vgl2BvNsUgPMUY
uV2BhBHUhwjksHVMfAxxISzo5O2IgzwMIrPSY2CR3PdjBfg3oVBh/basTcEf
pHyENaRSj7YMZPcqcxVFDzXPb5Fp+H2mFlw1IA12CpNBdOw0rKKQE/+UMHAs
L0nklnFlZnp2lRbnKrBO8jcrIsSCjwOokpvmzsCozZ0bxrlmDKDNXDnYLPCA
Diq44iMFSfiYVEXRdlz6jQTZaPTaEHW2xFVLcN9u3BzDUNnutTCnCQMmkDiI
39bRZdR7PlJdHyRxJ4FwLE7/a3YSOMfi9GhGrc41qOTi9FlP8QK6CxdJ3hz3
66QWCaU8I1PEtdURA+owE0mRrstXeyFdJzAH27//yq+5CyUvEj/Muk1PI0NK
dBjPIlzEBRLhwuOJmng8kZ3CgvYhOk22ZrKzCw6lufOFaQhiEPu+JRdWMgkF
56N6st/NSzRPEOgIA08H9bEaV56yG+p0mi418Ul8s0ZsJGF7pwlFaf5gjXwh
I9ldenidMrV7FHFHKuaupJuj+UdRJOMmRO5CKDYxZEq8WyNgX39x0N1N8Vju
4SALdSGj0SS1OGxNYgohczmWF4MJe3coV9AcD3l+S53EIMrCnMc/POWRqYGh
iZxMfKlS+7VDvsRObjBtpk5uXg7maOnXPIveD9M2/8CgkGe3PK9A1bz98mD+
i5P4DoC2O2jm7zU9X071STfQ5yHqzjg/ykIfJ4PuwOH7MwpLgQn7LcpVrTti
hPrT13OePQJKb+V8xrkVV/+vEn3BADk+tf/LZSIjDIdFektRZE/C1N1WAn/p
nDyM9OuOVQwoiL6vCL0sthgolBKUjnvQlEddAVy4CH2IzXpswnkQRyNBPAHx
uSfnV9JJEDlRpwPCXFKejkt4LDrsF/VKyMqjlqMWfUmVSedJlQkMYyKTHQbQ
4RpcPGGrflOSdkoKajbCeP1qrJCXAiVXwop+jtEp0457ZCslFXLc4XYNlem6
pkGMK+EhKpksYRf2j2hKZ1dBLxEqjJxEqOBWwpD+wGLOUSTox97w4sDog71x
Tpw/SL80fCZMA3ojIdmJxf58HOWAq1U/4A+TXU7rfvIbDn866pQ4m6DXG5Bf
moDH6OcNfVtIc/v6PAH3q4szFvGSIBBITFPCeQH1KGx7x3BcVu2ysF4UWFwk
ZzPcIgv047styyKlLUAK7RJHjulkMjnPGljU07CRNmA+OukybLAry7Sm/gRk
2cqA8+L6cmcjGV7GwzrvilsjI0F5aQ1bE5+LpSv4UGgc0HhL7qT4CuDzgPsj
xJ0S3Zv3/Uawa3DaaPTYEW5/wP7gsQ35bHBWQxoybXM78FS3KCAd2lzSOcS0
cdNzs2rkkox6Q62FNESdtFLuO/SJ0kj1jmMmmsDVvpF6uvd8/94Bzd54hixI
x3SPQg63OBPSS6Kao4hjlU9PPCwjxy8xDrjGDLeMEzORryAteWM64WM5ea2N
84MGBO5Dk59LBrzh7lVs8xbmL5L2YPd1qJj0x9ZL6ztJSkY8Sek9GvOt434R
fGgPDfWYyscCBtYmZNyIm3od+9300Gs03eJTyKHbJOs3oSBTCyB9uiwnuifX
k7gfTvhPEsizXgdqJ/qwRIybnZHMgFuFmxa6AFDdvy8hRw/mG+cdd/1oJLcb
mqfSqU8/BRGFfhY2Rll0BX40vSQrXXfc7NHOtj9dk3V7c3KRQZ8XX0z19YQV
ngzIfRKda2zaTXIRoBu9o8LeGbhJc0uVUy6X8VBZmKVsLlOkx/nnt50yUt1e
/g+dXDN/lBhVhcvolg2fIonVLrsDcGqVTeJvEUmqu77PyFFL6S5YKMOySTyq
JmQNJY+rAAROaty3ngDtHP0ws76i+kZantCQLw8jIR84tvC/eB/mUSqQubag
npzy5SYoWcpNA6/rrQQp22/3Ngd+IKRLSd2uIXqI03dOBWTXbSUnt0NndVcE
5ODIf2KeybcH4oAcnQFfGnmAFifjP8IegOXXgLeqreNjhFjH0qOOL1BOCkle
P2btDg8sv0j+ApVNJfAKPKI56A4Fg+gCy3DgN9C4AAi6aWq7bDtikxbJKDHS
Ew9lTdIMpKlOV2wGZ+0cqsIrohyBW8eiRq40sL+QkgcoAbW3BBf9TZRS8mRD
JIyGL49ohvzfLO1NS6FBdE7XFpHA6vbjNJ01jjqUguoF5Wmht+hp4Ds6bao7
3nxXhsURPI+w7Hs3zqLIPcH+BqeEA0JyeJxGk3dplPKVkCQK9lgQoYP4wp2A
EJ9XMktWPxw85WOqmCU5LCCHScEw9BANuXpO8Ygr4Mf5t+36YtLHActNB9E8
wlxamvR3oRCoCt8kMIj0AoDbw+aEJ+7M8SVtOn9Ujoaglq8K+dbTcaulqzlY
jzdGOFMIICGgiRdysbMIN01bBpevnJZlupLDikBHsTL9AdBB6TARJ3krmvr0
zUV/lSoByw5mY7b2DWYQcHCYPLx6ll7o6lqhjclAF6xP7hwM7pFR2oQ7h1+4
6dWPA5I7X4N7P5H/3EeWajDyk2pNF3gz5vaBAOSoldto+XhtkR6NhX/aFf5p
IPz9DAnGWrmegtiQ4/xUiOyeSjFvtiWAoY5gHnVCoD+kfVdIqJEMV0bjtTbU
aKrq23uTfiK1MFkmF/56S7p64KMwFGRyz0RnEGmTnQkLA7QYL55PDI0UCEid
Gse3RNh48yTTw6EIW7U203hZQxp6+LNLeLqiEE9Sdm/+9D3CrfUxv3q73TMK
j8wrTRqHcz24ax3pLF/EzCVt+2mx3A5wzBvkVoCcrlG0gwZoIdo7hhuebwgP
Wszfzx/gQMPbzTTYKZ3iZ2NYbA2K73vX9COWMLGQVWAdOjqITcTj9034CfQO
G13SdvFELf13GXIUM457bNWegOizH148//x5X84o+N9jSICRl0NehWMgCEzD
ONBHmXUBz3O5VZPoFQ8i3u4WluTfjSxOR/OqAvPla410r9OhpZwxsx3Rv0ig
f8nR3canaBnNeZr43QkcGio5T9nq8O9BrsJphFgumn3P78+G18zDIcd0Cnz7
J/MhK8/SMgAA

-->

</rfc>
