SPF Authentication Failure Reporting using the Abuse Report Format
draft-ietf-marf-spf-reporting-09

The information below is for an old version of the document
Document Type Active Internet-Draft (marf WG)
Last updated 2012-03-14 (latest revision 2012-03-12)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd Murray Kucherawy
Shepherd write-up Show (last changed 2012-02-08)
IESG IESG state IESG Evaluation
Telechat date
Needs a YES. Needs 8 more YES or NO OBJECTION positions to pass.
Responsible AD Pete Resnick
Send notices to marf-chairs@tools.ietf.org, draft-ietf-marf-spf-reporting@tools.ietf.org
MARF Working Group                                          S. Kitterman
Internet-Draft                                                     Agari
Updates: 4408 (if approved)                               March 12, 2012
Intended status: Standards Track
Expires: September 13, 2012

   SPF Authentication Failure Reporting using the Abuse Report Format
                    draft-ietf-marf-spf-reporting-09

Abstract

   This memo presents extensions to the Abuse Reporting Format (ARF),
   and Sender Policy Framework (SPF) specifications to allow for
   detailed reporting of message authentication failures in an on-demand
   fashion.

   This memo updates RFC4408 by providing an IANA registry for SPF
   modifiers.

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 September 13, 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

Kitterman              Expires September 13, 2012               [Page 1]
Internet-Draft         SPF Auth Failure Reporting             March 2012

   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  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  Keywords . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.2.  Imported Definitions . . . . . . . . . . . . . . . . . . .  4
   3.  Optional Reporting Address for SPF . . . . . . . . . . . . . .  5
   4.  Requested Reports  . . . . . . . . . . . . . . . . . . . . . .  7
     4.1.  Requested Reports for SPF Failures . . . . . . . . . . . .  7
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
     5.1.  SPF Modifier Registration  . . . . . . . . . . . . . . . .  8
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
     6.1.  Identity Selection . . . . . . . . . . . . . . . . . . . .  9
     6.2.  Report Volume  . . . . . . . . . . . . . . . . . . . . . .  9
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Appendix A.  Acknowledgements  . . . . . . . . . . . . . . . . . . 11
   Appendix B.  Examples  . . . . . . . . . . . . . . . . . . . . . . 12
     B.1.  SPF DNS record for domain that sends no mail, but
           requests reports . . . . . . . . . . . . . . . . . . . . . 12
     B.2.  Minimal SPF DNS record change to add a reporting
           address  . . . . . . . . . . . . . . . . . . . . . . . . . 12
     B.3.  SPF DNS record with reporting address, report
           percentage, and requested report type  . . . . . . . . . . 12
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13

Kitterman              Expires September 13, 2012               [Page 2]
Internet-Draft         SPF Auth Failure Reporting             March 2012

1.  Introduction

   [ARF] defines a message format for sending reports of abuse in the
   messaging infrastructure, with an eye toward automating both the
   generating and consumption of those reports.

   [SPF] is one mechanism for message sender authentication; it is
   "path-based" meaning it authenticates the route that a message took
   from origin to destination.  The output is a verified domain name
   that can then be subjected to some sort of evaluation process (e.g.,
   comparison to a known-good list, submission to a reputation service,
   etc.).

   This document extends [SPF] to add an optional reporting address and
Show full document text