Re: [apps-discuss] I-D Action: draft-ietf-appsawg-media-type-suffix-regs-00.txt

["Murray S. Kucherawy" <[e-mail]>]

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of [e-mail]
> Sent: Thursday, April 26, 2012 6:19 AM
> To: [e-mail]
> Cc: [e-mail]
> Subject: I-D Action: draft-ietf-appsawg-media-type-suffix-regs-00.txt
> 
> 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           : Additional Media Type Structured Syntax Suffixes
> 	Author(s)       : Tony Hansen
> 	Filename        : draft-ietf-appsawg-media-type-suffix-regs-00.txt
> 	Pages           : 9
> 	Date            : 2012-04-26
> 
>    This document defines several Structured Syntax Suffixes for use with
>    media type registrations.  In particular, it defines and registers
>    the "+json", "+ber", "+der", "+fastinfoset", "+wbxml" and "+zip"
>    Structured Syntax Suffixes, and updates the "+xml" Structured Syntax
>    Suffix registration.

<hat type='participant'>

This document looks reasonable to me as-is.  All of my comments are minor or nitty in nature except for the last one.

Sections 1, 3-7: The "may" in a document citing RFC2119 ought to be "can" or such.

Section 1: s/some Media Type registration/some Media Type registrations/

Section 1: "media type" is sometimes capitalized, sometimes not.

Section 2: s/provides receivers/allows receivers/  (or enables, or permits)

Sections 3 through 8: The hangText and the content of each bullet runs together.  Suggest a colon at the end of each hangText.

Section 3: Would a reference to someplace for a definition/explanation of "fragment identifier" be useful here to establish context?

Section 4: The two registrations run together as there's no separation between them.  Perhaps put each in its own section or subsection?

Section 8: Non-normative "should" ought to be something else.

Sections 3-8: I forget where we stand on the whole issue of the use of normative language in IANA registration materials.  It's there in this one.  Do we want to leave it?

</hat>

-MSK