[Docs] [txt|pdf|xml|html] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 RFC 6577

Individual submission                                       M. Kucherawy
Internet-Draft                                           Cloudmark, Inc.
Updates: 5451 (if approved)                            February 12, 2012
Intended status: Standards Track
Expires: August 15, 2012


       Authentication-Results Registration Update for SPF Results
                 draft-kucherawy-authres-spf-erratum-02

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 SPF
   specification.

   This memo updates RFC5451.

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 August 15, 2012.

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



Kucherawy                Expires August 15, 2012                [Page 1]

Internet-Draft          Auth-Results SPF Erratum           February 2012


   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

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


































Kucherawy                Expires August 15, 2012                [Page 2]

Internet-Draft          Auth-Results SPF Erratum           February 2012


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 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].

4.1.  Addition of 'Status' Columns

   IANA is requested to amend the Email Authentication Methods and Email
   Authentication Result Names registries, both in the Email
   Authentication Parameters group, by adding to each a column called
   "Status" that will indicate for each entry its current standards
   status.  Legal values for these columns are:

   active:  The entry is in current use.

   deprecated:  The entry is no longer in current use.

   New registrations to either table MUST specify one of these values.

   All exisitng entries, except as specified below, are to be noted as
   "active" as of publication of this memo.





Kucherawy                Expires August 15, 2012                [Page 3]

Internet-Draft          Auth-Results SPF Erratum           February 2012


4.2.  Update to Result Names

   [AUTHRES] listed "hardfail" as the result to be used when a message
   fails an [SPF] evaluation.  However, this latter specification used
   the string "fail" to denote such failures.

   Therefore, IANA is requested to mark "hardfail" in the Email
   Authentication Result Names registry as "deprecated", and amend the
   "fail" entry as follows:

   Code:  fail

   Defined:  [AUTHRES]

   Auth Method:  spf, sender-id

   Meaning:  [this memo] Section 3

   Status:  active

5.  Security Considerations

   This memo corrects a registry error.  It is possible that older
   implementations will not recognize or use the corrected entry.  Thus,
   implementers are advised to support both result strings for some
   period of time.  However, it is known that some implementations are
   already using the SPF-defined result string.

6.  References

6.1.  Normative References

   [AUTHRES]    Kucherawy, M., "Message Header Field for Indicating
                Message Authentication Status", RFC 5451, April 2009.

   [KEYWORDS]   Bradner, S., "Key words for use in RFCs to Indicate
                Requirement Levels", BCP 14, RFC 2119, March 1997.

6.2.  Informative References

   [IANA]       Narten, T. and H. Alvestrand, "Guidelines for Writing an
                IANA Considerations Section in RFCs", BCP 26, RFC 5226,
                May 2008.

   [SENDER-ID]  Lyon, J. and M. Wong, "Sender ID: Authenticating
                E-Mail", RFC 4406, April 2006.

   [SPF]        Wong, M. and W. Schlitt, "Sender Policy Framework (SPF)



Kucherawy                Expires August 15, 2012                [Page 4]

Internet-Draft          Auth-Results SPF Erratum           February 2012


                for Authorizing Use of Domains in E-Mail, Version 1",
                RFC 4408, April 2006.

Appendix A.  Examples in RFC5451

   It should be noted that this update also applies to the examples in
   [AUTHRES], specifically the one in Appendix B.5.  The error there is
   not corrected by this update, which only deals with the normative
   portions of that specification and the related IANA registrations.
   However, it is assumed one could easily see what needs to be
   corrected there.

   Corrected examples will be included in a full update to [AUTHRES] at
   some future time.

Appendix B.  Acknowledgements

   The author wishes to acknowledge the following for their review and
   constructive criticism of this proposal: S. Moonesamy, Scott
   Kitterman.

Author's Address

   Murray S. Kucherawy
   Cloudmark, Inc.
   128 King St., 2nd Floor
   San Francisco, CA  94107
   US

   Phone: +1 415 946 3800
   EMail: msk@cloudmark.com




















Kucherawy                Expires August 15, 2012                [Page 5]


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/