1 Updated as of 1 July 2014 Issues of the day at ICANN WHOIS KISA-ICANN Language Localisation Project Module 2.3

2 Updated as of 1 July 2014 Refining/Replacing WHOIS

3 Updated as of 1 July 2014 What is WHOIS? Background:  At time of registration, Registrants (domain name holder) must provide their contact and technical details  This information goes into a global, publicly-available directory called the WHOIS service  WHOIS is not a single centrally- managed database – data is held in multiple locations by registries and registrars in accordance with minimum requirements specified in their contracts with ICANN

4 Updated as of 1 July 2014 A WHOIS lookup example

5 Updated as of 1 July 2014 Problem: Policy Issues include -  Difficulty in taking into account varying interests, e.g. Individuals, law enforcement, legal rights etc. –Ensuring that WHOIS data is accurate, accessible & reliable –Ensuring adequate data & privacy protections as required by law Technical Issues include -  Outdated protocol**  Inability to fully support IDNs and internationalized registration data  Lack of standardization for query/response and error format Why WHOIS needs to be replaced ** RFC2912, Sept 2004

6 Updated as of 1 July 2014  Nov ICANN Board directs CEO to launch effort to redefine purpose of collecting & maintaining WHOIS data; initiates GNSO PDP on solutions to improve accuracy & access  Dec CEO creates Expert Working Group (EWG) on gTLD Directory Services  Foundation for a new global policy on WHOIS  Initial & status reports published in Jun & Nov 2013  June Final EWG report published. Info on the report and to download:  The final EWG report will feed into the ICANN Board-initiated GNSO Policy Development Process to serve as a foundation for the GNSO's creation of new consensus policy, and contractual negotiations on the new WHOIS as appropriate.  Stakeholders need to be informed and be part of the process. Current Work at ICANN on WHOIS – Expert Working Group

7 Updated as of 1 July 2014 In addition, the GNSO has launched Policy Development Processes on specific aspects of WHOIS:  Translation & Transliteration of gTLD Contact Data  Accreditation of Privacy & Proxy Services Current Work at ICANN on WHOIS – Policy Development Processes

8 Updated as of 1 July 2014 Example Address in English:  Hitotsubashi, Chiyoda-ku, Tokyo Address in Japanese:  テ 東京都千代田区一ツ橋 2 － 1 － 2 A possible English translation of the address:  One Bridge, Thousand Generations Field Ward, East Capital Metropolis, A possible Romanized transliteration of the address:  T ō ky ō to Chiyodaku Hitotsubashi Current Work at ICANN on WHOIS – Policy Development Processes  Translation & Transliteration of gTLD Contact Data  Accreditation of Privacy & Proxy Services

9 Updated as of 1 July 2014 Example Current Work at ICANN on WHOIS – Policy Development Processes  Translation & Transliteration of gTLD Contact Data  Accreditation of Privacy & Proxy Services Not the actual registrant but a proxy

10 Updated as of 1 July 2014  The new ICANN Whois website:  Expert Working Group on gTLD Directory Services:  Background information on WHOIS policy in the GNSO:  GNSO PDP on Privacy & Proxy Services Accreditation Issues:  GNSO PDP on Translation & Transliteration of gTLD Contact Data: contact contact For further information

11 Updated as of 1 July 2014  What specific concerns does the Asia Pacific community have about WHOIS?  What are some of your experiences and problems that ICANN should know about in considering a replacement for WHOIS?  WHOIS affects registrar ’ s work, and we need your feedback Participate at our ICANN meetings remotely or in person and give us your feedback WHOIS reform and Asia Pacific

12 Updated as of 1 July 2014 Thank you. Questions?