1 / 17

Internationalized Domain Names (IDN)

Internationalized Domain Names (IDN). APAN Busan James Seng jseng@pobox.org.sg former co-chair, IDN Working Group. Internationalized Domain Names. 华人.公司. cn 華人.商業. tw 高島屋.会社 .jp 삼성.회사 .kr 三星.회사. kr الاهرام.م viagénie .qc.ca ישראל . קום ทีเอชนิค.พาณิชย์.ไทย

tcotton
Download Presentation

Internationalized Domain Names (IDN)

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. Internationalized Domain Names (IDN) APAN Busan James Seng jseng@pobox.org.sg former co-chair, IDN Working Group

  2. Internationalized Domain Names 华人.公司.cn 華人.商業.tw 高島屋.会社.jp 삼성.회사.kr 三星.회사.kr الاهرام.م viagénie.qc.ca ישראל.קום ทีเอชนิค.พาณิชย์.ไทย 現代.com ヤフー.com

  3. PunycodeRFC3492 • Designed for use with Internationalized Domain Names • It uniquely and reversibly transforms a Unicode string into an LDH string (Letter, Digit, Hyphen) • Some compression to produce shorter string • e.g. 新加坡 xn--3bs3aw5wpa2a

  4. Stringprep/NameprepRFC3454/RFC3451 • Prepare internationalized domain name labels in order to increase the likelihood that name input and name comparison work in ways that make sense for typical users throughout the world. • Based on UTR#15 (Normalization) & UTR#22 (Case Mapping) • Stringprep is the generic processing [RFC3454] • Nameprep is a profile of stringprep for Internationalized Domain Names

  5. IDNARFC3490 • IDNA only upgrade in applications to handle IDN • Consideration of legacy encoding and interopability • Enforce Nameprep in applications • Uses Nameprep-ACE’ed IDN over the wire

  6. IDNA-Nameprep-Punycode User End System IDNA processing Punycode Resolver Punycode unless protocol is updated Punycode DNS Servers Application Servers

  7. IDNA-Nameprep-Punycode User Input: 新加坡 (48 34 28 51 38 34)GBK IDNA processing xn--3bs3aw5wpa2a Resolver (E6 96 B0 E5 8A A0 E5 9D A1)UTF-8 xn--3bs3aw5wpa2a DNS Servers Application Servers

  8. So… • 200 engineers • 30 months • 6,000 engineering man-months • more then 10 high-tech companies • over 1M names registered • >100M USD investment What next?

  9. The Eco-system Policy delegation RRP/EPP registration resolution Other Protocols

  10. What we have so far Policy delegation RRP/EPP registration IDNA resolution Other Protocols

  11. CJK Administration Guideline draft-jseng-idn-admin-01.txt Policy • JET effort (started in Feb 2002). • The goal is to reduce potential dispute conflict by reservation of variants • Provide an algorithm for the variants but allow zone admin to define further rules • An example how to bridge the gap between the technical restriction and users expection. delegation RRP/EPP registration resolution Other Protocols

  12. Email & Netnews Proposaldraft-faerber-i18n-email-netnews-names-00.txt • Internationalized Emails and Netnews names • Based on IDNA • Have consideration for Email identifiers Other Protocols

  13. Internationalized Resource Identifierdraft-duerst-iri-00.txt Policy Policy • Internationalized Resource Identifier (IRI) • Complement URI [RFC2396], with a mapping of IRI to URI • Define a new protocol element delegation RRP/EPP registration resolution ??? Other Protocols

  14. Policy Policy • Understand the technical limitation • Script vs. Language • Name vs. Identifier • Internationalization vs. Localization • Per label basis • Understand what users wants • Script vs. Language • Name vs. Identifier • Internationalization vs. Localization • Per “FQDN” (whole domain name) basis

  15. Other development • IDN Open Source • Develop quality RFC compliant software to support IDN capability in different applications running on all major operating system • Would consist of IDN libraries, IDN plugins, IDN tools & software patches • Supported by Internet Software Consortium (ISC)

  16. IDN OSS

  17. OR

More Related