<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" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;
color:black;}
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;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Century Gothic",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Century Gothic",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext">Dear Volker,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext">Thank you for your comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext">In a future hypothetical situation where there was a DNRD in which contact information was stored in many scripts and the information was not transformed into ASCII/English,
syntactic validation would be more difficult than the current situation, as many scripts would be involved. If transformed contact information were to be validated, the situation would be even more difficult because of the lack of (or in some cases the availability
of several) transliteration systems. I don’t think operational or identity validation would be affected.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext">(Further information: 2013 RAA. WHOIS Accuracy Program specification p.1 and
<a href="https://community.icann.org/display/tatcipdp/8+Verification+and+Validation">
https://community.icann.org/display/tatcipdp/8+Verification+and+Validation</a> )<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext">Chris.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext">Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599)
<a href="http://www.ucl.ac.uk/dis/people/chrisdillon"><span style="color:#0563C1">www.ucl.ac.uk/dis/people/chrisdillon</span></a>
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Century Gothic",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> Volker Greimann [mailto:vgreimann@key-systems.net]
<br>
<b>Sent:</b> 28 November 2014 14:58<br>
<b>To:</b> Pitinan Kooarmornpatana; Dillon, Chris; zhangzuan@conac.cn<br>
<b>Cc:</b> gnso-contactinfo-pdp-wg@icann.org; Chaichana Mitrpant; Werachai Prayoonpruk; Kriangkrai Charernroy; Ariya Nunnual; Thiphonphan Uthaithat<br>
<b>Subject:</b> Re: [gnso-contactinfo-pdp-wg] Straw poll on number of options<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Jumping in here, just to say that under the 2013 RAA the validation of contact info is already mandatory for registrars, requiring them to validate all required fields are present and that all data conforms
to the right format. So I am not sure where you are leading with this issue that I see as completely out of scope for this WG.
<br>
<br>
As an aside, validation is a completely useless exercise and waste of time and money as any criminal will just need to reach for the next phone book for a list of perfectly accurate verifyable contact details. As a registrar, I feel comfortable stating that
this is now the norm for abusive registrations and there is no way to prevent this with any amount of validation.<br>
<br>
Best,<br>
<br>
Volker<br>
Am 28.11.2014 05:05, schrieb Pitinan Kooarmornpatana:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Dear all,
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Hope this is not too late to cast my vote.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">My quick answer is
<b><i>"Yes - we should have one option" </i></b></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">that option is
<b><i>"Mandatory (..to have the trustable contact info)"</i></b></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">However, in my humble opinion, it is not mandatory to "transform the contact info" but Mandatory to "validate the contact info"</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">As much as I bear in mind that the validate-or-not is out of the scope of our WG’s scope, but I found it's very hard making decision of this two functions separately.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Kindly let me try to explain.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">-----------------------------</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">I think we do agree that:
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">-----------------------------</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">1. ICANN principle of non-discrimination and reach-out will always allow registrants to input the contact-info in local language – which is good,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">2. the validated contact info is preferable,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">3. there will surely be cost associated to the one who do the validation. But, the validation is much cheaper or even only-possible when using contact info in
local-script, and using local validator (like Thailand Post validating any Address in Thailand),</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">4. once the contact-info in local script is validated, then it is not too troublesome to 'transform' into any language, either using tool or human-translator for
quick understanding purpose or the first clue to contact the entity. And when you need to act any legal action to the entity you will need the legal document in local script or legally-notarized-translated version anyway.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">5. it is quite promising that ICANN approach of improving whois information will include the validating too.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">6. Lastly, internet is all connected, any critical rule or policy should apply to all (mandatory) across the globe to avoid the loophole of the internet governance.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">-----------------------------------------------------------------------------------------------------------</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">From points above, the answer of transforming-or-not depends on how we do validation.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">----------------------------------------------------------------------------------------------------------</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Scenario1: The contact info must be validated by local validator
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> --> then there is no need to transform</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Scenario2: The contact info could be validated by non-local validator
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> --> then it must be transformed in the standardized way so the non-local validator can perform
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Scenario3: There is no need to validate contact information
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> --> then there is no need to do anything… it’s trash in – trash out</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">---------------</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">In Summary</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">---------------</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">I believe that it will likely to be scenario1 – trustable data, not so costly</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">That’s why I would say,
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:18.0pt"><b><i><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Yes, there should be one option,
</span></i></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:18.0pt"><b><i><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">If is mandatory to validate the contact info, There is no need to transform the script.</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">-------------</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Thank you and Very Best Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#404040">Pitinan Kooarmornpatana</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#404040">Director of Information Infrastructure Office</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#404040"> </span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#404040">Electronic Transactions Development Agency (ETDA)
<br>
T: 02-123-1234, F: 02-123-1200</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#404040">+(66) 81 375 3433
</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#404040">pitinan at etda.or.th</span></b><o:p></o:p></p>
</blockquote>
<pre><o:p> </o:p></pre>
</div>
</body>
</html>