[gnso-contactinfo-pdp-wg] TR: Input Request:Translation and Transliteration of Contact Information Charter Questions

Mon Mar 10 10:46:15 UTC 2014

De : cuishutian [mailto:cuishutian at miit.gov.cn]
Envoyé : lundi 10 mars 2014 11:27
À : Glen de Saint Géry
Cc : gnso-secs at icann.org; Lars Hoffmann; heather.dryden at ic.gc.ca; guofeng at catr.cn
Objet : Re: Input Request:Translation and Transliteration of Contact Information Charter Questions

Dear colleagues,

Thanks for the request to comment on the Translation and Transliteration of Contact Information. I have communicate and solicit opinions from Chinese Internet community on this issue.  I would like to take this oppotunity to raise the following points:

*  In China the registration info(or contact info) are mainly collected by registrars in Chinese which could ensure the accuracy of the registration info.

*  It would be appropriate that the registration info(or contact info) in Chinese script is the basic requirement in the area of China.

*  The registry in China should check and verify the Chinese registration info(or contact info).

The globalization of ICANN is made of the localization of the policy and should respect local language and practice. And the intent of Whois is to accurately record and check the registration info(or contact info) and the Chinese registration info can better serve the Chinese community. The Chinese community thinks that the above-mentioned suggestions can be cost-saving and user-friendly for Chinese community.

Best regards,

Cui Shutian
----- Original Message -----
From: Glen de Saint Géry<mailto:Glen at icann.org>
To: cuishutian at miit.gov.cn<mailto:cuishutian at miit.gov.cn>
Cc: gnso-secs at icann.org<mailto:gnso-secs at icann.org> ; Lars Hoffmann<mailto:lars.hoffmann at icann.org>
Sent: Wednesday, February 05, 2014 6:41 AM
Subject: Input Request:Translation and Transliteration of Contact Information Charter Questions

Dear GAC representative, dear Cui

As you may be aware, the GNSO Council recently initiated a Policy Development Process<http://gnso.icann.org/en/basics/pdp-process.htm> (PDP) on the Translation and Transliteration of Contact Information; the relevant Issue Report can be found here<http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13-en.pdf>. A more detailed background<https://community.icann.org/x/eTOfAg> is available online on the Working Group's Wiki<https://community.icann.org/display/tatcipdp/Translation+and+Transliteration+of+Contact+Information+PDP+Home> where you can also consult the Charter<https://community.icann.org/display/ITPIPDWG/3.+WG+Charter>. As part of its efforts to obtain broad input from the ICANN Community at an early stage and we have written to Ms Heather Dryden, Chair of the GAC, already to solicit feedback from the GAC where possible.

However, as the matter of translating and/or transliteration of Contact information will be of special significance for countries that do not use Latin Scripts, we thought it useful to contact individual GAC representatives. Please note that we do not seek an official position on this matter but rather would welcome any thoughts and/or experiences you might have and what the best practice might be or ought to be in your country on this matter. An informal response to any of the questions below or any other thoughts you might have on the issue of translation and transliteration of Contact Information would be very much appreciated.  Please send these to the GNSO Secretariat (gnso.secretariat at gnso.icann.org<mailto:gnso.secretariat at gnso.icann.org>) who will forward these to the Working Group; ideally by Tuesday 11 March 2014

Finally, our Working Group is planning to gather for a face-to-face meeting during the forthcoming ICANN Meeting in Singapore. We would be delighted if you could join our discussions should you be in Singapore at the time. We will renew this invitation closer to the time when we have finalized our meeting time and agenda.

Many thanks and best wishes,

Chris Dillon (Co-Chair)
Rudi Vansnick (Co-Chair)

Input Request
Translation and Transliteration of Contact Information Charter Questions
Whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script.
What exactly the benefits to the community are of translating and/or transliterating contact information, especially in light of the costs that may be connected to translation and/or transliteration?
Should translation and/or transliteration of contact information be mandatory for all gTLDs?
Should translation and/or transliteration of contact information be mandatory for all registrants or only those based in certain countries and/or using specific non-ASCII scripts?
What impact will translation/transliteration of contact information have on the WHOIS validation as set out under the 2013 Registrar Accreditation Agreement?
When should any new policy relating to translation and transliteration of contact information come into effect?
Do you have suggestions concerning the basic principles to guide the cost burden discussion, such as the free of charge provision of the information, demand-oriented cost etc.?  In particular, the PDP WG is tasked with determining who should decide who should bear the burden translating contact information to a single common language or transliterating contact information to a single common script. This question relates to the concern expressed by the Internationalized Registration Data Working Group (IRD-WG) in its report that there are costs associated with providing translation and transliteration of contact information. For example, if a policy development process (PDP) determined that the registrar must translate or transliterate contact information, this policy would place a cost burden on the registrar.

Glen de Saint Géry
GNSO Secretariat
gnso.secretariat at gnso.icann.org<mailto:gnso.secretariat at gnso.icann.org>
http://gnso.icann.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-contactinfo-pdp-wg/attachments/20140310/c71fdaa3/attachment.html>