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

The information below is for an old version of the document
Document Type Active Internet-Draft (appsawg WG)
Last updated 2013-07-10 (latest revision 2013-06-28)
Replaces draft-kucherawy-rfc5451bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication Jun 2013
Consensus Yes
Document shepherd S Moonesamy
Shepherd write-up Show (last changed 2013-07-09)
IESG IESG state IESG Evaluation
Telechat date
Needs 2 more YES or NO OBJECTION positions to pass.
Responsible AD Barry Leiba
Send notices to appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-rfc5451bis@tools.ietf.org, sm+ietf@elandsys.com, apps-discuss@ietf.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Individual submission                                       M. Kucherawy
Internet-Draft                                             June 28, 2013
Obsoletes: 5451, 6577
(if approved)
Intended status: Standards Track
Expires: December 30, 2013

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

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 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 December 30, 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 December 30, 2013               [Page 1]
Internet-Draft     Authentication-Results Header Field         June 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 . . . . . . . . . . . . . . . . . . . . . . .  7
       1.5.3.  Email Architecture . . . . . . . . . . . . . . . . . .  7
       1.5.4.  Other Terms  . . . . . . . . . . . . . . . . . . . . .  8
     1.6.  Trust Environment  . . . . . . . . . . . . . . . . . . . .  8
     1.7.  Downward Standards References  . . . . . . . . . . . . . .  9
   2.  Definition and Format of the Header Field  . . . . . . . . . .  9
     2.1.  General Description  . . . . . . . . . . . . . . . . . . .  9
     2.2.  Formal Definition  . . . . . . . . . . . . . . . . . . . . 10
     2.3.  Authentication Identifier Field  . . . . . . . . . . . . . 12
     2.4.  Version Tokens . . . . . . . . . . . . . . . . . . . . . . 13
     2.5.  Defined Methods and Result Values  . . . . . . . . . . . . 14
       2.5.1.  DKIM and DomainKeys  . . . . . . . . . . . . . . . . . 14
       2.5.2.  SPF and Sender-ID  . . . . . . . . . . . . . . . . . . 15
       2.5.3.  "iprev"  . . . . . . . . . . . . . . . . . . . . . . . 16
       2.5.4.  SMTP AUTH  . . . . . . . . . . . . . . . . . . . . . . 16
       2.5.5.  Other Registered Codes . . . . . . . . . . . . . . . . 17
       2.5.6.  Extension Methods  . . . . . . . . . . . . . . . . . . 17
       2.5.7.  Extension Result Codes . . . . . . . . . . . . . . . . 18
   3.  The "iprev" Authentication Method  . . . . . . . . . . . . . . 18
   4.  Adding the Header Field to A Message . . . . . . . . . . . . . 19
     4.1.  Header Field Position and Interpretation . . . . . . . . . 21
     4.2.  Local Policy Enforcement . . . . . . . . . . . . . . . . . 22
   5.  Removing Existing Header Fields  . . . . . . . . . . . . . . . 22
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 23
     6.1.  The Authentication-Results Header Field  . . . . . . . . . 23
Show full document text