Re: I-D ACTION:draft-hoffman-utf8headers-00.txt

> Er, any comments at all?

there's no justification given for utf-8 headers.  the desired 
functionality can be accomplished by the address-map fields and 
encoding the fields in ascii.

there's no explanation as to where the address-map information would be 
obtained.

there's no cost analysis for a proposal which would appear to have a 
huge cost.  of course this is just a -00 version, but it's hard to 
evaluate the desirability of this proposal without considering the cost 
fairly quickly.

even accepting that it's a good idea to allow email addresses in raw 
utf-8 (and this is a stretch) many fields should remain ascii so that 
they can be read anywhere.  it will often make more sense to put 
ascii-encoded addresses, message-ids, etc. into log files than to put 
raw utf-8 there.

there are too many mail transport boundaries that don't use SMTP and 
thus may have no way to negotiate utf-8.

whether email addresses are in raw utf-8 or encoded in ascii there is 
still a need to define how they are compared, because there will often 
be more than one utf-8 representation of an address.

nit: the document repeatedly says that non-ASCII text is encoded in 
quoted-printable; this is incorrect.  RFC 2047 allows either a variant 
of quoted-printable ("Q" encoding, which isn't quite the same thing) or 
base64 ("B" encoding).