21 May 2000Chinese Domain Name Workshop1 Status and planning reports of JPNIC 宇井隆晴 (UI, Takaharu) JPNIC.

21 May 2000 Chinese Domain Name Workshop 1

Status and planning reports of JPNIC

宇井隆晴 (UI, Takaharu) <[email protected]>

JPNIC


.JP domain name space AD.JP: Network Administrative Organizations CO.JP: Commercial Companies AC.JP: Academic Organizations GO.JP: Governmental Agencies OR.JP: Other types of Organizations NE.JP: Network Service Domains (from Nov. 6, 1996) GR.JP: Group Domains (from Dec. 1, 1997) ED.JP: Schools (from Feb. 1, 1999) GEO: Geographical Domains

TOKYO.JP YOKOHAMA.JP ...


JPNIC Registered Domains

0

30000

60000

90000

120000

150000

1992/5/1 1993/5/1 1994/4/1 1995/4/1 1996/4/1 1997/4/1 1998/4/1 1999/4/1 2000/2/1

Others(Geographical etc.)EDGRNEORGOCOACAD

ftp://ftp.nic.ad.jp/jpnic/statistics/Allocated_Domains


Registration Policy(ASCII DN) First-come, first-served One domain name per organization Non-transferable Local presence in Japan

Discussion underway with a view to changing these policies


Future Plan for ASCII DN Effectuate dispute resolution

procedure. For problems of cyber squatting,

conflict with trademarks, and so on. Relax limitations for number of

domain name registration. … the above plans hopefully be

realized within this year.


JPNIC Status of mDN


Current status of JPNIC JPNIC published statement about

multilingual domain name on 25th Feb, and will publish revised version very soon. Please check our web page described

in next page. JPNIC promotes standardization

actively cooperate with IETF, MINC and related organizations.


Current status of JPNIC JPNIC formed a task force to deal with

multilingual domain name issues. IDN Task Force is in charge of research and

development of IDN issues. JPNIC started webpage about multilingual

domain name on middle of March. The URL is:

http://www.nic.ad.jp/en/research/idn/index.html JPNIC began joint meeting with another NICs

for information exchange and discuss about multilingual domain name related issues.


JPNIC implementations JPNIC has 2 own experimental

implementations of multilingual DNS. Those 2 experimental implementations

were study of university students who were JPNIC IDN-TF members.

JPNIC is planning to modify our implementations referring to the requirements of us presented at 47th IETF.


JPNIC implementations –

IDNX/idnx-jp Simple DNS proxy to translate Japanese local

character encodings into UTF-5. Add invisible ZLD when . 日本 is TLD in

query. Refer to IETF draft. Design goal is to separate

internationalization part and localization part easily.

No additional canonicalization or normalization in internationalization part.


JPNIC implementations –

GDNS 8bit through DNS Server based on

BIND-8. No character code conversion. Uses character code set tag in

reverse lookup table. Ex.4.3.2.1.EUC-JP.in-addr.arpa.


Related activities in Japan 2 companies (netpia.com and jp.io)

provides Japanese domain name registration service as keyword.

i-dns.net published press-release that they will start Japanese domain name registration service as DNS within this month in alliance with 3 companies (ASCII, Crayfish and InterQ).


Issues under discussion(not decided yet)


Dispute Resolution Multilingual domain names

registration may have more disputes than ASCII domain names. Because usually Trademarks are

written in local language. We think it needs dispute

resolution process(DRP) or/and examination before registration.


Limitation of Character Set/Language What character set should Registry allow

for domain name under multilingual TLDs? Belong to TLD’s character set

Ex) Japanese TLD(. 日本 ) has only Japanese Domain names.

No Limitation Ex) Japanese TLD can have Chinese, Korean, Tamil

and Arabic domain names.

We think mDN character set belong to TLD.


Limitation of Characters What characters should Registry

allow for domain name? All characters of the character set? Symbol marks? Similar glyph characters

… this problem has relation to canonicalization and normalization.


Canonicalization-1 Some character sets(including ISO10646)

have characters with almost the same glyph but different character codes. For example:

‘ 高’ (9ad8)‘ 髙’ (9ad9)

‘A‘ (0041, ASCII uppercase A)‘ Ａ’ (0391, Greek uppercase α)‘ Ａ’ (0410, Russian uppercase A)‘ Ａ’ (ff21, Japanese double width A)


Canonicalization-2 Same glyph characters bring users’

confusion. So, we think canonicalization should be done somewhere. In domain name registration. In making of mDN query in resolver

and/or proxy.


Normalization-1 Same words in one language can

be written in varieties of scripts. E.g. Japanese language has 4 scripts.

Latin alphabet : tagengo Kanji : 多言語 Hiragana : たげんご Katakana : タゲンゴ


Normalization-2 Another, same problems are caused

by some situations as follows: Same meaning words

E.g. ‘ 国際’ , ‘ 国家間’ Abbreviation

E.g. ‘ 高等学校’ , ‘ 高校’ Transliteration

E.g. ‘Japan’, ‘ 日本’


Normalization-3 In multilingual domain name

registration, those names should be dealt same name or not?

We think it needs normalization. But it is difficult to decide on what case normalization should be applied.


Name Space Coordination Multilingual domain name

registration services are already provided by some registries using different ZLDs and same multilingual TLDs.

Using different technology and same multilingual TLDs may cause the same problem.


When will JPNIC start mDN?


Service Schedule JPNIC will start Japanese domain

name experimental registration service after decide all of registration policy and effectuate dispute resolution procedure.

JPNIC will apply ASCII DRP to mDN DRP.

Experimental phase will continue until standardization to be finished.

21 May 2000Chinese Domain Name Workshop1 Status and planning reports of JPNIC 宇井隆晴 (UI, Takaharu) JPNIC.

Documents