Creation and Use of Email Feedback Reports: An Applicability Statement for the Abuse Reporting Format (ARF)
draft-ietf-marf-as-10

The information below is for an old version of the document
Document Type Active Internet-Draft (marf WG)
Authors J.D. Falk  , Murray Kucherawy 
Last updated 2011-09-13 (latest revision 2011-09-01)
Replaces draft-jdfalk-marf-as
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state In WG Last Call
Document shepherd Barry Leiba
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Pete Resnick
Send notices to marf-chairs@tools.ietf.org, draft-ietf-marf-as@tools.ietf.org
MARF Working Group                                               J. Falk
Internet-Draft                                               Return Path
Updates: 5965 (if approved)                            M. Kucherawy, Ed.
Intended status: Standards Track                               Cloudmark
Expires: August 26, 2012                               February 23, 2012

 Creation and Use of Email Feedback Reports: An Applicability Statement
                  for the Abuse Reporting Format (ARF)
                         draft-ietf-marf-as-10

Abstract

   RFC 5965 defines an extensible, machine-readable format intended for
   mail operators to report feedback about received email to other
   parties.  This Applicability Statement describes common methods for
   utilizing this format for reporting both abuse and authentication
   failure events.  Mailbox Providers of any size, mail sending
   entities, and end users can use these methods as a basis to create
   procedures that best suit them.  Some related optional mechanisms are
   also discussed.

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 26, 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

Falk & Kucherawy         Expires August 26, 2012                [Page 1]
Internet-Draft                   ARF AS                    February 2012

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Discussion . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Solicited and Unsolicited Reports  . . . . . . . . . . . . . .  4
   4.  Creating and Sending Complaint-Based Solicited Abuse
       Reports  . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  General Considerations . . . . . . . . . . . . . . . . . .  4
     4.2.  Where To Send Reports  . . . . . . . . . . . . . . . . . .  5
     4.3.  What To Put In Reports . . . . . . . . . . . . . . . . . .  5
   5.  Receiving and Processing Complaint-Based Solicited Abuse
       Reports  . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     5.1.  General Considerations . . . . . . . . . . . . . . . . . .  5
     5.2.  What To Expect . . . . . . . . . . . . . . . . . . . . . .  6
     5.3.  What To Do . . . . . . . . . . . . . . . . . . . . . . . .  6
   6.  Generating and Handling Unsolicited Abuse Reports  . . . . . .  6
     6.1.  General Considerations . . . . . . . . . . . . . . . . . .  6
     6.2.  When To Generate Reports . . . . . . . . . . . . . . . . .  7
     6.3.  Where To Send Reports  . . . . . . . . . . . . . . . . . .  7
     6.4.  What To Put In Reports . . . . . . . . . . . . . . . . . .  8
     6.5.  What To Do With Reports  . . . . . . . . . . . . . . . . .  9
   7.  Generating Automatic Authentication Failure Reports  . . . . . 10
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
     9.1.  In Other Documents . . . . . . . . . . . . . . . . . . . . 11
     9.2.  Forgeries  . . . . . . . . . . . . . . . . . . . . . . . . 11
     9.3.  Amplification Attacks  . . . . . . . . . . . . . . . . . . 11
     9.4.  Automatic Generation . . . . . . . . . . . . . . . . . . . 11
     9.5.  Reporting Multiple Incidents . . . . . . . . . . . . . . . 12
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 13
     11.2. Informative References . . . . . . . . . . . . . . . . . . 14
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Show full document text