From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Thu Nov 07 2002 - 05:23:49 CST
In <p0510030ab9ed7c1226d6@[192.168.100.103]> Jacob Palme <jpalme@dsv.su.se> writes:
>At 15:58 +0100 02-10-10, Charles Lindsey wrote:
>>2. If someone is writing a standards-track document (whether for news or
>>email) and wishes to introduce some new header-fields that can make use
>>of RFC 2047, what does he have to say?
>Note that the MHTML standard, RFC 2557, says that RFC2047
>should be used for encoding of URIs in Content-Location
>headers.
Hmmmm! I have looked at that RFC, and it says "use RFC 2047" but does not
really explain how sections 5 and 6 of RFC 2047 are to be satisfied (i.e.
it is asking you to use the RFC 2047 encoding on an object that is neither
a 'phrase' nor a 'comment' nor a '*text'). But I don't suppose that will
stop it from working :-) .
I think the wording I put in our draft to deal with RFC 2047 is now as
robust as it is possible to be, provided we don't try to do anyting funny
with User-Agent. Since noone has responed further on that issue, I propose
to include my 'safe' solution to that problem, which is to say that
product tokens are pure ASCII, and if you want to explain your product
more fully in your own language, then you put it in a comment.
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl Email: chl@clw.cs.man.ac.uk Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K. PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5