<html 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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="en-NO" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Olivier,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks for the questions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I have problems responding to your question “But why is ICANN not pursuing such complaints where there is domain hijacking?” In my view/understanding, the metrics from ICANN Compliance for “unathorized transfers”
cannot be counted as potential domain hijacking. I recommend listen to the recordings from the GNSO-TPR meeting on Jan 30, 2024 where ICANN Compliance present the metrics.
<a href="https://community.icann.org/display/TPRPDP/2024-01-30+Transfer+Policy+Review+PDP+WG+Call">
https://community.icann.org/display/TPRPDP/2024-01-30+Transfer+Policy+Review+PDP+WG+Call</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The high number in 2021 is connected to termination of an accredited Registrar.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I hope this help understanding the metrics.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Steinar Grøtterød<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">Olivier MJ Crépin-Leblond <ocl@gih.com><br>
<b>Date: </b>Saturday, 6 April 2024 at 02:38<br>
<b>To: </b>Steinar Grøtterød <steinar@recito.no>, CPWG <cpwg@icann.org><br>
<b>Subject: </b>Re: [CPWG] Resending Transfer Complaint metrics<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thanks for this, Steinar.<br>
<br>
Looking at the table, there are indeed many reasons why the complaints be closed as invalid, with a very small amount (15) in the period covered by 2023 and even less before. But why is ICANN not pursuing such complaints where there is domain hijacking? Are
there other avenues an end user would follow for this?<br>
<br>
My other question relating to this topic is why 2021 was a huge year for transfer related complaints being received. And an even larger number for Transfer Complaints Closed. That year, barely 6% of complaints were passed on to the Contracted Party.<br>
Did procedures change since?<br>
<br>
Kindest regards,<br>
<br>
Olivier</p>
<div>
<p class="MsoNormal">On 04/04/2024 10:27, Steinar Grøtterød via CPWG wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear CPWG,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">During the CPWG discussion on the Change of Registration data (CORD) on April 3, 2024, a question was asked in the chat about metrics connected to domain hijacking.
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I have attached data given by ICANN Compliance for the periode Sep 2020-Oct 2023 that include unauthorised transfers. This metrics was given to the GNSP-TPR working group as information when the working group
discussed the CORD policy.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I hope this metric is ansers some questions. My understanding is that “domain hijacking” is not necessary tracked by ICANN Compliance. Registrars also reports a low number of unauthorised transfers.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Regards,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Steinar Grøtterød</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________</pre>
<pre>CPWG mailing list</pre>
<pre><a href="mailto:CPWG@icann.org">CPWG@icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cpwg">https://mm.icann.org/mailman/listinfo/cpwg</a></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________</pre>
<pre>By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>-- </pre>
<pre>Olivier MJ Crépin-Leblond, PhD</pre>
<pre><a href="http://www.gih.com/ocl.html">http://www.gih.com/ocl.html</a></pre>
</div>
</div>
</div>
</body>
</html>