Sent on behalf of the GNSO Secretariat: https://www.icann.org/en/news/announcements/announcement-2-08jan13-en.htm <https://www.icann.org/en/news/announcements/announcement-2-08jan13-en.htm> Preliminary Issue Report on Translation and Transliteration of Contact Information Comment/Reply Periods (*)Important Information Links Comment Open:08 January 2013 Comment Close:08 February 2013 Close Time (UTC):23:59 UTCPublic Comment Announcement <https://www.icann.org/en/news/announcements/announcement-2-08jan13-en.htm> Reply Open:09 February 2013To Submit Your Comments (Forum) <mailto:comments-transliteration-contact-08jan12@icann.org> Reply Close:1 March 2013View Comments Submitted <http://forum.icann.org/lists/comments-transliteration-contact-08jan12/> Close Time (UTC):23:59 UTCReport of Public Comments Brief Overview Originating Organization:Generic Names Supporting Organization (GNSO) Categories/Tags:Policy Processes Purpose (Brief):As a required step in the GNSO Policy Development Process (PDP), ICANN Staff is seeking input on the Preliminary Issue Report on Translation and Transliteration of Contact Information <http://gnso.icann.org/en/issues/gtlds/transliteration-contact-prelim-07jan1 3-en.pdf> [PDF, 649 KB]. Current Status:Following the request for an Issue Report by the GNSO Council on 17 October 2012, ICANN Staff has now published the Preliminary Issue Report on Translation and Transliteration of Contact Information for public comment. Next Steps:The Preliminary Issue Report will be updated to reflect community feedback submitted through this forum. A Final Issue Report will then be presented to the GNSO Council for its consideration. Staff Contact:Julie HedlundEmail:Policy-staff@icann.org <mailto:policy-staff@icann.org?subject=More%20information%20on%20the%20%20Pr eliminary%20Issue%20Report%20on%20Translation%20and%20Transliteration%20of%2 0Contact%20Information%20public%20comment%20period> Detailed Information Section I: Description, Explanation, and Purpose ICANN staff is seeking comments on the Preliminary Issue Report on Translation and Transliteration of Contact Information <http://gnso.icann.org/en/issues/gtlds/transliteration-contact-prelim-07jan1 3-en.pdf> [PDF, 649 KB]. This Report addresses the following issues: 1. Whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script. 2. 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. 3. Whether to start a PDP to address these questions. This Public Comment solicitation represents an opportunity for the ICANN community to provide its views on the issues outlined above and on whether a PDP should be initiated. This Preliminary Issue Report will be updated to reflect community feedback submitted through this forum. A Final Issue Report will then be presented to the GNSO Council for its consideration. Section II: Background This preliminary Issue Report addresses three issues associated with the translation and transliteration of contact information at the request of the GNSO Council as approved in its motion on 17 October 2012. These issues are focused on Domain Name Registration Data and Directory Services, such as the WHOIS, in generic Top Level Domains (gTLDs). In the context of these issues, "contact information"is a subset of Domain Name Registration Data. It is the information that enables someone using a Domain Name Registration Data Directory Service (such as WHOIS) to contact the domain name registration holder. It includes the name, organization, and postal address of the registered name holder, technical contact, as well as administrative contact. Domain Name Registration Data is accessible to the public via a Directory Service (also known as the WHOIS service). The Registrar Accreditation Agreement (RAA 3.3.1) specifies the data elements that must be provided by registrars (via Port 43 and via web-based services) in response to a query, but it does not require that data elements, such as contact information, must be translated or transliterated. Section III: Document and Resource Links * Preliminary Issue Report on Translation and Transliteration of Contact Information <http://gnso.icann.org/en/issues/gtlds/transliteration-contact-prelim-07jan1 3-en.pdf> [PDF, 649 KB] * GNSO Council Motion 17 October 2012 <https://community.icann.org/display/gnsocouncilmeetings/Motions+17+October+ 2012> * Final Report of the Internationalized Registration Data Working Group <http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf> [PDF, 642 KB] Section IV: Additional Information Not applicable (*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses. Glen de Saint Géry GNSO Secretariat gnso.secretariat@gnso.icann.org http://gnso.icann.org