Re: [ietf-types] Registration of media type application/vcard+xml

[Simon Perreault <[e-mail]>]

On 2011-04-07 21:04, Chris Lilley wrote:
> On Thursday, April 7, 2011, 10:27:07 PM, Simon wrote:
> SP> On 2011-04-07 16:12, Bjoern Hoehrmann wrote:
>>> If you do not specify an optional 'charset' parameter, it is
>>> ambiguous what the encoding of
>>> `application/vcard+xml;charset=...` is; if you only read the
>>> registration you are likely to ignore the parameter, while, if 
>>> you read RFC 3023 you expect the 'charset' parameter to specify
>>> the en- coding, which has interoperability and security
>>> implications.
> 
> SP> I will update this to read:
> 
> SP>    Optional parameters: charset as defined for application/xml
> in SP>       [RFC3023]; per [RFC3023], use of the charset parameter
> with the SP>       value "utf-8" is "STRONGLY RECOMMENDED"
> 
> That verbatim quote from RFC3023 will probably suffice to deal with
> Bjoern's criticism, but as I just pointed out in another message to
> this thread his criticism is outdated and unwarranted, and raises
> security issues (as he himself points out).

So it looks like an update to RFC3023 would be needed?

In the meantime I think I'll go with the current consensus (RFC3023).

Thanks!
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca