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

Document Type Active Internet-Draft (dmarc WG)
Last updated 2018-04-23
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: October 25, 2018                                         Google
                                                           S. Jones, Ed.
                                                                     TDP
                                                           S. Blank, Ed.
                                                                Valimail
                                                       M. Kucherawy, Ed.
                                                                     TDP
                                                          April 23, 2018

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

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 create an attached, authenticated record
   of the status 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 existing
   authentication mechanisms 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 October 25, 2018.

Andersen, et al.        Expires October 25, 2018                [Page 1]
Internet-Draft                ARC-Protocol                    April 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
     1.1.  General Concepts  . . . . . . . . . . . . . . . . . . . .   5
     1.2.  Differences Between ARC and DKIM  . . . . . . . . . . . .   5
     1.3.  Definitions and Terminology . . . . . . . . . . . . . . .   6
       1.3.1.  Terms defined and used in this document . . . . . . .   6
       1.3.2.  Referenced Definitions  . . . . . . . . . . . . . . .   7
   2.  Protocol Elements and Features  . . . . . . . . . . . . . . .   7
     2.1.  The "ARC Set" of Header Fields  . . . . . . . . . . . . .   8
       2.1.1.  Instance Tags . . . . . . . . . . . . . . . . . . . .   9
     2.2.  Chain Validation Status . . . . . . . . . . . . . . . . .   9
     2.3.  Trace Information . . . . . . . . . . . . . . . . . . . .   9
     2.4.  Key Management  . . . . . . . . . . . . . . . . . . . . .   9
     2.5.  All Failures are Permanent  . . . . . . . . . . . . . . .  10
     2.6.  Chain of Custody  . . . . . . . . . . . . . . . . . . . .  10
     2.7.  Optional Participation  . . . . . . . . . . . . . . . . .  10
     2.8.  Broad Responsibility to Seal  . . . . . . . . . . . . . .  10
     2.9.  One Chain to Rule Them All  . . . . . . . . . . . . . . .  11
     2.10. Sealing is Always Safe  . . . . . . . . . . . . . . . . .  11
   3.  The ARC Header Fields . . . . . . . . . . . . . . . . . . . .  11
     3.1.  Instance ('i=') Tag . . . . . . . . . . . . . . . . . . .  11
     3.2.  ARC-Authentication-Results (AAR)  . . . . . . . . . . . .  12
     3.3.  ARC-Message-Signature (AMS) . . . . . . . . . . . . . . .  12
     3.4.  ARC-Seal (AS) . . . . . . . . . . . . . . . . . . . . . .  13
       3.4.1.  Covered Header Fields . . . . . . . . . . . . . . . .  13
       3.4.2.  The 'cv' Tag  . . . . . . . . . . . . . . . . . . . .  14
   4.  Verifier Actions  . . . . . . . . . . . . . . . . . . . . . .  14
     4.1.  Authentication-Results Information  . . . . . . . . . . .  15
Show full document text