W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2008

Re: PROPOSAL: i74: Encoding for non-ASCII headers

From: Roy T. Fielding <fielding@gbiv.com>
Date: Tue, 25 Mar 2008 11:21:56 -0700
Message-Id: <1E986054-5C0B-4842-89B8-A7A4BE32C2C4@gbiv.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
To: Mark Nottingham <mnot@mnot.net>

On Mar 25, 2008, at 4:06 AM, Mark Nottingham wrote:
>
> Based upon discussion, a proposal for closing i74:
>
> * p1, section 2.2 -
>
>> The TEXT rule is only used for descriptive field contents and  
>> values that are not intended to be interpreted by the message  
>> parser. Words of *TEXT MAY contain characters from character sets  
>> other than ISO- 8859-1 [ISO-8859-1] only when encoded according to  
>> the rules of [RFC2047].
>
>   - remove the requirement that only RFC2047 encoding be used;  
> instead, recommend that context-specific encoding rules be used  
> (giving examples), and failing that, the \u'nnnnnn' form from BCP137.
>   - add new issues for dealing with specific circumstances (e.g.,  
> From, Content-Disposition, Warning) as necessary.

I see no reason to change the existing encoding requirement unless
we are to allow raw UTF-8 in headers.  Anything else would just make
the implementations worse.  BCP137 is not mature enough to use in HTTP.

....Roy
Received on Tuesday, 25 March 2008 18:22:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:37 GMT