- From: <bugzilla@jessica.w3.org>
- Date: Tue, 15 May 2012 08:37:51 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15489
Martin D <duerst@it.aoyama.ac.jp> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |duerst@it.aoyama.ac.jp
--- Comment #16 from Martin D <duerst@it.aoyama.ac.jp> 2012-05-15 08:37:50 UTC ---
The discussion up to now seems to completely ignore the fact that Internet mail
is moving to UTF-8 throughout, including the left-hand side (LHS), and
including SMTP on the wire. See the work of the IETF EAI WG, in particular
http://tools.ietf.org/html/rfc6530, http://tools.ietf.org/html/rfc6531, and
http://tools.ietf.org/html/rfc6532.
That means that while the U-Label in www.mañana.com, when resolved as a domain
name, has to be converted at some point (as close as possible or inside the
actual resolver library) to an A-Label (punycode), an email address such as
résumés@mañana.com will go to an SMTP submission server AS SUCH, in UTF-8.
[At some point in the relay chain of course an SMTP server will have to look up
MX,... records for mañana.com, and there, a DNS packet will contain
xn--maana-pta rather than mañana, but there is no equivalent of punycode or
A-Label for the LHS whatsoever.]
While this will still take some time for implementation and deployment, and
this is expected to happen faster in some areas of the world than others, it
would be quite smart and helpful if HTML came up with a solution that deals
with non-ASCII in the LHS, too, and that wouldn't look totally antiquated in 5
or 10 years (or maybe even earler; even the infamous Sendmail these days is
8-bit clean, which means that implementing EAI is rather straightforward).
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 15 May 2012 08:38:00 UTC