internationalized domain name protocol (idn) & it’s test suite in ipv6 sunyoung han, keecheon...

20
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. [email protected] , [email protected]

Post on 18-Dec-2015

219 views

Category:

Documents


0 download

TRANSCRIPT

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

IPv6

Sunyoung Han, Keecheon KimDept. of Computer Science and EngineeringKonkuk Univ., Seoul, [email protected], [email protected]

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

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 co

untries 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

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

Background (Recent Works)

IDN Protocol Mechanism

IDNS Internationalized Domain Names System

IDNRA Internationalized Host Names Using Resolvers and Applications

IDNA Internationalizing Domain Names in Applications

Encoding

ACE : ASCII Compatible Encoding UTF : Universal Transformation Format

Punycode, DUDE, RACE, BRACE, TRACE, SACE

UTF-5, UTF-6, UTF-8, UTF-16

iDNSngDN Kit

iDNS

mBIND

mDNkitidnkit[1998, APNG]

IDNS mechanismUTF-5 encoding

IDNS/IDNRA/IDNAMany ACE, UTF encoding

IETF Proposed Standard 2002’10

IDNA, Punycode,Nameprep

ENUM IPv6 DNS

Nameprep A Stringprep Profile for Internationalized Domain Names

IDN Protocol Suite

IDN Protocol Suite Map

Cellular Phone

PDA

IDN Test Suite

ENUM Client

Computer

IP Phone

Web server

ftp server

mail server

IDN&ENUM server

Gateway

Client

Other ClientPSTN

ENUM QueryIDN Query

IPv4/IPv6

Internet

IDN : http:// 건국대 . 대학 . 한국 ENUM : 8224503537

202.30.38.1092001:220:1017::2

http:// 건국대 . 대학 . 한국mailto: 한선영 @ 건국대 . 대학 . 한국sip: 한선영 @ 건국대 . 대학 . 한국A :

Q :

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

IPv6 Address (16 octets)

Prefix len.(1 octet)

Address suffix(0..16 octets)

Prefix name(0..255 octets)

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 address

ing

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

IDN & ENUM ServerIDN Client

Protocol Design

ENUMClient

Application

NameResolver IDN & ENUM Check

ENUM Query

PunycodeEncoder

Name Service(A, AAAA or A6)

ENUM Service(NAPTR)

ASCII Domain Name Queryor

PTR Query

Internationalized Domain Name Query

PunycodeEncoder

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

IDN Test Suite (Implementation)

Encoding type choice

Query input

Query type choice

Name server input

Result output

Query send button

Status display line

[Query type choice]

[Encoding type choice]

[IDN Test Suite – Idnslook]

IDN Test Suite & ENUM Client

[IDNS Test Suite] [ENUM Client (prototype)]

International IPv6 IDN Testbed

International IDN Testbed

APAN-JP

vBNS, AbileneCA*Net2, etc

SingaREN

TEN-155Local Testbed

IDNS TestbedTestbed extension plan

IPv6 IDN Root Server

SingaporeUniv.

Interior Testbed

KOREN

유럽 GW

Network extension plan

DacomATM

XP -Singapore

TransPACXP -Tokyo

XP -Seoul

Local IDN Testbed

TLD ServerZone : “.한국”, “.싱가포르”OS : Linux kernel version 2.4.2IP : 203.255.249.70

“건국대.대학.한국”IP : 203.252.134.19

“서울대.대학.한국”IP : 203.252.134.170

“삼성.회사.한국”IP : 203.252.134.49

“현대.회사.한국”IP : 203.252.134.167

KOREN KonKuk-network

sLD ServerZone : “.회사”, “.대학”OS : Linux kernel version 2.2.14IP : 203.252.134.47

그림 일부 수정 예정

Virtual Domain Hierarchy

Root

.한국(Korean Language)

.대학(K)

.서울대 (K)

.회사 (K)

.삼성 (K) …

.Korea(Singaporean Language)

.대학(S)

.건국(S) …

.회사(S)

.삼성(S) …

.Singapore(Singaporean Language)

.싱가포르(Korean Language)

.ac(S)

.singapore(S)

.co(S)

•K : Korean Language•S : Singaporea Language

… …

Top Level iDN

Second Level iDN

Singapore University ZoneKonkuk University Zone

그림 일부 수정 예정

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

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]