<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Arial, sans-serif" size="2">
<div>All:</div>
<div> </div>
<div><font face="Times New Roman, serif" size="3">at the Council meeting on 16 February 2012 the following items have lead to further actions:</font></div>
<div><font face="Times New Roman, serif" size="3"> </font></div>
<ul style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 19pt; ">
<font face="Times New Roman, serif" size="3">
<li><b>Approval of the proposal to end the work on Whois access at this time</b>: on my request this shall remain on the GNSO agenda. I was asked to come up with a proposal how to handle it.</li></font>
</ul>
<div style="padding-left: 19pt; "><font face="Times New Roman, serif" size="3">My suggestion is to co-operate with staff (Liz Gasster offered support). One option could be that the Council could also direct the likely forthcoming RAA PDP to include this accessibility
element. Timeline is to be checked as to whether a related motion will be disussed at the CR meetings. If this is the case an ISPCP discussion at constituency day in CR only may be too late.</font></div>
<div style="padding-left: 19pt; "><font face="Times New Roman, serif" size="3"><b>Any idea from your side is welcome!</b></font></div>
<div style="padding-left: 19pt; "><font face="Times New Roman, serif" size="3"> </font></div>
<ul style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 19pt; ">
<font face="Times New Roman, serif" size="3">
<li style="margin-top: 5pt; margin-bottom: 5pt; "><b>Motion on the Initiation of a Policy Development Process (PDP) on ‘thick’ Whois:</b> this was deferred to CR</li><li><b>CR GNSO agenda:</b> was adopted. Topics suggested to be discussed with Board and GAC on Sunday: RAA, IOC/Red Cross names, WhoIs Review Team Final Report</li></font>
</ul>
<div style="padding-left: 19pt; "><font face="Times New Roman, serif" size="3"> </font></div>
<div><font face="Times New Roman, serif" size="3"> </font></div>
<div><font face="Times New Roman, serif" size="3"> </font></div>
<div><font face="Times New Roman, serif" size="3"><b>The following resolutions were passed:<br>
<br>
</b>1. Consent Agenda</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">· Approval that the <a href="http://gnso.icann.org/drafts/gnso-council-report-irtp-part-b-recommendation-9part2-06feb12-en.pdf"><font color="#0000FF"><u>Recommendations Report</u></font></a> on the Inter-Registrar
Transfer Policy Part B (IRTP B) Recommendation 9, part 2 be sent to the ICANN Board.</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">· Approval of the termination of the Open Council Drafting Team. </font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">· Approval of new calls for volunteers for the joint ccNSO/GNSO IDN Working Group (JIG). </font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3"><b>2. Motion on the Adoption of the Staff Proposal on IRTP Part B Recommendation #8</b></font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">WHEREAS on 24 June 2009, the GNSO Council launched a Policy Development Process (PDP) on IRTP Part B addressing the following five charter questions:</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">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"><font color="#0000FF"><u>http://www.icann.org/announcements/hijacking-report-12jul05.pdf</u></font></a>);
see also (<a href="http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm"><font color="#0000FF"><u>http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm</u></font></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.</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">WHEREAS this PDP has followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report delivered on 30 May 2011;</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">WHEREAS the IRTP Part B WG has reached full consensus on the recommendations in relation to each of the five issues outlined above;</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">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’;</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">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"><font color="#0000FF"><u>http://www.icann.org/en/public-comment/irtp-b-staff-proposals-22nov11-en.htm</u></font></a>);</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">WHEREAS no comments were received as part of the public comment forum and the proposal was submitted to the GNSO Council; </font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">WHEREAS on 10 January 2012, the IPC has provided its comments to ICANN staff proposal (as described in <a href="http://gnso.icann.org/mailing-lists/archives/council/msg12555.html"><font color="#0000FF"><u>http://gnso.icann.org/mailing-lists/archives/council/msg12555.html</u></font></a>
); </font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">WHEREAS ICANN staff has provided an updated proposal based on the IPC comments (as described in <a href="http://gnso.icann.org/mailing-lists/archives/council/msg12600.html"><font color="#0000FF"><u>http://gnso.icann.org/mailing-lists/archives/council/msg12600.html</u></font></a>
); </font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">WHEREAS the GNSO Council has reviewed and discussed the ICANN Staff proposal in relation to IRTP Part B recommendation #8.</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3">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 updated proposal (as described in</font></div>
<div style="margin-top: 5pt; margin-bottom: 5pt; padding-left: 18pt; padding-right: 18pt; ">
<font face="Times New Roman, serif" size="3"><a href="http://gnso.icann.org/drafts/irtp-recommendation-8-proposal-26jan12-en.pdf"><font color="#0000FF"><u>http://gnso.icann.org/drafts/irtp-recommendation-8-proposal-26jan12-en.pdf</u></font></a>). </font></div>
<div><font face="Times New Roman, serif" size="3"> </font></div>
<div><font face="Times New Roman, serif" size="3"> </font></div>
<div><font face="Arial, sans-serif">Kind regards</font></div>
<div><font face="Arial, sans-serif">Wolf-Ulrich </font></div>
<div><font face="Arial, sans-serif"> </font></div>
</font>
</body>
</html>