Internationalized Domain Name Protocol (IDN) & It’s Test Suite in IPv6

1. Internationalized Domain Name Protocol (IDN) & It’s Test Suite in IPv6 Sunyoung Han, Keecheon Kim Dept. of Computer Science and Engineering Konkuk Univ., Seoul, Korea. syhan@cclab.konkuk.ac.kr, kckim@konkuk.ac.kr

2. Contents • Introduction • Background (Recent works) • IDN Protocol Suite • IPv6 IDN protocol specification which supports ENUM • IDN Test Suite and ENUM Client • International IPv6 IDN Testbed • Conclusion and Future works

3. Introduction (1/2) • Necessity of Internationalized Domain Name (IDN) • Current Domain Name is restricted with ASCII’s subset (a~z, A~Z, 0~9, -) [RFC 1034, 1035] • Requests of IDN are being increased in non-English speaking countries like Korea, China, Japan, Taiwan, etc. • Necessity of ENUM and relation with IDN • Many Internet services and Many Domain Names • Use Telephone No. instead of Domain Names • Convergence of ENUM with DNS • Multilingual in ENUM service

4. Introduction (2/2) • Requirements of IPv6 on IDN & ENUM • NGN, 3GPP(IMT-2000), 4GPP -> IPv6/All IP • IDN & ENUM are mandatory service in IPv6/All IP • Increasing DNS’s importance • Solution • IPv6 + IDN + ENUM • IDN : Protocol specification, Test Suite, Testbed, Client library for application developer • ENUM : ENUM will be supported in IDNS, Client library for application developer

5. Background (Recent Works) mBIND ngDN Kit iDNS iDNS mDNkitidnkit [1998, APNG]IDNS mechanismUTF-5 encoding IDNS/IDNRA/IDNA Many ACE, UTF encoding

6. IDN Protocol Suite

7. IDN Protocol Suite Map IDN&ENUM server IDN Query Cellular Phone ENUM Query Web server PDA IPv4/IPv6Internet ftp server Computer Client mail server Gateway PSTN IDN Test Suite Other Client IP Phone Q : IDN : http://건국대.대학.한국 ENUM : 8224503537 http://건국대.대학.한국 mailto:한선영@건국대.대학.한국 sip:한선영@건국대.대학.한국 202.30.38.1092001:220:1017::2 A : ENUM Client

8. IPv6 DNS Requirements (1/2) • AAAA record • Stores a single IPv6 address • AAAA record is formatted as a fixed-length data • A6 record • Map a domain name to an IPv6 address, with a provision for indirection for leading "prefix" bits • A6 record is formatted as a variable-length data

9. IPv6 DNS Requirements (2/2) • IP6.INT • Nibble formatted IPv6 reverse mapping domain • Uses PTR record like in-addr.arpa • IP6.ARPA • IPv6 reverse mapping domain • Deprecates references to IP6.INT • DNAME record • Provides alternate naming to an entire subtree of the domain name space • Support renumberable and aggregatable IPv6 addressing

10. IPv6 IDN Specification • Follow an IDNA mechanism • There’s no overhead on server side. • But, Support IDNS mechanism • For not-IDNA and legacy application • If query type is A, AAAA or A6, etc. (not PTR or NAPTR) and include IDN(over 0x80 code) which was not Punycode encoded(no ‘IESG–’ prefix) then encode it on server side. • Use Punycode Encoding • Support NAPTR record (ENUM) • Fulfill IPv6 DNS Requirements

11. Protocol Design IDN Client IDN & ENUM Server Application Name Service (A, AAAA or A6) ENUM Service (NAPTR) Punycode Encoder ENUM Client Punycode Encoder Name Resolver IDN & ENUM Check ASCII Domain Name Queryor PTR Query Internationalized Domain Name Query ENUM Query

12. IDN Test Suite (Design) • IDN Test Suite (Idnslook) • For test IDNA and IDNS mechanism • Support GUI • Support many encoding algorithm • Punycode, DUDE, RACE, Encoding-n, UTF-5, UTF-8 • Support many query type • A, PTR, MX, TXT, HINFO, CNAME, SOA, etc. • Support multi platform (based on Java) • Modular design • Separate GUI, Encoding routine and Resolver • More flexible and extensible • For support IPv4/IPv6 Dual Stack • Now, We’re Implementing IPv6 resolver module

13. IDN Test Suite (Implementation) Name server input Query input Query type choice [Query type choice] Encoding type choice Result output Query send button Status display line [Encoding type choice] [IDN Test Suite – Idnslook]

14. IDN Test Suite & ENUM Client [IDNS Test Suite] [ENUM Client (prototype)]

15. International IPv6 IDN Testbed

16. International IDN Testbed IDNS Testbed Interior Testbed Testbed extension plan Network extension plan IPv6 IDN Root Server APAN-JP TransPAC XP - Tokyo XP - Seoul vBNS, AbileneCA*Net2, etc KOREN Singapore Univ. Dacom ATM XP - Singapore SingaREN 유럽 GW TEN-155 Local Testbed

17. Local IDN Testbed 그림 일부 수정 예정

18. Virtual Domain Hierarchy 그림 일부 수정 예정

19. Conclusion and Future works • Conclusion • Necessity of IDN and ENUM • IPv6 IDN & ENUM Server • IDN Test Suite & ENUM Client • International IDN Testbed • Future works • IPv6 IDN & ENUM Server • Consider DNSEXT, DNSSEC • Test Suite • Support IPv6 Query (AAAA, A6, DNAME, etc.) • Support Stability, Reliability test • Convergence with ENUM Client • Testbed extension

20. References • DOMAIN NAMES - CONCEPTS AND FACILITIES [RFC 1034] • DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION [RFC 1035] • E.164 number and DNS [RFC 2916] • DNS Extensions to support IP version 6 [RFC 1886] • DNS Extensions to Support IPv6 Address Aggregation and Renumbering [RFC 2672] • DNS Extensions to Support IPv6 Address Aggregation and Renumbering [RFC 2874] • Delegation of IP6.ARPA [RFC 3152] • Nameprep: A Stringprep Profile for Internationalized Domain Names [draft-ietf-idn-nameprep-11] • Internationalizing Domain Names in Applications (IDNA) [draft-ietf-idn-idna-14] • Punycode: A Bootstring encoding of Unicode for IDNA [draft-ietf-idn-punycode-03] • Internationalized Domain Names in URIs [draft-ietf-idn-uri-03] • Comparison of AAAA and A6 [draft-ietf-dnsext-aaaa-a6-01 ] • Number Portability in the GSTN: An Overview [draft-ietf-enum-e164-gstn-np-05] • The E.164 to URI DDDS Application (ENUM) [draft-ietf-enum-rfc2916bis-02] • Extensible Provisioning Protocol E.164 Number Mapping [draft-ietf-enum-epp-e164-01] • ENUM Usage Scenarios [draft-ietf-enum-usage-scenarios-00]