July 2013 - ispcp - lists.icann.org

Comments on the IGO protection PDP WG report
by Novoa, Osvaldo July 17, 2013

July 17, 2013

All, I am enclosing a proposal for our comments on the initial report for the IGO/INGO protection PDP. Please modify, correct or add according to what we discussed yesterday. We have to submit this document today. Best regards, Osvaldo El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

2 2

Link to the ATRT2 -- questions for Durban
by Mike O'Connor July 16, 2013

July 16, 2013

hi all, here's a link to the file contains the questions that the ATRT2 is asking https://community.icann.org/download/attachments/41884178/ATRT2+-+Questions… m PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

3 2

Nick Wood's "Statement" text
by Mike O'Connor July 16, 2013

July 16, 2013

hi all, here's a copy of Nick Wood's statement that he is hoping to read at the Public Forum PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

Fw: [council] Potential Postponement of the GNSO Review
by WUKnoben July 16, 2013

July 16, 2013

FYI Best regards Wolf-Ulrich From: Jonathan Robinson Sent: Tuesday, July 16, 2013 7:52 AM To: council(a)gnso.icann.org Subject: [council] Potential Postponement of the GNSO Review http://www.icann.org/en/news/public-comment/gnso-review-15jul13-en.htm The Board Structural Improvements Committee (SIC) is considering recommending to the ICANN Board of Directors that the review of the Generic Names Supporting Organization (GNSO), which is mandated by ICANNBylaws Article IV, Section 4, be postponed and that a new schedule for the review be established within the next 6 months. The SIC seeks comments from the ICANN Community to better form its recommendation or to reconsider its recommendation.

1 0

Fwd: [council] Potential Postponement of the GNSO Review
by Novoa, Osvaldo July 16, 2013

July 16, 2013

FYI Inicio del mensaje reenviado: De: "Jonathan Robinson" <jrobinson(a)afilias.info<mailto:jrobinson@afilias.info>> Fecha: 16 de julio de 2013 07:52:36 GMT+02:00 Para: <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Asunto: [council] Potential Postponement of the GNSO Review Responder a: <jrobinson(a)afilias.info<mailto:jrobinson@afilias.info>> http://www.icann.org/en/news/public-comment/gnso-review-15jul13-en.htm The Board Structural Improvements Committee (SIC) is considering recommending to the ICANN Board of Directors that the review of the Generic Names Supporting Organization (GNSO), which is mandated by ICANNBylaws Article IV, Section 4, be postponed and that a new schedule for the review be established within the next 6 months. The SIC seeks comments from the ICANN Community to better form its recommendation or to reconsider its recommendation. ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

With room correction: Dial in details for remote participation for the ISPCP meeting ICANN Meeting Durban
by WUKnoben July 12, 2013

July 12, 2013

FYI ----- Forwarded Message ----- From: Nathalie Peregrine <nathalie.peregrine(a)icann.org> To: "tony holmes (tonyarholmes(a)btinternet.com)" <tonyarholmes(a)btinternet.com> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Sent: Friday, 12 July 2013, 10:46 Subject: With room correction: Dial in details for remote participation for the ISPCP meeting ICANN Meeting Durban Dear All, Please find below the dial in details for the ISPCP meeting during the ICANN meeting in Durban. The meetings will be audio streamed, recorded and there will be a transcript available. For audio streaming please click on the link to the Adobe Connect on the meeting node below. · Tuesday 16th July – ISPCP meeting http://durban47.icann.org/node/39719 Room: Hall 4D 14:00 – 16:30 Password: ISP Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND Land Line: 106-33-203 0-800-9-14610 FINLAND Mobile: 09-106-33-203 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY 39-02-3600-6007 800-986-383 JAPAN OSAKA: 81-6-7739-4799 0066-33-132439 JAPAN TOKYO: 81-3-5539-5191 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 MALAYSIA 1-800-81-3065 MEXICO 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 POLAND 00-800-1212572 PORTUGAL 8008-14052 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 Kind regards Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org/ -------------------------------------------------------------------------------- _______________________________________________ Ispcp-private mailing list Ispcp-private(a)bgnws.com http://bgnws.com/mailman/listinfo/ispcp-private

1 0

Fw: Reminder: Call for Volunteers: Drafting Team to Develop Charter for a GNSO Working Group on GNSO Metrics & Reporting
by WUKnoben July 9, 2013

July 9, 2013

FYI Best regards Wolf-Ulrich From: Glen de Saint Géry Sent: Friday, July 05, 2013 8:40 PM To: mailto:tonyarholmes@btinternet.com ; Novoa, Osvaldo ; WUKnoben Cc: gnso-secs(a)icann.org Subject: Reminder: Call for Volunteers: Drafting Team to Develop Charter for a GNSO Working Group on GNSO Metrics & Reporting Dear Tony, We would like to bring to your notice, and that of your members, this call for volunteers for a drafting team to develop a Charter for a GNSO Working Group on GNSO Metrics & Reporting and encourage them to join this group so that all constituencies and stakeholder groups are represented in the policy development. process.http://gnso.icann.org/en/announcements/announcement-04jun13-en.htm Call for Volunteers: Drafting Team to Develop Charter for a GNSO Working Group on GNSO Metrics & Reporting In Brief The Generic Names Supporting Organization (GNSO) Council seeks volunteers to serve on a Drafting Team (DT) that will develop a charter for a new Working Group (WG). The GNSO Metrics & Reporting WG will be tasked with exploring opportunities with respect to reporting and metrics recommendations that could better inform policy development via fact-based decision making, where applicable. The Drafting Team is expected to submit the proposed Charter to the GNSO Council for approval. What This Team Will Do The Drafting Team is expected to develop a Charter on the basis of the GNSO Working Group Guidelines taking into account the Final Issue Report on Uniformity of Reporting, which recommended that such a Working Group should review how the community can collaborate with contracted parties and other service providers in the sharing of complaint and abuse data that may also further educate Registrants and Internet users in submission of complaints to the appropriate party. Such a Working Group could also investigate more formal processes for requests of data, metrics and other reporting needs from the GNSO that may aid in GNSO policy development efforts. How This Team Will Work ICANN Working Groups use transparent, open processes. The meetings of this DT will be recorded, and the recordings will be available to the public. The mailing list for the Drafting Team will be archived publicly. Drafting Team members are expected to submit Statements of Interest (SOI). The group will collaborate using a public workspace. The Drafting Team is expected to follow the GNSO Working Group Guidelines. How to Join The GNSO Council invites interested parties to provide names of expected participants who can then be added to the DT mailing list. The DT will be open to anyone interested to join. Community members who wish to be invited to join the group should contact the GNSO secretariat (gnso.secretariat(a)icann.org) Background In 2010, the Registration Abuse Policies Working Group (RAPWG) identified in its Final Report the 'need for more uniformity in the mechanisms to initiate, track, and analyze policy-violation reports'. The RAPWG as a result recommended in its Final Report that 'the GNSO and the larger ICANN community in general, create and support uniform reporting processes'. The GNSO in collaboration with the community and ICANN Contractual Compliance deliberated the issues through due diligence analysis, a review of current state compliance reporting systems, and future state implementation plans within ICANN. Based on the information gathered, the GNSO Council recommended the creation of an Issue Report to further research metrics and reporting needs in hopes to better aid the policy development process. The report created by ICANN Staff further outlined accomplishments regarding reporting and metrics for the Contractual Compliance function and it also reviewed other reporting sources that may be of relevance. On 9 May 2013, the GNSO Council approved the report's recommendations to await any further action regarding Contractual Compliance metrics and reporting until the conclusion of their three-year plan towards the end of 2013. At such time the GNSO Council will consider other actions, if any. In the meantime, the GNSO Council also adopted the recommendation to form a non-PDP Working Group tasked with exploring opportunities of reporting and metrics recommendations that could better inform policy development via fact-based decision making, where applicable. An availability review of both ICANN internal and external data sources is expected to be performed to help inform the deliberations of the WG. More information can be found on the GNSO Metrics & Reporting WG page. Please let us know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

2 1

Fwd: [community-finance] Communication: Update to FY14 Budget / Public comments responses
by Mike O'Connor July 6, 2013

July 6, 2013

hi all, here's the response to public comments on the budget -- including ours. mikey Begin forwarded message: > From: "Xavier J. Calvez" <xavier.calvez(a)icann.org> > Subject: [community-finance] Communication: Update to FY14 Budget / Public comments responses > Date: July 5, 2013 11:57:31 PM CDT > To: "community-finance(a)icann.org" <community-finance(a)icann.org> > > Dear Community members, > Please find attached a communication on the update of the FY14 budget and > draft responses of public comments following the end of the public comment > process on the Draft FY14 Budget. Both subjects will be discussed during > the Durban public Finance meeting. > Thanks. > > Sincerely, > Xavier > > Xavier Calvez > ICANN Internet Corporation for Assigned Names and Numbers > > CFO > Office: +1 (310) 301-5838 > Cell: +1 (805) 312-0052 > E-fax: +1 (310) 957-2348 > > 12025 Waterfront Drive, Suite 300 > Los Angeles, CA 90094-2536 > > > _______________________________________________ > community-finance mailing list > community-finance(a)icann.org > https://mm.icann.org/mailman/listinfo/community-finance PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

Fw: [council] GNSO Durban Background Briefing
by WUKnoben July 5, 2013

July 5, 2013

FYI! This is a really good work to getting prepared for Durban. Best regards Wolf-Ulrich From: Marika Konings Sent: Thursday, July 04, 2013 3:15 PM To: council(a)gnso.icann.org Subject: [council] GNSO Durban Background Briefing Dear All, To facilitate your preparation for the GNSO related meetings in Durban, please find attached a GNSO Background briefing that provides a short overview of the status of the different GNSO projects. This will hopefully also assist in focusing the conversation on the substance of the issues during the weekend sessions as set out as an objective by the GNSO during the wrap up session in Beijing. We hope you find this helpful (and if not, we look forward to receiving your suggestions / ideas on how to facilitate your preparation for the ICANN meeting going forward). With best regards, Marika

3 2

Fw: Reminder: Call for Volunteers: Drafting Team to Develop Charter for PDP Working Group on the Translation and Transliteration of Contact Information
by WUKnoben July 5, 2013

July 5, 2013

FYI! Interested members please get in contact to the GNSO secretariat with a copy to the ISPCP list Best regards Wolf-Ulrich From: Glen de Saint Géry Sent: Friday, July 05, 2013 12:34 AM To: mailto:tonyarholmes@btinternet.com ; 'WUKnoben' ; Novoa, Osvaldo Cc: gnso-secs(a)icann.org Subject: Reminder: Call for Volunteers: Drafting Team to Develop Charter for PDP Working Group on the Translation and Transliteration of Contact Information Dear Tony, We would like to bring to your notice, and that of your members, this call for volunteers for a drafting team to develop a Charter for the PDP Working Group on the Translation and Transliteration of Contact Information and encourage them to join this group so that all constituencies and stakeholder groups are represented in the policy development process. http://gnso.icann.org/en/announcements/announcement-19jun13-en.htm Call for Volunteers: Drafting Team to Develop Charter for PDP Working Group on the Translation and Transliteration of Contact Information Introduction At its meeting on 13 June 2013, the GNSO Council initiated a Policy Development Process (PDP) on the translation and transliteration of contact information. (See https://community.icann.org/display/gnsocouncilmeetings/Motions+13+June+2013) Accordingly a group of volunteers will now be convened to draft the charter for the PDP Working Group, which is to be approved by the GNSO Council. Those interested to join this effort are encouraged to contact the GNSO Secretariat by 05 July 2013 at gnso.secretariat(a)gnso.icann.org. Task of the Drafting Team The Drafting Team will be tasked with developing a charter for the PDP Working Group on the translation and transliteration of contact information. The WG is expected to address 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. These issues arise from recommendations in the Final Report provided by the Internationalized Registration Data Working Group (IRD-WG), see http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf. Further background on the issues and related questions is described below. In addition, the Charter should include, at a minimum, the following elements as specified in the GNSO Working Group Guidelines (http://gnso.icann.org/council/summary-gnso-wg-guidelines-06apr11-en.pdf) Working Group identification; Mission; Purpose and Deliverables; Formation, Staffing and Organization; and Rules of Engagement. The proposed Charter will be submitted to the GNSO Council for its consideration and approval. Volunteers If you wish to participate in the Drafting Team, please send an email to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org) by 05 July 2013. You will be required to complete a Statement of Interest in order to participate. Background Information on the Issues The translation and transliteration of contact information were but two issues addressed by the IRD-WG in its Final Report. That Report recommended that the GNSO Council should request an issue report on the translation and transliteration of contact information. 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. The IRD-WG identified internationalized domain name registration data requirements in addition to the translation and transliteration of contact information. It recommended that ICANN staff should develop, in consultation with the community, a data model for domain registration data. The data model should specify the elements of the registration data, the data flow, and a formal data schema that incorporates the standards for internationalizing various registration data elements. Accordingly, in its 08 November 2012 resolution and Action Plan (http://www.icann.org/en/groups/board/documents/briefing-materials-1-08nov12…) the ICANN Board directed staff to: 1) task a working group to determine the appropriate internationalized domain name registration data requirements, evaluating any relevant recommendations from the SSAC or GNSO; 2) produce a data model that includes (any) requirements for the translation or transliteration of the registration data, taking into account the results of any PDP initiated by the GNSO on translation/ transliteration, and the standardized replacement protocol under development in the IETF’s Webbased Extensible Internet Registration Data Working Group; 3) evaluate available solutions (including solutions being implemented by ccTLDs). Thus, the results of the PDP on translation and transliteration of contact information will be considered by the working group described above for which a separate Call for Volunteers will be issued. With respect to the two issues identified above concerning the translation and transliteration of contact information, the following additional background may be useful. On the first issue, whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script, the IRD-WG noted that, “[t]o balance the needs and capabilities of the local registrant with the need of the (potential) global user of this data, one of the key questions … is whether DNRD-DS [Domain Name Registration Data Directory Services] should support multiple representations of the same registration data in different languages or scripts.” In particular, the IRD-WG members discussed whether it is desirable to adopt a “must be present” representation of contact data, in conjunction with local script support for the convenience of local users. By “must be present” the IRD-WG meant that contact data must be made available in a common script. In general, the IRD-WG recognized that, “the internationalized contact data can be translated or transliterated into the ‘must be present’ representation. As noted above, in this context, Translation is the process of conveying the meaning of some passage of text in one language, so that it can be expressed equivalently in another language. Transliteration is the process of representing the characters of an alphabetical or syllabic system of writing by the characters of a conversion alphabet.” Based on this definition, and consistent with the current state of domain name registration data, the IRD-WG noted that if transliteration were desired, then the “must be present” script would be the Latin script. If translation were desired, then the “must be present” language would be English. The IRD-WG did note that many language translation systems are inexact and cannot be applied repeatedly to translate from one language to another. Thus the IRD-WG noted that there will likely be problems with both consistency and accuracy, such as: • Translation/transliteration may vary significantly across languages using the same script. • Two people may translate/transliterate differently even within a language and the same person may translate/transliterate differently at different times for the same language. • How would a registrar determine which particular spellings to use for a particular registrant? How would a registrant ever verify the correctness of a translation or transliteration, even if presented such data by the registrar or by a third organization that does the translation/transliteration? Furthermore, the IRD-WG noted that for a given script, there may exist multiple systems for transliteration into Latin scripts. In the case of Chinese, the multiple transliteration systems are not only quite different from each other, but most of the systems use particular Latin characters to represent phonemes that are quite different from the most common phoneme-character pairings in European languages. Finally, it is unclear whether translation or transliteration would serve the needs of the users of contact data. For example it is unclear that translating the name of the registrant and city would be useful. Would one have to translate "Los Angeles" into " City of the Angels" and translate “Beijing” into "Northern Capital"? The PDP should explore whether such translations facilitate or hinder the ability to contact the registrant. The second issue, 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, relates to the concern expressed by the IRD-WG in its report that there are costs associated with providing translation and transliteration of contact information. For example, if a PDP determined that the registrar must translate or transliterate contact information, this policy would place a cost burden on the registrar. The IRD-WG considered several alternatives to address translation and transliteration of contact information as follows: • The registrant submits the localized information as well the translated or transliterated information. • The registrant only submits the localized information, and the registrar translates and transliterates all internationalized contact information on behalf of the registrant. • The registrant only submits the localized information, and the registrars provide a point of contact at a service that could provide translation or transliteration upon request for a fee to be paid by the requester. • The registrant only submits the localized information, and the registry provides translation or transliteration. • The end users of the registration data translate and transliterate the contact information. During their deliberations the members of the IRD-WG recognized that many registrants will need to access domain names in their local scripts and languages, which is the one of the primary reasons for the expansion of internationalized domain names. Therefore, the IRD-WG determined that it is unreasonable to assume all registrants – wherever they happen to be located – will be able to enter the registration data in scripts or languages other than their local script or language. On 17 October 2012 the GNSO Council requested an Issue Report to address the three issues that were identified by the IRD-WG: • Whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script. • 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. • Whether to start a PDP to address these questions. The Final Issue Report on translation and transliteration of contact information was submitted to the GNSO Council on 21 March 2013 and on 13 June 2013 the GNSO Council approved the initiation of a PDP on the translation and transliteration of contact information. The GNSO Council also requested ICANN to commission a study on the commercial feasibility of translation or transliteration systems for internationalized contact data, which is expected to be completed in time to help inform the PDP Working Group in its deliberations. Recommended Reading for Volunteers • Final Issue Report on Translation and Transliteration of Contact Information (http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13…) • Final Report of the Internationalized Registration Data Working Group (http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf) • GNSO Working Group Guidelines, including charter guidelines (http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf) Please let us know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0