<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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",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:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@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-CA link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Thanks, Caitlin, Berry, Julie, and Emily!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Based on (a) it has “hold” in the name, and (b) the description “that “Registrar Hold” removes the name from the zone and causes it not to resolve”, and (c) we know that EPP statuses with “client” in the name are applied by the Registrar, it sounds like Registrar Hold was intended to be the same as Client Hold. </p><p class=MsoNormal><o:p> </o:p></p><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><span style='font-family:"Verdana",sans-serif'>-- <o:p></o:p></span></pre><pre><b><span style='font-family:"Verdana",sans-serif'>Sarah Wyld</span></b><span style='font-family:"Verdana",sans-serif'>, CIPP/E<o:p></o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'><o:p> </o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'>Policy & Privacy Manager<o:p></o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'>Pronouns: she/they<o:p></o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'><o:p> </o:p></span></pre><pre><a href="mailto:swyld@tucows.com"><span style='font-family:"Verdana",sans-serif'>swyld@tucows.com</span></a><span style='font-family:"Verdana",sans-serif'> <o:p></o:p></span></pre><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><img border=0 width=100 height=24 style='width:1.0416in;height:.25in' id="Picture_x0020_3" src="cid:image001.png@01D83207.759AD1B0"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:emily.barabas@icann.org">Emily Barabas</a><br><b>Sent: </b>March 3, 2022 1:57 PM<br><b>To: </b><a href="mailto:gnso-tpr@icann.org">gnso-tpr@icann.org</a><br><b>Subject: </b>[GNSO-TPR] Staff Action Item: Origins of language in 1.A.3.7.3</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Dear Working Group members,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Following Tuesday’s WG call, staff had an action item to research the origins of the following sentence, in bold, included in one of the reasons that a transfer may be denied:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='mso-fareast-language:EN-US'>1.A.3.7.3: </span></i><i><span style='mso-fareast-language:EN-US'>No payment for previous registration period (including credit card charge-backs) if the domain name is past its expiration date or for previous or current registration periods if the domain name has not yet expired. <b>In all such cases, however, the domain name must be put into "Registrar Hold" status by the Registrar of Record prior to the denial of transfer.<o:p></o:p></b></span></i></p><p class=MsoNormal><b><i><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></i></b></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>This sentence appears in the 2002 </span><span style='mso-fareast-language:EN-US'><a href="http://www.dnso.org/dnso/notes/20030212.NCTransferTF-gaining-and-losing-registrars.html"><span style='color:#0563C1'>ICANN DNSO Transfers Task Force Final Report & Recommendations</span></a></span><span lang=EN-US style='mso-fareast-language:EN-US'>, under recommendation 24. In the Report section Other Observations and Considerations, the following additional text is included “9. It is recommended that the Losing Registrar use the EPP or RRP command set equivalent of “Registrar Hold” prior to receiving a transfer notification from the Registry as a mechanism to secure payment from a Registrant in the event of non-payment. The Losing Registrar should not use the EPP or RRP command set equivalent of “Registrar Lock” for this same purpose.”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>We found some additional discussion on page 13 of the 2008 <a href="https://gnso.icann.org/sites/default/files/filefield_6444/final-report-irt-policy-09apr08.pdf"><span style='color:#0563C1'>GNSO Final Report on Inter-Registrar Transfer Policy:</span></a></span><span class=MsoHyperlink><span style='color:#0563C1;mso-fareast-language:EN-US'><o:p></o:p></span></span></p><p class=MsoNormal><span class=MsoHyperlink><span lang=EN-US style='color:#0563C1;mso-fareast-language:EN-US'><a href="https://gnso.icann.org/sites/default/files/filefield_6444/final-report-irt-policy-09apr08.pdf"><span style='color:#0563C1'>Clarification of Reasons for Denial</span></a></span></span><span lang=EN-US style='mso-fareast-language:EN-US'>, which was carried over from the Issue Report: “"4.2.8 The current provision in the Inter-Registrar Transfer Policy also provides that prior to denying any transfer requests for non-payment under this clause, a registrar must have placed the domain name on “Registrar Hold” status. This does not appear to be the usual practice, with many registrars using “Registrar Lock” status instead. It should be noted that “Registrar Hold” removes the name from the zone and causes it not to resolve, while a name in “Registrar Lock” may continue to function but will not be able to be transferred. As part of the discussion regarding this provision, it may be helpful to consider whether one is preferable to the other in instances of nonpayment.” It does not appear that the subsequent policy development work resulted in any changes to the language referenced above. </span><span style='mso-fareast-language:EN-US'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Please let us know if you have any questions.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Kind regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Caitlin, Berry, Julie, and Emily<o:p></o:p></span></p><p class=MsoNormal><b><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></b></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>Emily Barabas</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>Policy Development Support Senior Manager</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>Internet Corporation for Assigned Names and Numbers (ICANN)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>Phone: +31 (0)6 84507976</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><a href="http://www.icann.org/" title="http://www.icann.org/"><span style='color:#0563C1'>www.icann.org</span></a></span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p></div><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p></div></body></html>