Object Provisioning Protocol draft-jseng-provreg-opp-00.txt
Download
Report
Transcript Object Provisioning Protocol draft-jseng-provreg-opp-00.txt
Internationalization of
Domain Names
Multilingual Domain Names: Joint ITU / WIPO Symposium
International Conference Center of Geneva (CICG)
December 6-7, 2001
James Seng <[email protected]>
CTO, i-DNS.net International
co-chair, IETF IDN Working Group
Internationalized Domain Names
华人.公司.cn
華人.商業.tw
高島屋.会社.jp
삼성.회사.kr
三星.회사.kr
viagénie.qc.ca
קום.ישראל
ทีเอชนิ ค.พาณิ ชย ์.ไทย
現代.com
ヤフー.com
م.االهرام
Internet Engineering Task Force
IETF is a large open international community
of network designers, operators, vendors,
and researchers concerned with the evolution
of the Internet architecture and the smooth
operation of the Internet.
It is open to any interested individual.
IETF IDN Working Group
Mailing List
General Discussion: [email protected]
To subscribe: [email protected]
Archive: ftp://ops.ietf.org/pub/lists/idn*
Website http://www.i-d-n.net/
Chair
James Seng <[email protected]>
Marc Blanchet <[email protected]>
Primarily Goal
From the charter “The goal of the group is to specify
the requirements for internationalized access to
domain names and to specify a standards track
protocol based on the requirements.”
BoF in Nov 1999, WG formed in Jan 2000
Spend 6 months gathering requirements
draft-ietf-idn-requirements – Waiting for IESG action
Update charter to include standard protocol
specification in Jun 200
Where is IDN?
WWW
HTTP
Email
URI
SMTP
Mail
Format
DNS
TCP/UDP
Internet Protocol (IP)
Snapshot of network layers to provide some Internet Service
IDN is here
Stability and Compatibility
From the charter “A fundamental requirement in this
work is to not disturb the current use and operation
of the domain name system, and for the DNS to
continue to allow any system anywhere to resolve
any domain name.”
IDN is changing a fundamental service
IAB RFC2825 – “Issues of I18N, Domain Names, and the
other Internet protocols”
A lot of existing Internet Protocols assumed domain
names and assumed that it is A-Z, 0-9 and “-” only
Confusions & Consensus
Scripts v.s Language
Internationalization, Localization and Multilingualism
Domain Names is actually an Identifier
Character Set Encoding
“I” in IDN is Internationalization
Names v.s Identifier
we deal with script in ISO10646
ISO/IEC 10646 also known as Unicode
Matching
Normalization UTR#15 and Case Folding UTR#21
Action Items
An Informational RFC specifying the requirements for
providing International character sets in domain names.
A standard track specification on permitting international
characters in domain names, including specifying any
transition issues.
A standard track specification on an ASCII Compatible
Encoding (ACE), to be used in the standard track specification
on permitting international characters in domain names.
A standard track specification on normalization of domain
name identifiers for the purpose of string comparisons.
Number of Proposals (I-Ds)
IETF
Protocol
Matching Encoding Others
46 – 11/99 Washington
0(+1)
0
1
0
47 – 03/00 Adelaide
0(+1)
0
2
1
48 – 06/00 Pittsburg
6(+2)
1(+2)
3
4
49 – 12/00 San Diego
8
1(+2)
6
9
50 – 03/00 Minneapolis
9
1(+3)
7
10
51 – 08/00 London
3
1(+3)
3
4
52 – 12/01 Salt Lake City
2
1(+3)
1
2
NB: These are estimated numbers
Outstanding issues
IDN Protocol
DM-IDNS and IDNA
Matching
Note: DM-IDNS is superset of IDNA
Localization in Nameprep
ACE
Reordering
ACE prefix
But only the beginning…
From the charter “The group will not address
the question of what, if any, body should
administer or control usage of names that
use this functionality”
Issues not deal with in IETF
Trademark and Domain Name Dispute Policy
Use of Symbols and drawing characters
Policy on the delegation of IDN
Other business issues?
Deployment?
Conclusion
Many problems
This is not a simple problem
But solutions are emerging
No solution is perfect, engineering compromised
Many confusions
Took us many months to understand the issues
but we figure it out
More to come
There are non-technical (e.g. policy & trademark)
issues pending which cannot be deal with in IETF
Lastly
Join the working group!
All are welcome!
[email protected]
with the word “subscribe”
OR