I think John's point is that if you have xn--...@IDN the part before the @ will never go through ACE conversion. It is not treated as Punycode, because in that part of an email address you can have ASCII, or Unicode, but there is no standard that suggests you might put punycode there so you should not try to decode stuff as if someone did. cheers On Fri, 29 Dec 2017 07:00:26 +0100, Dr Ajay Data <ajay@data.in> wrote:

Lets discuss in detail when we are there in HK/China.

However, What if someone create local part email ID which starts >with xn--@idn , where xn-- is not punycode just a ascii string, >obviously ACE conversion will FAIL, that was the primary reason >that punycode in local is not recommended.

Thanks. Dr. Ajay DATA | Founder & CEOGet email id like अजय@डाटा.भारत in your own language, visit www.xgenplus.comFrom: "John R. Levine" <johnl@iecc.com> MailId : [76766077] To: "Ajay Data" <ajay@data.in> Cc: marksv@microsoft.com,"Don Hollander"

...

<don.hollander@icann.org>,ua-eai@icann.org Subject: Re: [UA-EAI] EAI Evaluation Widget Date: 29 Dec 2017 04:50:06 AM Should be warninf.. punycode@punycode obviously not required/

...

allowed..

punycode@punycode is certainly allowed, but the "punycode" in the >local part is an ASCII local part that starts xn--..., not coded UTF-8.

By the way, if people use this very much I expect you`ll find that >sites start to block you, because the address tests it`s doing look just >like the tests that spammers do to try to wash spamtraps out of their

...

purchasedlists.

Moral: spammers ruin things for everyone.

R`s from the train, John .

Do not Remove: [HID]20171229045003896[-HID]

-- Chaals is Charles McCathie Nevile find more at http://yandex.com