Japan Registry Service

Experience with 8 bit label inJP Zone
1st August 2004
IEPG Meeting
Yoshiro YONEYA <yone@jprs.co.jp>
Japan Registry ServiceCopyright © 2004 Japan Registry Service Co., Ltd.

Japan Registry ServiceOverview• Introduction• Specification• Result of Survey• Observed effects

Copyright © 2004 Japan Registry Service Co., Ltd.

2

Japan Registry ServiceIntroduction

Copyright © 2004 Japan Registry Service Co., Ltd.

Japan Registry Service

Brief history ofJapanese JP Domain name (JDN)
2000/11 Started DNS testbed by RACE
2001/02 Started registration of JDN
2001/05 Started DNS resolution service by
RACE for registered JDN
2003/03 Standardization of IDN
2003/07 Started DNS resolution service by Punycode
2003/09 Finished DNS resolution service by RACE
2004/02 Started Japanese JP-Navi service
2004/07 Around 42,000 JDNs

Copyright © 2004 Japan Registry Service Co., Ltd.

4

Japan Registry Service

Current situation of JDN• Registrants want to use JDN actively• However, if registrants advertise JDN, it willcause an unfavorable situation because
JDN/IDN-aware Web browsers are notdeployed widely yet– Windows Internet Explorer, which has more than
90% market share, is not JDN/IDN-aware yet– Registrants have difficulty in supporting users who
met an access error• The state is “difficult case” even if registrants
want to use– Chicken and Egg problem
Copyright © 2004 Japan Registry Service Co., Ltd.

5

Japan Registry Service

JPRS is doing• Utilize JDN much more
– Perform JDN promotion actively• Deploy JDN/IDN-aware environment– Introduction of technologies and countermeasures through media and so on– Influence to vendors such as browser, OS,
PC manufacturers and mobile phonecarriers
Copyright © 2004 Japan Registry Service Co., Ltd.

6

Japan Registry Service

Objectives of Japanese JP-navi• By using DNS– Inform users to use JDN/IDN-aware Web browsers– Decrease 8bit label DNS queries• Because JDN/IDN-aware Web browsers are notdeployed widely yet– Users happen to see unexpected error, but they can notunderstand the reason– JDN registrants want to utilize their JDN, but it is hard to getunderstanding of users that JDN/IDN-aware application isrequired– Without deployment of JDN/IDN-aware environment, itcontinues 8bit label DNS queries

Copyright © 2004 Japan Registry Service Co., Ltd.

7Japan Registry Service

Before and after
Before Japanese JP-navi

After Japanese JP-navi①Users type JDN to JDN/IDNunaware Web browser“http://日本語.jp/”①Users type JDN to JDN/IDNunaware Web browser“http://日本語.jp/”②Browser cause an error

Page not foundCopyright © 2004 Japan Registry Service Co., Ltd.

②Browser browses a web sitewhich inform users JDN/IDNaware environments-i-Nav download- Netscape download-Opera download

8

Japan Registry Service

Before starting Japanese JP-navi• Explained specification and result of oursurvey to Japanese Internet community– Highlighting that this is a temporary service• Opened 3 weeks public comment period
simultanously– From 19 Jan 2004 to 6 Feb 2004

• Started on 18 Feb 2004

Copyright © 2004 Japan Registry Service Co., Ltd.

9

Japan Registry ServiceSpecification

Copyright © 2004 Japan Registry Service Co., Ltd.

Japan Registry ServiceOverview• Only when JDN registrant wishes, adds UTF8 encoded JDN onto JP zone
– Japanese JP-navi is opt-in– Requires existence of NS– Adds A and MX RRs• When users type JDN through JDN/IDNunaware Web browser, a certain Web page isshown– To navigate i-Nav™ plug-in download page
– To introduce JDN/IDN-aware browsers such as
Opera and Netscape Navigator

Copyright © 2004 Japan Registry Service Co., Ltd.

11

Japan Registry Service

Example of the Page

Copyright © 2004 Japan Registry Service Co., Ltd.

12

Japan Registry ServiceRRs added onto JP•

A and MX RRs for UTF-8 encoded JDN and with www
xn--wgv71a119e.jp. NS日本語.jp.
A
MX 10
www.日本語.jp.
AMX 10

ns. xn--wgv71a119e.jp.
10.10.10.10
not-exist.jp.
10.10.10.10
not-exist.jp.

• AAAA is not provided•Basically, 4 RRs are added per domain– In maximum, 12 RRs are added if the JDN includes alphabet• To support compatible characters of alphabets
ASCII“JPRS会社.jp”
Full-width (Upper)“ＪＰＲＳ会社.jp”
Half-width (lower)“ｊｐｒｓ会社.jp”– If JDN includes digit and/or hyphen, 8 RRs are added
ASCII
Full-width“123-会社.jp”“１２３−会社.jp”

Copyright © 2004 Japan Registry Service Co., Ltd.

13

Japan Registry Service

Treatment of SMTP
• Due to A RR addition, SMTP connection is expected– To avoid receiving E-Mail, add MX RR which does not existto make immediate error• There are MTAs that try to connect A if connect toMX failed (RFC2821 violation)– No SMTP service provided• Not to record any connection– RFC2821 incompliant MTAs will retry for a several days

• SMTP connection may be rare (our assumption)– MTA will cause error during address format checking

Copyright © 2004 Japan Registry Service Co., Ltd.

14

Japan Registry Service

Result of Survey

Copyright © 2004 Japan Registry Service Co., Ltd.

Japan Registry Service

UTF-8 8bit label treatment in DNS• 8bit is permitted as a protocol, but there are very few
operational experiences– Cite from RFC1035, 3.1 Name space definitions
Although labels can contain any 8 bitvalues in octets that make up a label…
• Target of survey on UTF-8 8bit label treatment on
DNS servers– Authoritative server• BIND, which is used as authoritative server of JP DNS– Cache server• BIND, dnscache and Windows DNS service, which is widelyused in Japan

Copyright © 2004 Japan Registry Service Co., Ltd.

16

Japan Registry Service

Items of the 8bit label survey• Can contain A and MX RRs• Can zone transfer• Can hold a lot of 8bit label• Can hold a long label (up to 63 octets)• No influence to 7bit queries• 8bit label and its masked 7bit label are
distinguished completely– Both authoritative and cache serverCopyright © 2004 Japan Registry Service Co., Ltd.

17

Japan Registry Service

Results of the 8bit label survey•

No problem was found for authoritative servers used in JP DNS– Also no problem was found for NSD, tinydns and other versions ofBIND•

No problem was found for BIND (as a cache) available from
ISC’s ftp site
– Works fine even on BIND Version 4.8.3– Excluded non release (Alpha, beta and RC) versions of BIND 9series to decrease target (for time constraints)••

No problem was found for dnscache (djbdns)
No problem was found for Windows DNS service if 8bit label isUTF-8– Another encodings were not responded•

No problem was found for SOHO routers (NAT boxes) as far as
availed

Copyright © 2004 Japan Registry Service Co., Ltd.

18

Japan Registry Service

Example: Current test environment

Copyright © 2004 Japan Registry Service Co., Ltd.

19

Japan Registry ServiceTIPS: Using UTF-8 on DNS• In dig, ‘¥’ followed 3digits decimal can representarbitrary code
– Example for lookup A RR of “日本語.jp” in UTF-8– dig ‘¥230¥151¥165¥230¥156¥172¥232¥170¥158.jp' a– Using UTF-8 directly is also available if yourcommand line accepts it• BIND’s zone file notation is the same

Copyright © 2004 Japan Registry Service Co., Ltd.

20

Japan Registry Service

Observed effects

Copyright © 2004 Japan Registry Service Co., Ltd.

Japan Registry Service

Case study: Campaign of afamous beverage maker• A Japanese famous beverage maker used aJDN for a product’s campaign– http://生茶.jp/ in addition to http://namacha.jp/• Campaign period– Jun 15 09:00 to Jul 31 21:00 (JST)• Medias to have been used to advertise JDN– Posters inside store– Posters on vending machine– Advertisement in magazines
Copyright © 2004 Japan Registry Service Co., Ltd.

22

Japan Registry Service

Access count of Japanese JP-navi
Total AccessJDN Link

Opera DL

Netscape DL
i-Nav DL
2/19

3/4

3/18

4/1

4/15

4/29

5/13

Copyright © 2004 Japan Registry Service Co., Ltd.

5/27

6/10

6/24

7/823