IDN aware application implementation guideline
draft-yoneya-idn-app-guideline-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yoshiro Yoneya | ||
| Last updated | 2005-02-23 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Since IDN Standards [RFC3490-3492] were published, some of gTLDs and ccTLDs began IDN registration and resolution service. Furthermore, many major Web browsers became IDN aware. IDNs seem to be popularized soon. Meanwhile, IDN introduces huge number of characters which can represent domain name, so it increases human misreading of domain name with similar looking characters. This issue was discussed deeply during IDN standardization and service development, and as a result, JET Guideline [RFC3743] and ICANN IDN Guideline [ICANN-IDN] was published. Even if TLD registries comply such guidelines, bad-faith guys may use IDNs to deceive human eyes with similar looking characters. To protect users from such deceiver, implementation guideline for how to handle IDNs at the User Interface level is important. This document is intended to be such guideline for application implementers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)