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

[Bjoern Hoehrmann <[e-mail]>]

* Simon Perreault wrote:
>   Type name:  application
>
>   Subtype name:  vcard+xml
>
>   Required parameters:  none
>
>   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.

If this omission of the parameter is not an oversight, I would expect a
rationale for its omission as part of the review request and expect the
interoperability and security issues that arise from this to be noted in
the specification.

>   Encoding considerations:  Same as for application/xml.

This should use the wording given in RFC 3023 section 7.1.

>   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.

>   Interoperability considerations:  This media type provides an
>      alternative syntax to vCard data [draft-ietf-vcarddav-vcardrev-08]
>      based on XML.
>
>   Published specification:  [draft-ietf-vcarddav-vcardrev-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.

>   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.
-- 
Björn Höhrmann · mailto:[e-mail] · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: [phone] · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/