ISSUE-286: Standardizing on IDNA 2003 in the URL Standard ⓣ
Standardizing on IDNA 2003 in the URL Standard ⓣ
- State:
- CLOSED
- Product:
- url
- Raised by:
- Richard Ishida
- Opened on:
- 2013-08-20
- Description:
- Thread start: http://lists.w3.org/Archives/Public/public-iri/2013Aug/0000.html
By: Anne van Kesteren
[[
http://lists.w3.org/Archives/Public/www-archive/2013Aug/0008.html
might be of interest to readers of these lists.
]]
Here are the contents of that email:
[[
Hey hey,
So one part that's missing in http://url.spec.whatwg.org/ is domain
names. As far as I can tell no browser has moved beyond IDNA 2003
(Opera "regressed" when it adopted Chromium) other than updating their
Unicode implementation and nobody is interested in implementing IDNA
2008 (whatever that means, it doesn't exactly define it all the way
from code points in an unparsed URL to host bytes).
Given that, my plan is to put that in the specification. IDNA 2003,
its label separators, the Unicode normalization it uses (but without
restrictions to a particular Unicode version), ...
Some registrars have moved to IDNA 2008, but this creates security
issues as pointed out in http://unicode.org/reports/tr46/ and people
are unlikely to register names that do not work. I suspect long term
the IETF will have to revisit this, but in the mean time it would be
good to have accurate documentation for how we want everything around
URLs to work.
If there's anything I'm missing here, I'd love to hear about it. If
you want more background reading, I wrote this after doing some
research last year: http://annevankesteren.nl/2012/11/idna-hell
Kind regards,
]]
- Related Actions Items:
- No related actions
- Related emails:
- I18N-ISSUE-286: Standardizing on IDNA 2003 in the URL Standard [..track-me] (from sysbot+tracker@w3.org on 2013-08-20)
Related notes:
https://github.com/w3c/i18n-activity/issues/57
Richard Ishida, 17 Mar 2016, 13:23:18Display change log