Internationalized Domain
Names (IDN)
APAN Busan
James Seng
[email protected]
former co-chair, IDN Working Group
Internationalized Domain Names
华人.公司.cn
華人.商業.tw
高島屋.会社.jp
三星.회사.kr
삼성.회사.kr
‫م‬.‫االهرام‬
viagénie.qc.ca
‫קום‬.‫ישראל‬
ทีเอชนิ ค.พาณิ ชย ์.ไทย
現代.com
ヤフー.com
Punycode
RFC3492


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
Stringprep/Nameprep
RFC3454/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
IDNA
RFC3490


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
End
System
IDNA
processing
Punycode
Resolver
Punycode unless
protocol is updated
Punycode
DNS
Servers
Application
Servers
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
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?
The Eco-system
Policy
delegation
registration
RRP/EPP
resolution
Other
Protocols
What we have so far
Policy
delegation
registration
RRP/EPP
IDNA
Other
Protocols
resolution
CJK Administration Guideline
draft-jseng-idn-admin-01.txt
Policy

JET effort (started in Feb 2002).
delegation

registration
The goal is to reduce potential
dispute conflict by reservation of
variants
RRP/EPP


Provide an algorithm for the
variants but allow zoneresolution
admin to
define further rules
An example how to bridge the gap
Other the technical restriction
between
and
users expection.
Protocols
Email & Netnews Proposal
draft-faerber-i18n-email-netnews-names-00.txt

Internationalized Emails and Netnews
names

Based on IDNA

Have consideration for Email identifiers
Other
Protocols
Internationalized Resource Identifier
draft-duerst-iri-00.txt

Policy
Internationalized Resource
Identifier (IRI)

Complement URI [RFC2396],delegation
with a
mapping of IRI to URI
registration
 Define
RRP/EPP
a new protocol element
???
Other
Protocols
resolution
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
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)
IDN OSS
Advisory
Council
Project
Convener
Legal
Counsel
Chief
Software Architect
Programmers
Project
Manager
Technical
Writers
Translators
Quality
Assurance
OR