DMARC Failure reporting Interval tag
draft-davids-dmarc-fi-tag-01

Document Type Active Internet-Draft (individual)
Last updated 2016-11-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DMARC Working Group                                            M. Davids
Internet-Draft                                                 SIDN Labs
Updates: 7489 (if approved)                            November 24, 2016
Intended status: Standards Track
Expires: May 28, 2017

                  DMARC Failure reporting Interval tag
                      draft-davids-dmarc-fi-tag-01

Abstract

   This document extends the DMARC (RFC7489) record format by defining
   an additional tag.  This new tag, the "fi" tag, is to be used in
   conjunction with the "ruf" tag used for message-specific failure
   reporting.  It provides a Domain Owner with a simple way of
   requesting limitation of the rate at which such reports are sent.

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 http://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 May 28, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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

Davids                    Expires May 28, 2017                  [Page 1]
Internet-Draft                  DMARC-fi                   November 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used In This Document . . . . . . . . . . . . . .   3
   3.  Extension to the General Record Format  . . . . . . . . . . .   3
   4.  Formal Definition . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Domain Owner Example  . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
     10.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   DMARC [RFC7489] enables Domain Owners to request for detailed failure
   reports for individual messages by means of the "ruf" tag.  There may
   be various reasons to permanently configure such a "ruf" tag.  For
   example to facilitate reputation management, monitoring or simply for
   research or operational purposes.

   Failure reports are normally generated and sent almost immediately
   after the Mail Receiver detects a DMARC failure.  These reports are
   useful for quickly notifying the Domain Owners of an authentication
   failure, without waiting for an aggregate report.  However, under
   certain circumstances this property can potentially lead to an
   undesirably high volume of reports.  Especially when a Domain Owner's
   name is spoofed and abused in a large-scale phishing or other
   impersonation attack.

   DMARC [RFC7489] Section 7.3 leaves it to the discretion of
   participating Mail Receivers and report generators if and how they
   take measures against sending high volumes of failure reports.
   However, what a Mail Receiver or report generator considers
   acceptable may exceed the capacity of the receiving Domain Owner.
   The lack of a mechanism for a Domain Owner to influence the volume of
   reports constitutes an obstacle to deployment of the "ruf" tag
   feature.

   This document updates [RFC7489] by defining the "fi" tag, a mechanism
Show full document text