For decades, the email ecosystem has operated on a foundation of "educated guesswork." Senders, tasked with delivering billions of messages, have long existed in a state of asymmetric information: mailbox providers (MBPs) hold the keys to the kingdom—data on why an email landed in the inbox, the spam folder, or was rejected entirely—while senders are left to reverse-engineer their own reputation based on vague bounce codes and fluctuating open rates.
That era may be approaching a quiet, technical end. On March 17, 2026, an IETF Internet-Draft titled Aggregate Performance Reporting Format (APRF) was published, signaling a potential paradigm shift in how the internet handles email deliverability. By proposing a standardized, machine-readable pipeline for placement and engagement data, the authors of APRF are attempting to drag the "black box" of email reputation into the light.
The Main Facts: What is APRF?
At its core, APRF is a proposed standard for mailbox providers to share aggregate data regarding how they treat incoming mail. Authored by a powerhouse coalition—Alex Brotman (Comcast), Tom Corbett (Iterable), and Emil Gustafsson (Google)—the draft seeks to provide senders with the visibility they have requested for years.
The protocol functions as a feedback loop. Using the existing DKIM (DomainKeys Identified Mail) infrastructure, a mailbox provider can query a DNS TXT record associated with a sender’s domain to determine where to send a daily aggregate report. These reports, delivered as JSON files via SMTP, would provide granular, domain-based metrics.
Unlike previous efforts that were siloed behind proprietary dashboards, APRF is designed to be interoperable. It is built to leverage the same logic as DMARC (Domain-based Message Authentication, Reporting, and Conformance), meaning the industry’s existing tooling for parsing DMARC reports could, with minimal modification, be extended to process APRF data.
Chronology: From LinkedIn Post to IETF Draft
The journey of APRF began not in a sterile committee room, but in the trenches of daily operations.
Two weeks prior to the draft’s publication, Alex Brotman, Senior Engineer for Anti-Abuse at Comcast, broke the silence on LinkedIn. He didn’t share a theoretical roadmap or a polished slide deck; he shared evidence of "running code." Brotman confirmed that Comcast had already implemented a beta version of this reporting system in production, generating reports for its own recipients.
March 17, 2026: The formal Internet-Draft draft-brotman-aggregate-performance-reporting-00 was published. This date marks the official entry of the concept into the IETF standards track.
The Current Phase: The draft is currently in its infancy. It is an "individual draft," meaning it has not yet been formally adopted by an IETF Working Group. The authors are actively soliciting feedback from the technical community to refine the Abbreviated Backus-Naur Form (ABNF) and address open questions regarding report re-transmission and data segmentation.
Supporting Data: Why the Industry Needs a Standard
The frustration of the modern deliverability professional is rooted in the "blind spot" of reputation systems. Currently, a sender’s reputation is managed by algorithms that account for throttling, filtering, and placement decisions, yet these algorithms remain proprietary and opaque.
The Breakdown of Current Feedback Loops
- Complaint Loops: These have existed for years but are inconsistent and limited to specific types of negative feedback.
- Provider-Specific Dashboards: Tools like Google Postmaster Tools and Microsoft SNDS are invaluable, but they are walled gardens. A sender must log into multiple portals, each with its own UI, data definitions, and limitations.
- The Absence of Standardization: There is currently no way to pull a machine-readable, cross-provider feed of performance metrics that correlates directly with a specific signing domain.
APRF aims to bridge this gap by moving away from IP-based or "From" header-based reporting and focusing instead on the DKIM signing domain. By using the d= and selector tags, APRF aligns with the broader industry trend toward domain-level reputation, providing a more stable and accurate identifier for modern email infrastructure.
The Weight of the Authorship
Perhaps the most significant aspect of the APRF proposal is the composition of its author list. In the world of email standards, the "who" is often as important as the "what."
- Comcast (The Mailbox Provider): By putting code into production, Comcast has demonstrated that this is not merely a theoretical exercise.
- Iterable (The ESP): Representing the sender-side, Iterable brings the perspective of the platforms that manage millions of emails daily.
- Google (The Market Mover): The inclusion of a Google engineer is the detail that industry analysts are highlighting as the "game changer." Google’s participation suggests that the largest consumer mailbox provider in the world is at least considering a standardized approach to transparency. If Google were to adopt APRF, it would effectively set a new global standard for the entire email ecosystem.
Implications: A New Era for Deliverability?
If APRF is adopted and widely implemented, the implications for the industry would be profound.
1. The Death of Guesswork
Deliverability experts would finally be able to correlate specific campaigns—tracked via the optional sdi (Signer-Defined Identifier) attribute—with actual placement data. Instead of guessing why a campaign saw a dip in engagement, senders would have empirical data regarding how their signing domains are being treated by the receiving provider.
2. Operational Efficiency
By utilizing a JSON-based, SMTP-delivered report format, APRF allows for automated ingestion. Large-scale senders could pipe this data directly into their internal monitoring systems, allowing for real-time adjustments to their sending strategies.
3. The "Inbox" Myth
It is critical to manage expectations. The proponents of APRF are clear: DMARC passing never guaranteed an inbox placement, and APRF will not either. However, APRF provides the "what" and the "where." It offers the diagnostic tools necessary to move a sender closer to the inbox. It changes the conversation from "Why did my mail fail?" to "How can I improve my performance based on this specific, actionable data?"
The Reality Check: Managing Expectations
Despite the excitement, stakeholders should approach APRF with a measured perspective. This is a -00 draft. It is intentionally incomplete, containing unresolved questions regarding how to handle data at scale and the technical nuances of report authentication.
What senders should do now:
- Update Mental Models: Recognize that the industry is shifting toward transparent, domain-based reporting.
- Monitor the IETF: The draft is expected to move toward the MAILMAINT working group. Watching the mailing list for that group will be the best way to stay informed on the proposal’s trajectory.
- Engage in the Feedback Process: The window to influence the standard is now. Technical teams at large senders and infrastructure providers should review the draft and provide the feedback that Alex Brotman has explicitly requested.
Conclusion
The publication of the APRF draft represents a rare moment of alignment between mailbox providers and the sender community. While it is not a "shipping feature" to be added to next quarter’s product roadmap, it is the beginning of a credible, cross-industry effort to solve one of the oldest problems in digital communication.
In an era where email remains the primary vehicle for business, marketing, and transactional communication, the ability to see clearly into the mailbox provider’s decision-making process is not just a luxury—it is an infrastructure necessity. For the first time in the history of the internet, the path toward a transparent, data-driven email ecosystem is being mapped in public, one RFC at a time.
