ISSUE-96: Allowing for EAI

Allowing for EAI

Raised by:
Addison Phillips
Opened on:
Description: E-mail state

The email address validation scheme quotes ABNF from RFC 5322 and doesn't appear to allow addresses that are IDNA. While EAI is kinda slow moving, shouldn't HTML5 allow for it?
Related Actions Items:
No related actions
Related emails:
  1. [minutes] Internationalization telecon 2017-05-25 (from on 2017-05-25)
  2. Review of tracker issues for best practices (Part III) (from on 2015-03-30)
  3. Re: [I18N-ACTION-150] Review of HTML open issues (from on 2014-02-21)
  4. [I18N-ACTION-150] Review of HTML open issues (from on 2014-02-18)
  5. [minutes] Internationalization WG telecon 2011-07-27 (from on 2011-07-27)
  6. I18N-ISSUE-96: Allowing for EAI [HTML5-prep] (from on 2011-07-22)

Related notes:

[aphillip]: add this issue to HTML5 bug 11579

27 Jul 2011, 16:44:58

There is a note in this section that "user agents should convert punycode in the value to IDN in the display and vice versa", and if they do the "vice versa" before any validation, we're probably fine. For the mailbox part of the email address, we can't say anything because EAI seems abandoned.

Norbert Lindenberg, 21 Mar 2012, 05:36:12

potentially close, see telecon notes

Addison Phillips, 28 Mar 2012, 15:38:36

checking bug 11579 and moving to active comment.

Hixie closed 11579 as WONTFIX because he claims that the spec allows IDNs.

Addison Phillips, 18 Jul 2013, 01:13:47

added bug link.

Addison Phillips, 18 Feb 2014, 18:37:52

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $