1 / 43

Evolution of Multilingual Domain Name

Evolution of Multilingual Domain Name. Kenny Huang huangk@alum.sinica.edu. Technology Perspective. Making the Internet International. Human factors. People would like to name themselves and their objects in their own language ISO 10646+UNICODE is a necessary answer, but not sufficient

penha
Download Presentation

Evolution of Multilingual Domain Name

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Evolution of Multilingual Domain Name Kenny Huang huangk@alum.sinica.edu

  2. Technology Perspective Making the Internet International

  3. Human factors • People would like to name themselves and their objects in their own language • ISO 10646+UNICODE is a necessary answer, but not sufficient • DNS has some shortcomings as well

  4. Deployment Issues • Objectives of Internationalizing Protocols • Deploying parallel name spaces • Deploying parallel communication spaces

  5. Objectives of Internationalizing Protocols • Many protocols internationalized: • SMTP, HTML, etc • Domain Name Service foundational • and therefore has earthquake effects if changed without thinking clearly

  6. Deploying parallel name spaces • Simple to do - • Deploy many DNS roots with different name spaces • Effect: • People using one cannot find people in another • Commerce diminished • Mail exchange impeded, etc

  7. Correctness issues • Many servers running Bind • Often as old as version 4 • Incompatible upgrades cause other systems to fail • Software reliability is one of the big issues, and this is a key component

  8. IETF Standardization Report Design Team Protocol for Application Area NamePrep : Global Name Processing Selection of ACE New WG: Provision Registration Protocol that enables a Registrar to access multiple Registries IETF focuses mainly on Global Standards.

  9. IETF Comments • Application-based solution will be adequate • Directory service • Partial, local matching rule is needed

  10. ASCII (ACE) or non ASCII MDN • The MDN solutions can be very extreme, there is no intermediate solution • ACE has short-term benefit but has long-term penalty • 8bit clean technique introduces system vulnerability ?

  11. Policy Perspective Delegation and Deployment

  12. Who Own and Control the Internet? • Domain Names(gTLD, ccTLD) • IP Address • Protocol Parameter • Root Server • BIND

  13. ICANN ICANN (Formally IANA) Govt. Advisory Committee DNS Root Server TLDs: gTLD/ccTLD ARIN,RIPE APNIC IETF/IAB

  14. What ICANN does • To Coordinate the unique assignment of • Three values that are essential to the • Proper functioning of the Internet • - Domain Names • - IP addresses • - Protocol port and parameter numbers

  15. What ICANN does not do • Content Control • Network Security • Data Privacy Protection • Setting multilingual name standards • Multilingual Internet interoperability

  16. ICANN’s Responses • 2000. 3 Cairo • 2000. 6 Yokohama • ASCII, Internet Language • 2000. 11Marina del Rey • To host Internationalized Domain Names Workshop • 2001. 3 Melbourne • To discuss Internationalized DN in the public forum

  17. MINC • Coordination of R&D on multilingual names • Coordination on deployment of multilingual names • Coordination with the relevant organizations i.e. IETF, W3C, ICANN, ISOC, Unicode, IEEE, ISO and ITU • Coordination for standards development

  18. Issues of Interoperability • Tower of Babel – Babelisation of Internet has taken place. • “Islands” of the Internet should be prevented i.e. which should not fragment the network with multiple non-interoperable standards • Asia Pacific Taskforce on internationalising Domain Names set up • Internet Engineering Task Force urgently set up IDN Working Group

  19. Several Multilingual Domain Names Testbeds emergent • Industry driving this • NSI (Verisign) and partner companies setting up multilingual.com services testbed • JPNIC, KRNIC launching production level testbeds for japanese.jp and korean.kr • CNNIC, TWNIC, HKNIC, MONIC forms CDNC - in progress • ICANN defers to IETF’s progress in IDN before making any decisions – need to keep pace with Internet speed of developments.

  20. MINC’s Role • MINC will coordinate the Interoperability Testing as a whole. • MINC will commission the Interoperability Testing Working Group to manage the Testing. • MINC will operate the testing using a self-financing cost-recovering model.

  21. What is JET? • Joint Engineer Team for developing • Open Multilingual Domain Name System • for ICANN TLDs. • Core members are CNNIC, JPNIC, KRNIC and TWNIC. • ISC, IETF co-chair and VeriSign GRS are invited. • Business status & plan are exchanged for the better service introduction.

  22. JET meetings & Discussions 1st : July 15 2000 (Yokohama) Local charset or ACE 2nd : Aug 28-30 2000 (Beijing) Common mDNS 3rd : Nov. 29-30 2000 (Taipei) Global/Localized components 4th : Feb. 28 – Mar 1 2001 (Kuala Lumpur) IETF Standardization & Localization 5th : June 25-26 2001 (Shanghai)

  23. Open Source Code TWNIC mDNS with 8-bit clean BIND 8-bit clean Squid proxy/Apache web server JPNIC mDNkit To be fully compatible with IETF standards Core library for processing mDN Code conversion between local charset and ACEs Normalization Tools for code conversion mdnconv, dnsproxy, runmdn, mDN Wrapper BIND 8 & 9 Patches

  24. Meeting in Kuala Lumpur Information exchange on the business Service menu & schedule System development Reserved words DRP IETF Standardization Report JPNIC’s mDNkit Plan Localization Test bed

  25. Unicode-to-ACE Conversion NAMEPREP domain name in local codeset domain name in ACE Big Picture Local-to-Unicode Conversion Localization= National Standards? Delimiter Mapping Local Mapping based on TLD Global Standards

  26. CDNC • Members : TWNIC, CNNIC, HKNIC, MONIC • Development • multilingual domain name system • system interoperability • Information Sharing • Multilingual ccTLDs, gTLDs trial operation

  27. CDNC Experience • Strong momentum from official registries • First organization introduce multiple root systems model (chain table) and multilingual ccTLDs, gTLDs • Normalization • Simplified Chinese Characters vs. traditional Chinese Characters

  28. From Isolation into Harmonization Who has been isolated? Who will be isolated? Multilingual Domain Names encourage 1) non-native English speakers to the NET 2) native English speakers to diverse culture

  29. Connectivity(Usability) • How can we learn all the different character sets? • How can we communicate globally in Chinese/Arabic/…. domain names? There might be scope for creating generic SLDs with the same meaning in multi-languages that would point to the same database of names.

  30. Policy Function Players • Local Internet Communities • ccTLD registries • Governments • Other relevant international bodies

  31. Issues Registry and Registrar Model Standard Requirements Who Controls Database? Pre-registrations How to bridge the gap? Start-up Domain Dispute Resolution Policy

  32. Registry and Registrar Model • ICANN accredited registrars? • Any other models?

  33. Standard Requirements • Minimum and maximum length of names • Excluded characters, codes, abbreviations and words • CNNIC • JPNIC • KRNIC • AENIC? • ……… • ………

  34. Second Level Domains • Direct registration in the 2nd level • .com, .org, .net • Some European ccTLDs • Asian ccTLDs? • Generic Second Level Domains

  35. Who Controls Database? • .COM: NSI, ICANN(US DoC) • .EU: Within the EU, ICANN(US DoC) • .JP: JPNIC, ICANN(US DoC) • .中文.tw: .TW registry, ICANN(US DoC) • .中文: Registry, ICANN, ??? • .中文.台灣: .台灣Registry, ICANN, ???

  36. Pre-registrations • What’s pre-registration? • Not legal but Marketing Concept? • How can we protect registrants? • Market decides….

  37. How to bridge the gap between the standard track in IETF and the market demands? • Multilingual.COM • Multilingual.tw • Multilingual.multilingual

  38. Domain Names in the Market(I) Case 1 ASCII & gTLD & NSI ACER.COM Case 2 Non-ASCII & gTLD &NSI 宏碁.COM Case 3 Non-ASCII & gTLD & non-NSI 宏碁.公司

  39. Domain Names in the Market(II) Case 4: ASCII & ccTLD & ccTLD registry acer.com.tw Case 5: Name-Non-ASCII Only & ccTLD 宏碁.tw 宏碁. 公司.tw Case 6: Full-Non-ASCII & ccTLD 宏碁.公司.台灣

  40. Start-up • Requiring “waiting or challenging” period • Requiring submission of proof of ownership • Multiple registration discouraged • Round-robin among registrars

  41. Legal EnforcementLaw and Jurisdiction • National sovereignty • Globally standardized community • Strong market drive • Flexible adaptation • Binding Force

  42. Multilingual DN Next Step • IETF standardization • standards, not solutions • ICANN still keep monitoring, without privileged control of root systems • Many testbeds still exist • Strong demands for mgTLDs, mccTLDs

  43. Other Issues • Reserved/Priority words • DRP • Ripple effect • ISO3166 creation: 20 years • new TLD creation: several months • Will some ISO standards be vanished ?

More Related