<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Mike,<div class=""><br class=""></div><div class="">This is an issue that I (and the small team) spent a lot of time trying to reconcile: the desires of registrars to be able to deny transfers for registration agreement violations (which in theory could be something other than fraud or illegal or abusive, but still very objectionable), and those of NCSG (and myself) about being able to deny a transfer for any minor breach of the registration agreement. </div><div class=""><br class=""></div><div class="">We compromised and decided to include this implementation guidance in the report, which will need to be included in a final report (and thus form basis of any eventual policy): </div><div class=""><br class=""></div><div class=""><i class="">Implementation Guidance: The intent of “violation of the Registration Agreement” is not to allow the blocking of transfers due to minor violations, but to allow action in case of substantive contravention of the Registration Agreement. </i><br class=""><br class="">We also provided a rationale in the notes, which will also carry forward into the final report: </div><div class=""><br class=""></div><div class=""><i class="">The working group noted that such abusive activities typically constitute a violation of the Registration Agreement, and therefore by including “violation of the Registration Agreement” to the reasons that the Registrar of Record MAY deny a transfer, the Policy will explicitly permit denials in these circumstances. The Implementation Guidance provides additional “guardrails” to protect against denial of transfers for minor, inadvertent violations of the Registration Agreement. The Working Group notes that Registration Agreement violations have in the past formed the basis of formal ICANN Compliance enforcement relating to domain transfer. </i><br class=""><br class="">I pushed hard to ensure the guardrails, because of the referenced Compliance case. I cannot provide further details (as they remain confidential), but basically agreeing to the registration agreement (and its problematic wording) would have immediately subjected the registrant to breaching the agreement (and potentially losing the domain name). </div><div class=""><br class=""></div><div class="">With that in mind, here is a real world example of “violation of user agreement” that could result in denying a transfer rather than for evidence of fraud. As you may know, Namecheap has a large presence in Ukraine. Recently, a customer spewed horrific propaganda towards our support team, and after being asked several times to treat our team with respect and to transfer away, he continued to escalate the rhetoric. We suspended his account, and now he cannot transfer out his domains. We canceled the registration agreement, so this falls under non-Transfer Policy reasons, but this is a time when there was a clear violation of our registration agreement that could be used to deny a transfer. For the record, we disclosed this issue to ICANN because of the gray area in “denying” the Transfer (and they did not object). </div><div class=""><br class=""></div><div class="">Happy to discuss further, but we did want to put more than just “illegal” activities as a reason to deny transfers. I also note that “abuse” is generally defined as “DNS abuse” and not “being abusive to customer support”. </div><div class=""><br class=""></div><div class="">Regards,</div><div class=""><br class=""></div><div class="">Owen<br class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 10, 2022, at 14:49, Mike Rodenbaugh <<a href="mailto:mike@rodenbaugh.com" class="">mike@rodenbaugh.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I wish to raise a further issue wrt Reco 19, allowing registrars to deny a transfer for virtually any breach of the registration agreement.  Given that registrars can put just about anything they like into a registration agreement, and that they are given full discretion whether to judge whether the RNH is in some breach of it, I am concerned this is far too broad of a reason and far too much discretion for a registrar to deny a transfer.  <div class=""><br class=""></div><div class="">It seems to be a fairly radical change unless we can develop some restrictive language.  I think our intent was to allow greater freedom to stop transfers where there has been abuse, other than 'fraud'.  And that is a laudable goal that certainly the IPC supports.  So perhaps we should expand on 'fraud' but not so far as 'almost any breach of any provision of the registration agreement' (..., I am paraphrasing).  We could say "fraud or other illegal or abusive behavior", or something like that?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Mike<br class=""><div class=""><div class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div style="font-family:arial;font-size:small" class=""><span class=""><br class=""><div dir="ltr" style="margin-left:0pt" align="left" class=""><table style="border:none;border-collapse:collapse" class=""><colgroup class=""><col width="203" class=""><col width="86" class=""><col width="335" class=""></colgroup><tbody class=""><tr style="height:20.25pt" class=""><td rowspan="4" style="border-right:0.75pt solid rgb(0,133,61);vertical-align:middle;padding:5pt;overflow:hidden" class=""><div style="line-height: 1.38; text-align: center; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class=""><span style="border:none;display:inline-block;overflow:hidden;width:159px;height:95px" class=""><img alt="Logo" src="https://lh4.googleusercontent.com/S_Oxvn9Vep0rF8IVyiOnDwA4LymtHrWirggIxlsU26JihhEYDv5A5D03ZY0k_npND2t8xfiWCdTM5NTO_LSZMksjO_UlJm5IAP3FEi5cw96AwIPgVzvoOfHIux_qNA26n5UuxvQZ" width="159" height="95" style="margin-left:0px;margin-top:0px" class=""></span></span></div></td><td colspan="2" style="border-left:0.75pt solid rgb(0,133,61);vertical-align:top;padding:5pt;overflow:hidden" class=""><div style="line-height: 1.38; margin-left: 3.6pt; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size:12pt;font-family:Arial;color:rgb(0,133,61);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap" class="">Mike Rodenbaugh</span></div></td></tr><tr style="height:18pt" class=""><td style="vertical-align:top;padding:5pt;overflow:hidden" class=""><div style="line-height: 1.38; margin-left: 3.6pt; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,133,61);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap" class="">address:</span></div></td><td style="vertical-align:top;padding:5pt;overflow:hidden" class=""><div style="line-height: 1.53; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 9.5pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">548 Market Street, Box 55819</span></div><div style="line-height: 1.53; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 9.5pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">San Francisco, CA 94104</span></div></td></tr><tr style="height:12.75pt" class=""><td style="vertical-align:top;padding:5pt;overflow:hidden" class=""><div style="line-height: 1.38; margin-left: 3.6pt; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,133,61);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap" class="">email:</span></div></td><td style="vertical-align:top;padding:5pt;overflow:hidden" class=""><div style="line-height: 1.53; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 9.5pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class=""><a href="mailto:mike@rodenbaugh.com" target="_blank" class="">mike@rodenbaugh.com</a></span></div></td></tr><tr style="height:24pt" class=""><td style="vertical-align:top;padding:5pt;overflow:hidden" class=""><div style="line-height: 1.38; margin-left: 3.6pt; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,133,61);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap" class="">phone:</span></div></td><td style="vertical-align:top;padding:5pt;overflow:hidden" class=""><div style="line-height: 1.53; margin-top: 0pt; margin-bottom: 0pt;" class=""><span style="font-size: 9.5pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;" class="">+1 (415) 738-8087</span></div></td></tr></tbody></table></div></span></div></div></div></div></div></div></div></div></div><br class=""></div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 9, 2022 at 2:36 AM Emily Barabas <<a href="mailto:emily.barabas@icann.org" class="">emily.barabas@icann.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

<div lang="en-BE" style="overflow-wrap: break-word;" class="">

<div class="gmail-m_-3246326773081067400WordSection1"><p class="MsoNormal"><span lang="EN-US" class="">Dear working group members,<u class=""><u class=""><p class="MsoNormal"><span lang="EN-US" class=""><u class=""> <u class=""><p class="MsoNormal"><span lang="EN-US" class="">As a reminder, the <b class="">deadline for submitting input on the draft Initial Report is 14 May 2022.

</b>Please see instructions below for additional details.<b class=""><u class=""></u><u class=""></u></b></span></p><p class="MsoNormal"><b class=""><span lang="EN-US" class=""><u class=""></u> <u class=""></u></span></b></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class="">Kind regards,</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> Caitlin, Julie, Berry, and Emily</span><u class=""></u><u class=""></u></p><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p>

<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm" class=""><p class="MsoNormal"><b class=""><span style="font-size: 12pt;" class="">From: </span></b><span style="font-size: 12pt;" class="">Emily Barabas <<a href="mailto:emily.barabas@icann.org" target="_blank" class="">emily.barabas@icann.org</a>><br class="">

<b class="">Date: </b>Friday, 29 April 2022 at 16:27<br class="">

<b class="">To: </b>"<a href="mailto:gnso-tpr@icann.org" target="_blank" class="">gnso-tpr@icann.org</a>" <<a href="mailto:gnso-tpr@icann.org" target="_blank" class="">gnso-tpr@icann.org</a>><br class="">

<b class="">Subject: </b>Draft Initial Report - Input Due 14 May 2022<u class=""></u><u class=""></u></span></p>

</div>

<div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p>

</div>

<div class="">

<div class="">

<div class=""><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class="">Dear working group members,</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class="">As discussed on Tuesday’s call, staff had an action item to provide the draft Initial Report to the Working Group today for review. Please see the draft attached.</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class="">Please carefully review this draft Initial Report in coordination with the groups you represent. If you feel that there are items that need to be revised, please enter them

<a href="https://docs.google.com/document/d/1s9xumJ1XBPdTb7kQmc5sAC2AkszvfAF0freMvnx6G18/edit" target="_blank" class="">

here</a>. For each item, please include:</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p>

<ul style="margin-top:0cm" type="disc" class="">

<li class="gmail-m_-3246326773081067400xmsolistparagraph" style="margin-left:0cm"><span lang="EN-US" style="" class="">Report version (the date listed in the header of the Initial Report draft) and applicable line numbers ( these are listed along the left margin

 of the document).</span><u class=""></u><u class=""></u></li><li class="gmail-m_-3246326773081067400xmsolistparagraph" style="margin-left:0cm"><span lang="EN-US" style="" class="">Name and group you represent: If multiple WG members represent a group, input should be in coordination with these other members.</span><u class=""></u><u class=""></u></li><li class="gmail-m_-3246326773081067400xmsolistparagraph" style="margin-left:0cm"><span lang="EN-US" class="">Rationale: please provide a clear explanation for why you are proposing the revision.</span><u class=""></u><u class=""></u></li><li class="gmail-m_-3246326773081067400xmsolistparagraph" style="margin-left:0cm"><span lang="EN-US" style="" class="">Specific proposed revision: Provide the language you would like to see added/removed/edited.</span><u class=""></u><u class=""></u></li></ul><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><b class=""><span lang="EN-US" class="">The deadline for submitting input is 14 May 2022.</span></b><span lang="EN-US" class=""> After the deadline, the working group will spend the following four working group meetings reviewing the items submitted in the input

 document. If your groups are unable to provide input by 14 May, feedback on the Initial Report can be provided during the public comment period.

</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class="">As you review, please note that some sections of the report are highlighted:</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p>

<ul style="margin-top:0cm" type="disc" class="">

<li class="gmail-m_-3246326773081067400xmsolistparagraph" style="margin-left:0cm"><span lang="EN-US" class="">Text highlighted in purple is relatively new and should be reviewed closely.

</span><u class=""></u><u class=""></u></li><li class="gmail-m_-3246326773081067400xmsolistparagraph" style="margin-left:0cm"><span lang="EN-US" class="">Text highlighted in orange is still under discussion and may change.</span><u class=""></u><u class=""></u></li><li class="gmail-m_-3246326773081067400xmsolistparagraph" style="margin-left:0cm"><span lang="EN-US" class="">Yellow highlights are administrative in nature can be ignored.</span><u class=""></u><u class=""></u></li></ul><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class="">Please do not hesitate to reach out with any questions about the review process.</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class="">Kind regards,</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> Caitlin, Julie, Berry, and Emily</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><b class=""><span lang="EN-US" class=""> </span></b><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p>

<div class=""><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" style="font-size: 10pt; font-family: Arial, sans-serif;" class="">Emily Barabas</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" style="font-size: 10pt; font-family: Arial, sans-serif;" class="">Policy Development Support Senior Manager</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" style="font-size: 10pt; font-family: Arial, sans-serif;" class="">Internet Corporation for Assigned Names and Numbers (ICANN)</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" style="font-size: 10pt; font-family: Arial, sans-serif;" class="">Phone: +31 (0)6 84507976</span><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><a href="https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?url=http*3A*2F*2Fwww.icann.org*2F&data=05*7C01*7Crcarney*40godaddy.com*7C810c8f9ee92147643f6508da294c9280*7Cd5f1622b14a345a6b069003f8dc4851f*7C0*7C0*7C637867706113500635*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=qBOqnTAGdkl3Qzxd8PqC3fzUo*2F7kGYQZIIFIxuj47s4*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!PtGJab4!pQ9yxEYbvsSY9NeLpnBn7A2Sax8Rfx2bpnkvXethxY_inljc5Dxm9rYeB72hJWscJHdf1SIM0g$" title="http://www.icann.org/" target="_blank" class=""><span lang="EN-US" style="font-size:10pt;font-family:Arial,sans-serif" class="">www.icann.org

 [nam10.safelinks.protection.outlook.com]</span></a><u class=""></u><u class=""></u></p><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" style="" class=""> </span><u class=""></u><u class=""></u></p>

</div><p class="gmail-m_-3246326773081067400xmsonormal"><span lang="EN-US" class=""> </span><u class=""></u><u class=""></u></p>

</div>

</div>

</div>

</div>

</div>

_______________________________________________<br class="">

GNSO-TPR mailing list<br class="">

<a href="mailto:GNSO-TPR@icann.org" target="_blank" class="">GNSO-TPR@icann.org</a><br class="">

<a href="https://mm.icann.org/mailman/listinfo/gnso-tpr" rel="noreferrer" target="_blank" class="">https://mm.icann.org/mailman/listinfo/gnso-tpr</a></blockquote></div>

_______________________________________________<br class="">GNSO-TPR mailing list<br class=""><a href="mailto:GNSO-TPR@icann.org" class="">GNSO-TPR@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-tpr</div></blockquote></div><br class=""></div></body></html>