Since EAI deployment is on the way, gmail, outlok2016, postfix, yandex,
xgenplus and many more have adopted EAI.
In order to make EAI environment more friendly, I suggest that this WG
considers to move this document/work forward.
Best Regards
Jiankang Yao
From: John R. Levine
Date:
On a bit of a side note, I wonder how much appetite there
is for a document update? Besides this, we have no way to
include non-ASCII UTF-8 local parts in i=.
I wrote a draft about it, but I can't say it's gotten a lot of attention
other than from Alexey:
I had formulated the errata as a quick patch, along the
same lines of had been done elsewhere. It’s so good to
feel understood! :)
On a bit of a side note, I wonder how much appetite there
is for a document update? Besides this, we have no way to
include non-ASCII UTF-8 local parts in i=.
..
tl;dr: I agree with the change suggested
Yeah, if we were opening this up, the ABNF could be considerably
clarified. But since we're just patching, one line will have to do.
R's,
John
*) I agree with John that "/" and "=" do not need to be encoded because there’s
no ambiguity if those
tl;dr: I agree with the change suggested
*) I agree with John that "/" and "=" do not need to be encoded because there’s
no ambiguity if those were to be present.
*) I also agree with John that WS is already covered by the production.
*) But ":" DOES need to be encoded for sig-q-tag-method.
*)
