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

---- 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?

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."

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

Tom Petch

> 
> > In other words, this is a recommended action, not some sort of 
> > registration
> > criteria the type must meet.
> >
> >> Do you mean
> >> the name of the new media type can be used as the value of this 
> >> attribute?
> >
> > No, that's a given for such types.
> 
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss