Hmm, this complicates things. If the Email input type were revised in a future spec to match the “standard” RFC definition, it would still disallow some Coremail-assigned email addresses – did I understand this correctly?

From: ua-eai-bounces@icann.org [mailto:ua-eai-bounces@icann.org] On Behalf Of cyt@coremail.cn
Sent: Tuesday, July 25, 2017 3:38 AM
To: HEALTH Yao <yaojk@cnnic.cn>
Cc: john c klensin <john-ietf@jck.com>; ua-eai@icann.org
Subject: Re: [UA-EAI] HTML 5.2 and Internationalized Eamil Addresses

Hi,

Coremail doesn't use email input type. Different versions of the browser, the implementation of the e-mail address of the inspection specifications may be different.

On the other hand, some customers require to use some special characters( may be forbidden by standard RFC) to compose the email address. So we decide to use Text input type and validate the email address by regular expression.

cyt

2017.07.25

-----原始邮件-----
发件人:"Jiankang Yao" <yaojk@cnnic.cn>
发送时间:2017-07-25 14:02:34 (星期二)
收件人: "Mark Svancarek" <marksv@microsoft.com>, "John C Klensin" <john-ietf@jck.com>
抄送: "Jan Nelson" <Jan.Nelson@microsoft.com>, "Nalini Elkins" <nalini.elkins@insidethestack.com>, "uki Ho" <ylhe@coremail.cn>, "ua-eai@icann.org" <ua-eai@icann.org>, "Shawn Steele" <Shawn.Steele@microsoft.com>, "Harish Chowdhary" <harish@nixi.in>
主题: Re: [UA-EAI] HTML 5.2 and Internationalized Eamil Addresses

From: Mark Svancarek

Date: 2017-07-25 08:22

To: John C Klensin

CC: Jiankang; Hollander Don; Nalini J Elkins; HEALTH Yao; Marvin Cheng; uki Ho; Harish Chowdhary; Dr. AJAY D A T A; ua-eai@icann.org; Jan Nelson; Shawn Steele; Stuart Stuple

Subject: RE: HTML 5.2 and Internationalized Eamil Addresses

>But I don't understand why one would resist changing a spec which is known to be "wrong" and non-RFC compliant. Is the argument that revising it to be RFC-compliant would risk destabilizing more sites than fixing it?

>

+1

I share the same concern with you.

Jiankang Yao