The following might be a personal opinion: What is the advantage of having a charset parameter? When I see how this has caused issues with faulty transmissions (most commonly servers claiming media type text/html; charset=iso-8859-1 without certainty that it is in the right charset), I would like to discourage any charset parameter anywhere possible. From your registration the parameter brings no information (am I right?). So why include it and not simply rely on the Byte-Order-Mark? Paul Le 18 août 2010 à 18:21, Simon Perreault <simon.perreault@viagenie.ca> a écrit :
Type name: text
Subtype name: vcard
Required parameters: none
Optional parameters: version
The "version" parameter is to be interpreted identically as the VERSION vCard property. If this parameter is present, all vCards in a text/vcard body part MUST have a VERSION property with value identical to that of this MIME parameter.
Encoding considerations: The "charset" MIME parameter, if present, MUST be set to "UTF-8", as defined in [RFC3629].
Security considerations: See Section 9.
Interoperability considerations: The text/vcard media type is intended to identify vCard data of any version. There are older specifications of vCard [RFC2426][oldreference_VCARD] still in common use. While these formats are similar, they are not strictly compatible. In general, it is necessary to inspect the value of the VERSION property (see Section 6.7.9) for identifying the standard to which a given vCard object conforms.
In addition, the following media types are known to have been used to refer to vCard data. They should be considered deprecated in favor of text/vcard.
* text/directory
* text/directory; profile=vcard
* text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-13
Applications that use this media type: They are numerous, diverse, and include mail user agents, instant messaging clients, address book applications, directory servers, customer relationship management software, etc.
Additional information:
Magic number(s):
File extension(s): .vcf
Macintosh file type code(s):
Person & email address to contact for further information: Simon Perreault <simon.perreault@viagenie.ca>
Intended usage: COMMON
Restrictions on usage: none
Author: Simon Perreault and Pete Resnick
Change controller: IETF
-- NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca vCard 4.0 --> http://www.vcarddav.org