# ICANN/ISOC cctld workshop # October 2006 # Sofia, Bulgaria. # implementing IDNs. Andrzej Bartosiewicz

Transcription

1 # ICANN/ISOC cctld workshop # October 2006 # Sofia, Bulgaria # implementing IDNs Andrzej Bartosiewicz andrzejb@nask.pl

2 # schedule for.pl. August the 11 th, 2003: NASK s IETF draft September the 11 th, 2003: (Polish script) for.pl domains only September the 18 th, 2003: (Polish script) for 3rd level domain names under.com.pl.net.pl.org.pl.biz.pl etc NASK has divided IDN implementation (as described above) ) to avoid heavy load on the servers (technical reason only)

3 # schedule for.pl. October 6,, 2003: +German umlauts October 20,, 2003: +Latin November 3, 2003: +Hebrew, Arabic*, Greek ek February 26, 2004: +Cyrylic *) Arabic script domain names registration is currently suspended

4 # IDN implementation ( ) 2005).jp (July 2003).pl (Sep.( 2003) kr (Oct. 2003).se (Oct( Oct. 2003).dk (Jan. 2004).museum (Jan.( 2004).no (Feb( Feb.2004).de (Mar. 2004).br (May( 2005).gr (July 2005).fi (Sept. 2005).cl (Sept. 2005).at (Mar. 2004).ch (Mar.( 2004).lv (2004).at (2004).info (Mar 2004).org (Mar.( 2005)

5 # rules First Come, First Served method no special trademark protection no waiting lists,, no pre-registrations registrations Big Bang (launch at 0400 ZULU TIME) no o sunrise period ACE version only (consistent with RFC 3490 & draft-bartosiewicz bartosiewicz-idn-pltld-04) for input, output, processing xn is the only accepted prefix for ACE domain names no o special rules for ACE domain names no scripts mixing

6 # scripts mixing _1 Since the release of the Cyrillic script, allowed characters have been divided into several sets in order to prevent mixing of characters derived from different scripts. Valid IDN (ACE form), after ToUnicode operation was applied to, must not contain characters being derived from different sets. Such solution eliminates possibilities of mix-script spoofing (see UTR 36). ToUnicode The ToUnicode operation reverses the action of ToASCII. When applied to an ACE label, it takes off the ACE prefix and decodes the string of code points using decoding algorithm in punycode. In result, the obtained label is equivalent internationalized label (Unicode coded). If applied to a sequence of Unicode code points that make up one label, ToUnicode returns an unaltered sequence of Unicode code points. ToUnicode never fails, because it always returns the original string if decoding would fail. In particular, this means that ToUnicode has no effect on a string that does not begin with the ACE prefix.

7 # scripts mixing _2 Nevertheless, this approach do not prevent threat of single-script script spoofing. To address this problem, ASCII-like characters have been selected from the Cyrillic set, i.e.: a (U+0430), e (U+0435), o (U+043E), p (U+0440), c (U+0441), y (U+0443), x (U+0445), s (U+0455), i (U+0456), j (U+0458). Any IDN consisting only from hyphen -,, digits and mentioned above characters has to undergo a check- up before a registration. The ASCII-like characters of the label are mapped to their similar ASCII characters and next received in this way ASCII variant of the Cyrillic IDN is checked against registered or booked domain names in the registry system. If there is no such domain, then the registration process may be continued.

8 # stats New registrations, growing, weekly

9 # stats Months Number of domains

10 # preparations & IDN promotion in.pl

11 # preparations / promotion a study of the subject; test registrations; establishment of a registration policy; preparation of an on-line conversion tool and a registration system; trainings of a contact centre; creation of an IDN WWW sub-service service ( and several presentations to different forums information exchange with journalists (PR activities)

12 # preparations cont. the rules of registering IDN registration under.pl were published (August 2003) at IETF as internet draft all changes in IDN registration rules had been reflected in the subsequent versions of this internet draft allowed scripts has been uploaded into (ICANN) IANA Language Table repository we decided to keep Language Tables up- to-date in ICANN repository as the best source of information for Registrars

13 # (international) presentations CENTR GeneralG Assembly, Administrative and Technical Workshops): 5 presentations in RIPE conferences: 3 presentations in ICANN conferences and GAC meetings: 5 presentations in IETF: 1 presentation

14 # ITU activities as part of international.pl activities active participation in ITU activities: Acting as Rapporteur and Chairman for Question 16 (IDN) of Study Group 17 of ITU-T Promoting ITU-T T activities in RIPE, CENTR and ICANN meetings promoting IDNs (ICANN and IETF standards) among Member States (Governments) in ITU focusing on networkn security risks, use of regional language tables, problems with IDNs adoption worldwide, deployment scenarios etc. facilitation role to promote solutions for multilingual internet based on RFC / ICANN standards FOR MORE INFO GO TO:

15 # ITU activities cont. There is no controversy IMHO between ICANN and ITU in the field of IDNs. ITU is promoting IDNs,, not creating new standards or solutions for IDNs ITU is on our site (IETF RFC based cctld registires

16 # PP and WTSA Resolutions "ITU Plenipotentiary Resolution 102 (Marrakesh( arrakesh, 2002): Management of Internet domain names and addresses "ITU Plenipotentiary Resolution 133 (Marrakesh( Marrakesh, 2002): Role of administrations of Member States in the management of internationalized (multilingual) domain names World Telecommunication Standardization Assembly (WTSA,, 2004) Resolution 48 on "Internationalized Domain Names"

17 # issues covered by ITU-T SG17 Technical background (including IETF, ISO/IEC, ICANN documents) Network security risks Use of regional language tables, Liaison mechanisms with the relevant study groups and appropriate entities Requirements for ITU-T Recommendations (if any), Problems with IDNs adoption worldwide, deployment scenarios etc. Web page open to public dedicated to IDNs hosted by SG17.

18 # types of IDNs

19 # IDN types General: IDN.ASCII IDN.IDN Types of IDN.IDN: Existing cctld Registry is offering IDN.IDN domain names Third party (not cctld) ) is offering IDN.IDN cctld domain names gtld IDN.IDN is offered as "local" implementation of.com/.net/.org/.info

20 # IDN.IDN cont _1 Existing cctld Registry is offering IDN.IDN domain names (examples: China, some Arab States) When ICANN implements IDN at the root level, all cctlds already offering IDN.IDN will be automatically supported Facilitating role, no harm to DNS, Win-win situation.

21 # IDN.IDN cont _2 Third party (not existing cctld manager) is offering IDN.IDN cctld domain names, When ICANN implements IDN at the root level, no clear situation who is IDN-ccTLD Manager, Who lose? Internet users.

22 # IDN.IDN cont _3 Third party (not VeriSign, Afilias, NeuStar ) is offering IDN.IDN gtld domain names Examples:.com/.net/.org version in: Cyrillic script (Regtime.net( Regtime.net) Korean script (Digital Names) Hebrew script (Domain The Net) When ICANN implements IDN at the root level, the problem WHO is the authority over IDN-gTLD arises?

23 # how to promote IDNs (European experience)?

24 # int. experience presentations, meetings press and electronic media join activities between DENIC, NIC.AT and SWITCH (German speaking counties) Registration for free (for limited time): NIC.AT, NIC.SE

25 # before IDN implementations

26 # basic questions to be answered before implementing IDN What characters, scripts or languages ti support? What is the subject of the contract with Registrant? ACE or Unicode form of domain name? Is the registration policy: a script-based one a language-based one Is necessary to associate IDN registered with a language or script tag? With regard to confusable characters issue, did registry implement equivalent domain name registration as a bundle or other solution?

27 # basic questions to be answered before implementing IDN What do your LIC prefers: have a sunrise period or First Come First Served rule. Do you have to establish special UDRP (Uniform Domain Name Dispute Resolution Policy) with regard to implementation of IDN?

28 For more on.pl experience and ITU activities visit: