Charles Lindsey wrote:
In <20030208025028(_dot_)42420(_dot_)qmail(_at_)cr(_dot_)yp(_dot_)to> "D. J.
Bernstein" <djb(_at_)cr(_dot_)yp(_dot_)to> writes:
Keith Moore writes:
The burden on those who want to see raw utf-8 in message headers is to
convincingly demonstrate how to make it work well, without breaking the
installed base.
It works just like other mandatory protocol extensions. Readers are
upgraded to support the extended format; once that's complete, writers
can safely use the format. Examples:
It is even easier than that. For a charset change, they just have to wait
until people who are interested in that charset have changed.
Provided the charset is properly tagged and the content properly encoded.
But that's besides the point. Dan Berstein's point about the process
is valid -- but is not what the current Usefor draft proposes. That
draft proposes writers generating an "extended" (a.k.a. illegal)
format *before* all of the installed base of readers (gateways, etc.)
are prepared for it.
Anyway, here is a wicked thought.
<hare-brained scheme which is non-compliant with 822/2822 and MIME snipped>