Domain-based Message Authentication, Reporting, and Conformance (DMARC) Failure Reporting
draft-ietf-dmarc-failure-reporting-00
DMARC Working Group S. M. Jones, Ed.
Internet-Draft DMARC.org
Obsoletes: 7489 (if approved) A. Vesely, Ed.
Intended status: Standards Track Tana
Expires: 16 May 2021 12 November 2020
Domain-based Message Authentication, Reporting, and Conformance (DMARC)
Failure Reporting
draft-ietf-dmarc-failure-reporting-00
Abstract
Domain-based Message Authentication, Reporting, and Conformance
(DMARC) is a scalable mechanism by which a domain owner can request
feedback about email messages using their domain in the From: address
field. This document describes "failure reports," or "failed message
reports," which provide details about individual messages that failed
to authenticate according to the DMARC mechanism.
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 16 May 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Jones & Vesely Expires 16 May 2021 [Page 1]
Internet-Draft DMARC Failure Reporting November 2020
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 Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Definitions . . . . . . . . . . . . . . . . . 3
3. Failure Reports . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Reporting Format Update . . . . . . . . . . . . . . . . . 4
3.2. Verifying External Destinations . . . . . . . . . . . . . 5
4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 7
4.1. Data Exposure Considerations . . . . . . . . . . . . . . 7
4.2. Report Recipients . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5.1. Attacks on Reporting URIs . . . . . . . . . . . . . . . . 8
5.2. DNS Security . . . . . . . . . . . . . . . . . . . . . . 9
5.3. External Reporting Addresses . . . . . . . . . . . . . . 9
5.4. Secure Protocols . . . . . . . . . . . . . . . . . . . . 10
6. Normative References . . . . . . . . . . . . . . . . . . . . 10
7. Informative References . . . . . . . . . . . . . . . . . . . 10
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 11
A.1. Entire Domain, Monitoring Only, Per-Message Reports . . . 11
A.2. Per-Message Failure Reports Directed to Third Party . . . 12
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
Domain-based Message Authentication, Reporting, and Conformance
(DMARC) [RFC7489] is a scalable mechanism by which a mail-originating
organization can express domain-level policies and preferences for
message validation, disposition, and reporting, that a mail-receiving
organization can use to improve mail handling. This document focuses
on one type of reporting that can be requested under DMARC.
"Failure reports," or "failed message reports," provide diagnostic
information about messages that a Mail Receiver has determined do not
pass the DMARC mechanism. These reports are generally sent at the
time such messages are received and evaluated, to provide the Domain
Owner with timely notification that such failures are occurring, and
to provide information that may assist in diagnosing the cause of the
failures.
Jones & Vesely Expires 16 May 2021 [Page 2]
Internet-Draft DMARC Failure Reporting November 2020
Show full document text