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

Document Type Active Internet-Draft (dmarc WG)
Last updated 2018-01-22
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: Experimental                               B. Long, Ed.
Expires: July 26, 2018                                            Google
                                                           S. Jones, Ed.
                                                                     TDP
                                                           S. Blank, Ed.
                                                                ValiMail
                                                       M. Kucherawy, Ed.
                                                                     TDP
                                                        January 22, 2018

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

Abstract

   The Authenticated Received Chain (ARC) protocol creates a mechanism
   whereby a series of handlers of an email message can conduct
   authentication of the email message as it passes among them on the
   way to its destination, and record the status of that authentication
   at each step along the handling path, for use by the final recipient
   in making choices about the disposition of the message.  Changes in
   the message that might break DKIM or DMARC 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 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 July 26, 2018.

Andersen, et al.          Expires July 26, 2018                 [Page 1]
Internet-Draft                ARC-Protocol                  January 2018

Copyright Notice

   Copyright (c) 2018 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Definitions and Terminology . . . . . . . . . . . . . . . . .   6
     3.1.  Referenced Definitions  . . . . . . . . . . . . . . . . .   6
   4.  Protocol Elements and Features  . . . . . . . . . . . . . . .   7
     4.1.  Features of the ARC Protocol  . . . . . . . . . . . . . .   8
       4.1.1.  Chain of Custody  . . . . . . . . . . . . . . . . . .   8
       4.1.2.  Optional Participation  . . . . . . . . . . . . . . .   8
       4.1.3.  Only one ARC Chain (One Chain to Rule Them All) . . .   9
       4.1.4.  All Failures are Permanent  . . . . . . . . . . . . .   9
       4.1.5.  Benign nature of an ARC Set . . . . . . . . . . . . .   9
       4.1.6.  Key Management  . . . . . . . . . . . . . . . . . . .   9
       4.1.7.  Trace Information . . . . . . . . . . . . . . . . . .  10
       4.1.8.  Instance Tags . . . . . . . . . . . . . . . . . . . .  10
       4.1.9.  Chain Validation Status . . . . . . . . . . . . . . .  10
   5.  The ARC Header Fields . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Instance ('i=') Tag . . . . . . . . . . . . . . . . . . .  10
       5.1.1.  Valid Range for Instance Tags . . . . . . . . . . . .  10
     5.2.  ARC-Authentication-Results (AAR)  . . . . . . . . . . . .  11
       5.2.1.  ptypes and properties for arc-info  . . . . . . . . .  11
     5.3.  ARC-Message-Signature (AMS) . . . . . . . . . . . . . . .  12
     5.4.  ARC-Seal (AS) . . . . . . . . . . . . . . . . . . . . . .  12
       5.4.1.  The 'cv' Tag  . . . . . . . . . . . . . . . . . . . .  13
       5.4.2.  Implicit Header Fields  . . . . . . . . . . . . . . .  13
   6.  Verifier Actions  . . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  Handling DNS Problems While Validating ARC  . . . . . . .  15
     6.2.  Responding to ARC Validity Violations During the SMTP
Show full document text