<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Hi Amr,</div><div><br></div><div>Thank you very much for the helpful clarification and the context for your comments/questions. I agree that the WG may want to place the questions in some order of priority.</div><div><br></div><div>Best regards,</div><div>Julie</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Amr Elsadr <<a href="mailto:aelsadr@egyptig.org">aelsadr@egyptig.org</a>><br><span style="font-weight:bold">Date: </span> Friday, February 21, 2014 12:27 PM<br><span style="font-weight:bold">To: </span> Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>><br><span style="font-weight:bold">Cc: </span> "<a href="mailto:gnso-contactinfo-pdp-wg@icann.org">gnso-contactinfo-pdp-wg@icann.org</a>" <<a href="mailto:gnso-contactinfo-pdp-wg@icann.org">gnso-contactinfo-pdp-wg@icann.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [gnso-contactinfo-pdp-wg] WHOIS-Related Current and Completed Work<br></div><div><br></div><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi Julie,</div><div><br></div><div>Thanks for laying this all out for us. It’s quite helpful. Just in case I wasn’t clear during the call, my comment/question was related to two of the questions this PDP has been chartered to answer and listed on a <a href="https://community.icann.org/pages/viewpage.action?pageId=44960091">separate
page on the WG wiki</a>:</div><div><br></div><div>Q6. When would policy come into effect?</div><div><br></div><div>I imagine that the timelines involved in the concurrent projects will influence the answer to this question, of course also depending on what this WG recommends on how desirable or undesirable it is to translate and/or transliterate contact info. The EWG
on gTLD Directory Services is wrapping up its work with the public comment period on their report nearing conclusion. I guess this means we can expect an issue report on this soon.</div><div><br></div><div>Q7. What should be mandatory?</div><div><br></div><div>Although I personally think it would have been helpful for this PDP to address what data elements in registrants' contact info should be translated, this is not a really relevant observation right now. It is clearly outside of our scope, and in answering
this question, we need to focus on wether it should be mandatory to translate/transliterate contact info associated with all gTLDs as well as for all registrants in all countries.</div><div><br></div><div>Perhaps, in light of all the projects potentially influencing this PDP and their timelines, we should start discussing the order in which we would like to answer our charter questions. That is assuming we’re settled on the actual questions. :)</div><div><br></div><div>Thanks.</div><div><br></div><div>Amr</div><div><br></div><div><div>On Feb 20, 2014, at 9:50 PM, Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-family: Calibri, sans-serif;"><div>Dear PDP WG members,</div><div><br></div><div>In response to the question from Amr today about whether there is WHOIS-related PDP (or other) work that may be addressing the same issues as the PDP WG please see below the list of current and recently completed work. Staff have presented some of this
information at various times in the formation of this PDP WG, and via presentations from Margie Milam and Steve Sheng at a previous meeting, but it appears that it would be helpful to put it all in one place to avoid any confusion. One thing to note is that
following the Board resolutions on WHOIS in November 2012 a large number of projects (both PDP and non-PDP) were launched and the Board envisioned that these would proceed concurrently, rather than consecutively. See the helpful blog from Margie Milam on
all of the WHOIS-related developments at: <a href="http://blog.icann.org/2013/03/whois-whats-to-come" style="color: purple; text-decoration: underline;">http://blog.icann.org/2013/03/whois-whats-to-come</a>/. </div><div><br></div><div>As I noted on today's call, this PDP WG is the only PDP that addresses the specific issues relating to the translation and transliteration of contact information. The work of this PDP WG will be taken into consideration in conjunction with the Board-initiated
PDP on gTLD directory services, which is tied to the work of the Expert Working Group on gTLD Directory Services (see below). The final report of the EWG will form the Final Issue Report for that Board-initiated PDP. </div><div><br></div><div>The Expert Working Group that is defining requirements for internationalized registration data and a corresponding data model for gTLD registries (#3 below) is the group that Jim Galvin is leading. The work of that group is tied closely to that of this
PDP WG. Both relate to item #13 in the chart in Margie's blog, which is taken from the Board's work plan. That plan states, "ICANN will form a community working group to determine appropriate internationalized domain name registration data requirements based
on requirements set forth in GNSO internationalized registration data working Group final Report." The work this PDP WG will be considered by this EWG so the two groups will coordinate closely.</div><div><br></div><div>I have added this information to the studies and background page on the wiki at: <a href="https://community.icann.org/display/tatcipdp/7.+Studies+and+Background+Documents" style="color: purple; text-decoration: underline;">https://community.icann.org/display/tatcipdp/7.+Studies+and+Background+Documents</a>.
For a list of active GNSO PDP and non-PDP projects see: <a href="http://gnso.icann.org/en/group-activities/active" style="color: purple; text-decoration: underline;">http://gnso.icann.org/en/group-activities/active</a>. </div><div><br></div><div>As you can see, these efforts are very much intertwined. Policies resulting from this PDP WG (if any) will be key elements in future policies relating to the development of a new gTLD directory service, in defining requirements for internationalized registration
data, and in the development of the data model for gTLD registries.</div><div><br></div><div>Please let me know if you have further questions.</div><div><br></div><div>Best regards,</div><div>Julie</div><div><br></div><div>Julie Hedlund, Policy Director</div><div><br></div><div><b>Recently Completed Work: </b></div><div><br></div><div>PDP on Thick WHOIS: <a href="http://gnso.icann.org/en/group-activities/active/thick-whois" style="color: purple; text-decoration: underline;">http://gnso.icann.org/en/group-activities/active/thick-whois</a> </div><div><br></div><div>The GNSO Council requested an Issue Report on 'thick' Whois at its meeting on 22 September 2011 noting that the Issue Report should '<em>not only consider a possible requirement of 'thick' WHOIS for all incumbent gTLDs in the context of IRTP, but should
also consider any other positive and/or negative effects that are likely to occur outside of IRTP that would need to be taken into account when deciding whether a requirement of 'thick' WHOIS for all incumbent gTLDs would be desirable or not'.</em></div><div><em><br></em></div><div>The Final Report was adopted by the ICANN Board on 07 February 2014. See the resolution at<em>: </em><a href="http://www.icann.org/en/groups/board/documents/resolutions-07feb14-en.htm#2.c" style="color: purple; text-decoration: underline;">http://www.icann.org/en/groups/board/documents/resolutions-07feb14-en.htm#2.c</a>. </div><div><em><br></em></div><div><b>Current Work:</b></div><div><br></div><div><b>1. Study Group to Evaluate Available Solutions for the Submission and Display of Internationalized Contact Data.</b></div><div>See: <a href="https://community.icann.org/display/whoisird/Study+to+Evaluate+Available+Solutions+for+the+Submission+and+Display+of+Internationalized+Contact+Data" style="color: purple; text-decoration: underline; font-family: Cambria; font-size: 16px;"><font face="Calibri" size="3">https://community.icann.org/display/whoisird/Study+to+Evaluate+Available+Solutions+for+the+Submission+and+Display+of+Internationalized+Contact+Data</font></a></div><div><div><br></div><div><div>The purpose of the study is to: </div><div><ol style="margin-bottom: 0in;"><li>Document the submission and display practices of internationalized registration data at a representative set of gTLD and ccTLD registries and registrars. </li><li><font color="#333333"><span style="line-height: 1.4285715;">Investigate and document how other e-merchants or web sites manage internationalized contact data.</span></font></li><li><span style="line-height: 1.4285715;">Consider and assess the cost and functionality of commercial, open source, or other known but as yet not widely implemented solutions for 1) transliterating internationalized contact information to US-ASCII, 2) translating
internationalized contact information to English, 3) transcribing internationalized contact information to US-ASCII, or 4) a mixture of translation, transliteration and transcription. </span><span style="line-height: 1.4285715;"> </span></li><li>Consider and assess the accuracy implications for transliteration and translation of the internationalized contact data</li><li>Based on practices documented in 1 and understanding the issues raised in 3 and 4 and best practices by other e-merchants in 2, summarize some common best practices registry/registrar could do to minimize these variations, if translation and/or transliteration
is deemed necessary. </li></ol><div> <span style="font-family: Calibri; font-size: inherit;"> </span><span style="font-family: Calibri; font-size: inherit;">The study team is currently on the first task, and has prepared a registry and registrar survey to complete. Since this group is
closely working in this area, we appreciate very much if you have any feedback on these survey questions. Such feedback will help us to make sure we ask the right questions. </span></div><div><span style="font-family: Calibri; font-size: inherit;"><br></span></div><div><span style="font-family: Calibri; font-size: inherit;"><b>2. Expert Working Group on gTLD Directory Services,<span class="Apple-converted-space"> </span></b>See: </span><a href="http://www.icann.org/en/groups/other/gtld-directory-services" style="color: purple; text-decoration: underline;">http://www.icann.org/en/groups/other/gtld-directory-services</a></div><div><br></div><div>13 December 2012 – Fadi Chehadé,<span class="Apple-converted-space"> </span><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>'s President and CEO, announces the creation of an Expert Working Group on<span class="Apple-converted-space"> </span><abbr title="generic Top Level Domain">gTLD</abbr><span class="Apple-converted-space"> </span>Directory
Services. This first step in fulfilling the<span class="Apple-converted-space"> </span><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr><span class="Apple-converted-space"> </span>Board's directive to help redefine the purpose
and provision of<span class="Apple-converted-space"> </span><abbr title="generic Top Level Domain">gTLD</abbr><span class="Apple-converted-space"> </span>registration data will provide a foundation to help the<span class="Apple-converted-space"> </span><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr><span class="Apple-converted-space"> </span>community
(through the Generic Names Supporting Organization,<span class="Apple-converted-space"> </span><abbr title="Generic Names Supporting Organization">GNSO</abbr>) create a new global policy for<span class="Apple-converted-space"> </span><abbr title="generic Top Level Domain">gTLD</abbr><span class="Apple-converted-space"> </span>directory
services. Interested individuals are invited to indicate their interest in serving as volunteer working group members.</div><div>Initial Report: <a href="http://www.icann.org/en/groups/other/gtld-directory-services/initial-report-24jun13-en.pdf" style="color: purple; text-decoration: underline;">http://www.icann.org/en/groups/other/gtld-directory-services/initial-report-24jun13-en.pdf</a></div><div>Status Update Report: <a href="http://www.icann.org/en/groups/other/gtld-directory-services/status-update-11nov13-en.pdf" style="color: purple; text-decoration: underline;">http://www.icann.org/en/groups/other/gtld-directory-services/status-update-11nov13-en.pdf</a> </div><div>See the Preliminary Issue Report of the Board-initiated PDP at: <a href="http://www.icann.org/en/news/public-comment/gtld-registration-data-15mar13-en.htm" style="color: purple; text-decoration: underline;">http://www.icann.org/en/news/public-comment/gtld-registration-data-15mar13-en.htm</a>. </div><div><br></div><div><b>3. Expert Working Group to Define Requirements for Internationalized Registration Data and Corresponding Data Model for gTLD Registries</b></div><div>See:<span class="Apple-converted-space"> </span><a href="http://www.icann.org/en/news/announcements/announcement-08jul13-en.htm" style="color: purple; text-decoration: underline;">http://www.icann.org/en/news/announcements/announcement-08jul13-en.htm</a>. </div><div><br></div><div>As part of the process to implement WHOIS review team recommendations related to Internationalized Domain Name registration data requirements,<span class="Apple-converted-space"> </span><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr><span class="Apple-converted-space"> </span>seeks
volunteers who are community representatives with expertise in linguistics, IDNA, policy and registry/registrar operations to participate in a working group to determine appropriate Internationalized Domain Name registration data requirements and data model
for Registration Data Directory Services (aka WHOIS services). The result of the<span class="Apple-converted-space"> </span><abbr title="Working Group">WG</abbr><span class="Apple-converted-space"> </span>product will go through a public comment process to
ensure broad input is received. It will form the basis for further policy development and/or contractual framework for generic Top-level domains, as well as ideally becoming a best practice for country code top-level domains.</div><div><span style="font-family: Calibri; font-size: inherit;"><br></span></div><div><span style="font-family: Calibri; font-size: inherit;"><br></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Cambria;"><br></div></div></div></div></div><br class="Apple-interchange-newline"></blockquote></div><br></div></div></span></body></html>