From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Wed Sep 25 2002 - 20:04:48 CDT
In <3D892AAC.7010809@alex.blilly.com> Bruce Lilly <blilly@erols.com> writes:
>> Again, you have sidestepped the issue. Our MIME is defined in 6.21. What
>> do you see in 6.21 that would not interoperate with mail MIME?
>We were discussing MIME-style parameters in non-MIME headers...
>Nevertheless, in 6.21:
>"subject to the revised syntax of parameter"
>"UTF-xtra-chars to appear within quoted-strings"
Exactly. That is the ONLY non-interoperable change we have made in MIME.
And the cure is RFC 2231. User agents will need to be able to generate RFC
2231 in any case. So all we do is to give them the opportunity not to
generate it when the article is for Usenet only, or in the Usenet version
if it is mailed as well. It is for the implementor to choose which
strategy to employ.
>6.21.2.2:
>" The Content-Type "message/rfc822" should be used for the
> encapsulation ...
And that is not a separate problem. It is just a particular manifestation
of the same phenomenon.
-- 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