<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi Caitlin and Team:</div>
<div><br>
</div>
<div>First, I should apologize for missing the last 2 calls. I have had frequent schedule conflicts with this group, including an “off the grid” vacation last week. So please accept my apologies if these edits/comments appear to be “last minute”.</div>
<div><br>
</div>
<div>Next, I have noted a few changes to this draft (attached). Here are the highlights:</div>
<ul>
<li>I think we should call Section II. “Inter-Registrant Transfer (Change of Registrant)” to keep it consistent with Section I. “Inter-Registrar Transfer”. </li><li>Also, I think we should allow for non-material changes to Registrant information to include “equivalent” data, such as changing “Inc.” to “Incorporated” or “Mike” to “Michael.” I welcome ideas form the group on how to define this (or set some boundaries).</li><li>I’m still unclear whehter or not the Registrar has the right to refuse a Change of Registrant. What if there is some reason that the Registrar cannot legally serve or enter in to an agreement with the new Registrant? For example, in the US we cannot serve
Registrants in Cuba or North Korea. Similarly, the US and several other nations have levied sanctions against individuals and organizations in Crimea. I would hate to see this policy used as a backdoor to compel Registrars to violate local law. Finally, there
is the case where a Registrar has simply banned a particular Registrant from using their services. This right to refuse service should be maintained in the new policy.</li><li>Speaking of the Registration Agreement, I do not see where in the Draft Process (Sec. II(3)) where the Registrar presents this agreement to the new Registrant, and obtain their explicit acceptance. This is required buy the RAA (Sec. 3.7.7).</li></ul>
<div>Thanks—</div>
<div><br>
</div>
<div>J.</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org">caitlin.tubergen@icann.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, March 11, 2015 at 13:40 <br>
<span style="font-weight:bold">To: </span>"<a href="mailto:gnso-impl-irtpc-rt@icann.org">gnso-impl-irtpc-rt@icann.org</a>" <<a href="mailto:gnso-impl-irtpc-rt@icann.org">gnso-impl-irtpc-rt@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>[gnso-impl-irtpc-rt] Reminder: Comments on Change of Registrant/Transfer Policy - due Thursday 12 March<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi All,</div>
<div><br>
</div>
<div>Please note that the deadline for the Implementation Review Team to provide comments on the attached draft COR policy is tomorrow,
<b>Thursday, 12 March</b>.</div>
<div><br>
</div>
<div>If you are unable to provide feedback by that time, you are welcome to submit any comments during the public comment period.</div>
<div><br>
</div>
<div>Thank you.</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div>Caitlin</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<span id="OLK_SRC_BODY_SECTION">
<div 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">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">
<a href="mailto:owner-gnso-impl-irtpc-rt@icann.org">owner-gnso-impl-irtpc-rt@icann.org</a> [<a href="mailto:owner-gnso-impl-irtpc-rt@icann.org">mailto:owner-gnso-impl-irtpc-rt@icann.org</a>]
<b>On Behalf Of </b>Caitlin Tubergen<br>
<b>Sent:</b> Thursday, March 05, 2015 10:19 PM<br>
<b>To:</b> <a href="mailto:gnso-impl-irtpc-rt@icann.org">gnso-impl-irtpc-rt@icann.org</a>; Theo Geurts<br>
<b>Subject:</b> [gnso-impl-irtpc-rt] For your review: Change of Registrant/Transfer Policy - by Thursday 12 March<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Hi All,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Thank you to everyone who participated in the call today. For those of you who were unable to attend, please find a link to the recording here: <a href="https://icann.adobeconnect.com/p4howkg3hce/"><b><span style="color:black;background:white">https://icann.adobeconnect.com/p4howkg3hce/</span></b></a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">During the call, we discussed the outstanding issue from our last call, which was the issue of third party privacy/proxy providers and the potential challenge
of transmitting the change of registrant credential to the underlying registrant. The members of the IRT that were on the call with okay with the proposed solution, which you will find in footnote 1. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">The P/P issue was the last outstanding issue to discuss before we post the draft policy for public comment. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I have attached the draft policy for your final review. You will note that this is the hybrid “Transfer Policy,” which will go out for public comment. The
Transfer Policy has two sections: the IRTP in section I, and the Change of Registrant in section II. The hybrid policy was recommended by the WG. As you may remember, we had already worked through recommendation 2, the time limiting of FOAs, before we began
discussing the Change of Registrant function. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Calibri, sans-serif;">If you have any final questions or comments on the draft policy, please submit them to me by <b><u>Thursday, 12 March</u></b>. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Calibri, sans-serif;">Thank you!</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: Calibri, sans-serif;">Kind regards,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Caitlin <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</span></div>
</span><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></div>
</div>
</span>
</body>
</html>