Internationalized Domain Names IDN and Reverse DNS APNIC

  • Slides: 14
Download presentation
Internationalized Domain Names (IDN) and Reverse DNS APNIC Taipei James Seng jseng@pobox. org. sg

Internationalized Domain Names (IDN) and Reverse DNS APNIC Taipei James Seng jseng@pobox. org. sg co-chair, IDN Working Group

Punycode RFC 3492 ¡ Designed for use with Internationalized Domain Names ¡ It uniquely

Punycode RFC 3492 ¡ 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—yfro 4 i 67 omp 3 m

Stringprep/Nameprep RFC 3454/RFC 3451 ¡ Prepare internationalized domain name labels in order to increase

Stringprep/Nameprep RFC 3454/RFC 3451 ¡ 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 [RFC 3454] ¡ Nameprep is a profile of stringprep for Internationalized Domain Names

IDNA RFC 3490 ¡ IDNA only upgrade in applications to handle IDN ¡ Consideration

IDNA RFC 3490 ¡ 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

IDNA-Nameprep-Punycode User (Any encoding) IDNA processing Punycode Resolver Punycode unless protocol is updated Punycode

IDNA-Nameprep-Punycode User (Any encoding) IDNA processing Punycode Resolver Punycode unless protocol is updated Punycode DNS Servers Application Servers End System

IDNA-Nameprep-Punycode User Input: 新加坡 (48 34 28 51 38 34)GBK IDNA processing xn—yfro 4

IDNA-Nameprep-Punycode User Input: 新加坡 (48 34 28 51 38 34)GBK IDNA processing xn—yfro 4 i 67 omp 3 m Resolver xn—yfro 4 i 67 omp 3 m DNS Servers (E 6 96 B 0 E 5 8 A A 0 E 5 9 D A 1)UTF-8 Application Servers

So what? What does it mean to me as an DNS operator?

So what? What does it mean to me as an DNS operator?

Delegation of 新加坡. sg sg. IN SOA IN NS . . . xn—yfro 4

Delegation of 新加坡. sg sg. IN SOA IN NS . . . xn—yfro 4 i 67 omp 3 m ns. singapore. sg. ns 2. singapore. sg. nic. sg. root. nic. sg ( 2003011401 ; Serial 3 H ; Refresh 15 M ; Retry 7 D ; Expire 1 D) ; Minimum TTL ns. nic. sg. IN IN NS NS ns. singapore. sg. ns 2. singapore. sg. IN IN A A 11. 22. 33. 44. 55

Hosting of 新加坡. sg (in named. conf) zone "xn—yfro 4 i 67 omp 3

Hosting of 新加坡. sg (in named. conf) zone "xn—yfro 4 i 67 omp 3 m. sg" { type "master“; file "singapore_db"; } (in singapore_db) xn—yfro 4 i 67 omp 3 m. sg. IN IN IN NS NS A IN SOA singapore. sg. root. singapore. sg ( 2003011401 ; Serial 3 H ; Refresh 15 M ; Retry 7 D ; Expire 1 D) ; Minimum TTL ns. singapore. sg. ns 2. singapore. sg. 1. 2. 3. 4

Hosting of 新加坡. sg (Reverse) (in named. conf) zone "3. 2. 1. in-addr. arpa"

Hosting of 新加坡. sg (Reverse) (in named. conf) zone "3. 2. 1. in-addr. arpa" { type "master"; file "3. 2. 1_db"; } (in 3. 2. 1_db) @ IN 1 IN IN IN SOA NS NS A singapore. sg. root. singapore. sg ( 2003011401 ; Serial 3 H ; Refresh 15 M ; Retry 7 D ; Expire 1 D) ; Minimum TTL ns. singapore. sg. ns 2. singapore. sg. xn—yfro 4 i 67 omp 3 m. sg.

One Problem How the !@#$%^& I know 新加坡 => xn—yfro 4 i 67 omp

One Problem How the !@#$%^& I know 新加坡 => xn—yfro 4 i 67 omp 3 m?

Known tools available ¡ IDNKIT-1. 2 l ¡ GNU libidn l ¡ http: //www.

Known tools available ¡ IDNKIT-1. 2 l ¡ GNU libidn l ¡ http: //www. nic. ad. jp/ja/idn/mdnkit/do wnload/#source http: //www. gnu. org/software/libidn/ Others?

OR

OR