<HTML xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=Generator content="Microsoft Word 14 (filtered medium)">
<STYLE><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Lucida Grande";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></STYLE>
</HEAD>
<BODY lang=FR dir=ltr link=blue vLink=purple>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>FYI!</DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">Interested
members please get in contact to the GNSO secretariat with a copy to the ISPCP
list<BR><BR>Best regards<BR><BR>Wolf-Ulrich <BR><BR></DIV>
<DIV
style="FONT-SIZE: small; FONT-FAMILY: 'Calibri'; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; TEXT-DECORATION: none; DISPLAY: inline">
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=Glen@icann.org
href="mailto:Glen@icann.org">Glen de Saint Géry</A> </DIV>
<DIV><B>Sent:</B> Friday, July 05, 2013 12:34 AM</DIV>
<DIV><B>To:</B> <A title=tonyarholmes@btinternet.com
href="mailto:tonyarholmes@btinternet.com">mailto:tonyarholmes@btinternet.com</A>
; <A title=wolf-ulrich.knoben@t-online.de
href="mailto:wolf-ulrich.knoben@t-online.de">'WUKnoben'</A> ; <A
title=onovoa@Antel.com.uy href="mailto:onovoa@Antel.com.uy">Novoa, Osvaldo</A>
</DIV>
<DIV><B>Cc:</B> <A title=gnso-secs@icann.org
href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</A> </DIV>
<DIV><B>Subject:</B> Reminder: Call for Volunteers: Drafting Team to Develop
Charter for PDP Working Group on the Translation and Transliteration of Contact
Information</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style="FONT-SIZE: small; FONT-FAMILY: 'Calibri'; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; TEXT-DECORATION: none; DISPLAY: inline">
<DIV class=WordSection1>
<P class=MsoNormal><o:p></o:p> </P>
<P class=MsoNormal><SPAN style="mso-fareast-language: fr">Dear
Tony,<o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p></o:p> </P>
<P class=MsoNormal><SPAN lang=EN-US>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.</SPAN><SPAN lang=EN-US
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><A
href="http://gnso.icann.org/en/announcements/announcement-19jun13-en.htm"><SPAN
lang=EN-US>http://gnso.icann.org/en/announcements/announcement-19jun13-en.htm</SPAN></A><SPAN
lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>Call for Volunteers: Drafting Team to
Develop Charter for PDP Working Group on the Translation and Transliteration of
Contact Information</SPAN><SPAN lang=EN-US
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>Introduction<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>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 </SPAN><A
href="https://community.icann.org/display/gnsocouncilmeetings/Motions+13+June+2013"><SPAN
lang=EN-US>https://community.icann.org/display/gnsocouncilmeetings/Motions+13+June+2013</SPAN></A><SPAN
lang=EN-US>) 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 </SPAN><A
href="mailto:gnso.secretariat@gnso.icann.org"><SPAN
lang=EN-US>gnso.secretariat@gnso.icann.org</SPAN></A><SPAN
lang=EN-US>.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>Task of the Drafting
Team<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>The Drafting Team will be tasked with
developing a charter for the PDP Working Group on the translation and
transliteration of contact information. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>The WG is expected to address the following
issues:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>1.<SPAN
class=apple-tab-span>
</SPAN>Whether it is desirable to translate contact information to a single
common language or transliterate contact information to a single common
script.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>2.<SPAN
class=apple-tab-span> </SPAN>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. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>These issues arise from recommendations in
the Final Report provided by the Internationalized Registration Data Working
Group (IRD-WG), see </SPAN><A
href="http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf"><SPAN
lang=EN-US>http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf</SPAN></A><SPAN
lang=EN-US>. Further background on the issues and related
questions is described below.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>In addition, the Charter should include, at
a minimum, the following elements as specified in the GNSO Working Group
Guidelines (</SPAN><SPAN
style="FONT-SIZE: 8.5pt; FONT-FAMILY: 'Lucida Grande'"><A
href="http://gnso.icann.org/council/summary-gnso-wg-guidelines-06apr11-en.pdf"><SPAN
lang=EN-US>http://gnso.icann.org/council/summary-gnso-wg-guidelines-06apr11-en.pdf</SPAN></A></SPAN><SPAN
lang=EN-US style="FONT-SIZE: 8.5pt; FONT-FAMILY: 'Lucida Grande'">)</SPAN><SPAN
lang=EN-US>: 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.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>Volunteers<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>If you wish to participate in the Drafting
Team, please send an email to the GNSO Secretariat (</SPAN><A
href="mailto:gnso.secretariat@gnso.icann.org"><SPAN
lang=EN-US>gnso.secretariat@gnso.icann.org</SPAN></A><SPAN lang=EN-US>) by 05
July 2013. You will be required to complete a Statement of Interest in order to
participate.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>Background Information on the
Issues<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>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. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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 (</SPAN><A
href="http://www.icann.org/en/groups/board/documents/briefing-materials-1-08nov12-en.pdf"><SPAN
lang=EN-US>http://www.icann.org/en/groups/board/documents/briefing-materials-1-08nov12-en.pdf</SPAN></A><SPAN
lang=EN-US>) 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.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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: <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>Translation/transliteration may vary significantly across languages using
the same script.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>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.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>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?
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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:
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>The registrant submits the localized information as well the translated
or transliterated information. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>The registrant only submits the localized information, and the registrar
translates and transliterates all internationalized contact information on
behalf of the registrant.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>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.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>The registrant only submits the localized information, and the registry
provides translation or transliteration.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>The end users of the registration data translate and transliterate the
contact information.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>On 17 October 2012 the GNSO Council
requested an Issue Report to address the three issues that were identified by
the IRD-WG:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>Whether it is desirable to translate contact information to a single
common language or transliterate contact information to a single common
script.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>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.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>Whether to start a PDP to address these questions.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>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.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>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.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>Recommended Reading for
Volunteers<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>Final Issue Report on Translation and Transliteration of Contact
Information (</SPAN><A
href="http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13-en.pdf"><SPAN
lang=EN-US>http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13-en.pdf</SPAN></A><SPAN
lang=EN-US>). <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>Final Report of the Internationalized Registration Data Working Group
(</SPAN><A
href="http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf"><SPAN
lang=EN-US>http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf</SPAN></A><SPAN
lang=EN-US>).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>•<SPAN
class=apple-tab-span>
</SPAN>GNSO Working Group Guidelines, including charter guidelines (</SPAN><A
href="http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf"><SPAN
lang=EN-US>http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf</SPAN></A><SPAN
lang=EN-US>).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>Please let us know if you have any
questions.<BR>Thank you.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US>Kind regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN lang=EN-US>Glen<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="mso-fareast-language: fr">Glen de Saint Géry
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="mso-fareast-language: fr">GNSO Secretariat
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="mso-fareast-language: fr"><A
href="mailto:gnso.secretariat@gnso.icann.org">gnso.secretariat@gnso.icann.org</A>
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="mso-fareast-language: fr"><A
href="http://gnso.icann.org">http://gnso.icann.org</A><o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p></o:p> </P></DIV></DIV></DIV></DIV></BODY></HTML>