AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
...
- 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?
- 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.
- Who does your SG/C believe should bear the cost, bearing in mind, however, the limits in scope set in the Initial Report on this issue?
Please click here to download a copy of the PDF below.
...