<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1026835659;
mso-list-template-ids:-418763504;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:2001883276;
mso-list-type:hybrid;
mso-list-template-ids:-410458606 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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 lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Firstly, I’m so sorry for the delay in responding and many thanks to all the Staff for taking this on for me - I’m very grateful. And at the risk of becoming a phantom, also apologies for the
1<sup>st</sup> meeting this afternoon: it clashes with the GAC-GNSO joint session.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I’ve made some comments inline below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">And to comment briefly on the “support” thread: I’m from the BC. I’m of course not representing the BC in this WG – I’m 100% here for my employer – but I hope this goes to show that no one member
of this WG speaks for the BC (indeed, for any C/SG) so that can’t be a “support measure” IMO.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thanks again<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Marie <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><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 lang="EN-US" style="font-size:11.0pt">From:</span></b><span lang="EN-US" style="font-size:11.0pt"> Ariel Liang <<a href="mailto:ariel.liang@icann.org">ariel.liang@icann.org</a>>
<br>
<b>Sent:</b> Monday, October 15, 2018 5:32 PM<br>
<b>To:</b> Marie Pattullo <<a href="mailto:marie.pattullo@aim.be">marie.pattullo@aim.be</a>><br>
<b>Cc:</b> Mary Wong <<a href="mailto:mary.wong@icann.org">mary.wong@icann.org</a>>; Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>>; Berry Cobb Mail <<a href="mailto:mail@berrycobb.com">mail@berrycobb.com</a>><br>
<b>Subject:</b> URS Proposal #13 - WG Comments & Questions <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Hello Marie, <o:p>
</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">We hope this email finds you well.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Staff helped present your proposal #13 to the WG during its 10 Oct meeting. You may reference
<b>page 28-35</b> of <a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/transcript-rpm-review-10oct18-en.pdf">
transcript</a> and <b>page 9-13</b> of the <a href="https://community.icann.org/download/attachments/95095467/Attendance%20%26%20AC%20chat%20RPM%2010%20Oct%202018.pdf?version=1&modificationDate=1539210143000&api=v2">
AC chat record</a> for the full record of discussion of your proposal. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Some WG members supported your proposal, while some opposed and/or expressed concerns. We have highlighted the WG’s
<u>questions</u>, <u>oppositions</u>, <u>suggestions</u> below. If you wish to respond, please be so kind to send your response via the WG mailing list. Thank you for your time and help!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Mary, Julie, Ariel & Berry
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">==<o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="color:red;mso-list:l1 level1 lfo3"><b><span lang="EN-US" style="font-size:11.0pt;color:windowtext">Michael Karanicolas:
</span></b><span lang="EN-US" style="font-size:11.0pt;color:windowtext">What is the evidence supporting the claim that a losing respondent is able to reregister a domain name once it becomes available? Does it happen often? (Staff’s data: Up to 2017, recall
one domain that was re-registered by the original registrant. The domain was dropped after suspension and seemed to be legit use. There were other domains that were dropped and re-registered by a different registrant. Not a huge % but still significant.)</span><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">
</span><span lang="EN-US" style="font-size:11.0pt">We based this on the comments in the Super Consolidated URS Topics Table, F(2)/Practitioners Sub-Team: “in some cases, a losing Respondent is able to re-register a domain once it becomes available”; “after
the lock, the cybersquatters just renew the domain name” – if it were an important enough concern to be in that Table, we thought it ought to be discussed further.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><b><span lang="EN-US" style="font-size:11.0pt">Kristine Dorrain:
</span></b><span lang="EN-US" style="font-size:11.0pt">Strong disagreement -<b> </b>
It's absolutely impossible to implement. You cannot distinguish between registrants even within a registry or registrar. There's evidence that there are cyber squatters that have thousands of new accounts with new identities, and they can hop from place to
place and even between registrars. How can those people be prevented from registering the domain name? Assuming a registrar/registry can identify a single customer (who hasn’t opened a new account), how would that information be included across hundreds of
registrars? As a complainant, let's say you win a URS and the domain is immediately re-registered. How will you know if the registrant is the same? How will you enforce this proposal? How would ICANN enforce this proposal?<span style="color:#1F497D">
</span><span style="color:red">We hadn’t gone into implementation, but in essence: we’d like to disrupt the business model of those who abuse the system – as we assume everyone here would, as it negatively affects us all! Could we consider the systematic verification
of a registrant’s data when they are trying to register a domain name that has been the subject of a URS where the Complainant prevailed? Connected to a common database of such cases to which all Registrars/Registries would have access?</span><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><b><span lang="EN-US" style="font-size:11.0pt">George Kirikos:</span></b><span lang="EN-US" style="font-size:11.0pt"> There's no registrant verification taking place, so it would be nearly impossible for
a registrar to handle it on their own, let alone having all registrars potentially block one registrant from registering the relevant domain name at the other registrar. How can we overcome these technical problems with regard to implementation? There is no
“know your client” requirement for registrars to know the registrant. Also, what if the WHOIS of the registrant is fake?<span style="color:#1F497D">
</span><span style="color:red">The lack of KYC and fake info are without doubt huge problems. Data accuracy is something I know we would all love to work towards.</span><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><b><span lang="EN-US" style="font-size:11.0pt">Maxim Alzoba:
</span></b><span lang="EN-US" style="font-size:11.0pt">There are two issues with this proposal. 1) It would create gaming concerns, as the registrant can simply use false contact information.<span style="color:red"> Wouldn’t it be great if they couldn’t...
But also – as said in the proposal – it could actually reduce gaming. (</span></span>“<span lang="EN-US" style="font-size:11.0pt;color:red">This would help to prevent gaming of the system and unnecessary cluttering of the providers’ workload with spurious
or vexatious cases”).</span><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">
</span><span lang="EN-US" style="font-size:11.0pt">2) For registrars, there is almost no way to identify the person behind it – it could be a good guys’ domain name that is stolen and used for bad things, and the registrars cannot share information with those
parties outside the law. There are no safeguards for the situation where trademark is no longer protected. There is no way to identify a bad guy before they do something fishy or before they follow a pattern.<span style="color:red"> They would have done here
– that’s exactly the point.</span> Maybe something limited could be implemented, such as limiting the registration of this domain name for one year.
<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><b><span lang="EN-US" style="font-size:11.0pt">Christine Farley:</span></b><span lang="EN-US" style="font-size:11.0pt"> If a registrant has been shown to have a bad faith in registering a domain, does it
mean that all future registrations will be in bad faith? Or might it be possible for that registrant to re-register that domain with a good faith in future?<span style="color:#1F497D">
</span><span style="color:red">Is that not a bit unrealistic? </span><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><b><span lang="EN-US" style="font-size:11.0pt">Griffin Barnet</span></b><span lang="EN-US" style="font-size:11.0pt">: Could perhaps link the registrant to his/her email address, payment info, or something
more unique to the actual registrant? <b>Maxim Alzoba:</b> Payment info does not propagate further than one registrar and potentially ICANN.<span style="color:red"> See idea above re a database.
</span><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><b><span lang="EN-US" style="font-size:11.0pt">Justine Chew</span></b><span lang="EN-US" style="font-size:11.0pt">: Could perhaps use a blacklist to identify "losing respondent" as named by that party itself,
even if they used false name, contact info etc.<span style="color:#1F497D"> </span>
<span style="color:red">Interesting.</span><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
</div>
</body>
</html>