Message Header Field for Indicating Message Authentication Status
draft-ietf-appsawg-rfc5451bis-02

The information below is for an old version of the document
Document Type Active Internet-Draft (appsawg WG)
Last updated 2013-05-12
Replaces draft-kucherawy-rfc5451bis
Stream IETF
Intended RFC status Internet Standard
Formats plain text pdf html
Stream WG state In WG Last Call Jun 2013
Document shepherd S Moonesamy
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Individual submission                                       M. Kucherawy
Internet-Draft                                              May 12, 2013
Obsoletes: 5451, 6577
(if approved)
Intended status: Standards Track
Expires: November 13, 2013

   Message Header Field for Indicating Message Authentication Status
                    draft-ietf-appsawg-rfc5451bis-02

Abstract

   This document specifies a header field 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 make sorting and filtering
   decisions.

   This document is a candidate for Internet Standard status.  [RFC
   Editor: Please delete this notation, as I imagine it will be
   indicated some other way.]

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 November 13, 2013.

Copyright Notice

   Copyright (c) 2013 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

Kucherawy               Expires November 13, 2013               [Page 1]
Internet-Draft     Authentication-Results Header Field          May 2013

   (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
   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 . . . . . . . . . . . . . . . . . . . . . .  5
     1.3.  Processing Scope . . . . . . . . . . . . . . . . . . . . .  6
     1.4.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  6
     1.5.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  6
       1.5.1.  Key Words  . . . . . . . . . . . . . . . . . . . . . .  6
       1.5.2.  Security . . . . . . . . . . . . . . . . . . . . . . .  6
       1.5.3.  Email Architecture . . . . . . . . . . . . . . . . . .  7
     1.6.  Trust Environment  . . . . . . . . . . . . . . . . . . . .  8
   2.  Definition and Format of the Header Field  . . . . . . . . . .  8
     2.1.  General Description  . . . . . . . . . . . . . . . . . . .  8
     2.2.  Formal Definition  . . . . . . . . . . . . . . . . . . . .  9
     2.3.  Authentication Identifier Field  . . . . . . . . . . . . . 11
     2.4.  Version Tokens . . . . . . . . . . . . . . . . . . . . . . 13
     2.5.  Result Values  . . . . . . . . . . . . . . . . . . . . . . 13
       2.5.1.  DKIM and DomainKeys Results  . . . . . . . . . . . . . 13
       2.5.2.  SPF and Sender-ID Results  . . . . . . . . . . . . . . 14
       2.5.3.  "iprev" Results  . . . . . . . . . . . . . . . . . . . 15
       2.5.4.  SMTP AUTH Results  . . . . . . . . . . . . . . . . . . 15
       2.5.5.  Extension Result Codes . . . . . . . . . . . . . . . . 16
     2.6.  Authentication Methods . . . . . . . . . . . . . . . . . . 16
       2.6.1.  Definitions for Existing Methods . . . . . . . . . . . 17
       2.6.2.  Extension Methods  . . . . . . . . . . . . . . . . . . 17
   3.  The "iprev" Authentication Method  . . . . . . . . . . . . . . 18
   4.  Adding the Header Field to A Message . . . . . . . . . . . . . 19
     4.1.  Header Field Position and Interpretation . . . . . . . . . 20
     4.2.  Local Policy Enforcement . . . . . . . . . . . . . . . . . 21
   5.  Removing the Header Field  . . . . . . . . . . . . . . . . . . 22
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 23
     6.1.  The Authentication-Results Header Field  . . . . . . . . . 23
     6.2.  Email Authentication Method Name Registry  . . . . . . . . 23
Show full document text