Public Forum: IDN committee.

Katoh-san, trying to be brief. Members of the committee, time line, Created in March 2001 by board. Permissible code point issue. Try to limit the number of character sets. Current Unicode over inclusive for purpose of domain names. Carefully stud…

Katoh-san, trying to be brief. Members of the committee, time line, Created in March 2001 by board. Permissible code point issue. Try to limit the number of character sets. Current Unicode over inclusive for purpose of domain names. Carefully study symbols, icons etc. which aren’t necessary for domain names, but may create confusion. On October 24, IETF came out with standard. Client-side approach. Client translates non-ascii to ascii. Punycode, nameprep, … Issues remain: Chinese-Japanses-Korean registration and administrative guidelines. More than 68000 characters in Unicode. Just use all of them is a problem: Similar characters, read the same way, mean the same thing, but are expressed at different code points. Potential for much confusion. When implementing IDN, need administration and registration guidelines. More limited character set instead of entire Unicode. Some companies already operade 2nd level IDNs. […] Discussed about non-ASCII top level domain names. Adopt then? When? Need dialogue and coordination among registries. Actual use is not coming yet. Need user interfaces. Suggestions and recommendations from committee: Not much time before IDN is going to be implemented by businesses. Need awareness and education. IDN committee has limited life. Asks board to consider continuation of committee for undefinite time period.