[Top] [All Lists]

Re: [ietf-822] Encoding (Re: 😟 Re: Fwd: New Version Notification for draft-crocker-inreply-react-00.txt)

2020-10-05 21:29:30
In article <d4b6a868-2db3-ea46-6ffd-627bfc35b25d(_at_)dcrocker(_dot_)net>,
Dave Crocker  <dcrocker(_at_)bbiw(_dot_)net> wrote:

To be fair, when I saw the lack of any specified encoding

As a few postings have demonstrated with emoticons in this thread, it's 
clear that at least some MUAs (or MSAs or MTAs?) are already able to 
take 'raw' Unicode and pass it successfully to recipient MUAs.

That's a UTF8SMTP aka EAI feature. They're only supposed to do that
for recipients that advertise UTF8SMTP as an EHLO option but having
just done a bunch of EAI compliance tests I can tell you that they're
pretty sloppy about when they do.

Still since there's been concern about encoding raised, I'll ask for 
suggested text to include in the draft.

Make it a MIME word with the usual base64 or QP encoding, like the
subject line of the message you just sent. As far as I can tell, only
Unicode has an interesting repertoire of emoji so you could say that
they must be encoded UTF-8.

John Levine, johnl(_at_)taugh(_dot_)com, Primary Perpetrator of "The Internet 
for Dummies",
Please consider the environment before reading this e-mail.

ietf-822 mailing list