Message Header Field for Indicating Message Authentication Status
draft-ietf-dmarc-rfc7601bis-03

Document Type Active Internet-Draft (dmarc WG)
Last updated 2018-08-22
Replaces draft-kucherawy-dmarc-rfc7601bis
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state In WG Last Call
Document shepherd Tim Draegen
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Tim Draegen <tim@dmarcian.com>
DMARC Working Group                                         M. Kucherawy
Internet-Draft                                           August 22, 2018
Obsoletes: 7601 (if approved)
Intended status: Standards Track
Expires: February 23, 2019

   Message Header Field for Indicating Message Authentication Status
                     draft-ietf-dmarc-rfc7601bis-03

Abstract

   This document specifies a message header field called Authentication-
   Results for use with electronic mail messages to indicate the results
   of message authentication efforts.  Any receiver-side software, such
   as mail filters or Mail User Agents (MUAs), can use this header field
   to relay that information in a convenient and meaningful way to users
   or to make sorting and filtering decisions.

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 February 23, 2019.

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
   (http://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

Kucherawy               Expires February 23, 2019               [Page 1]
Internet-Draft     Authentication-Results Header Field       August 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Purpose  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.2.  Trust Boundary . . . . . . . . . . . . . . . . . . . . . .  6
     1.3.  Processing Scope . . . . . . . . . . . . . . . . . . . . .  6
     1.4.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  6
     1.5.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  7
       1.5.1.  Key Words  . . . . . . . . . . . . . . . . . . . . . .  7
       1.5.2.  Internationalized Email  . . . . . . . . . . . . . . .  7
       1.5.3.  Security . . . . . . . . . . . . . . . . . . . . . . .  7
       1.5.4.  Email Architecture . . . . . . . . . . . . . . . . . .  8
       1.5.5.  Other Terms  . . . . . . . . . . . . . . . . . . . . .  9
     1.6.  Trust Environment  . . . . . . . . . . . . . . . . . . . .  9
   2.  Definition and Format of the Header Field  . . . . . . . . . .  9
     2.1.  General Description  . . . . . . . . . . . . . . . . . . .  9
     2.2.  Formal Definition  . . . . . . . . . . . . . . . . . . . . 10
     2.3.  Property Types (ptypes) and Properties . . . . . . . . . . 13
     2.4.  The "policy" ptype . . . . . . . . . . . . . . . . . . . . 14
     2.5.  Authentication Identifier Field  . . . . . . . . . . . . . 14
     2.6.  Version Tokens . . . . . . . . . . . . . . . . . . . . . . 16
     2.7.  Defined Methods and Result Values  . . . . . . . . . . . . 16
       2.7.1.  DKIM and DomainKeys  . . . . . . . . . . . . . . . . . 16
       2.7.2.  SPF and Sender ID  . . . . . . . . . . . . . . . . . . 18
       2.7.3.  "iprev"  . . . . . . . . . . . . . . . . . . . . . . . 19
       2.7.4.  SMTP AUTH  . . . . . . . . . . . . . . . . . . . . . . 20
       2.7.5.  Other Registered Codes . . . . . . . . . . . . . . . . 21
       2.7.6.  Extension Methods  . . . . . . . . . . . . . . . . . . 21
       2.7.7.  Extension Result Codes . . . . . . . . . . . . . . . . 22
   3.  The "iprev" Authentication Method  . . . . . . . . . . . . . . 23
   4.  Adding the Header Field to a Message . . . . . . . . . . . . . 24
     4.1.  Header Field Position and Interpretation . . . . . . . . . 25
     4.2.  Local Policy Enforcement . . . . . . . . . . . . . . . . . 26
   5.  Removing Existing Header Fields  . . . . . . . . . . . . . . . 27
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 28
     6.1.  The Authentication-Results Header Field  . . . . . . . . . 28
     6.2.  "Email Authentication Methods" Registry Description  . . . 28
     6.3.  "Email Authentication Methods" Registry Update . . . . . . 28
Show full document text