Re: [ispcp] ISPCP Statement on Adoption of the Current Strategic Plan -- FOR COMMENT
Mark, OK with me Tony Harris
The ISPCP Constituency urges the ICANN Board not to ratify, adopt, or approve the current Strateigc Plan in its current form.
The current Strategic Plan simply does not have the consensus of the ICANN Community. Ratifying the Strategic Plan would confer an stamp of authority on the plan that is inappropriate. It would also codify strategic goals which do not have the consensus buy-in of the ICANN community.
Instead, the ISPCP community thinks the current Strategic Plan should remain as a guide and historically significant document for ICANN's work until a Strategic Plan emerges from the revised planning process underway this week.
Some have suggested that the current Strategic Plan is needed as a defense against organizations who might be inclined to suggest that ICANN has no plan or vision for the future. We do not agree. ICANN has an operational plan that takes us through the next year that defines, very clearly, short-term goals for the organization. In addition, an open and participative planning process is currently beging developed for the next planning cycle.
The ISPCP constituency remains committed to the strategic planning process and many of our members have participated in this week's group planning process. However, adopting the current version of the Strategic Plan would be a significant retreat from the basic principle of consensus development of policy and plans for our organization. We urge all members of the board to not formally adopt or ratify the current Strategic Plan. -- Mark McFadden Internet and Security Programs University of Wisconsin Milwaukee School of Continuing Education 161 W. Wisconsin Ave., Suite 6000 Milwaukee, WI 53203 v: 414-227-3243 e: mcf@uwm.edu w: http://www.sce.uwm.edu
--
I'm also ok with this ANTÓNIO TAVARES -----Mensagem original----- De: owner-ispcp@gnso.icann.org [mailto:owner-ispcp@gnso.icann.org] Em nome de Your Name Enviada em: terça-feira, 12 de julho de 2005 07:30 Para: Mark McFadden; ISPCP@icann.org; mcf@uwm.edu Assunto: Re: [ispcp] ISPCP Statement on Adoption of the Current Strategic Plan -- FOR COMMENT Mark, OK with me Tony Harris
The ISPCP Constituency urges the ICANN Board not to ratify, adopt, or approve the current Strateigc Plan in its current form.
The current Strategic Plan simply does not have the consensus of the ICANN Community. Ratifying the Strategic Plan would confer an stamp of authority on the plan that is inappropriate. It would also codify strategic goals which do not have the consensus buy-in of the ICANN community.
Instead, the ISPCP community thinks the current Strategic Plan should remain as a guide and historically significant document for ICANN's work until a Strategic Plan emerges from the revised planning process underway this week.
Some have suggested that the current Strategic Plan is needed as a defense against organizations who might be inclined to suggest that ICANN has no plan or vision for the future. We do not agree. ICANN has an operational plan that takes us through the next year that defines, very clearly, short-term goals for the organization. In addition, an open and participative planning process is currently beging developed for the next planning cycle.
The ISPCP constituency remains committed to the strategic planning process and many of our members have participated in this week's group planning process. However, adopting the current version of the Strategic Plan would be a significant retreat from the basic principle of consensus development of policy and plans for our organization. We urge all members of the board to not formally adopt or ratify the current Strategic Plan. -- Mark McFadden Internet and Security Programs University of Wisconsin Milwaukee School of Continuing Education 161 W. Wisconsin Ave., Suite 6000 Milwaukee, WI 53203 v: 414-227-3243 e: mcf@uwm.edu w: http://www.sce.uwm.edu
-- -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.12/46 - Release Date: 11/7/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.12/46 - Release Date: 11/7/2005
participants (2)
-
Antonio Tavares -
Your Name