Registration of media type text/vcard

[Julian Reschke]

On 26.08.2010 14:59, Simon Perreault wrote:
> On 2010-08-26 07:42, Julian Reschke wrote:
>>>> That's why we say instead that if it is used, then it MUST say UTF-8.
>>>
>>> While this approach does not violate any restriction I'm aware of, it
>>> definitely violates the MIME design philosophy, which was to avoid
>>> unnnecessary
>>> silly states.
>>
>> Well, it has the benefit that if you send content to a recipient that
>> has some default handling for text/*, but not for text/vcard, you can
>> specify the encoding (I just verified that with Thunderbird).
>
> Interesting! I think many implementors will be happy to know that...
>
> So do we have consensus on keeping the optional charset parameter and
> restricting its possible value set to just "UTF-8"? (i.e. keeping the
> registration template exactly as it is)

I now believe this is good; an alternative would be application/vcard, 
which would be simpler but would loose the default display behavior in 
"legacy" mail clients (browsers do not display unknown text types 
anyway; I just checked).

Best regards, Julian