You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Recommendation 20

That the GNSO Council should review annually ICANN’s Strategic Objectives with a view to planning future policy development that strikes a balance between ICANN’s Strategic Objectives and the GNSO resources available for policy development.

Working Party (initial assessment of feasibility and usefulness): CG - Accept with modification:  What would doing this mean?  The Strategic Objectives are at a very high level while policy development tends to be at a very low, almost operational level.  It seems like a good idea to regularly confirm that policy development efforts are in alignment with the strategic plan, or at least not inconsistent with strategic objectives.  The GNSO Council’s role is more tactical than strategic.  That doesn’t mean that strategic thinking shouldn’t be applied.
Staff (initial assessment of feasibility and usefulness):
  • Accept As-Is
  • Accept With modification
  • Reject

Rationale:

MK: accept with modification. From my perspective, it should be the other way around - that ICANN's Strategic Objectives should factor in future policy development activities to ensure there is alignment between the Strategic Objectives and the GNSO resources available for policy development. This could be achieved by requiring/soliciting GNSO Council confirmation that the Strategic Objectives align with future policy development activities.

Basis for Assessment: 
Work in Progress: 
Expected Completion Date for Work in Progress: 
Milestones: 
Responsibility: 

 

 

  • No labels