Charles Lindsey wrote:
In <3E1C2D8B(_dot_)1080207(_at_)Sonietta(_dot_)blilly(_dot_)com> Bruce Lilly
<blilly(_at_)erols(_dot_)com> writes:
The design defect is in the Usefor draft proposal, which requires
gateways to perform processing which in turn requires header field
syntax to be known, but which is *not* known in all cases, and cannot
be known in advance in the case of experimental header fields.
There are many more pieces of software than Usefor gateways which get
stuck because they do not know the correct way to parse some field. The
design flaw was in RFC 2047 which allowed that situation to be gotten into
in the first place.
RFC 2047 encoded-words should be decoded for diplay only, and non-ASCII
text should always remain in encoded form in header fields. That is
clearly the intent of RFC 2047. The design flaw, as has been already
mentioned, is decoding encoded-words for transmission. In the case of
Usefor, that flaw in the current draft, which does not exist in the
current standard, can be remdied by complying with the Internet text
message format and with the Multipurpose Internet Mail Extensions.