John,
Thanks for your detailed feedback.
-17 does support an all-ASCII email address if a non-ASCII email is provided,
but during a transition period that is up to server policy. There is no way
for the extension to forecast the support for SMTPUTF8 globally. The
complexity and the need fo
James,
I believe I've said most of what I'm about to say in early
November or even earlier, but it looks like that several of
those notes didn't go to the WG list much less the Last Call
one. So, since you asked, let me try once more. In the
process, let me try a slightly different perspective i
Thanks very much. For the record, I agree with your choice of option
2. It would be great if we could hear from others and resolve this
issue.
-andy
On Thu, Jan 26, 2023 at 8:17 AM Gould, James wrote:
>
> Andy,
>
> Sorry for the late response to your message. The updates in -17 were made to
>
Andy,
Sorry for the late response to your message. The updates in -17 were made to
address the feedback from John Klensin during the IETF Last Call, which
included changing the cardinality to the One or Two (ASCII or SMTPUTF8) Option
defined in the IETF-115 presented deck
(https://datatracker
Hi all,
I was looking at the diffs between -16 and -17 of the EAI drafts, and
the draft looks to have doubled in size since being submitted to the
IESG. A lot of the new content are examples (always a good thing), but
there has been some other normative language added. Does that need to
be discuss
