RFC 6591 on Authentication Failure Reporting Using the Abuse Reporting Format

rfc-editor@rfc-editor.org Fri, 13 April 2012 18:02 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90D4311E8074; Fri, 13 Apr 2012 11:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.123
X-Spam-Level:
X-Spam-Status: No, score=-104.123 tagged_above=-999 required=5 tests=[AWL=0.954, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDumZfbjwmAH; Fri, 13 Apr 2012 11:02:50 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id E97BF11E809C; Fri, 13 Apr 2012 11:02:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 00ED1B1E00E; Fri, 13 Apr 2012 11:02:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6591 on Authentication Failure Reporting Using the Abuse Reporting Format
From: rfc-editor@rfc-editor.org
Message-Id: <20120413180201.00ED1B1E00E@rfc-editor.org>
Date: Fri, 13 Apr 2012 11:02:00 -0700
Cc: marf@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 18:02:50 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6591

        Title:      Authentication Failure Reporting Using the 
                    Abuse Reporting Format 
        Author:     H. Fontana
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2012
        Mailbox:    hilda@hfontana.com
        Pages:      16
        Characters: 32378
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-marf-authfailure-report-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6591.txt

This memo registers an extension report type for the Abuse Reporting
Format (ARF), affecting multiple registries, for use in generating
receipt-time reports about messages that fail one or more email
message authentication checks. [STANDARDS-TRACK]

This document is a product of the Messaging Abuse Reporting Format Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC