PROPOSAL: i74: Encoding for non-ASCII headers

• From: Mark Nottingham <mnot@mnot.net>
• Date: Tue, 25 Mar 2008 22:06:09 +1100
• To: HTTP Working Group <ietf-http-wg@w3.org>
• Message-Id: <5682A9EB-7005-4E8A-AFA0-FB9D45F35C40@mnot.net>

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.




--
Mark Nottingham     http://www.mnot.net/

Received on Tuesday, 25 March 2008 11:06:57 UTC