Page History
1. Motion on the Adoption of the IRTP Part B Recommendation #3 (Issue Report on ‘Thick’ WHOIS)
Made by:Tim Ruiz
Seconded by: Stéphane van Gelder
WHEREAS on 24 June 2009, the GNSO Council launched a Policy Development Process (PDP) on IRTP Part B addressing the following five charter questions:
a. Whether a process for urgent return/resolution of a domain name should be developed, as discussed within the SSAC hijacking report
http://www.icann.org/announcements/hijacking-report-12jul05.pdf); see also (http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm)
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;
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;
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.
WHEREAS this PDP has followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report delivered on 30 May 2011;
WHEREAS the IRTP Part B WG has reached full consensus on the recommendations in relation to each of the five issues outlined above;
WHEREAS the GNSO Council has reviewed and discussed these recommendations;
WHEREAS the GNSO Council resolved at its meeting on 22 June to ‘consider IRTP Part B Recommendation #3 concerning the request of an Issue Report on the requirement of 'thick' WHOIS for all incumbent gTLDs at its next meeting on 21 July’.
RESOLVED, the GNSO Council requests an Issue Report on the requirement of ‘thick’ WHOIS for all incumbent gTLDs. Such an Issue Report and possible subsequent Policy Development Process should not only consider a possible requirement of 'thick' WHOIS or all incumbent gTLDs in the context of IRTP, but should also consider any other positive and/or negative effects that are likely to occur outside of IRTP that would need to be taken into account when deciding whether a requirement of 'thick' WHOIS for all incumbent gTLDs would be desirable or not. (IRTP Part B Recommendation #3)
_____________________________________________________________________________________________________________________________________________________________
2. Motion regarding the nature of Internet-based criminal activity and the information and tools available to help address crime that involves the domain name system;
...
b. The purpose of these monitoring and reporting requirements are to allow the GNSO to determine when, if ever, these recommendations and any ensuing policy require additional amendment, clarification or attention based on the results of the reports prepared by ICANN staff.
...
23. Initiation of a Policy Development Process (PDP) on the Inter-Registrar Transfer Policy (IRTP) Part C
...
A Working Group will be created for the purpose of fulfilling the requirements of the PDP.
...
34. Motion for Approval of a Charter for the Inter-Registrar Transfer Policy (IRTP) Part C Working Group (WG)
...
The Working Group shall follow the rules outlined in the GNSO Working Group Guidelines http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-07apr11-en.pdf.
...
45. MOTION RE. REVISION OF THE GNSO COUNCIL OPERATING PROCEDURES RELATING TO PROXY VOTING
...
RESOLVED FURTHER that as the OSC has completed all of its tasks the GNSO Council hereby disbands the OSC and its Work Teams and expresses its gratitude and appreciation to the members of the OSC and its Work Teams for their dedication, commitment, and thoughtful recommendations.
...
56. Motion to Address the Remaining Registration Abuse Policies Working Group Recommendations
...
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.
...
67. MOTION TO CREATE JOINT WORKING GROUP ON CONSUMER CHOICE, COMPETITION, AND INNOVATION (CCI):
...
Resolved further, that in the event that no other SO/AC approves of the terms of this Charter http://gnso.icann.org/drafts/cci-charter-07sep11-en.pdf, the CCI WG shall continue to proceed as a GNSO Council chartered joint Working Group.
...
78. Draft Motion to approve charter for Whois Survey Working Group (WS-WG)
...
