Authenticated Received Chain (ARC) Protocol
draft-ietf-dmarc-arc-protocol-00

The information below is for an old version of the document
Document Type Active Internet-Draft (dmarc WG)
Last updated 2016-06-25
Replaces draft-andersen-arc
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DMARC Working Group                                          K. Andersen
Internet-Draft                                                  LinkedIn
Obsoletes: draft-andersen-arc-17 (if                   J. Rae-Grant, Ed.
           approved)                                        B. Long, Ed.
Intended status: Standards Track                                  Google
Expires: December 27, 2016                                 T. Adams, Ed.
                                                                  Paypal
                                                           S. Jones, Ed.
                                                                     TDP
                                                           June 25, 2016

              Authenticated Received Chain (ARC) Protocol
                    draft-ietf-dmarc-arc-protocol-00

Abstract

   Authenticated Received Chain (ARC) permits an organization which is
   creating or handling email to indicate its involvement with the
   handling process.  It defines a set of cryptographically signed
   header fields in a manner analagous to that of DKIM.  Assertion of
   responsibility is validated through a cryptographic signature and by
   querying the Signer's domain directly to retrieve the appropriate
   public key.  Changes in the message that might break DKIM can be
   identified through the ARC set of header fields.

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 December 27, 2016.

Copyright Notice

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

Andersen, et al.        Expires December 27, 2016               [Page 1]
Internet-Draft                ARC-Protocol                     June 2016

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Primary Design Criteria . . . . . . . . . . . . . . . . .   4
     2.2.  Out of Scope  . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Utility . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Definition  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Description of the New Header Fields  . . . . . . . . . .   6
       5.1.1.  ARC-Seal  . . . . . . . . . . . . . . . . . . . . . .   6
       5.1.2.  ARC-Message-Signature . . . . . . . . . . . . . . . .   9
       5.1.3.  ARC-Authentication-Results  . . . . . . . . . . . . .  10
     5.2.  Constructing the ARC-Seal Set . . . . . . . . . . . . . .  10
       5.2.1.  Handling Violations in the ARC Sets . . . . . . . . .  11
     5.3.  Key Management and Binding  . . . . . . . . . . . . . . .  12
       5.3.1.  Namespace . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  Participation . . . . . . . . . . . . . . . . . . . . . .  12
     6.2.  Relationship between DKIM Signatures and ARC Headers  . .  13
     6.3.  Validating the ARC Set of Header Fields . . . . . . . . .  13
     6.4.  ARC Set Validity  . . . . . . . . . . . . . . . . . . . .  13
       6.4.1.  Assessing Chain Validity Violations . . . . . . . . .  13
       6.4.2.  Responding to ARC Validity Violations . . . . . . . .  13
       6.4.3.  Recording the Results of ARC Evaluation . . . . . . .  13
       6.4.4.  Output Data Points from ARC Evaluation  . . . . . . .  14
       6.4.5.  Reporting ARC Effects for DMARC Local Policy  . . . .  14
Show full document text