Re: [media-types] I-D Action: draft-ietf-mediaman-suffixes-00.txt

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

On Wed, Dec 1, 2021 at 2:53 PM <[e-mail]> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Media Type Maintenance WG of the IETF.
>
>         Title           : Media Types with Multiple Suffixes
>         Authors         : Manu Sporny
>                           Amy Guy
>         Filename        : draft-ietf-mediaman-suffixes-00.txt
>         Pages           : 4
>         Date            : 2021-11-21
>
> Abstract:
>    This document updates RFC 6838 "Media Type Specifications and
>    Registration Procedures" to describe how to interpret subtypes with
>    multiple suffixes.
>

Some initial feedback:

The prose in the Abstract and elsewhere says this updates RFC 6838, but
it's not shown that way in the front page header.  Please add that.

I think Section 2 is fine, but I'm confused by Section 2.1.  Let's ignore
the multi-leveled thing for the moment.  I've always read "foo/bar+baz" as
"a foo/bar, encoded or expressed using baz".  Or put another way: Take this
payload and apply the inverse of "baz", and I should get a "foo/bar".  This
section seems to suggest the idea that if I don't know what a "foo/bar" is,
maybe I know what a "foo/baz" is, and I should try that.  Why is that the
right thing to do here?

For Appendix A, it's a little curious for an author to be thanking himself.

-MSK, just participating