Specifically, instead of the familiar
From: personal name <user@domain>
header lines, we will now see
From: personal name <uuser@udomain <auser@adomain>>
where uuser@udomain is in UTF-8 and auser@adomain is in ASCII.
The reason for this incompatible change is...compatibility! This is so an
SMTP server can "downgrade" the UTF-8 headers to ASCII on a system that
does not support UTF-8 headers. The purported precedent is 8-bit SMTP and
allowing 8BIT Content-Transfer-Encoding with SMTP downgrade to 7-bit and
BASE64/QUOTED-PRINTABLE.
We all know how well SMTP downgrade for 8-bit worked, and especially how
well it prevented leakage. NOT. But that was just a case of having to
tolerate high order bits being set, and relatively few programs and
environments had problems with that.
This is different. MUA developers need to be on the alert for this new
address format NOW, because "experimental" or not, we ARE going to start
seeing these.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
At least there these will leak.
That is area where IETF is not traditionally intrested.
> From: personal name <uuser@udomain <auser@adomain>>
> where uuser@udomain is in UTF-8 and auser@adomain is in ASCII.
For those looking for links, there are drafts at
http://www.ietf.org/html.charters/eai-charter.html and the particular
draft mentioned by Mark is
http://www.ietf.org/internet-drafts/draft-ietf-eai-utf8headers-10.txt
Regards,
David.