Re: proposed media type registration: application/voicexml+xml

> There are two separate issues:
> 1) Does a registration allow the 'charset' parameter or not.
> 2) Does an actual entity have the 'charset' parameter or not.
> 
> It is not totally clear to me which one of these you are talking above.

1)

> In my opinion, it is highly preferable that all registrations
> allow the 'charset' parameter, to avoid a patchwork. The draft
> should contain some justification for this.

RFC 3023 already provides a registration template which introduces the 
charset parameter.  But the recommendation to introduce the charset parameter 
is a SHOULD rather than a MUST.  People read RFC 3023 but they intentionally 
dropped the charset.

I studied existing +xml media types registered at IANA.  
Here is the result.

1. IETF tree

With the exception of application/cnrp+xml, all +xml media types 
have the charset parameter.

1) beep+xml  	[RFC3080]
This keeps the charset parameter.

2) cnrp+xml  	[RFC3367]