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

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

Embed Size (px)

Citation preview

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

1Updated as of 1 July 2014Updated as of 1 July 2014

Issues of the day at ICANNWHOIS

KISA-ICANN Language Localisation Project

Module 2.3

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

2Updated as of 1 July 2014

Refining/Replacing WHOIS

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

3Updated 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

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

4Updated as of 1 July 2014

A WHOIS lookup example

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

5Updated 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

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

6Updated as of 1 July 2014

Nov 2012 -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 2012 - 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 2014 - Final EWG report published. Info on the report and to download: https://www.icann.org/resources/pages/gtld-directory-services-2013-02-14-en

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

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

7Updated 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

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

8Updated as of 1 July 2014

ExampleAddress in English: 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-

8430Address in Japanese: テ 101-8430   東京都千代田区一ツ橋 2- 1- 2 A possible English translation of the address: 2-1-2 One Bridge, Thousand Generations

Field Ward, East Capital Metropolis, 101-8430

A possible Romanized transliteration of the address: 101-8430 Tōkyōto Chiyodaku Hitotsubashi

2-1-2

Current Work at ICANN on WHOIS – Policy Development Processes

Translation & Transliteration of gTLD Contact Data

Accreditation of Privacy & Proxy Services

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

9Updated 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

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

10Updated as of 1 July 2014

The new ICANN Whois website: http://whois.icann.org/ Expert Working Group on gTLD Directory Services:

https://community.icann.org/x/VQZlAg Background information on WHOIS policy in the GNSO:

http://gnso.icann.org/en/group-activities/other/whois GNSO PDP on Privacy & Proxy Services Accreditation Issues:

http://gnso.icann.org/en/group-activities/active/ppsa GNSO PDP on Translation & Transliteration of gTLD Contact

Data: http://gnso.icann.org/en/group-activities/active/transliteration-contact

For further information

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

11Updated 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

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

12Updated as of 1 July 2014

[email protected]

Thank you.

Questions?