Global Registry Services 1 INTERNATIONALIZED Domain Names Testbed presented to ITU/WIPO Joint Symposium Geneva 6-7 Dec An Overview On VeriSign Global Registry Services

Global Registry Services 2 Purpose of the Testbed Create a working environment for testing Internationalized Domain Names in the Domain Name System (DNS) Provide operational experience with current IETF proposals for Internationalized Domain Names

Global Registry Services 3 Testbed Guiding Principles IETF – based standards The ICANN framework is committed to… The IAB single root structure

Global Registry Services 4 IDN Testbed The Testbed allows Internationalized Domain Names in com, net and org to be registered. - e.g., اوتيل.com The technology used in the testbed is based on IETF proposals for IDN. …which means hotel.com Name Preparation draft-ietf-idn-nameprep-03.txt ASCII-compatible encoding- AMCE-ACE-Z draft-ietf-idn-amc-ace-z-01.txt /

Global Registry Services 5 Participation All ICANN com/net/org accredited registrars are currently eligible. Successful completion of an Operational Test and Evaluation (OT&E) certification process is required. Thirty-five (35) registrars have certified Twenty-six (26) registrars have registered an IDN in the last sixty days

Global Registry Services 6 OT & E Certified 35 have passed the International OT&E certification. CN US FR UK DE ES KR SE JP AU DK CA

Global Registry Services 7 Staged Deployment 17 OCT 00 - STAGE 1: Certification & Preparation of Registrars 10 NOV 00 - STAGE 2: Internationalized Domain Name Registration 15 JAN 01 - STAGE 3: Internationalized Domain Name Resolution To ensure the continued stability of the Domain Name System (DNS), VeriSign is employing a staged approach to its testbed.

Global Registry Services 8 Resolution Phases Resolution (Stage 3) of the Testbed is being conducted in three phases: No External Delegation Phase JAN 01 3 rd Level اوتيل.com Publication of ACE in gTLD constellation Phase nd level External Delegation Phase rd Level اوتيل.mltbd.com

Global Registry Services 9 Testbed Status 10 Nov 00Start of Internationalized Domain Name Registrations - Introduction of Chinese, Japanese, Korean (CJK) scripts 26 Feb 01Introduction of additional scripts: Extended Latin, Greek, Cyrillic, Armenian, and Georgian which includes letters with diacritical marks, such as é, ç and ä 05 April 01 Introduction of remaining scripts supported by UNICODE, including Arabic scripts

Global Registry Services 10 Testbed Status 2 May 01Resolution Phase 3.2 Begins – End-users can reach internationalized web-sites using IDN 20 Jun 01RealNames Resolution – IDNs leverage RealNames as a bridging technology to improve end-user experience Move to new ACE – future Move to Resolution Phase 3.3 – Z representation of IDN placed in the com/net/org zones

Global Registry Services 11 Testbed Status ACE RFC – Expect an RFC for AMC-ACE-Z to be published Introduce new name prep draft - 06 AMC-ACE-Z Certification – Begin certification of qualified registrars for registration of AMC- ACE-Z AMC-ACE-Z Registration – Migrate all certified registrars from RACE representation of IDN to AMC-ACE-Z

Global Registry Services 12 Key Points for REGISTRANTS The uniqueness of a domain name registration in the testbed is determined by its Unicode representation. –Different Unicode characters require separate registrations. Example: ole.com and olé.com are separate and distinct registrations VeriSign GRS processes IDN transactions through the Shared Registration System in the same first-come/first-served manner as with all registrations of com/net/org. REGISTRANTS are participating in a Testbed, which is subject to change.

Global Registry Services 13 Key Points for REGISTRANTS The IETF has not finalized the International standards. Future revisions to the Internet draft documents could cause: –A Registrants domain name registration to become invalid and be deleted –Modification to the VeriSign GRS Registrys internal representation of the domain name-- to comply with revisions to the Internet draft documents. Such occurrences will be resolved on a case-by- case basis, as they occur.

Global Registry Services 14 For more information… Scott Hollenbeck –Technology Liaison Patrick Kane –IDN projectVGRS Michael Aisenberg –Corporate Director of Public Policy