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

Document Type Active Internet-Draft (dmarc WG)
Last updated 2017-03-16
Replaces draft-andersen-arc
Stream IETF
Intended RFC status (None)
Formats plain text xml 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
Intended status: Standards Track                            B. Long, Ed.
Expires: September 16, 2017                                       Google
                                                           S. Jones, Ed.
                                                                     TDP
                                                          March 15, 2017

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

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 September 16, 2017.

Copyright Notice

   Copyright (c) 2017 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

Andersen, et al.       Expires September 16, 2017               [Page 1]
Internet-Draft                ARC-Protocol                    March 2017

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   5
   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 . . . . . . . . . . . . . . . .  10
       5.1.3.  ARC-Authentication-Results  . . . . . . . . . . . . .  11
     5.2.  Constructing the ARC-Seal Set . . . . . . . . . . . . . .  12
       5.2.1.  Handling Minor Violations in the ARC Sets . . . . . .  13
       5.2.2.  Handling Major Violations in the ARC Sets . . . . . .  13
     5.3.  Key Management and Binding  . . . . . . . . . . . . . . .  14
       5.3.1.  Namespace . . . . . . . . . . . . . . . . . . . . . .  14
     5.4.  Supporting Alternate Signing Algorithms . . . . . . . . .  14
       5.4.1.  Introductory Period . . . . . . . . . . . . . . . . .  14
       5.4.2.  Co-Existence Period . . . . . . . . . . . . . . . . .  14
       5.4.3.  Deprecation Period  . . . . . . . . . . . . . . . . .  14
       5.4.4.  Obsolescence Period . . . . . . . . . . . . . . . . .  15
   6.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
     6.1.  Participation . . . . . . . . . . . . . . . . . . . . . .  15
     6.2.  Relationship between DKIM Signatures and ARC Headers  . .  15
     6.3.  Validating the ARC Set of Header Fields . . . . . . . . .  15
     6.4.  ARC Set Validity  . . . . . . . . . . . . . . . . . . . .  15
       6.4.1.  Assessing Chain Validity Violations . . . . . . . . .  15
       6.4.2.  Responding to ARC Validity Violations . . . . . . . .  16
Show full document text