Hi Danny Alan has responded with an excellent outline of matters and response to some of your 'matters of principal and practice issues' so there is no need for me to repeat any of that... As we strive to improve and most importantly to aid the RALO and ALSes proper role in policy analysis and comment *and Yes it is a work in progress but I believe it IS progressing all be it not fast enough for many of us ME included* I know you know Danny but all on this list may not that the ICANN Bylaws <http://www.icann.org/en/general/bylaws.htm#XI>(Article XI, Sec. 2, Part 4g) state that "....Each RALO shall serve as the main forum and coordination point for public input to ICANN ...." and as we continue to 'workshop' this with the Regional Leadership and the ALAC in Seoul I'll ensure that your questions (and any others forwarded to this list) are used as focus points to our discussions and debate... Again thanks for helping to make ALAC and At-Large what it is today, and most importantly what it will be after the implementation of the recommendations from the ALAC Review by your diligent and thoughtful ( though at time challenging {not a bad thing at all IMO} input) I hope that time zones and work commitments will also mean your remotely participating in the October Meetings we'll be holding in Seoul, as I and many others find you input very valuable indeed. CLO 2009/10/11 Danny Younger <dannyyounger@yahoo.com>
Hi Cheryl,
I'm sure that you understand that one of the primary points brought forth in the Document Publication Operational Policy was the need to provide ample time for document evaluation (at least fifteen days for public review and download). It's a good policy.
This leads one to ask: "How much time elapsed between the moment this Statement/document was prepared and the time that it was submitted?" Likely that timeframe was measured in minutes rather than in days or weeks.
Did ALAC members or anyone else have the opportunity to comment on this Statement before it was submitted? It sure doesn't look like it.
There is a value in having a set process in place by which Statements are prepared, discussed, reviewed, ratified and submitted. The GAC certainly has a well-defined process, as does the SSAC.
All that I asked for was an explanation of the process by which the ALAC generates Statements on behalf of the at-large community...
please feel free to outline that process step by step that we might better understand things like:
1. at what point is a proposed Statement brought to the attention of the RALOs for discussion and input
2. how much time is allowed for discussion of a proposed Statement before a vote occurs
3. are votes required to affirm a Statement
4. will Statements continue to be submitted to ICANN before they are ratified by a vote
in short, do you have any rules of procedure to govern the formulation and ratification of ALAC Statements, or are you just making it up as you go?
-- Cheryl Langdon-Orr (CLO)