<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Dear Julie,<div><br></div><div>Thank you very much for the quick response and the provided information.</div><div><br></div><div>Kind regards,</div><div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: 'Euphemia UCAS'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="font-size: 13px; ">Rudi Vansnick</span></div><div style="color: rgb(0, 0, 0); font-family: 'Euphemia UCAS'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="font-size: 13px; ">NPOC chair Policy Committee</span></div><div style="color: rgb(0, 0, 0); font-family: 'Euphemia UCAS'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="font-size: 13px; ">NPOC treasurer</span></div><div style="color: rgb(0, 0, 0); font-family: 'Euphemia UCAS'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="font-size: 13px; "><a href="mailto:rudi.vansnick@npoc.org">rudi.vansnick@npoc.org</a></span></div><div style="color: rgb(0, 0, 0); font-family: 'Euphemia UCAS'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="font-size: 13px; ">Tel : +32 (0)9 329 39 16</span></div><div style="color: rgb(0, 0, 0); font-family: 'Euphemia UCAS'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="font-size: 13px; ">Mobile : +32 (0)475 28 16 32</span></div><div style="color: rgb(0, 0, 0); font-family: 'Euphemia UCAS'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><a href="http://www.npoc.org">www.npoc.org</a></div></div></span>
</div>
<br><div><div>Op 20-feb.-2014, om 21:50 heeft Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>> het volgende geschreven:</div><br class="Apple-interchange-newline"><blockquote type="cite"><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; font-size: 14px; 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">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">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">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">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">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="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><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, </b>See: </span><a href="http://www.icann.org/en/groups/other/gtld-directory-services">http://www.icann.org/en/groups/other/gtld-directory-services</a></div><div><br></div><div>13 December 2012 – Fadi Chehadé, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>'s President and CEO, announces the creation of an Expert Working Group on <abbr title="generic Top Level Domain">gTLD</abbr> Directory Services. This first step in fulfilling the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board's directive to help redefine the purpose and provision of <abbr title="generic Top Level Domain">gTLD</abbr> registration data will provide a foundation to help the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community (through the Generic Names Supporting Organization, <abbr title="Generic Names Supporting Organization">GNSO</abbr>) create a new global policy for <abbr title="generic Top Level Domain">gTLD</abbr>
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">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">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">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: <a href="http://www.icann.org/en/news/announcements/announcement-08jul13-en.htm">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,
<abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
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 <abbr title="Working Group">WG</abbr> 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><p class="MsoNormal" style="font-family: Cambria; "><br></p></div></div></div><style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:853033055;
mso-list-template-ids:-2079274624;}
@list l1
{mso-list-id:999386070;
mso-list-type:hybrid;
mso-list-template-ids:-1892256084 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style></div>
</blockquote></div><br></div></body></html>