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

Ned Freed <ned.freed@mrochek.com> Tue, 27 September 2011 22:38 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 405D621F8F7C for <apps-discuss@ietfa.amsl.com>; Tue, 27 Sep 2011 15:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level:
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, 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 89OSsMl3qAlS for <apps-discuss@ietfa.amsl.com>; Tue, 27 Sep 2011 15:38:07 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 611EE21F8EEA for <apps-discuss@ietf.org>; Tue, 27 Sep 2011 15:38:07 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O6JWZRGLSG00IJGK@mauve.mrochek.com> for apps-discuss@ietf.org; Tue, 27 Sep 2011 15:38:55 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O68GZ66CTS014O5Z@mauve.mrochek.com>; Tue, 27 Sep 2011 15:38:50 -0700 (PDT)
Message-id: <01O6JWZO2QPQ014O5Z@mauve.mrochek.com>
Date: Tue, 27 Sep 2011 15:34:01 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Tue, 27 Sep 2011 12:34:57 +0200" <013901cc7d01$214dfc20$4001a8c0@gateway.2wire.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20110922053351.2337.12758.idtracker@ietfa.amsl.com> <4E805282.5050004@isode.com> <01O6I5IVA4F2014O5Z@mauve.mrochek.com> <4E80DA9E.6000101@isode.com> <013901cc7d01$214dfc20$4001a8c0@gateway.2wire.net>
To: "t.petch" <ietfc@btconnect.com>
Cc: Ned Freed <ned.freed@mrochek.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-rfc3462bis-01.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: Tue, 27 Sep 2011 22:38:08 -0000

> ---- Original Message -----
> From: "Alexey Melnikov" <alexey.melnikov@isode.com>
> To: "Ned Freed" <ned.freed@mrochek.com>
> Cc: <apps-discuss@ietf.org>
> Sent: Monday, September 26, 2011 10:03 PM
> > >> >
> > >> 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?
> > >
> > > It means you're supposed to say something like:
> > >
> > >    This media type is suitable for use in report-type parts per
> > > RFC3462bis.
> > >
> > > in the Intended Usage section of the type registration.
> >
> > Ok, maybe this is just me, but I don't think this is clear. Maybe say
> > "suitable for use as the second body part of a multipart/report" instead?

Seems like a reasonable change to me.

> Surely it should say

> "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
> **whether or not
> the type being registered is suitable for use
> as a report-type in the context of this specification."

No, because a new report format is by definition suitable for use in
this area. If it weren't it would not qualify as this sort of type.

> As the text stands, it merely says that all new media types are suitable,
> which seems rather pointless:-)

That might apply if this document was discusingg media types in general, but
it isn't. This is quite specifically about report formats, and this text
is about the need to note that such formats identify themselves as such
in their registration.

				Ned