[gnso-policyimpl-wg] FW: Request for input from Policy & Implementation WG
Here is what I believe is our first feedback in response to the letter we sent to SOs and ACs. Chuck From: Olivier MJ Crepin-Leblond [mailto:ocl@xxxxxxx] Sent: Friday, November 29, 2013 7:01 AM To: Glen de Saint Géry Cc: Heidi Ullrich; gnso-policyimpl-chairs (gnso-policyimpl-chairs@xxxxxxxxx) (gnso-policyimpl-chairs@xxxxxxxxx); Gomes, Chuck; J. Scott Evans; ICANN AtLarge Staff; Olivier MJ Crepin-Leblond Subject: Re: Request for input from Policy & Implementation WG Dear Chuck, Dear J. Scott, please be so kind to find attached the "ALAC Statement on the Policy & Implementation Working Group" submitted to you in response to the request for input which was sent on your behalf in the email below. The Statement was ratified by the ALAC at the Buenos Aires meeting with 12 votes in favor, 0 votes against, and 0 abstentions. Please do not hesitate to contact me if you have any enquiry regarding any aspect of this Statement. Best regards, Olivier MJ Crépin-Leblond ALAC Chair On 20/09/2013 15:52, Glen de Saint Géry wrote: To Supporting Organisation and Advisory Committee Chairs: Dear Olivier, We are the Chairs of the newly constituted Policy & Implementation Working Group. This Working Group (WG) has been tasked with providing the GNSO Council with a set of recommendations on the following issues: - A set of principles that would underpin any GNSO policy implementation related discussions, taking into account existing GNSO procedures; - A process for developing gTLD policy, perhaps in the form of "Policy Guidance," including criteria for when it would be appropriate to use such a process (for a process developing something other than "Consensus Policy") instead of the GNSO Policy Development Process; - A framework for implementation related discussions associated with GNSO Policy recommendations; - Criteria to be used to determine when an action should be addressed by a policy process and when it should be considered implementation; and - Further guidance on how GNSO Implementation Review Teams, as defined in the PDP Manual, are expected to function and operate. As part of the effort, the WG wants to reach out at the beginning of our efforts to the various GNSO Stakeholder Groups and Constituencies as well as other Supporting Organizations and Advisory Committees to gain input to assist us in our efforts. In this regard, we would ask for your organization to consider the following questions which are set out in the WG's Charter and provide us with your input on any or all of these issues by 31 October. 1. What guidance do the ICANN core values (Bylaws Article 1, Sec. 2) directly provide with regard to policy development work and policy implementation efforts? (e.g., multi-stakeholder participation). 2. What guidance do other ICANN core values provide that relate indirectly to policy development and policy implementation? (e.g., effective and timely process). 3. "Questions for Discussion" contained in the Policy versus Implementation Draft Framework prepared by ICANN staff. (See, http://www.icann.org/en/news/public-comment/policy-implementation-31jan13-en.htm). 4. What lessons can be learned from past experience? * What are the consequences of action being considered "policy" vs. "implementation"? * Does it matter if something is "policy" or "implementation"? If so, why? * Under what circumstances, if any, should the GNSO Council make recommendations or state positions to the Board on matters of policy and implementation as a representative of the GNSO as a whole? * How do we avoid the current morass of outcome-derived labeling (i.e., I will call this "policy" because I want certain consequences or "handling instructions" to be attached to it?) * Can we answer these questions so the definitions of "policy" and "implementation" matter less, if at all? 1. What options are available for policy ("Consensus Policy" or other) and implementation efforts and what are the criteria for determining which should be used? * Are "policy" and "implementation" on a spectrum rather than binary? * What are the "flavors" of policy and what consequences should attach to each "flavor? * What happens if you change those consequences? 1. Who determines the choice of whether something is "policy" or "implementation"? * How is policy set/recommended/adopted and do different paths lead to different "flavors"? * How is the "policy" versus "implementation" issue reviewed and approved? * What happens if reviewing bodies come to a deadlock? 1. What is the process by which this identification, analysis, review and approval work is done? * How are "policy and implementation" issues first identified (before, during and after implementation)? * What is the role of the GNSO in implementation? * In order to maintain the multi-stakeholder process, once policy moves to implementation, how should the community be involved in a way that is meaningful and effective? * Should policy staff be involved through the implementation process to facilitate continuity of the multi-stakeholder process that already occurred? Alternatively, if you would prefer to set up an exchange of views by teleconference or possibly in person during the ICANN meeting in Buenos Aires, the Working Group would welcome such an approach as well. Finally, we would like to remind you that the WG is open to the full community and we welcome any additional members from your organization that my wish to participate in this work. To review the current membership, please see https://community.icann.org/x/81V-Ag. Thank you in advance for your consideration. Please do not hesitate to reach out to either of us if you have any questions or if you require any additional information. Kind regards. Chuck Gomes (cgomes@xxxxxxxxxxxx<mailto:cgomes@xxxxxxxxxxxx>) J. Scott Evans (jscottevans@xxxxxxxxx<mailto:jscottevans@xxxxxxxxx>) -- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html Attachment:
AL-ALAC-ST-1113-03-00-EN.pdf |