ICANN ICANN Email List Archives

[gnso-irtpc]


<<< Chronological Index >>>    <<< Thread Index >>>

[gnso-irtpc] Change of Registrant Language: Combined, Separate, or Hybrid Policy - Final Language

  • To: "IRTPC Working Group" <gnso-irtpc@xxxxxxxxx>
  • Subject: [gnso-irtpc] Change of Registrant Language: Combined, Separate, or Hybrid Policy - Final Language
  • From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Date: Sun, 23 Sep 2012 20:16:03 -0700

<html><body><span style="font-family:Arial; color:#000000; 
font-size:10pt;"><div><span><div style="color: rgb(0, 0, 0);margin-top: 
0.1pt;margin-right: 0in;margin-bottom: 0.1pt;margin-left: 0in;" 
mce_style="color: #000000;margin-top: 0.1pt;margin-right: 0in;margin-bottom: 
0.1pt;margin-left: 0in;"><span><font face="Calibri"><span style="font-size: 
15px;line-height: 22px;" mce_style="font-size: 15px;line-height: 
22px;"></span></font></span></div></span></div><div><span><span 
style="font-family: Arial; color: rgb(0, 0, 0); font-size: 10pt; clear: both;" 
mce_style="font-family:Arial;color:#000000;font-size:10pt;"><div>Team:</div><div><br></div><div>Please
  review the FINAL language for our recommendation on the question of Policy 
Separation. &nbsp; Please indicate on the list if you have objections or 
edits.&nbsp;  Silence = agreement.&nbsp; </div><div><br>Cut off for comments is 
end of day 
Tuesday.</div><div><br>Thanks!</div><div><br></div><div>J.</div><div><br></div></span></span><span><font
 face="Calibri"><span style="font-size: 15px;line-height: 22px;" 
mce_style="font-size: 15px;line-height: 
22px;">=======================</span></font></span></div><div 
style="font-family: Calibri, sans-serif;font-size: 14px;color: rgb(0, 0, 
0);margin-top: 0.1pt;margin-right: 0in;margin-bottom: 0.1pt;margin-left: 0in;" 
mce_style="font-family: Calibri, sans-serif;font-size: 14px;color: 
#000000;margin-top: 0.1pt;margin-right: 0in;margin-bottom: 0.1pt;margin-left: 
0in;"><span style="font-family: Calibri,sans-serif; font-size: 14px;" 
mce_style="font-family: Calibri,sans-serif; font-size: 14px;"><a 
target="_blank" 
style="mso-comment-reference:MK_1;mso-comment-date:20120912T1146;" 
mce_style="mso-comment-reference:MK_1;mso-comment-date:20120912T1146;"><i 
style="mso-bidi-font-style:normal;" 
mce_style="mso-bidi-font-style:normal;"><span 
style="font-size:11.0pt;mso-bidi-font-size:10.0pt;line-height:150%;font-family:Calibri;"
 
mce_style="font-size:11.0pt;mso-bidi-font-size:10.0pt;line-height:150%;font-family:Calibri;">Change
 of Registrant - a separate policy or part of the 
IRTP?</span></i></a><span><span style="font-size:8.0pt;line-height: 150%;" 
mce_style="font-size:8.0pt;line-height: 150%;"></span></span></span></div> <div 
style="font-family: Calibri,sans-serif; font-size: 14px; margin: 0.1pt 0in; 
clear: both;" mce_style="font-family: Calibri, sans-serif;font-size: 
14px;margin-top: 0.1pt;margin-right: 0in;margin-bottom: 0.1pt;margin-left: 
0in;"><span style="font-size: 11pt;line-height: 150%;font-family: Calibri;" 
mce_style="font-size: 11pt;line-height: 150%;font-family: Calibri;">The WG 
discussed <font color="#ff0000">as part of its Initial 
Report&nbsp;</font>whether a change of registrant policy as outlined above 
should become part of the existing IRTP <strike>or</strike> should be 
established as a separate consensus policy <font color="#ff0000">or a hybrid 
approach should be followed</font>. <font color="#ff0000">The WG would like to 
express a preference for the creation of a hybrid policy, whereby the IRTP 
would become a Transfer Policy whereby one Part or Section&nbsp; details the 
policy for a change of registrar, and another Part or Section details the 
policy for a change of registrant. However, if as part of the implementation 
process there are strong arguments for why a different approach should be 
followed, the WG suggests that those arguments are reviewed by the IRTP Part C 
Implementation Review Team</font></span></div><div><br 
mce_bogus="1"></div><div></div></span></body></html>



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy