A Property Types Registry for the Authentication-Results Header Field
draft-ietf-appsawg-authres-ptypes-registry-02

The information below is for an old version of the document
Document Type Active Internet-Draft (appsawg WG)
Author Murray Kucherawy 
Last updated 2014-09-15 (latest revision 2014-08-26)
Replaces draft-kucherawy-authres-ptypes-registry
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Scott Kitterman
Shepherd write-up Show (last changed 2014-09-15)
IESG IESG state AD Evaluation
Consensus Boilerplate Unknown
Telechat date
Responsible AD Barry Leiba
Send notices to appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-authres-ptypes-registry@tools.ietf.org, scott@kitterman.com
Individual submission                                       M. Kucherawy
Internet-Draft                                           August 26, 2014
Updates: 7001 (if approved)
Intended status: Standards Track
Expires: February 27, 2015

 A Property Types Registry for the Authentication-Results Header Field
             draft-ietf-appsawg-authres-ptypes-registry-02

Abstract

   [RFC7001] describes a header field called Authentication-Results for
   use with electronic mail messages to indicate the results of message
   authentication efforts.  Any receiver-side software, mainly Mail
   Transfer Agents (MTAs) or mail filters, can add or use this header
   field to relay that information in a convenient and meaningful way to
   later-stage systems, such as for sorting and filtering decisions.

   One portion of the definition in that document limits the types of
   authentication properties about a message to a small, fixed set.
   This document updates the specification, making it extensible to
   allow new property types to be declared and used.

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 27, 2015.

Copyright Notice

   Copyright (c) 2014 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 February 27, 2015               [Page 1]
Internet-Draft    Authentication-Results Property Types      August 2014

   (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  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     2.1.  Key Words . . . . . . . . . . . . . . . . . . . . . . . . . 3
     2.2.  Email Architecture  . . . . . . . . . . . . . . . . . . . . 3
   3.  Updated 'ptype' Definition  . . . . . . . . . . . . . . . . . . 3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . . . 5

Kucherawy               Expires February 27, 2015               [Page 2]
Internet-Draft    Authentication-Results Property Types      August 2014

1.  Introduction

   [RFC7001] defines the email Authentication-Results header field that
   presents the results of an authentication effort in a machine-
   readable format.  The header field creates a place to collect the
   output from authentication processes that are disjoint from later
   processes that might use the output, such as analysis, filtering or
   sorting mechanisms.

   The specification in that document enumerated a small set of types of
   properties that can be reported using this mechanism.  There has
   emerged a desire to report types of properties about a message
   through this mechanism.  Accordingly, this document updates the
   specification to allow for additional property types ("ptypes")
   beyond the original set, and creates a registry where new ones can be
   listed and their defining documents referenced.

2.  Definitions

2.1.  Key Words

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].

2.2.  Email Architecture

   Many of the definitions and acronyms regarding general email
   architecture can be found in [RFC5598].

3.  Updated 'ptype' Definition

   Advanced Backus Naur Form (ABNF) is defined in [RFC5234].

   The ABNF in Section 2.2 of [RFC7001] is updated as follows:
Show full document text