Using Multiple Signing Algorithms with the ARC (Authenticated Received Chain) Protocol
draft-ietf-dmarc-arc-multi-01

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01

DMARC Working Group                                          K. Andersen
Internet-Draft                                                  LinkedIn
Intended status: Experimental                              S. Blank, Ed.
Expires: September 20, 2018                                     ValiMail
                                                          J. Levine, Ed.
                                                    Taughannock Networks
                                                          March 19, 2018

 Using Multiple Signing Algorithms with the ARC (Authenticated Received
                            Chain) Protocol
                     draft-ietf-dmarc-arc-multi-01

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.

   Initial development of ARC has been done with a single allowed
   signing algorithm, but parallel work in the DCRUP working group
   (https://datatracker.ietf.org/wg/dcrup/about/) is expanding the
   supported algorithms.  This specification defines how to extend ARC
   for multiple signing algorithms.

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 September 20, 2018.

Copyright Notice

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

Andersen, et al.       Expires September 20, 2018               [Page 1]
Internet-Draft                  ARC-Multi                     March 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Definitions and Terminology . . . . . . . . . . . . . . . . .   3
   4.  Supporting Alternate Signing Algorithms . . . . . . . . . . .   3
   5.  General Approach  . . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  Signers . . . . . . . . . . . . . . . . . . . . . . . . .   3
     5.2.  Validators  . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Phases of Algorithm Evolution . . . . . . . . . . . . . . . .   4
     6.1.  Introductory Period . . . . . . . . . . . . . . . . . . .   4
     6.2.  Co-Existence Period . . . . . . . . . . . . . . . . . . .   4
     6.3.  Deprecation Period  . . . . . . . . . . . . . . . . . . .   4
     6.4.  Obsolescence Period . . . . . . . . . . . . . . . . . . .   4
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   5
     10.2.  Informative References . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   6
   Appendix B.  Comments and Feedback  . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Authenticated Received Chain (ARC) protocol adds a traceable
   chain of signatures that cover the handling of an email message
   through a chain of intermediary handlers.

   Initial development of ARC has been done with a single allowed
   signing algorithm, but parallel work in the DCRUP working group
   (https://datatracker.ietf.org/wg/dcrup/about/) is expanding the
   supported algorithms.  This specification defines how to extend ARC
   for multiple signing algorithms.

Andersen, et al.       Expires September 20, 2018               [Page 2]
Internet-Draft                  ARC-Multi                     March 2018