1 / 30

Multilingual Domain Name

Multilingual Domain Name. 22 Feb 2001 YONEYA, Yoshiro <yone@nic.ad.jp> JPNIC IDN-TF. What is MDN?. M ultilingual D omain N ame. Current domain name is represented with ASCII alpha-numeric and hyphen characters. Multilingualization of Domain Name is,

sibley
Download Presentation

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. Multilingual Domain Name 22 Feb 2001 YONEYA, Yoshiro <yone@nic.ad.jp> JPNIC IDN-TF

  2. What is MDN? • Multilingual Domain Name. • Current domain name is represented with ASCII alpha-numeric and hyphen characters. • Multilingualization of Domain Name is, • Technical challenge to represent domain name with not only ASCII but also NON-ASCII characters. • Almost equivalent to Internationalization of domain name. IWS2001

  3. What is IDN? • Internationalized Domain Name. • Framework to multilingualize domain name. • Need to be a Global Standard. • IETF IDN (Internationalized Domain Name) WG is doing the work. • Some confusion by using the word ‘Internationalized’. IWS2001

  4. Why MDN? • Increase of the Internet users who are not familiar with English. • Easy to memorize, type in, etc. • Drastic change of usage of domain name. • Domain name is now used as not only host name but also signboard. • Creates new business opportunities. • Many ventures began services. IWS2001

  5. Drawback of MDN • Actually, it is localization. • Loses global acceptability. • Hard to type in or display without appropriate I/O devices. • Cause impact to the operation. • Requires software update and / or additional processing. • Deployment issue. IWS2001

  6. Standardization trend of MDN • REQUIREMENTS • ACE • NAMEPREP • IDNA IWS2001

  7. Requirements • draft-ietf-idn-requirements-04.txt • Definition of requirements for MDN. • 30 items such as • Interoperability / compatibility with current DNS protocol. • ISO-10646/Unicode for Character set. • Normalization of representation. • Easy to add current domain name space. IWS2001

  8. Requirements • Respect to IAB statement. • RFC2825 • Preservation compatibility with current domain name. • RFC2826 • Preservation of uniqueness of domain name space. • Not to divide the Internet into islands. IWS2001

  9. ACE • ASCII Compatible Encoding. • Represent NON-ASCII characters by ASCII characters. • Easy to apply current DNS. • Minimize impact to current applications. • Decreases maximum characters in each label. • Penalty of using 5bit to represent 8bit data. • Requires some sort of compression algorithm. IWS2001

  10. ACE • Requires explicit ACE-identifier. • For reverse conversion. • Choice of ACE-ID is political issue. • ACE-ID itself is ASCII string, so that if any proposal for ACE-ID is raised, it will be registered as ASCII domain name. • Actually happened at gTLD. • ZLD – Zero Level Domain – such as ‘.I’ is not realistic. IWS2001

  11. ACE • Impact to operation. • Configuration file and zone files should be written in ACE. • Therefore, supporting tools such as editor and / or filter are essential. • Application solution. • Local encoding at user interface. • ACE at network interface. IWS2001

  12. ACE • Proposed ACEs. • RACE (Row-based ACE) draft-ietf-idn-race-03.txt • BRACE (Bi-mode Row-based ACE) draft-ietf-idn-brace-00.txt • LACE (Length-based ACE) draft-ietf-idn-lace-01.txt • DUDE (Differential Unicode Domain Encoding) draft-ietf-idn-dude-00.txt • AMC-ACE-M draft-ietf-idn-amc-ace-m-00.txt IWS2001

  13. Flow of ACE conversion IWS2001

  14. NAMEPREP • Preparation of Internationalized Host Names • draft-ietf-idn-nameprep-02.txt • Normalization of representation of the same string in meaning or displaying. • Character case (upper, lower), compatible characters (Fullwidth, Halfwidth) • Composed characters • Umlaut in German, accent in French, voiced sound in Japanese, etc. IWS2001

  15. NAMEPREP • Processes in NAMEPREP • map • Case folding of upper/lower characters (UTR#21) • normalize • Normalize representation of string (UTR#15) • prohibit • Check out inappropriate character as domain name. • unassigned • Treatment of unassigned characters IWS2001

  16. IDNA • Internationalizing Host Names in Applications. • Applications do following process. • Character set conversion between local and Unicode. • NAMEPREP. • Character encoding conversion between Unicode and ACE. IWS2001

  17. IDNA • Requires adaptation of Application programs. • Alternatives are, • Adaptation at resolver. • IDNRA – Internationalized Host Names using Resolvers and Applications • May work well at name resolution, but might not work within application protocol such as SMTP and HTTP. • Adaptation at DNS server. • Requires DNS protocol modification. • Hard to deploy due to back bone system replacement. IWS2001

  18. IDNRA User Local UI Application Internal Representation End system Resolver Resolver API Int’l DNS servers DNS servers Application servers IWS2001

  19. To/From Unicode NAMEPREP To/From ACE IDNA Local User Application UI To/From Unicode NAMEPREP Internal Representation End system To/From ACE Resolver API Int’l DNS servers Application servers IWS2001

  20. What is mDNkit? • Project of JPNIC • Started on Apr 2000 • Multilingual Domain Name evaluationkit • mDNkit-1.x release series • Objectives • Evaluation of the MDN technology • Promoting standardization of MDN • Technical contribution to the Internet community IWS2001

  21. Components of mDNkit • libmdn • Core library for MDN processing • mdnconv • DNS zone / configuration file code converter • dnsproxy • DNS query / response code converter • runmdn / mDN Wrapper • Dynamic link resolver library for UNIX / Windows • BIND 9 patch • MDN enhancements for BIND 9 resolver library IWS2001

  22. Diagram of components Local Encoding (SJIS, EUC…) zone file Legacy client Windows client UNIX client mdnconv Multilingualizedresolver / runmdn mDN wrapper dnsproxy libmdn zone file named named Encoding on DNS Protocol (ACE) IWS2001

  23. mDNkit Position of mDNkit User Local UI Application Internal Representation End system Resolver Resolver API Int’l DNS servers DNS servers Application servers IWS2001

  24. Come to be … New features in mDNkit(work in progress) • Adopting NAMEPREP • Provides local mapping APIs • Provides high-level MDN APIs • Multilingual Domain Name toolkit • mDNkit-2.x release series IWS2001

  25. mDNkit High-level APIs Local Mapping NAMEPREP To/From ACE mDNkit Diagram ofNew features in mDNkit Local User Application UI Local Mapping NAMEPREP Internal Representation End system To/From ACE Resolver Resolver API Int’l DNS servers DNS servers Application servers IWS2001

  26. Localization • Support proposals to be involved in NAMEPREP in the future • Should be discussed at IETF IDN WG • Delimiter mapping • To avoid some harmful behavior • Local mapping • To complement NAMEPREP IWS2001

  27. Delimiter mapping • Characters that IME converts when ‘.’ is typed in • Looks like a domain name, but a single word • Ex. ジェーピーニック。JP (means JPNIC.JP in Japanese) • Web Browser sends query to Search Engine • DNS clients sends query to Root Server! IWS2001

  28. Local mapping • Practically NFKC is sufficient but some exceptions • Depends on mapping table of Unicode and Local charset • Map such exceptions onto suitable ones for NFKC • Ex.1 ‘゛’, ‘゜’ (Voiced and semi-voiced sound mark in Japanese) • Need to map onto combining character • “シ゛ェーヒ゜ーニック”  “ジェーピーニック” • Ex.2 ‘－’ (Full-width Hyphen) • Need to map onto ASCII hyphen IWS2001

  29. APIs ACE Local ACE Local UI APIs Code Converter (Local  UTF-8) UTF-8 UTF-8 Delimiter map Local map NAMEPREP Map Normalize Prohibit Code Converter (UTF-8  ACE) ACE ACE Service Servers IWS2001

  30. References • IETF IDN WG Web page • http://www.i-d-n.net/ • JPNIC IDN Web page • http://www.nic.ad.jp/en/research/idn/ • Unicode Consortium • http://www.unicode.org/ IWS2001

More Related