[apps-discuss] STD 73, RFC 6522 on The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages

rfc-editor@rfc-editor.org Tue, 17 January 2012 19:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5497C11E80BB; Tue, 17 Jan 2012 11:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.774
X-Spam-Status: No, score=-103.774 tagged_above=-999 required=5 tests=[AWL=1.303, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Q1czRO7jKKzg; Tue, 17 Jan 2012 11:17:54 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id C20F511E807F; Tue, 17 Jan 2012 11:17:54 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D617F72E041; Tue, 17 Jan 2012 11:14:53 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120117191453.D617F72E041@rfc-editor.org>
Date: Tue, 17 Jan 2012 11:14:53 -0800 (PST)
Cc: apps-discuss@ietf.org, rfc-editor@rfc-editor.org
Subject: [apps-discuss] STD 73, RFC 6522 on The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 19:17:55 -0000

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

        STD 73        
        RFC 6522

        Title:      The Multipart/Report Media Type for 
                    the Reporting of Mail System Administrative 
        Author:     M. Kucherawy, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2012
        Mailbox:    msk@cloudmark.com
        Pages:      9
        Characters: 15715
        Obsoletes:  RFC3462
        See Also:   STD0073

        I-D Tag:    draft-ietf-appsawg-rfc3462bis-04.txt

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

The multipart/report Multipurpose Internet Mail Extensions (MIME)
media type is a general "family" or "container" type for electronic
mail reports of any kind.  Although this memo defines only the use of
the multipart/report media type with respect to delivery status
reports, mail processing programs will benefit if a single media type
is used for all kinds of reports.

This memo obsoletes "The Multipart/Report Content Type for the
Reporting of Mail System Administrative Messages", RFC 3462, and
marks RFC 3462 and its predecessor as "Historic".  [STANDARDS-TRACK]

This document is a product of the Applications Area Working Group Working Group of the IETF.

This is now an Internet Standard.

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

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