A Property Types Registry for the Authentication-Results Header Field
RFC 7410
| Document | Type |
RFC - Proposed Standard
(December 2014; No errata)
Obsoleted by RFC 7601
Updates RFC 7001
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-kucherawy-authres-ptypes-registry | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication (wg milestone: Sep 2014 - Publication requeste... ) | |
| Document shepherd | D. Kitterman | ||
| Shepherd write-up | Show (last changed 2014-09-15) | ||
| IESG | IESG state | RFC 7410 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Barry Leiba | ||
| Send notices to | (None) | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) M. Kucherawy Request for Comments: 7410 December 2014 Updates: 7001 Category: Standards Track ISSN: 2070-1721 A Property Types Registry for the Authentication-Results Header Field Abstract This document updates RFC 7001 by creating a registry for property types in the Authentication-Results header field, used in email authentication work, rather than limiting participants to using the original, small set of fixed values. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7410. 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 (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. Kucherawy Standards Track [Page 1] RFC 7410 Authentication-Results Property Types December 2014 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Updated "ptype" Definition . . . . . . . . . . . . . . . . . 2 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. Normative References . . . . . . . . . . . . . . . . . . . . 5 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 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. Updated "ptype" Definition Advanced Backus Naur Form (ABNF) is defined in [RFC5234]. The ABNF in Section 2.2 of [RFC7001] is updated as follows: ptype = Keyword ; indicates whether the property being evaluated was ; a parameter to an [SMTP] command, was a value taken ; from a message header field, was some property of ; the message body, or was some other property evaluated by ; the receiving Message Transfer Agent (MTA) The ABNF token "Keyword" is defined in Section 4.1.2 of [RFC5321]. Kucherawy Standards Track [Page 2] RFC 7410 Authentication-Results Property Types December 2014 Legal values of "ptype" are as defined in the IANA "Email Authentication Property Types" registry (see Section 3). The initial values are as follows, matching those defined in [RFC7001]: body: Indicates information that was extracted from the body of the message. This might be an arbitrary string of bytes, a hash of a string of bytes, a Uniform Resource Identifier, or some other content of interest. header: Indicates information that was extracted from the header of the message. This might be the value of a header field or some portion of a header field.Show full document text