On Sat, 4 Nov 2006, John Levine wrote:
It's still an open question how Unicode is going to show up in mail
headers, with 8 bit UTF8 being only one of multiple possibilities.
More likely there will be some kludge to smoosh it into 7 bits so it
can transit through old MTAs.
It's much less of an open question than you seem to think. Transmitting
unicode over the current 7bit braindamage is handled with RFC 2047 which
has been around for many years, so your last sentence above is wrong in
its use of the future tense. The only proposed change is to allow raw UTF8
when the MTA advertises the capability.
I don't think anyone is opposed to DKIM handling whatever happens, but I
also don't think it's productive to try to guess at this point which way
it'll turn out.
It just needs to be 8 bit clean.
I think that what the wording should say is that messages must be valid
RFC2822 (or maybe RFC822) messages. This came up in connection with
what to do with messages with bare CR or LF characters, with the answer
being "don't do that".
This implies DKIM cannot be used with 8bitmime or binarymime.
Tony.
--
f.a.n.finch <dot(_at_)dotat(_dot_)at> http://dotat.at/
FORTH TYNE DOGGER: WEST 5 TO 7, OCCASIONALLY GALE 8. MODERATE OR ROUGH. FAIR.
GOOD.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html