编辑: 学冬欧巴么么哒 | 2019-07-08 |
2002 Members of the IDN Committee Vincent Wen-Sung CHEN 陈文生 (TWNIC)Mouhamet DIOP (ICANN Address Council Observer, ICANN Director elect)Patrik F?LTSTR?M (IETF/IESG)Qiheng HU 胡启恒 (Internet Society of China)Masanobu KATOH 加藤 干之 (かとう まさのぶ)Committee Chair, ICANN Director) John KLENSIN (Former IAB Chair) Sang-Hyon KYONG ? ? ? (景商铉)ICANN Director)Stuart LYNN (ICANN President)Elisabeth PORTENEUVE El?bieta PORTENEUVE (ICANN Names Council)Mohd Sharil TARMIZI ?????? ????? ????(GAC Vice Chair) Administrative support was provided by:David G THOMPSON Andrew J McLAUGHLIN ICANN IDN Activities Timeline March 2001- Creation of ICANN Board IDN Working Group (Melbourne) June 2001- IDN Working Group Status Report (Stockholm)September 2001- IDN Working Group Final Report (Montevideo)September 2001- Creation of IDN Committee (Montevideo) June 2002- Final Proceeding Report of IDN Committee (Bucharest)June 2002- Extension of IDN Committee until Shanghai (Bucharest) Key Issues Considered before Bucharest IDN.
IDN KeywordsPermissible Code PointsNon ASCII TLDsRegistrar Selection ProcessUDRP Review The Permissible Code Point Issue By 'permissible code point' issues, we refer to the problems that might arise from the use of certain non-ASCII characters included in the Unicode Standard within IDN domain name labels. At present, the DNS host name specifications limit permissible code points in domain name labels to a restricted subset of 7-bit ASCII.In addition to the characters of every language that could be identified and standardized by the Unicode Consortium, the Unicode Standard contains several sets of "characters" that do not, in fact, appear in any conventional human language. The Permissible Code Point Issue (2) The IDN Committee has communicated a recommendation to the IETF that it should proceed conservatively, using an "inclusion-based" approach to the definition of "Internationalized Hostnames", so as to leave out C at least temporarily C the sets of potentially problematic characters, most notably: - line and symbol-drawing characters;
- symbols and icons that are neither alphabetic nor ideographic language characters, such as typographical dingbats;
- punctuation characters;
and - spacing characters.These comments were submitted for IESG review IETF (IESG) approval of Internet-Drafts, Oct. 24,
2002 Internationalizing Domain Names In Applications (IDNA)draft-ietf-idn-idna-14.txt> as a Proposed Standard. Nameprep: A Stringprep Profile for Internationalized Domain Names Punycode: An encoding of Unicode for use with IDNA Issues for Further Consideration Permissible Code Point Issue C e.g. CJK (Chinese-Japanese-Korean) issue -- Registration and Administrative Guidelines (?)Second-level IDNA Implementation C Need to slow down (?)Whether and when to proceed and adopt non-ASCII TLDs C Need to wait and see (?)Need dialogue and coordination among registries doing SLD/IDN implementation? User Interface Issues (?) Recommendations Public Awareness and EducationContinue ICANN IDN Committee C (1) to serve as a general coordination body for the work on policy issues, and (2) to advise the Board as needed in the area of IDN