Authentication-Results Registration Update for Sender Policy Framework (SPF) Results
RFC 6577

 
Document Type RFC - Proposed Standard (March 2012; No errata)
Obsoleted by RFC 7001
Updates RFC 5451
Was draft-kucherawy-authres-spf-erratum (individual in app area)
Last updated 2013-02-12
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 6577 (Proposed Standard)
Telechat date
Responsible AD Peter Saint-Andre
Send notices to msk@cloudmark.com, draft-kucherawy-authres-spf-erratum@ietf.org
Internet Engineering Task Force (IETF)                      M. Kucherawy
Request for Comments: 6577                               Cloudmark, Inc.
Updates: 5451                                                 March 2012
Category: Standards Track
ISSN: 2070-1721

             Authentication-Results Registration Update for
                 Sender Policy Framework (SPF) Results

Abstract

   This memo updates the registry of authentication method results in
   Authentication-Results: message header fields, correcting a
   discontinuity between the original registry creation and the Sender
   Policy Framework (SPF) specification.

   This memo updates RFC 5451.

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/rfc6577.

Copyright Notice

   Copyright (c) 2012 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 6577                Auth-Results SPF Erratum              March 2012

Table of Contents

   1. Introduction ....................................................2
   2. Keywords ........................................................2
   3. New 'fail' Definition ...........................................2
   4. IANA Considerations .............................................2
      4.1. Addition of 'Status' Columns ...............................3
      4.2. Update to Result Names .....................................3
   5. Security Considerations .........................................3
   6. References ......................................................4
      6.1. Normative References .......................................4
      6.2. Informative References .....................................4
   Appendix A. Examples in RFC 5451 ...................................5
   Appendix B. Acknowledgements .......................................5

1.  Introduction

   [AUTHRES] defined a new header field for electronic mail messages
   that presents the results of a message authentication effort in a
   machine-readable format.  That Request for Comments created a
   registry of results for a few message authentication mechanisms, one
   of which was the Sender Policy Framework [SPF].  The registry
   contains one entry that is inconsistent with the latter
   specification, which was noted in an erratum [ERR2617] filed with the
   RFC Editor.  This memo updates the IANA registries accordingly.

2.  Keywords

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

3.  New 'fail' Definition

   The new "fail" result, replacing the existing "hardfail" result for
   [SPF] (and thus also for [SENDER-ID]) has the same definition for
   "hardfail" that was used in Section 2.4.2 of [AUTHRES], namely:

      This client is explicitly not authorized to inject or relay mail
      using the sender's DNS domain.

4.  IANA Considerations

   This section enumerates requested actions of IANA, per [IANA].

Kucherawy                    Standards Track                    [Page 2]
RFC 6577                Auth-Results SPF Erratum              March 2012

4.1.  Addition of 'Status' Columns

   IANA has amended the Email Authentication Methods and Email
   Authentication Result Names registries, both in the Email
Show full document text