IETF Logo Mail Archive

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

Ned Freed <ned.freed@mrochek.com> Thu, 08 September 2011 17:08 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95B3621F8AF7 for <apps-discuss@ietfa.amsl.com>; Thu, 8 Sep 2011 10:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.468
X-Spam-Level:
X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599]
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 x+hBkS1zFHhv for <apps-discuss@ietfa.amsl.com>; Thu, 8 Sep 2011 10:08:12 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C109D21F85A4 for <apps-discuss@ietf.org>; Thu, 8 Sep 2011 10:08:12 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5T1WNQG0W011N7Y@mauve.mrochek.com> for apps-discuss@ietf.org; Thu, 8 Sep 2011 10:08:35 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5KP14T1K0014O5Z@mauve.mrochek.com>; Thu, 8 Sep 2011 10:08:32 -0700 (PDT)
Message-id: <01O5T1WLWWPI014O5Z@mauve.mrochek.com>
Date: Thu, 08 Sep 2011 10:06:16 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 08 Sep 2011 09:23:12 -0700" <F5833273385BB34F99288B3648C4F06F13512DFB31@EXCH-C2.corp.cloudmark.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20110830041853.24036.37.idtracker@ietfa.amsl.com> <4E68DB1E.6090007@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DFB31@EXCH-C2.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1315501722; bh=AKhHWEQD0ZIq+U2tTf6/+EBHbJYkQOpzZlh4Re4Dpxs=; h=Cc:Message-id:Date:From:Subject:In-reply-to:MIME-version: Content-type:References:To; b=WRbeyOH3ZZUgOG1cPeSiEkgddSlwEdIBjPptMYkIPG7iNyKngHkOMHmCRtiLbsGec YTtE2SizV0B9TcgRn0E7vC+UsIKg5l/T1tEeQlUA/MVDHSbthNOYpxBSXHCfMkvL/R u75YnnEeam/36stfVOe95kS0HuhMpzcnN6OsEXlA=
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-rfc3462bis-00.txt
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: Thu, 08 Sep 2011 17:08:13 -0000

> > -----Original Message-----
> > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Mykyta Yevstifeyev
> > Sent: Thursday, September 08, 2011 8:11 AM
> > To: apps-discuss@ietf.org
> > Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-rfc3462bis-00.txt
> >
> > Is the "report-type" parameter values tracked somewhere?  Is there an
> > IANA registry for this parameter, or is it going to be created?

> The document says: "The report-type parameter ... is the MIME sub-type of the
> second body part of the multipart/report."  Since MIME types are registered,
> the report-type value is always a value in that registry, so no new registry is
> needed.

However, the fact that a given media subtype is suitable for use as report-type
value needs to be noted in the registration. Perhaps a note to this effect
is in order in this document.

BTW, there's no need for an additional field for this. We can just note it
under intended usage.

				Ned

v2.23.0 | Report a Bug | By Email