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

> Is it forbidden by structured suffix reg procedures to register stacked suffixes?
> e.g. application/foo+bar+xml

The syntax allows it, but the meaning is undefined. The rule is that the
material after the last plus sign is the suffix. Plus signs before that
currently have no special meaning. Since that could change in the future,
this is one of those things where it makes sense to push back on such
usage in registrations should someone ever try it.

				Ned

> > -----Original Message-----
> > From: apps-discuss-bounces@ietf.org
> > [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Alexey Melnikov
> > Sent: September 11, 2012 15:06
> > To: apps-discuss@ietf.org
> > Subject: Re: [apps-discuss] I-D Action:
> > draft-ietf-appsawg-media-type-suffix-regs-03.txt
> >
> > On 11/09/2012 19:59, internet-drafts@ietf.org wrote:
> > > 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
> > >                            Alexey Melnikov
> > > 	Filename        :
> > draft-ietf-appsawg-media-type-suffix-regs-03.txt
> > > 	Pages           : 14
> > > 	Date            : 2012-09-11
> > >
> > > Abstract:
> > >     A content media type name sometimes includes partitioned meta-
> > >     information distinguish by a Structured Syntax, to
> > permit noting an
> > >     attribute of the media as a suffix to the name.  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" Message Type Structured Syntax
> > >     Suffix registration.
> >
> > This version addresses the following issues:
> >
> > 1) make the text about fragment identifiers for +ber/+der
> > consistent with the rest of registrations (some minor textual
> > differences, as there is no generic application/ber media
> > type registered)
> >
> > 2) added a warning that updates to generic fragment
> > identifier handling rules can break existing specific media
> > type registrations.
> >
> > I didn't feel there was enough support for reversing the
> > fragment identifier rules to make media type specific rules
> > override generic
> > +suffix rules, so I didn't do this change.
> >
> > I believe this addresses all outstanding issues I know of.
> >
> > Please have a quick look and let submit this document to IESG.
> >
> > Best Regards,
> > Alexey
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
> >
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss