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

[Simon Perreault <[e-mail]>]

On 2011-04-07 16:12, Bjoern Hoehrmann wrote:
>>   Optional parameters:  none
> 
> 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.

I will update this to read:

   Optional parameters: charset as defined for application/xml in
      [RFC3023]; per [RFC3023], use of the charset parameter with the
      value "utf-8" is "STRONGLY RECOMMENDED"

>>   Encoding considerations:  Same as for application/xml.
> 
> This should use the wording given in RFC 3023 section 7.1.

I will update this to read:

   Encoding considerations:  Same as encoding considerations of
      application/xml as specified in [RFC3023]

>>   Security considerations:  See Section 7 of [draft-ietf-vcarddav-
>>      vcardrev-08].
> 
> This reference appears to be outdated. In -18 I don't see a reference to
> RFC 3023 which is RECOMMENDED in RFC 3023.

There's a typo, sorry about that. I meant [draft-ietf-vcarddav-vcardxml-08].

> This should probably be [RFCXXXX] if the idea is to advance the document
> to RFC status but I would expect the RFC editor to take care of that.

Yes, that is my expectation also.

>>   Applications which use this media type:  Applications that currently
>>      make use of the text/vcard media type can use this as an
>>      alternative.
> 
> I think this should identify the kind of application in addition to the
> indirect reference, something like "applications that maintain or pro-
> cess contact information" or something like that.

I will update this to read:

   Applications which use this media type:  Applications that currently
      make use of the text/vcard media type can use this as an
      alternative. In general, applications that maintain or process
      contact information can use this media type.

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