W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 11579] Support for IDNs in e-mail addresses should be "should" or "must", not just "may"

From: <bugzilla@jessica.w3.org>
Date: Mon, 11 Jul 2011 14:12:47 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QgHE7-0006eV-27@jessica.w3.org>

Mounir Lamouri <mounir.lamouri@gmail.com> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #12 from Mounir Lamouri <mounir.lamouri@gmail.com> 2011-07-11 14:12:44 UTC ---
(In reply to comment #10)
> Isn't e-mail (SMTP) one of the systems that doesn't handle IDN yet? I assumed
> it was, which is why I didn't allow IDN to go to the server. If it's not I'm
> happy to change it. File another bug for that with evidence that typical
> servers won't be screwed up if they na´vely pass IDN to their mail subsystems.

I do not think this is a good reason to not submit UTF-8 email addresses.
Currently, websites using <input type='text'> get UTF-8 e-mail addresses so
they obviously know how to handle them. If they want a client-side check, the
pattern attribute would do the job. In addition, it looks like there is some
work around a standard for internationalized email addresses [1].

I think the specifications should just make clear that UTF-8 e-mail addresses
should be validated. Whether by requesting them to be puny-encoded before the
validation or by extending the ABNF used for validation to include UTF-8
characters (like in [1]).

[1] http://tools.ietf.org/html/rfc5335#section-4.1

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 11 July 2011 14:12:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:55 UTC