Page History
...
Made by: Jeff Neuman
Seconded by: Carlos Aguirre
WHEREAS, in October 2008, the GNSO Council established a framework (see GNSO Council Improvement Implementation Plan;
(http://www.icann.org/en/topics/gnso-improvements/gnso-improvements-implementation-plan-16oct08.pdf) for implementing the various GNSO Improvements identified and approved by the ICANN Board of Directors on 26 June 2008
(http://www.icann.org/en/minutes/resolutions-26jun08.htm#_Toc76113182)
(http://www.icann.org/en/minutes/resolutions-26jun08.htm);
...
RESOLVED, the GNSO Council directs the PDP-WT to review the Summary and Analysis document as well as the comments and make any changes to the PDP-WT Final Report as deemed appropriate. The PDP-WT should submit the updated version of the Final Report to the GNSO Council as soon as possible, preferably in time for consideration at its next meeting on 8 September.
5. Motion to Address the Remaining Registration Abuse Policies Working Group Recommendations
(For discussion only)
Whereas the Registration Abuse Policies (RAP) Working Group submitted its report to the GNSO Council on 29 May 2010 (see http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf);
Whereas the GNSO Council reviewed the report and its recommendations and decided to form an implementation drafting team to draft a proposed approach with regard to the recommendations contained in the Registration Abuse Policies Working Group Final Report;
Whereas the Registration Abuse Policies Implementation Drafting Team submitted its proposed response to the GNSO Council on 15 November 2010 (see http://gnso.icann.org/correspondence/rap-idt-to-gnso-council-15nov10-en.pdf);
Whereas the GNSO Council considered the proposed approached at its Working Session at the ICANN meeting in Cartagena;
Whereas the GNSO Council acted on a number of RAP recommendations at its meeting on 3 February 2011 (see http://gnso.icann.org/resolutions/#201102);
Whereas the GNSO Council requested feedback from ICANN Compliance in relation to WHOIS Access recommendation #2 and Fake Renewal Notices recommendation #1 and a response was received on 23 February 2011 (http://gnso.icann.org/mailing-lists/archives/council/msg10766.html). In addition, a discussion with Compliance Staff was held at the ICANN meeting in San Francisco.
Whereas the GNSO Council considered the remaining RAP recommendations in further detail during its working session at the ICANN meeting in Singapore based on an overview prepared by ICANN Staff (see http://gnso.icann.org/correspondence/overview-rapwg-recommendations-18may11-en.pdf).
NOW THEREFORE BE IT:
RESOLVED, the GNSO Council thanks the ICANN Compliance Department for its feedback in relation to WHOIS Access recommendation #2 and determines that no further work on this recommendation is needed.
RESOLVED, the GNSO Council thanks the ICANN Compliance Department for its feedback in relation to Fake Renewal Notices recommendation #1 and determines that no further work on this recommendation is needed.
RESOLVED, the GNSO Council determines that additional information is needed from the Registrar Stakeholder Group with regard to the conditional Fake Renewal Notices recommendation #2 before an Issue Report should be requested of Staff. The GNSO Council hereby requests that the Registrar Stakeholder Group provide further information and data on the nature and scope of the issue of Fake Renewal Notices to help inform the GNSO Council’s deliberations on whether an Issue Report should be requested.
RESOLVED, in response to WHOIS Access recommendation #1, the GNSO Council acknowledges receipt of this recommendation and determines to defer its consideration until the results of the WHOIS studies that are currently being undertaken are available. At that time, the GNSO Council intends to consider the appropriate next steps in relation to WHOIS access recommendation #1 in light of the data obtained from these WHOIS studies.
RESOLVED, with regard to the recommendation on Meta Issue: Collection and Dissemination of Best Practices, the GNSO Council acknowledges receipt of this recommendation and determines to defer its consideration until it evaluates the outcome of Malicious Use of Domain Names recommendation #1, which aims to develop best practices to help registrars and registries address the illicit use of domain names. In light of the pending request to Staff to develop a Discussion Paper on the Malicious Use of Domain Names, the GNSO Council believes that the upcoming review and analysis of this Discussion Paper may serve to inform the Council of the issues related to the Meta Issue: Collection and Dissemination of Best Practices recommendation.
RESOLVED, in regard to the recommendations on cross-TLD Registration Scam and Domain Kiting/Tasting, the GNSO Council Chair shall communicate to the Security and Stability Advisory Committee (SSAC) the findings of the RAP WG in this regard and request that the SSAC consider evaluating and/or monitoring these abuses. If the SSAC elects to conduct this work, the GNSO Council requests that the SSAC inform the GNSO Council if it believes that further policy work by the GNSO Council should be undertaken to address these two types of abuse. In addition, the GNSO Council suggests that the issue of cross-TLD registration scam be included in the agenda of its next meeting with the ccNSO Council since this type of abuse may also affect ccTLDs.
RESOLVED, in response to the recommendation on Meta Issue: Uniformity of Reporting, the GNSO Council acknowledges receipt of this recommendation, and hereby requests feedback from ICANN Compliance Department on whether improvements / changes have been made since the RAPWG Report or are foreseen in the near future to facilitate reporting and tracking of violations and/or complaints. Further consideration of this Meta Issue is deferred pending receipt of such information from the ICANN Compliance Department.
RESOLVED, in response to the recommendations on Uniformity of Contracts; Gripe Sites, Deceptive and/or Offensive Domain Names recommendation #2, and; Cybersquatting recommendation #2, since the RAPWG did not achieve consensus on these recommendations, the GNSO Council declines to undertake further policy work on these recommendations at this time.
RESOLVED, in response to Gripe Sites; Deceptive and/or Offensive Domain Names recommendation #1, the GNSO Council acknowledges receipt of this recommendation, and agrees with the RAPWG that no further action is called for at this time.
