Comment Close
Date
Statement
Name 

Status

Assignee(s) and
RALO(s)

Call for
Comments
Call for
Comments
Close 
Vote
Announcement 
Vote OpenVote
Reminder
Vote CloseDate of SubmissionStaff Contact and EmailStatement Number
31.10.2013Policy & Implementation Working GroupTBCTBCTBCTBCTBCTBCTBCTBCTBCn/aTBC

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:

  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?
    1. What are the consequences of action being considered “policy” vs. 
      “implementation”?
    2. Does it matter if something is “policy” or “implementation”?  If so, why?
    3. 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?
    4. 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?)
    5. Can we answer these questions so the definitions of “policy” and “implementation” matter less, if at all?
  5. What options are available for policy (“Consensus Policy” or other) and implementation efforts and what are the criteria for determining which should be used?
    1. Are “policy” and “implementation” on a spectrum rather than binary?
    2. What are the “flavors” of policy and what consequences should attach to each “flavor?
    3. What happens if you change those consequences?
  6. Who determines the choice of whether something is “policy” or “implementation”?
    1. How is policy set/recommended/adopted and do different paths lead to different “flavors”?
    2. How is the “policy” versus “implementation” issue reviewed and approved?
    3. What happens if reviewing bodies come to a deadlock?
  7. What is the process by which this identification, analysis, review and approval work is done?
    1. How are “policy and implementation” issues first identified (before, during and after implementation)?
    2. What is the role of the GNSO in implementation?
    3. 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?
    4. 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@verisign.com)
J. Scott Evans (jscottevans@yahoo.com)

 

FINAL VERSION TO BE SUBMITTED IF RATIFIED

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.

FIRST DRAFT SUBMITTED

The first draft submitted will be placed here before the call for comments begins.