Re: [apps-discuss] I-D Action: draft-ietf-appsawg-rfc3462bis-01.txt

Alexey Melnikov <> Mon, 26 September 2011 10:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 634E221F8B7B for <>; Mon, 26 Sep 2011 03:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0v8Cp0PR6Rvm for <>; Mon, 26 Sep 2011 03:20:20 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 974F921F8B78 for <>; Mon, 26 Sep 2011 03:20:19 -0700 (PDT)
Received: from [] ((unknown) []) by (submission channel) via TCP with ESMTPA id <>; Mon, 26 Sep 2011 11:23:00 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <>
Date: Mon, 26 Sep 2011 11:22:58 +0100
From: Alexey Melnikov <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
References: <>
In-Reply-To: <>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-rfc3462bis-01.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 26 Sep 2011 10:20:20 -0000 wrote:

>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Applications Area Working Group Working Group of the IETF.
>	Title           : The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages
>	Author(s)       : Murray S. Kucherawy
>	Filename        : draft-ietf-appsawg-rfc3462bis-01.txt
>	Pages           : 15
>	Date            : 2011-09-21
>   The multipart/report Multipurpose Internet Mail Extensions (MIME)
>   media type is a general &quot;family&quot; or &quot;container&quot; 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 RFC3462.
The new version addresses my earlier concerns.
One small new issue:

The newly added:
5. Registering New Report Types   
    Registration of new media types for the purpose of creating a new   
    report format SHOULD note in the Intended Usage section of the media   
    type registration that the type being registered is suitable for use   
    as a report-type in the context of this specification.

What does "suitable for use as a report-type" means exactly? Do you mean 
the name of the new media type can be used as the value of this attribute?