ICANN wants transparency and accountability input
Date: Monday October 16 2006, @06:23PM
Topic: The Big Picture

ehasbrouck writes: "ICANN today announced the opening of a new public comment forum and list of questions related to principles of transparency and accountability.

Responses are sought by October 31, 2006. Based on the responses received and other research, a first draft of the principles will be published for community comment in November, 2006. It is hoped that the Management Operating Principles will be adopted by the Board as part of the Strategic Plan at the Sao Paulo meeting.

Among the specific questions ICANN is asking is, "What standards of transparency are appropriate in ICANN operations and activity?"

The obvious answer is that the appropriate standard of transparency is set by ICANN's Bylaws: "the maximum extent feasible". It's impossible to tell from today's announcment whether someone at ICANN wants to change that standard.

It's odd that this is intended for inclusion in ICANN's Strategic Plan. The only non-spam comments submitted to ICANN's previous public forum on the draft Strategic Plan were related to exactly this issue. But until now, ICANN has entirely ignored them.

Comments can be sent to principles-comments@icann.org."

This discussion has been archived. No new comments can be posted.
ICANN wants transparency and accountability input | Log in/Create an Account | Top | 1 comments | Search Discussion
Click this button to post a comment to this story
The options below will change how the comments display
Check box to change your default comment view
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Clarification from ICANN
by ehasbrouck on Friday October 27 2006, @03:28PM (#16904)
User #3130 Info | http://hasbrouck.org
Clarification of Consultation Process for the Development of Transparency and Accountability Management Operating Principles [icann.org] (27 October 2006)
[ Reply to This | Parent ]

This article comes from ICANNWatch

The URL for this story is: