International Domain Name CommitteeProceedings Report.ppt

1、International Domain Name Committee Proceedings Report,Shanghai, China October, 2002,Creation of IDN Committee Members of the IDN Committee ICANN IDN Activities Timeline Key Issues Considered before Bucharest The IDN.IDN Keyword Issue The Permissible Code Point Issue A Preliminary Framework for non

2、ASCII TLDs A Preliminary Registry Selection Policy IDN UDRP Review IETF (IESG) approval of Internet-Drafts, Oct. 24, 2002 Issues for Further Consideration Recommendations,Table of Contents,Creation of IDN Committee,At the September 10, 2001 meeting in Montevideo, the ICANN Board passed a resolution

3、establishing a new IDN Committee “to serve as a general coordination body for the work on policy issues identified in the IDN Working Group Report and such other policy issues that the IDN Committee shall identify.“,Members of the IDN Committee,Vincent Wen-Sung CHEN 陳文生 (TWNIC) Mouhamet DIOP (ICANN

4、Address Council Observer, ICANN Director elect) Patrik FLTSTRM (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

5、Elbieta 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 (Stockh

6、olm) 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 Keyw

7、ords Permissible Code Points Non ASCII TLDs Registrar Selection Process UDRP Review,The IDN.IDN Keyword Issue,The IDN Committee strongly recommends against the introduction of Internet keyword services that utilize the period, or dot (“.“) or Unicode characters that can be mistaken for it, as the se

8、parator between the different name segments.,This recommendation is particularly emphatic in the case of non-ASCII Internet keyword offerings.,The IDN Committee recommends that ICANN and its Domain Name Supporting Organization (particularly the registries and registrars) consider how best to educate

9、 Internet users about the differences between DNS domain names and Internet keywords.,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 labe

10、ls. 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, theUnicode Standard contains several sets of

11、 “characters“ that donot, 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 Hostna

12、mes“, so as to leave out at least temporarily 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 c

13、haracters. These comments were submitted for IESG review,A Preliminary Framework for non ASCII TLD - Introductory Comments,A comprehensive selection and implementation process for non-ASCII TLDs would include a number of steps, including: - Finalization of IDNA standard; - The decision whether and w

14、hen to proceed and adopt non-ASCII TLDs - Root zone implementation testing; - Selection of registry operators; and - Registry-level testing and deployment. The focus of the next three slides is a preliminary selection framework for non-ASCII TLDs themselves.,A Preliminary Framework for non ASCII TLD

15、s Brief Explanation of the Six Categories,Semantic association with Geographic UnitsA TLD string that to a typical reader would be clearly linked to recognized geographic unit, as is the case with the existing ASCII ccTLDs.,2. Semantic association with LanguagesA TLD string that to a typical reader

16、would be clearly linked to the name of a language. For example, the Arabic word for “Arabic.“,3. Semantic association with Cultural Groups or EthnicitiesA TLD string that to a typical reader would be clearly linked to a cultural group or ethnicity that is not defined by recognized national boundarie

17、s. For example, the Kurdish or Swahili peoples.,A Preliminary Framework for non ASCII TLDs Brief Explanation of the Six Categories (2),Everything elseIn this category, we mean to include every word, abbreviation or other string that is not semantically associated with one of the previous five catego

18、ries.,Semantic association with Existing Unsponsored TLDsA non-ASCII TLD string that to a typical reader would be clearly linked to the existing unsponsored ASCII gTLDs, such as .com, .net, .org, .info, .biz, or .name.,4. Semantic association with Existing Sponsored TLDsA non-ASCII TLD string that t

19、o a typical reader would be clearly linked to an existing ASCII sponsored TLD.,A Preliminary Framework for non ASCII TLDs Summary Diagrammatic View,Preliminary Potential non ASCII TLDs,Semantically Associated With Geographic Units,Everything Else,Community Considerations,Baseline Considerations,Prel

20、iminary Registry Selection Process,Technical Competence,Consideration By ICANN Board,UDRP Review,Internationalized domain names is highly likely to dramatically increase the opportunities for cybersquatting.,2. The IDN Committee continues to urge the UDRP Review Working Group to consider IDN issues

21、as it performs its review,IETF (IESG) approval of Internet-Drafts, Oct. 24, 2002,Internationalizing Domain Names In Applications (IDNA) as a Proposed Standard. Nameprep: A Stringprep Profile for Internationalized Domain Names Punycode: An encoding of Unicode for use with IDNA ,Issues for Further Con

22、sideration,Permissible Code Point Issue e.g. CJK (Chinese-Japanese-Korean) issue - Registration and Administrative Guidelines (?) Second-level IDNA Implementation Need to slow down (?) Whether and when to proceed and adopt non-ASCII TLDs Need to wait and see (?) Need dialogue and coordination among

23、registries doing SLD/IDN implementation? User Interface Issues (?),Recommendations,Public Awareness and Education Continue ICANN IDN Committee (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,Thank you very much. Questions?,