Message Header Field for Indicating Message Authentication Status
RFC 8601
Document | Type |
RFC - Proposed Standard
(May 2019; Errata)
Obsoletes RFC 7601
|
|
---|---|---|---|
Author | Murray Kucherawy | ||
Last updated | 2020-03-24 | ||
Replaces | draft-kucherawy-dmarc-rfc7601bis | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Tim Draegen | ||
Shepherd write-up | Show (last changed 2018-10-24) | ||
IESG | IESG state | RFC 8601 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alexey Melnikov | ||
Send notices to | Tim Draegen <tim@dmarcian.com> | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) M. Kucherawy Request for Comments: 8601 May 2019 Obsoletes: 7601 Category: Standards Track ISSN: 2070-1721 Message Header Field for Indicating Message Authentication Status 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. This document obsoletes RFC 7601. 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 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8601. Kucherawy Standards Track [Page 1] RFC 8601 Authentication-Results Header Field May 2019 Copyright Notice Copyright (c) 2019 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 (https://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 .............................................6 1.3. Processing Scope ...........................................7 1.4. Requirements ...............................................7 1.5. Definitions ................................................7 1.5.1. Key Words ...........................................7 1.5.2. Internationalized Email .............................7 1.5.3. Security ............................................8 1.5.4. Email Architecture ..................................8 1.5.5. Other Terms .........................................9 1.6. Trust Environment .........................................10 2. Definition and Format of the Header Field ......................10 2.1. General Description .......................................10 2.2. Formal Definition .........................................11 2.3. Property Types (ptypes) and Properties ....................13 2.4. The "policy" ptype ........................................15 2.5. Authentication Service Identifier Field ...................15 2.6. Version Tokens ............................................17 2.7. Defined Methods and Result Values .........................17 2.7.1. DKIM ...............................................17 2.7.2. SPF ................................................19 2.7.3. "iprev" ............................................20 2.7.4. SMTP AUTH ..........................................21 2.7.5. Other Registered Codes .............................22 2.7.6. Extension Methods ..................................22 2.7.7. Extension Result Codes .............................23 3. The "iprev" Authentication Method ..............................23 4. Adding the Header Field to a Message ...........................25 4.1. Header Field Position and Interpretation ..................26 4.2. Local Policy Enforcement ..................................27 Kucherawy Standards Track [Page 2] RFC 8601 Authentication-Results Header Field May 2019 5. Removing Existing Header Fields ................................28 6. IANA Considerations ............................................29 6.1. The Authentication-Results Header Field ...................29 6.2. "Email Authentication Methods" Registry Description .......30 6.3. "Email Authentication Methods" Registry Update ............31 6.3.1. "header.a" for DKIM ................................32Show full document text