1. A brief introduction of JET and its activities 25 Mar 2003 Hiro HOTTA hotta@jprs.co.jp

2. What is JET? Joint Engineering Team –CJK NICs CNNIC KRNIC TWNIC JPNIC+JPRS – individual experts James Seng John Klensin … Formed in July, 2000 Objectives –to work for the early, solid and cost-effective introduction of standardized Internationalized Domain Name (IDN) system Co-chairs –K. Huang (TWNIC) –K. Konishi (JPNIC)

3. Meetings 2000July1 st meeting@Yokohama Aug.2 nd meeting@Beijing Nov.3 rd meeting@Taipei 2001Feb.4 th meeting@Kuala Lumpur May.5 th meeting@Shanghai Oct.6 th meeting@Beijing Nov.7 th meeting@Beijing 2002Jan.8 th meeting@Taipei Mar.9 th meeting@Bangkok July10 th meeting@Yokohama Oct.11 th meeting@Shanghai 2003Feb.12 th meeting@Taipei

4. Outputs(1) Evaluation of proposed ACE algorithms using real- world IDNs (practically registered and used) –Led AMC-ACE-Z (later named Punycode) to the final selection Raising TC/SC issues –There are cases where 2 or multiple characters should be regarded as the same e.g., 國 & 国 –IETF recognized the importance and difficulties of the issue

5. Outputs(2) Proposal of IDN-Admin –http://www.ietf.org/internet-drafts/draft-jseng-idn-admin- 02.txthttp://www.ietf.org/internet-drafts/draft-jseng-idn-admin- 02.txt –Language table for C/J/K defined by each NIC E.g., http://www.ietf.org/internet-drafts/draft-yoneya-idn-jpchar- 01.txthttp://www.ietf.org/internet-drafts/draft-yoneya-idn-jpchar- 01.txt –Considering the background of IDN-admin, IESG published a statement on IDN Language information associated to IDN Set of characters to be used as an IDN declared Equivalency among characters concerned Conversion between display format and wire format of characters http://www1.ietf.org/mail-archive/ietf- announce/Current/msg22545.htmlhttp://www1.ietf.org/mail-archive/ietf- announce/Current/msg22545.html

6. Status Extracting 2-layered documents from CJK guideline as an example wrt. IDN-Admin –Making a general mechanism for all languages –Making examples for Chinese/Japanese/Korean JET would not make IDN-Admin’s scope out of CJK Defining variant tables for Chinese/Japanese/Korean

7. TODOs Complete IDN-Admin mechanism Complete a variant table of each NIC Complete a variant table of each language –Japanese, Korean : as defined by each NIC –Chinese : defined by CN, TW, MO, HK, SG,... … and then terminate and dissolve

8. IDNConnect

9. Overview(1) Days & Place –May 28 through 30, 2003 –Embassy Suites, San Francisco Airport hotel, near South San Francisco Purposes –To help implementers of IDNs in programs, software libraries, and DNS servers to test their software against other programs and against reference implementations evolving experiments as participants offer their experiences and test systems through using each others‘ –To foster a discussion of issues with registering IDNs in zones throughout the world Convener –Paul Hoffman

10. Overview(2) Agenda –1 st & 2 nd day : interoperability testing to allow IDNA, Nameprep, and Punycode specifications to progress from Proposed Standard to Draft Standard in a short period of time –3 rd day : discussion of registration policies Expected attendees –Anyone who is working on end-user implementations of IDNs, such as web browsers and email clients –Software developers who are creating IDN-aware libraries –Developers of front-ends to DNS servers –Registries and registrars who are grappling with IDN registration policies Mailing list –To subscribe send a message to: idnconnect-announce-request@idnconnect.jdna.jp with the single word "subscribe" in the body of the message Web site –http://idnconnect.jdna.jp/ –described in several languages