Changes

Jump to navigation Jump to search
no edit summary
Line 11: Line 11:     
==Initiation==
 
==Initiation==
The board assembled a GNSO Review Working Group of the [[Board Governance Committee]], and approved its charter,<ref> in March 2007<ref>[https://www.icann.org/minutes/resolutions-30mar07.htm#_Toc36876533 Resolution of the Board], March 30, 2007</ref> The working group was charged to answer the traditional Article 4.4 (as amended at the time) questions: does the GNSO have a continuing purpose within the ICANN structure; and if so, what can be done to improve its effectiveness. The charter document goes further, tasking the working group to develop a "comprehensive proposal" to improve the effectiveness of the GNSO.<ref name="background" GNSO Community Reference - Background on GNSO Improvements], January 9, 2013</ref>  
+
The board assembled a GNSO Review Working Group of the [[Board Governance Committee]], and approved its charter, in March 2007<ref>[https://www.icann.org/minutes/resolutions-30mar07.htm#_Toc36876533 Resolution of the Board], March 30, 2007</ref> The working group was charged to answer the traditional Article 4.4 (as amended at the time) questions: does the GNSO have a continuing purpose within the ICANN structure; and if so, what can be done to improve its effectiveness? The charter document goes further, tasking the working group to develop a "comprehensive proposal" to improve the effectiveness of the GNSO.<ref name="background">[https://gnso.icann.org/en/group-activities/inactive/2012/improvements/background-en.htm GNSO Community Reference - Background on GNSO Improvements], January 9, 2013</ref>  
    
==Review of Prior Assessments==
 
==Review of Prior Assessments==
Line 19: Line 19:  
The GNSO, in preparing the Terms of Reference for the its 2004 review, conducted a self-review process. The self-review described a number of policy development successes, including updates to the transfer policy, WHOIS, and deletion policy.<ref name="gnsosr">[https://gnso.icann.org/reviews/gnso-review-sec2-22dec04.pdf 2004 GNSO Review - Terms of Reference and Self-Assessment], December 22, 2004</ref> The GNSO made three categories of recommendations:
 
The GNSO, in preparing the Terms of Reference for the its 2004 review, conducted a self-review process. The self-review described a number of policy development successes, including updates to the transfer policy, WHOIS, and deletion policy.<ref name="gnsosr">[https://gnso.icann.org/reviews/gnso-review-sec2-22dec04.pdf 2004 GNSO Review - Terms of Reference and Self-Assessment], December 22, 2004</ref> The GNSO made three categories of recommendations:
 
# Recommendations re: the ICANN Bylaws: maintain GNSO Council compostion of 3 representatives from each constituency; amend the policy development process bylaws to state that PDP timelines are flexible, and may be set and revised by the GNSO Council to reflect the work being considered and status updates from the working group.
 
# Recommendations re: the ICANN Bylaws: maintain GNSO Council compostion of 3 representatives from each constituency; amend the policy development process bylaws to state that PDP timelines are flexible, and may be set and revised by the GNSO Council to reflect the work being considered and status updates from the working group.
# Recommendations re: staff support: multiple requests for staff support around the policy development process, task forces, and work of the GNSO Council; make legal staff available to the GNSO Council, task forces, and subcommittees, and in particular for review of policy recommendations and other policy statement for compliance with bylaws and contractual obligations; and create monitoring, compliance, and complaint policies related to gTLDs.<ref name="gnsosr" />
+
# Recommendations re: staff support: multiple requests for staff support around the policy development process, task forces, and work of the GNSO Council; make legal staff available to the GNSO Council, task forces, and subcommittees, and in particular for review of policy recommendations and other policy statement for compliance with bylaws and contractual obligations; and create monitoring, compliance, and complaint policies related to gTLDs.
 +
# Actions required of the GNSO Council: Ensure that legal advice from ICANN staff is in writing and allow registrars or registries to submit the opinion of their counsel; ensure that policies are ready to be implemented upon approval; establish key metrics for measuring the success of a given party; encourage community-wide participation in the policy development process.<ref name="gnsosr" />
    
==References==
 
==References==
 
{{reflist}}
 
{{reflist}}
Bureaucrats, Check users, lookupuser, Administrators, translator
3,197

edits

Navigation menu