Domain-based Message Authentication, Reporting and Conformance (DMARC)
draft-kucherawy-dmarc-base-12

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Murray Kucherawy  , Elizabeth Zwicky 
Last updated 2015-01-28 (latest revision 2015-01-13)
Stream ISE
Intended RFC status Informational
Formats pdf htmlized (tools) htmlized bibtex
IETF conflict review conflict-review-kucherawy-dmarc-base
Stream ISE state Sent to the RFC Editor
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2014-12-14)
IESG IESG state I-D Exists
Telechat date
Responsible AD Pete Resnick
Send notices to "Nevil Brownlee" <rfc-ise@rfc-editor.org>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Details
Network Working Group                                  M. Kucherawy, Ed.
Internet-Draft
Intended status: Informational                            E. Zwicky, Ed.
Expires: July 17, 2015                                            Yahoo!
                                                        January 13, 2015

 Domain-based Message Authentication, Reporting and Conformance (DMARC)
                     draft-kucherawy-dmarc-base-12

Abstract

   Domain-based Message Authentication, Reporting and Conformance
   (DMARC) 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.

   Originators of Internet Mail need to be able to associate reliable
   and authenticated domain identifiers with messages, communicate
   policies about messages that use those identifiers, and report about
   mail using those identifiers.  These abilities have several benefits:
   Receivers can provide feedback to domain owners about the use of
   their domains, which can provide valuable insight about the
   management of internal operations and the presence of external domain
   name abuse.

   DMARC does not produce or encourage elevated delivery privilege of
   authenticated email.  DMARC is a mechanism for policy distribution
   that enables increasingly strict handling of messages that fail
   authentication checks, ranging from no action, through altered
   delivery, up to message rejection.

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."

Kucherawy & Zwicky        Expires July 17, 2015                 [Page 1]
Internet-Draft                    DMARC                     January 2015

   This Internet-Draft will expire on July 17, 2015.

Copyright Notice

   Copyright (c) 2015 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Kucherawy & Zwicky        Expires July 17, 2015                 [Page 2]
Internet-Draft                    DMARC                     January 2015

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  6
     2.1.  High-Level Goals . . . . . . . . . . . . . . . . . . . . .  7
     2.2.  Out Of Scope . . . . . . . . . . . . . . . . . . . . . . .  7
     2.3.  Scalability  . . . . . . . . . . . . . . . . . . . . . . .  7
     2.4.  Anti-Phishing  . . . . . . . . . . . . . . . . . . . . . .  8
   3.  Terminology and Definitions  . . . . . . . . . . . . . . . . .  8
     3.1.  Identifier Alignment . . . . . . . . . . . . . . . . . . .  9
     3.2.  Organizational Domain  . . . . . . . . . . . . . . . . . . 12
   4.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     4.1.  Authentication Mechanisms  . . . . . . . . . . . . . . . . 13
     4.2.  Key Concepts . . . . . . . . . . . . . . . . . . . . . . . 13
     4.3.  Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . 14
   5.  Use of RFC5322.From  . . . . . . . . . . . . . . . . . . . . . 15
   6.  Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     6.1.  DMARC Policy Record  . . . . . . . . . . . . . . . . . . . 17
     6.2.  DMARC URIs . . . . . . . . . . . . . . . . . . . . . . . . 17
     6.3.  General Record Format  . . . . . . . . . . . . . . . . . . 18
     6.4.  Formal Definition  . . . . . . . . . . . . . . . . . . . . 21
     6.5.  Domain Owner Actions . . . . . . . . . . . . . . . . . . . 23
     6.6.  Mail Receiver Actions  . . . . . . . . . . . . . . . . . . 23
     6.7.  Policy Enforcement Considerations  . . . . . . . . . . . . 27
   7.  DMARC Feedback . . . . . . . . . . . . . . . . . . . . . . . . 28
Show full document text