<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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 name=Generator content="Microsoft Word 12 (filtered medium)"><title>RE: Motions for next week's meeting</title><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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dear All,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The amended motions have been posted on the Wiki.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="https://community.icann.org/display/gnsocouncilmeetings/Motions+19+January+2012">https://community.icann.org/display/gnsocouncilmeetings/Motions+19+January+2012</a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thank you.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Kind regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Glen<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>Glen de Saint Géry<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>GNSO Secretariat<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'><a href="mailto:gnso.secretariat@gnso.icann.org">gnso.secretariat@gnso.icann.org</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'><a href="http://gnso.icann.org">http://gnso.icann.org</a><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De :</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] <b>De la part de</b> Mason Cole<br><b>Envoyé :</b> samedi 14 janvier 2012 23:04<br><b>À :</b> Mason Cole; council@gnso.icann.org<br><b>Objet :</b> [council] RE: Motions for next week's meeting<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p style='margin-bottom:12.0pt'><span style='font-size:10.0pt'>All --<br><br>At Jeff's request, I have amended the sections below that discuss receipt of comments.<br><br>Thanks --<br><br>Mason<br><br><br>-----Original Message-----<br>From: Mason Cole<br>Sent: Tue 1/10/2012 10:57 AM<br>To: <a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br>Subject: Motions for next week's meeting<br><br>Happy New Year all --<br><br>I move for the following two items:<br><br><br><br><br>Motion on the Adoption of the Staff Proposal on IRTP Part B Recommendation #8<br><br>WHEREAS on 24 June 2009, the GNSO Council launched a Policy Development Process (PDP) on IRTP Part B addressing the following five charter questions:<br>a. Whether a process for urgent return/resolution of a domain name should be developed, as discussed within the SSAC hijacking report (<a href="http://www.icann.org/announcements/hijacking-report-12jul05.pdf);">http://www.icann.org/announcements/hijacking-report-12jul05.pdf);</a> see also (<a href="http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm);">http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm);</a><br>b. Whether additional provisions on undoing inappropriate transfers are needed, especially with regard to disputes between a Registrant and Admin Contact (AC). The policy is clear that the Registrant can overrule the AC, but how this is implemented is currently at the discretion of the registrar;<br>c. Whether special provisions are needed for a change of registrant when it occurs near the time of a change of registrar. The policy does not currently deal with change of registrant, which often figures in hijacking cases;<br>d. Whether standards or best practices should be implemented regarding use of a Registrar Lock status (e.g. when it may/may not, should/should not be applied);<br>e. Whether, and if so, how best to clarify denial reason #7: A domain name was already in 'lock status' provided that the Registrar provides a readily accessible and reasonable means for the Registered Name Holder to remove the lock status.<br><br>WHEREAS this PDP has followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report delivered on 30 May 2011;<br><br>WHEREAS the IRTP Part B WG has reached full consensus on the recommendations in relation to each of the five issues outlined above;<br><br>WHEREAS in relation to recommendation #8, the GNSO Council resolved at its meeting on 22 June to request ‘ICANN staff to provide a proposal designed to ensure a technically feasible approach can be developed to meet this recommendation. Staff should take into account the IRTP Part B WG deliberations in relation to this issue (see IRTP Part B Final Report). (IRTP Part B Recommendation #8). The goal of these changes is to clarify why the Lock has been applied and how it can be changed. Upon review of the proposed plan, the GNSO Council will consider whether to approve the recommendation’;<br><br>WHEREAS ICANN staff developed the proposal in consultation with the IRTP Part B Working Group which was put out for public comment (see <a href="http://www.icann.org/en/public-comment/irtp-b-staff-proposals-22nov11-en.htm);">http://www.icann.org/en/public-comment/irtp-b-staff-proposals-22nov11-en.htm);</a><br><br>WHEREAS comments were received from the Intellectual Property Constituency, and though received after the comment deadline were nonetheless considered by the GNSO Council, and and the proposal was submitted to the GNSO Council;<br><br>WHEREAS the GNSO Council has reviewed and discussed the ICANN Staff proposal in relation to IRTP Part B recommendation #8.<br><br>RESOLVED, the GNSO Council recommends to the ICANN Board of Directors that it adopts and implements IRTP Part B recommendation #8 and the related ICANN Staff proposal (as described in <a href="http://gnso.icann.org/issues/transfers/irtp-b-final-report-30may11-en.pdf">http://gnso.icann.org/issues/transfers/irtp-b-final-report-30may11-en.pdf</a> and <a href="http://gnso.icann.org/mailing-lists/archives/council/msg12545.html">http://gnso.icann.org/mailing-lists/archives/council/msg12545.html</a>). <br><br><br>==============<br><br>Motion on the Adoption of the Staff Proposal on IRTP Part B Recommendation #9 part 2<br><br>WHEREAS on 24 June 2009, the GNSO Council launched a Policy Development Process (PDP) on IRTP Part B addressing the following five charter questions:<br>a. Whether a process for urgent return/resolution of a domain name should be developed, as discussed within the SSAC hijacking report?(<a href="http://www.icann.org/announcements/hijacking-report-12jul05.pdf);">http://www.icann.org/announcements/hijacking-report-12jul05.pdf);</a> see also (<a href="http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm);">http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm);</a><br>b. Whether additional provisions on undoing inappropriate transfers are needed, especially with regard to disputes between a Registrant and Admin Contact (AC). The policy is clear that the Registrant can overrule the AC, but how this is implemented is currently at the discretion of the registrar;<br>c. Whether special provisions are needed for a change of registrant when it occurs near the time of a change of registrar. The policy does not currently deal with change of registrant, which often figures in hijacking cases;<br>d. Whether standards or best practices should be implemented regarding use of a Registrar Lock status (e.g. when it may/may not, should/should not be applied);?e. Whether, and if so, how best to clarify denial reason #7: A domain name was already in 'lock status' provided that the Registrar provides a readily?accessible and reasonable means for the Registered Name Holder to remove the lock status.<br><br>WHEREAS this PDP has followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report delivered on 30 May 2011;<br><br>WHEREAS the IRTP Part B WG has reached full consensus on the recommendations in relation to each of the five issues outlined above;<br><br>WHEREAS in relation to recommendation #9 part b, the GNSO Council resolved at its meeting on 22 June to request ICANN Staff to provide a proposal for a new provision on locking / unlocking of a domain name, taking into account the IRTP Part B WG deliberations in relation to this issue (see IRTP Part B Final Report - (Recommendation #9 - part 2). Upon review of the proposal, the GNSO Council will consider whether to approve the recommendation;<br><br>WHEREAS ICANN staff developed the proposal in consultation with the IRTP Part B Working Group which was put out for public comment (see <a href="http://www.icann.org/en/public-comment/irtp-b-staff-proposals-22nov11-en.htm);">http://www.icann.org/en/public-comment/irtp-b-staff-proposals-22nov11-en.htm);</a><br><br>WHEREAS comments were received from the Intellectual Property Constituency, and though received after the comment deadline were nonetheless considered by the GNSO Council, and and the proposal was submitted to the GNSO Council;<br><br>WHEREAS the GNSO Council has reviewed and discussed the ICANN Staff proposal in relation to IRTP Part B recommendation #9 part 2.<br><br>RESOLVED, the GNSO Council recommends to the ICANN Board of Directors that it adopts and implements IRTP Part B recommendation #9 part 2 and the related ICANN Staff proposal (as described in <a href="http://gnso.icann.org/issues/transfers/irtp-b-final-report-30may11-en.pdf">http://gnso.icann.org/issues/transfers/irtp-b-final-report-30may11-en.pdf</a> and <a href="http://gnso.icann.org/mailing-lists/archives/council/msg12545.html">http://gnso.icann.org/mailing-lists/archives/council/msg12545.html</a>). <br><br></span><o:p></o:p></p></div></body></html>