<HTML xmlns="http://www.w3.org/TR/REC-html40" 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 15 (filtered medium)">
<STYLE><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
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:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0cm;
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Century Gothic","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=EN-US dir=ltr link=blue vLink=purple>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>As to question #1 the answer of the Thailand GAC member provides good input
re the issues behind. One common language and one common script would be
comfortable if – at least for the majority of cases – non-ambiguity could be
guaranteed. Are there experts for the different languages/scripts to answer this
question?</DIV>
<DIV>There may be additional criteria to be looked at.</DIV>
<DIV> </DIV>
<DIV><BR>Best regards<BR><BR>Wolf-Ulrich<BR><BR></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=c.dillon@ucl.ac.uk
href="mailto:c.dillon@ucl.ac.uk">Dillon, Chris</A> </DIV>
<DIV><B>Sent:</B> Tuesday, February 25, 2014 4:19 PM</DIV>
<DIV><B>To:</B> <A title=gnso-contactinfo-pdp-wg@icann.org
href="mailto:gnso-contactinfo-pdp-wg@icann.org">gnso-contactinfo-pdp-wg@icann.org</A>
</DIV>
<DIV><B>Subject:</B> [gnso-contactinfo-pdp-wg] RE: Input Request:Translation and
Transliteration of Contact Information Charter Questions</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>Dear
colleagues,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>I have added
this Thai letter to <A
href="https://community.icann.org/display/tatcipdp/List+of+correspondence+received">https://community.icann.org/display/tatcipdp/List+of+correspondence+received</A>
. Please have a critical look at it and make any comments either before the
meeting on this list or during agenda point 4: <A
href="https://community.icann.org/display/tatcipdp/27+February+2014">https://community.icann.org/display/tatcipdp/27+February+2014</A>
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>I have added
the two main questions (and sub-questions) from the charter for your convenience
and for discussion under agenda point 5. We will be considering the
prioritization of the questions.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>Breaking
difficult questions into several easier ones is only one possible working
methodology and we are open to other approaches. Again, please make any comments
either before the meeting or during agenda point 6.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>Although at
least one of the Study for the Submission and Display of Internationalized
Contact Data’s surveys has been opened, they will be raised under AOB for any
comments.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>Regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>Chris.<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>--<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'>Research
Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St,
London WC1E 6BT Tel +44 20 7679 1599 (int 31599)
ucl.ac.uk/dis/people/chrisdillon<o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style='FONT-FAMILY: "Century Gothic","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<DIV>
<DIV
style="BORDER-TOP: #e1e1e1 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0cm; PADDING-TOP: 3pt; PADDING-LEFT: 0cm; BORDER-LEFT: medium none; PADDING-RIGHT: 0cm">
<P class=MsoNormal><B><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'>From:</SPAN></B><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'>
owner-gnso-contactinfo-pdp-wg@icann.org
[mailto:owner-gnso-contactinfo-pdp-wg@icann.org] <B>On Behalf Of </B>Glen de
Saint Géry<BR><B>Sent:</B> 25 February 2014 09:46<BR><B>To:</B>
gnso-contactinfo-pdp-wg@icann.org<BR><B>Subject:</B> [gnso-contactinfo-pdp-wg]
TR: Input Request:Translation and Transliteration of Contact Information Charter
Questions<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p></o:p> </P>
<P class=MsoNormal><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'>FYI<o:p></o:p></SPAN></P>
<P class=MsoNormal><A name=_MailEndCompose></A><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<DIV>
<DIV
style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0cm; PADDING-TOP: 3pt; PADDING-LEFT: 0cm; BORDER-LEFT: medium none; PADDING-RIGHT: 0cm">
<P class=MsoNormal><B><SPAN lang=FR
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"'>De :</SPAN></B><SPAN
lang=FR style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"'> Wanawit
Ahkuputra <BR><B>Envoyé :</B> mardi 25 février 2014 10:22<BR><B>À :</B> Glen de
Saint Géry<BR><B>Cc :</B> <A
href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</A>; Lars Hoffmann; GAC
Secretariat; Hugh Thaweesak Koanantakool; Pitinan<BR><B>Objet :</B> Re: Input
Request:Translation and Transliteration of Contact Information Charter
Questions<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P>
<P><SPAN lang=FR>Dear GNSO Secretariat;<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<P><SPAN lang=FR>Reference made to your letter on 5 February 2014: Input
Request: Translation and Transliteration of Contact Information Charter
Questions. On the role of our official position as the GAC Representative
of Thailand to ICANN and Deputy Executive Director of Electronic
Transaction Development Agency, Ministry of Information and Technology, Royal
Thai Government; and also the fact that we had been participated as
individual memberer in Charter Drafting Team of Translation and Transliteration
of Contact Information PDP working group. We would like to give some thoughts
and express our opinions on this issue for the Working Group as
follow:<o:p></o:p></SPAN></P>
<P><STRONG><U><SPAN lang=FR>Input Request</SPAN></U></STRONG><SPAN
lang=FR><o:p></o:p></SPAN></P>
<P><STRONG><SPAN lang=FR>Translation and Transliteration of Contact Information
Charter Questions</SPAN></STRONG><SPAN lang=FR><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<P><STRONG><SPAN lang=FR>Whether it is desirable to translate contact
information to a single common language or transliterate contact information to
a single common script.</SPAN></STRONG><SPAN lang=FR><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><EM><SPAN lang=FR>Reference from <A
href="http://www.academia.edu/3830294/English_as_a_Lingua_Franca_in_Thailand_Characterisations_and_Implications">http://www.academia.edu/3830294/English_as_a_Lingua_Franca_in_Thailand_Characterisations_and_Implications</A></SPAN></EM><SPAN
lang=FR><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <EM>“ Given that Thailand does not have a
history of colonisation by the British and that English is not an official
language in the country, Thailand is typically classified as an ‘expanding
circle’ country (Kachru, 2005) in which English is used as a means of
intercultural communication. Importantly such a classification also entails that
Thailand is a norm dependent country which does not have its own variety of
English and which does not use English for intra cultural communication. While
the extent to which this classification of English in Thailand will be
questioned in this paper, the expanding circle tag serves as a useful, if
simplified, means for distinguishing Thailand from countries which use English
as a first language, or as an official second
language.</EM><o:p></o:p></SPAN></P></DIV>
<P><EM><SPAN lang=FR>The linguistic landscape of Thailand is often portrayed as
monolingual and highly homogenous with government sources claiming that almost
100% of the population speak standard Thai (National Identity Board, 2000). As
might be expected this hides a more complex linguistic picture. Other languages
including Chinese, Malay, Lao, and Khmer are also spoken by minority groups
(National Identity Board, 2000; Foley, 2005) and the majority of the population
use one of the four regional dialects of Thai rather than standard Thai (Simpson
and Thammasathien 2007).</SPAN></EM><SPAN lang=FR><o:p></o:p></SPAN></P>
<P><EM><SPAN lang=FR>Nevertheless, given the relatively minor status given to
other languages in the country, English forms the ‘de facto’ second language of
Thailand. There are a number of domains in which English is widely used in
Thailand including: as a compulsory subject in school and in higher education,
as a medium of instruction in international education programs, as the language
of international organisations and conferences (including ASEAN and ASEAN +3),
for international business transactions, tourism, the internet, global
advertising, scientific and technology transfer, media (including imported films
and music), international safety and international law(Wongsatorn et al 1996;
2003; Foley, 2005)”</SPAN></EM><SPAN lang=FR><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR>From the reference, even English has given the
relatively minor status and not being used for intracultural communication,
English, however, is the 'de facto' for intercultural communication and
international business transactions including the internet. Therefore, It is
quite clear that it is desirable to translate contact information to a single
common language or transliterate contact information to a single common script
and preferable in English.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<P><STRONG><SPAN lang=FR>What exactly the benefits to the community are of
translating and/or transliterating contact information, especially in light of
the costs that may be connected to translation and/or
transliteration?</SPAN></STRONG><SPAN lang=FR><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR>As the result of using single official language
system, most of the contact information used is in Thai and the translating
and/or transliterating of contact information form Thai to English has been
loosely handling by applicants or data owners. Several government entities
handling English contact information by accepting the information given by data
owners per se, therefore, it is possible that the English contact information is
inconsistent.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR>In other cases which government bodies need to
provide English contact information such as the geographical name of a street.
There are several related standards such as 'Romanization' by Royal
Institute, 'the list of exception or reserved words' by geographical name
committee. The result of adopting these standards appears in the list of
geographical names for places in Thailand in UNGEGN (United Nations Group of
Experts on Geographical Names). However, the standards are not widely known and
it is not mandatory to adopt. Therefore, it is possible that each
government entity could use different method for translation and/or
transliteration.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<P><SPAN lang=FR>From the stated current condition, if the contact information
needs validation, it could be a burden trying to figure out the suitable
reference, if any. We have no objection with the approach from the Translation
and Transliteration of Whois Contact Information DPD Working Group that this
issue is tightly related to the role of government. Currently we are under the
consideration to provide the infrastructure for translation and/or
transliteration as the single registry system. This approach could benefit as in
the most accurate reference for contact information in English and the
validation could be handled at the most economic cost.<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<P><STRONG><SPAN lang=FR>Should translation and/or transliteration of contact
information be mandatory for all gTLDs?</SPAN></STRONG><SPAN
lang=FR><o:p></o:p></SPAN></P>
<P><SPAN lang=FR>We support that it should be mandatory. From the statistic,
around one-third of the domain names in Thailand registered with ccTLD (.th) and
anther two-third of the names are gTLD, which is open to all ICANN's registrars.
Many cases that Thai domain owner registers for a domain name from foreign
registrar, as the nature of internet is borderless. Not having translation
and/or transliteration mandatory for all gTLD would create discrimination to
registries and registrars.<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR>However to minimize the impact to the cost
bearer, the translation and/or transliteration of local language to common
language should be established in each country. And this methodology should be
accredited by ICANN.<o:p></o:p></SPAN></P></DIV>
<P><SPAN lang=FR><o:p></o:p></SPAN> </P>
<P><STRONG><SPAN lang=FR>Should translation and/or transliteration of contact
information be mandatory for all registrants or only those based in certain
countries and/or using specific non-ASCII scripts?</SPAN></STRONG><SPAN
lang=FR><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR>It is unarguable that the translation and/or
transliteration should be mandatory for those cased based in non-ASCII script
countries. So it is possible that the non-ASCII script countries have higher
priority to catalyst this issue.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<P><STRONG><SPAN lang=FR>What impact will translation/transliteration of contact
information have on the WHOIS validation as set out under the 2013 Registrar
Accreditation Agreement?</SPAN></STRONG><SPAN lang=FR><o:p></o:p></SPAN></P>
<P><SPAN lang=FR>Reference to section: Whois Accuracy Program Specification
§1(e),<o:p></o:p></SPAN></P>
<P><EM><SPAN lang=FR>"Validate that all postal address fields are consistent
across fields (for example: street exists in city, city exists in
state/province, city matches postal code) where such information is technically
and commercially feaible for the applicable country or
territory."</SPAN></EM><SPAN lang=FR><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR>This could draw to the question of who would
make the decision if a country or territory is technically and commercially
feasible and what would be the decision making criteria. As the validation of
all postal address both newly registered and the backlog could be costly,
it might turn out that not many territories or countries is feasible to
comply.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<P><SPAN lang=FR>Reference to section: Whois Accuracy Program Specification
§1(f) and §2<o:p></o:p></SPAN></P>
<P><EM><SPAN lang=FR>"if Registrar does not receive an affirmative response from
the Account Holder, Registrar shall verify the applicable contact information
manually"</SPAN></EM><SPAN lang=FR><o:p></o:p></SPAN></P>
<P><SPAN lang=FR>It occurs in Thailand that more than half of the domain name
owners using gTLD and it is possible to choose foreign Registrars. The manual
verification might occur when registrar does not receive an affirmative response
via email or phone. Even it is not specified the method, this manual
verification could costly for Registrar when it is cross-border
verification. This also emphasizes the need of single point of
registration system for common language/script of contact information for each
country. To minimize any cost that might occur during verification, and the more
important point is to provide the eligible contact address
information.<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<P><STRONG><SPAN lang=FR>When should any new policy relating to translation and
transliteration of contact information come into effect?</SPAN></STRONG><SPAN
lang=FR><o:p></o:p></SPAN></P>
<P><SPAN lang=FR>(Reference: <A
href="http://docs.apwg.org/reports/APWG_GlobaTolPhishingSurvey_1H2013.pdf">http://docs.apwg.org/reports/APWG_GlobaTolPhishingSurvey_1H2013.pdf</A>)<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>Thailand has been, disappointedly, in the top-5 of phishing for
the past several years. From our view, we see that having translation and
transliteration pocily in place would be one of the phishing mitigations as the
verified contact information would be the important eligible linkage between
internet identities to the real person. We encourage that this policy should
come into effect at the earliest possible timeline.<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<P><STRONG><SPAN lang=FR>Do you have suggestions concerning the basic principles
to guide the cost burden discussion, such as the free of charge provision of the
information, demand-oriented cost etc.? In particular, the PDP WG is
tasked with determining 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.</SPAN></STRONG><SPAN lang=FR><o:p></o:p></SPAN></P>
<P><SPAN lang=FR>In compliance with the "Proposal by THAILAND’s Government
Advisory Committee (GAC)" submitted into the PDP working group earlier, it is
government role to facilitate establishment of the infrastructure for
translation/transliteration of contact information. Once the infrastructure is
in place, the cost of translation/transliteration and the cost of validation
should be economic. This eligible registered contact address information will
also be applicable for many other applications for data owner, not limited to
ICANN whois database but it could also benefit the e-invoice and all electronic
transaction services.<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>We would suggest considering demand-oriented approach for this
matter. In this case, the demand to translate/transliterate and maintain contact
address information is belong to the data owners or registrants, and the demand
for address validation could be from registrars. Therefore, the cost of
conversion from local language into common language should belong to registrants
and the cost for validation should belong to registrars.<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P></DIV>
<P><SPAN lang=FR>We are looking forward to gather for a face-to-face meeting
during the ICANN Meeting in Singapore.<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<P><SPAN lang=FR>Regards<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<P><SPAN lang=FR>Mr. Wanawit Ahkuputra<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>Deputy Executive Director <o:p></o:p></SPAN></P>
<P><SPAN lang=FR>ETDA Electronic Transactions Development Agency (Public
Organization)<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>MICT Ministry of Information and Communication
Technology<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=FR> <o:p></o:p></SPAN></P>
<P><SPAN lang=FR>The Government Complex Commemorating His Majesty the King's
80th Birthday Anniversary<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>120 M.3 Ratthaprasasanabhakti Building (building
B),<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>7th floor, Chaengwattana Rd., Thung Song
Hong,<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>Laksi Bangkok 10210, THAILAND<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>Tel : +66 2142 1159<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>Fax. +66 2143 8071<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>Mobile +669 301 8818<o:p></o:p></SPAN></P>
<P><SPAN lang=FR>E-Mail: <A
href="mailto:wanawit@etda.or.th">wanawit@etda.or.th</A><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=FR><o:p></o:p></SPAN> </P></DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR>On Feb 5, 2557 BE, at 5:35 AM, Glen de Saint
Géry <<A href="mailto:Glen@icann.org">Glen@icann.org</A>>
wrote:<o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
lang=FR><o:p></o:p></SPAN> </P>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>Dear GAC
representative, dear <SPAN
style="BACKGROUND: white">Thaweesak</SPAN></SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'> </SPAN><SPAN
lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>As you may be
aware, the GNSO Council recently initiated a<SPAN
class=apple-converted-space> </SPAN></SPAN><SPAN lang=FR
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'><A
href="http://gnso.icann.org/en/basics/pdp-process.htm"><SPAN lang=EN-US
style="COLOR: purple">Policy Development Process</SPAN></A></SPAN><SPAN
class=apple-converted-space><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'> </SPAN></SPAN><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>(PDP) on the
Translation and Transliteration of Contact Information; the relevant<SPAN
class=apple-converted-space> </SPAN></SPAN><SPAN lang=FR
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'><A
href="http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13-en.pdf"><SPAN
lang=EN-US style="COLOR: purple">Issue Report can be found
here</SPAN></A></SPAN><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>. A more<SPAN
class=apple-converted-space> </SPAN></SPAN><SPAN lang=FR
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'><A
href="https://community.icann.org/x/eTOfAg"><SPAN lang=EN-US
style="COLOR: purple">detailed background</SPAN></A></SPAN><SPAN
class=apple-converted-space><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'> </SPAN></SPAN><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>is available
online on the<SPAN class=apple-converted-space> </SPAN></SPAN><SPAN lang=FR
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'><A
href="https://community.icann.org/display/tatcipdp/Translation+and+Transliteration+of+Contact+Information+PDP+Home"><SPAN
lang=EN-US style="COLOR: purple">Working Group’s Wiki</SPAN></A></SPAN><SPAN
class=apple-converted-space><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'> </SPAN></SPAN><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>where you can
also consult the<SPAN class=apple-converted-space> </SPAN></SPAN><SPAN
lang=FR style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'><A
href="https://community.icann.org/display/ITPIPDWG/3.+WG+Charter"><SPAN
lang=EN-US style="COLOR: purple">Charter</SPAN></A></SPAN><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>. As part of its
efforts to obtain broad input from the ICANN Community at an early stage and we
have written to Ms Heather Dryden, Chair of the GAC, already to solicit feedback
from the GAC where possible.</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'> </SPAN><SPAN
lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>However, as the
matter of translating and/or transliteration of Contact information will be of
special significance for countries that do not use Latin Scripts, we thought it
useful to contact individual GAC representatives. Please note that we do not
seek an official position on this matter but rather would welcome any thoughts
and/or experiences you might have and what the best practice might be or ought
to be in your country on this matter. An informal response to any of the
questions below or any other thoughts you might have on the issue of translation
and transliteration of Contact Information would be very much appreciated.
Please send these to the GNSO Secretariat (</SPAN><SPAN lang=FR
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'><A
href="mailto:gnso.secretariat@gnso.icann.org"><SPAN lang=EN-US
style="TEXT-DECORATION: none; COLOR: purple">gnso.secretariat@gnso.icann.org</SPAN></A></SPAN><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>) who will
forward these to the Working Group; ideally by Tuesday 11 March
2014.</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'> </SPAN><SPAN
lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>Finally, our
Working Group is planning to gather for a face-to-face meeting during the
forthcoming ICANN Meeting in Singapore. We would be delighted if you could join
our discussions should you be in Singapore at the time. We will renew this
invitation closer to the time when we have finalized our meeting time and
agenda.</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'> </SPAN><SPAN
lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"'>Many thanks and
best wishes,</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'> </SPAN><SPAN
lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>Chris
Dillon (Co-Chair)</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>Rudi
Vansnick (Co-Chair)</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'> </SPAN><SPAN
lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 10pt"><B><U><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>Input
Request</SPAN></U></B><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 10pt"><B><SPAN
style='FONT-SIZE: 11.5pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>Translation
and Transliteration of Contact Information Charter Questions</SPAN></B><SPAN
lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 16pt; MARGIN-LEFT: 36pt; MARGIN-RIGHT: 0cm; TEXT-INDENT: -18pt; mso-margin-top-alt: 0cm"><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>Whether
it is desirable to translate contact information to a single common language or
transliterate contact information to a single common script.</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 16pt; MARGIN-LEFT: 36pt; MARGIN-RIGHT: 0cm; TEXT-INDENT: -18pt; mso-margin-top-alt: 0cm"><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>What
exactly the benefits to the community are of translating and/or transliterating
contact information, especially in light of the costs that may be connected to
translation and/or transliteration?</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 16pt; MARGIN-LEFT: 36pt; MARGIN-RIGHT: 0cm; TEXT-INDENT: -18pt; mso-margin-top-alt: 0cm"><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>Should
translation and/or transliteration of contact information be mandatory for all
gTLDs?</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 16pt; MARGIN-LEFT: 36pt; MARGIN-RIGHT: 0cm; TEXT-INDENT: -18pt; mso-margin-top-alt: 0cm"><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>Should
translation and/or transliteration of contact information be mandatory for all
registrants or only those based in certain countries and/or using specific
non-ASCII scripts?</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 16pt; MARGIN-LEFT: 36pt; MARGIN-RIGHT: 0cm; TEXT-INDENT: -18pt; mso-margin-top-alt: 0cm"><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>What
impact will translation/transliteration of contact information have on the WHOIS
validation as set out under the 2013 Registrar Accreditation
Agreement?</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 16pt; MARGIN-LEFT: 36pt; MARGIN-RIGHT: 0cm; TEXT-INDENT: -18pt; mso-margin-top-alt: 0cm"><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #313131'>When
should any new policy relating to translation and transliteration of contact
information come into effect?</SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 16pt; MARGIN-LEFT: 36pt; MARGIN-RIGHT: 0cm; TEXT-INDENT: -18pt; mso-margin-top-alt: 0cm"><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'>Do you have
suggestions concerning the basic principles to guide the cost burden discussion,
such as the free of charge provision of the information, demand-oriented cost
etc.? In particular, the PDP WG is tasked with determining<SPAN
class=apple-converted-space> </SPAN><SPAN style="COLOR: #313131">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.</SPAN></SPAN><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'> </SPAN><SPAN
lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'>Glen de Saint
Géry<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'>GNSO
Secretariat<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><A
href="mailto:gnso.secretariat@gnso.icann.org"><SPAN
style="COLOR: purple">gnso.secretariat@gnso.icann.org</SPAN></A><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=FR
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'><A
href="http://gnso.icann.org/"><SPAN
style="COLOR: purple">http://gnso.icann.org</SPAN></A><o:p></o:p></SPAN></P></DIV></DIV></DIV>
<P class=MsoNormal><SPAN
lang=FR><o:p></o:p></SPAN> </P></DIV></DIV></DIV></DIV></BODY></HTML>