ISSUE-96: Allowing for EAI
Allowing for EAI
- State:
- CLOSED
- Product:
- html
- Raised by:
- Addison Phillips
- Opened on:
- 2011-07-22
- Description:
- 4.10.7.1.5 E-mail state
http://dev.w3.org/html5/spec/single-page.html#e-mail-state-type-email
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?
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11579 - Related Actions Items:
- No related actions
- Related emails:
- [minutes] Internationalization telecon 2017-05-25 (from ishida@w3.org on 2017-05-25)
- Review of tracker issues for best practices (Part III) (from addison@lab126.com on 2015-03-30)
- Re: [I18N-ACTION-150] Review of HTML open issues (from ishida@w3.org on 2014-02-21)
- [I18N-ACTION-150] Review of HTML open issues (from addison@lab126.com on 2014-02-18)
- [minutes] Internationalization WG telecon 2011-07-27 (from ishida@w3.org on 2011-07-27)
- I18N-ISSUE-96: Allowing for EAI [HTML5-prep] (from sysbot+tracker@w3.org on 2011-07-22)
Related notes:
[aphillip]: add this issue to HTML5 bug 11579
27 Jul 2011, 16:44:58There 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:12potentially close, see telecon notes
Addison Phillips, 28 Mar 2012, 15:38:36checking bug 11579 and moving to active comment.
Hixie closed 11579 as WONTFIX because he claims that the spec allows IDNs.
added bug link.
Addison Phillips, 18 Feb 2014, 18:37:52Display change log
