Independent W. Chuang Internet-Draft A. Robinson Intended status: Informational Google, Inc. Expires: 20 May 2027 16 November 2026 Feedback-id Email Header Field draft-chuang-feedback-id-header-00 Abstract 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. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 20 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. Chuang & Robinson Expires 20 May 2027 [Page 1] Internet-Draft feedback-id November 2026 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology and Definitions . . . . . . . . . . . . . . . . . 3 3. *Header Format* . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. ABNF Syntax . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Identifier Selection . . . . . . . . . . . . . . . . . . 4 3.3. Illustrative Example . . . . . . . . . . . . . . . . . . 4 4. *Feedback Loop* . . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Authentication and Infrastructure Requirements . . . . . 5 4.2. Data Aggregation and Reporting . . . . . . . . . . . . . 6 5. *Security Considerations* . . . . . . . . . . . . . . . . . . 6 6. *IANA Considerations* . . . . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . 8 7.2. Informative References . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction Large-volume email senders and Email Service Providers (ESPs) use Feedback Loops (FBLs) [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. Traditional FBL implementations generate per-complaint messages using the Abuse Reporting Format (ARF) [RFC5965] (often routed to addresses advertised via [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. 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 Chuang & Robinson Expires 20 May 2027 [Page 2] Internet-Draft feedback-id November 2026 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. 2. Terminology and Definitions 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 [RFC2119]. Syntax definitions in this document use ABNF [RFC5234]. Email transport and message header formatting are defined in SMTP [RFC5321] and the Internet Message Format [RFC5322]. DomainKeys Identified Mail (DKIM) is defined in [RFC6376], Sender Policy Framework (SPF) is defined in [RFC7208], and DNS resource records (including PTR) are defined in [RFC1035]. Internet mail architecture terms such as Originator, Relay, Receiver, and Administrative Management Domain (ADMD) follow [RFC5598]. 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. 3. *Header Format* Senders embed the "Feedback-ID" header field in outbound [RFC5322] messages to associate mail traffic with campaign, customer, mail- type, and sender Identifiers. Conceptually, the header field has the following format: Feedback-ID: a:b:c:SenderId The fields of this header are defined as follows: * "Feedback-ID": Name of the header field to be embedded in the message header section. Per [RFC5322], header field names are case-insensitive. * "a", "b", "c": OPTIONAL fields that MAY be used by the sender to embed up to three (3) Identifiers (for example, campaign/customer/ other). * "SenderId": REQUIRED unique Identifier (5 to 15 characters RECOMMENDED) chosen by the sender. It SHOULD remain consistent across the sender's mail stream. Chuang & Robinson Expires 20 May 2027 [Page 3] Internet-Draft feedback-id November 2026 3.1. ABNF Syntax The formal syntax of the "Feedback-ID" header field is specified using ABNF [RFC5234], importing FWS and CRLF from [RFC5322]: 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 / "-" / "_" / "." / "+" / "/" / "=" 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"). 3.2. Identifier Selection When choosing Identifiers, the following operational requirements apply to ensure accurate aggregation: * 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 [RFC5322]), because single-message Identifiers cannot accumulate aggregate volume. * 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. * 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. 3.3. Illustrative Example Below is a non-normative example illustrating the use of all four fields in a "Feedback-ID" header field: Chuang & Robinson Expires 20 May 2027 [Page 4] Internet-Draft feedback-id November 2026 Feedback-ID: CampaignIDX:CustomerID2:MailTypeID3:SenderId * "CampaignIDX": Campaign Identifier specific to Customer 2 and unique across all customers (that is, no two customers share the same campaign ID). * "CustomerID2": Unique customer Identifier. * "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. * "SenderId": The sender's unique Identifier, which can be used for overall statistics. 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. 4. *Feedback Loop* 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. 4.1. Authentication and Infrastructure Requirements 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: * DKIM Signing: Outbound traffic MUST be signed with DKIM [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. * Single Verified Header: Senders SHOULD ensure that their outbound traffic carries only one such verified "Feedback-ID" header field per message. * 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. Chuang & Robinson Expires 20 May 2027 [Page 5] Internet-Draft feedback-id November 2026 * SPF and Reverse DNS Alignment: Senders MUST publish the IP addresses from which they send mail in the SPF records [RFC7208] of their signing domains. In addition, sending IP addresses MUST have valid DNS PTR records [RFC1035] that resolve to a valid hostname, which SHOULD preferably be one of the DKIM signing domains. 4.2. Data Aggregation and Reporting Receiving mailbox providers generate and report aggregated FBL statistics according to the following rules: * 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. * 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. * 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. * 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. * Recipient Scope: FBL data reported by a mailbox provider pertains only to recipients hosted within that provider's Administrative Management Domain (ADMD) [RFC5598]. 5. *Security Considerations* 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 [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 Chuang & Robinson Expires 20 May 2027 [Page 6] Internet-Draft feedback-id November 2026 restrict access to FBL reports to domain owners that have verified control of the corresponding DKIM signing domain. 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 [RFC6376] Section 8.15 to prevent downstream insertion of additional "Feedback-ID" header fields. As described in [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. Traditional per-message feedback mechanisms such as [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. 6. *IANA Considerations* 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 ([RFC3864]) is a draft placeholder and is not yet approved or ready for IANA action: Header field name: Feedback-ID Applicable protocol: mail Status: informational Author/Change controller: IETF Specification document(s): This document -- 7. References Chuang & Robinson Expires 20 May 2027 [Page 7] Internet-Draft feedback-id November 2026 7.1. Normative References [RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, November 1987, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3864] Klyne, G., Nottingham, M., and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90, RFC 3864, DOI 10.17487/RFC3864, September 2004, . [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, . [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, DOI 10.17487/RFC5321, October 2008, . [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, DOI 10.17487/RFC5322, October 2008, . [RFC6376] Crocker, D., Ed., Hansen, T., Ed., and M. Kucherawy, Ed., "DomainKeys Identified Mail (DKIM) Signatures", STD 76, RFC 6376, DOI 10.17487/RFC6376, September 2011, . [RFC7208] Kitterman, S., "Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1", RFC 7208, DOI 10.17487/RFC7208, April 2014, . 7.2. Informative References [RFC5598] Crocker, D., "Internet Mail Architecture", RFC 5598, DOI 10.17487/RFC5598, July 2009, . Chuang & Robinson Expires 20 May 2027 [Page 8] Internet-Draft feedback-id November 2026 [RFC5965] Shafranovich, Y., Levine, J., and M. Kucherawy, "An Extensible Format for Email Feedback Reports", RFC 5965, DOI 10.17487/RFC5965, August 2010, . [RFC6449] Falk, J., Ed., "Complaint Feedback Loop Operational Recommendations", RFC 6449, DOI 10.17487/RFC6449, November 2011, . [RFC9477] Benecke, J., "Complaint Feedback Loop Address Header", RFC 9477, DOI 10.17487/RFC9477, September 2023, . Authors' Addresses Weihaw Chuang Google, Inc. 1600 Amphitheatre Parkway Mountain View, California 94043 United States of America Email: weihaw@google.com Allen Robinson Google, Inc. 20 Breithaupt Street, Kitchener, ON N2H 5G5 Kitchener Ontario N2H 5G5 Canada Email: arobins@google.com Chuang & Robinson Expires 20 May 2027 [Page 9]