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

Document Type Active Internet-Draft (dmarc WG)
Last updated 2017-07-21
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: January 22, 2018                                         Google
                                                           S. Jones, Ed.
                                                       M. Kucherawy, Ed.
                                                                     TDP
                                                           July 21, 2017

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

Abstract

   The Authenticated Received Chain (ARC) protocol creates a mechanism
   whereby a series of handlers of a message can conduct authentication
   of a 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.

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 January 22, 2018.

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
   publication of this document.  Please review these documents

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

   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.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Instance ('i=') Tags  . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Valid Range for Instance Tags . . . . . . . . . . . . . .   6
   5.  The ARC Header Fields . . . . . . . . . . . . . . . . . . . .   6
     5.1.  ARC-Authentication-Results (AAR)  . . . . . . . . . . . .   6
       5.1.1.  Additional Information for the AAR Header . . . . . .   7
     5.2.  ARC-Message-Signature (AMS) . . . . . . . . . . . . . . .   7
     5.3.  ARC-Seal (AS) . . . . . . . . . . . . . . . . . . . . . .   8
       5.3.1.  The 'cv' Tag  . . . . . . . . . . . . . . . . . . . .   9
       5.3.2.  Selected Header Fields  . . . . . . . . . . . . . . .   9
   6.  Verifier Actions  . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Signer Actions  . . . . . . . . . . . . . . . . . . . . . . .  11
   8.  Key Management  . . . . . . . . . . . . . . . . . . . . . . .  12
   9.  Usage of ARC and Chain Validity . . . . . . . . . . . . . . .  12
     9.1.  Relationship between DKIM-Signature and AMS signing
           scopes  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     9.2.  Assessing Chain Validity Violations . . . . . . . . . . .  12
     9.3.  Marking and Sealing "cv=fail" (Invalid) Chains  . . . . .  12
     9.4.  Handling DNS Problems While Validating ARC  . . . . . . .  13
     9.5.  Responding to ARC Validity Violations . . . . . . . . . .  13
     9.6.  Recording the Results of ARC Evaluation . . . . . . . . .  13
       9.6.1.  Output Information from an ARC Evaluation . . . . . .  13
       9.6.2.  Reporting ARC Effects for DMARC Local Policy -
               Interim . . . . . . . . . . . . . . . . . . . . . . .  14
   10. Supporting Alternate Signing Algorithms . . . . . . . . . . .  14
     10.1.  Introductory Period  . . . . . . . . . . . . . . . . . .  15
     10.2.  Co-Existence Period  . . . . . . . . . . . . . . . . . .  15
     10.3.  Deprecation Period . . . . . . . . . . . . . . . . . . .  15
Show full document text