Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain that we are using UTS #46 for IDNA support rather than IDNA2008 directly #498

Closed
TimothyGu opened this issue May 6, 2020 · 0 comments · Fixed by #722
Closed
Labels
clarification Standard could be clearer editorial Changes that do not affect how the standard is understood

Comments

@TimothyGu
Copy link
Member

It seems like quite a few people have been thinking that we use IDNA2008 or 2003 directly, but we actually do not. The motivation for using UTS 46 rather than either IDNA versions is pretty clearly stated in the document itself:

A system was introduced in 2003 for internationalized domain names (IDN). This system is called Internationalizing Domain Names for Applications, or IDNA2003 for short. … A revision of IDNA was approved in 2010 (IDNA2008). This revision has a number of incompatibilities with IDNA2003.

The incompatibilities force implementers of client software, such as browsers and emailers, to face difficult choices during the transition period as registries shift from IDNA2003 to IDNA2008. This document specifies a mechanism that minimizes the impact of this transition for client software, allowing client software to access domains that are valid under either system.

So we probably don't need to explain why UTS 46 is used. However, it might be good to make it clear in the spec that we are using UTS 46, perhaps as an introduction paragraph in https://url.spec.whatwg.org/#idna.

@TimothyGu TimothyGu added clarification Standard could be clearer editorial Changes that do not affect how the standard is understood labels May 6, 2020
annevk added a commit that referenced this issue Dec 9, 2022
annevk added a commit that referenced this issue Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer editorial Changes that do not affect how the standard is understood
Development

Successfully merging a pull request may close this issue.

1 participant