Here’s the applicable portion of the spec:

https://w3c.github.io/html/sec-forms.html#valid-e-mail-address

The assumption is that all local parts are ASCII letters-digits and that IDNs in the domain part should be expressed in punycode.  This is of course doubly broken, because humans can’t really use punycode.

Fixing the local part is a good start and I encourage it.  But if the domain name part continues to prohibit Unicode, it won’t actually help anyone.

Is the plan is to fix the local part in v5.2 now and fix the domain name part in v5.3?

From: UA-discuss [mailto:ua-discuss-bounces@icann.org] On Behalf Of Dr. Ajay Data
Sent: Sunday, November 12, 2017 9:08 PM
To: chaals@yandex.ru; ua-discuss@icann.org
Subject: Re: [UA-discuss] Progress on HTML and email...

This is good initiative. I have few queries challs.

1. After @ , are you not checking / validating. What's the plan.?
2. Any specific reason, team decided to consider for before @ only.

Thanks.

AD

On 12 November 2017 08:43:54 GMT+05:30, Chaals McCathie Nevile <chaals@yandex.ru> wrote:

Hi,

just to note that this week we reached a provisional agreement to change  
the HTML email input type, and make it accept a unicode value before the  
"@" instead of the current restriction to ASCII. Once we get this change  
made and published - hopefully in a few weeks - we would appreciate help  
encouraging browsers to implement it fast.

cheers

chaals

--
Sent from my Android device with XGenPlus.