[governance] Fwd: [At-Large] ICANN Summit Progress Report

[Adam Peake]

perhaps of interest given the recent thread on ICANN and the general public

The at large list is open to anyone interested.

Adam


>Delivered-To: ajp at glocom.ac.jp
>Date: Mon, 10 Sep 2007 13:59:23 -0400
>Thread-Topic: ICANN Summit Progress Report
>Thread-Index: Acfz1FHQz8cGYwCoSCeQZxNEMlws6Q==
>From: "Thompson, Darlene" <DThompson at gov.nu.ca>
>To: <secretariat at atlarge-lists.icann.org>,
>	<na-discuss at atlarge-lists.icann.org>, <alac at atlarge-lists.icann.org>
>X-EMWD-MailScanner: Found to be clean, Not 
>scanned: please contact your Internet E-Mail 
>Service Provider for details
>X-EMWD-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
>	score=3.997, required 5, BAYES_99 2.50, HTML_MESSAGE 0.00,
>	MIME_QP_LONG_LINE 1.40, RDNS_NONE 0.10),
>X-EMWD-MailScanner-SpamScore: sss
>Subject: [At-Large] ICANN Summit Progress Report
>X-BeenThere: alac at atlarge-lists.icann.org
>List-Id: At-Large Worldwide Community
>	<alac_atlarge-lists.icann.org.atlarge-lists.icann.org>
>List-Unsubscribe: 
><http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org>,
>	<mailto:alac-request at atlarge-lists.icann.org?subject=unsubscribe>
>List-Archive: 
><http://atlarge-lists.icann.org/pipermail/alac_atlarge-lists.icann.org>
>List-Post: <mailto:alac at atlarge-lists.icann.org>
>List-Help: <mailto:alac-request at atlarge-lists.icann.org?subject=help>
>List-Subscribe: 
><http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org>,
>	<mailto:alac-request at atlarge-lists.icann.org?subject=subscribe>
>Sender: alac-bounces at atlarge-lists.icann.org
>X-EMWD-MailScanner-Information: Please contact the ISP for more information
>X-EMWD-MailScanner-From: alac-bounces at atlarge-lists.icann.org
>
>Hi all,
>
>Evan and I just has a conference call with Nick 
>regarding the Summit plans so far. It's of 
>course critical that we come up with a plan that 
>meets the expectations of the community, as well 
>as ICANN itself as it will be funding all the 
>costs. As it turns out from our discussion, our 
>goals for the Summit are remarkably similar.
>
>From the point of view of ICANN (as expressed by 
>Nick), the At-Large Community ultimately exists 
>to provide the general public's point of view on 
>relevant issues. For the Summit to be considered 
>as a worthwhile achievement of that goal ­ not 
>to mention provide value for its substantial 
>expense -- it must actually produce policy 
>analysis and recommendations to the rest of the 
>ICANN community.
>
>Certainly educational and social components are 
>vital. However, for the Summit to succeed a 
>significant amount of education and discussion 
>on issues must take place in advance, within the 
>RALOs and ALSs, with final debate taking place 
>and formal consensus recommendations being 
>delivered at the Summit. The event's success 
>will be judged ­ within ICANN itself ­ by its 
>ability to provide useful recommendations and 
>analysis regarding issues of importance, 
>reflecting the diverse but common needs of the 
>At-Large community.
>
>Summit delegates, in order to be funded, will be 
>expected to have already raised relevant issues 
>within their constituencies. We received 
>commitments from Nick that sufficient background 
>information will be provided in many languages, 
>to allow such debate to start well in advance.
>
>We started with the attached ICANN Ensemble 
>document. Nick liked many of the ideas shown 
>there but was concerned the plan did not 
>sufficiently commit the Summit to produce 
>concrete policy documents.
>
>Here is what we need to do:
>
>1.
>Decide which (and how many) policies we would 
>like to work on. Obviously we don¹t have time to 
>work on ALL of ICANN¹s policies at once. So, we 
>need to choose between 3 to 5 of the current 
>issues and work on them. This can be achieved by 
>an on-line poll. (While it will be possible to 
>start debate on long-term issues to be turned 
>into policy at a later date, it is important to 
>choose a number of issues on which At-Large can 
>have an impact within the coming year.)
>
>2.
>Create actual realistic milestones. We need to 
>have dates and things accomplished by those 
>dates to prove to ICANN that we are actually 
>working on this stuff. When they see this, they 
>will be much more likely to fund this venture. 
>This will also be our opportunity to get a 
>commitment out of them. They won¹t commit unless 
>they see work getting done.
>
>3.
>Only those that put the effort into doing the 
>policy work will have the opportunity to go. 
>ICANN will not fund those that just want travel 
>or to socialize. Period.
>
>ICANN will, more than likely, be funding the 
>Secretariats and Chairs to go to the LA meeting 
>to discuss this further. They may also fund one 
>or two others but that is it. The group will 
>schedule at least one conference call during the 
>LA meeting to involve anyone else who wants to 
>participate but will not be there.
>
>
>
>
>
>
>Content-Type: application/msword;
>	name="ICANN Ensemble.doc"
>Content-Description: ICANN Ensemble.doc
>Content-Disposition: attachment;
>	filename="ICANN Ensemble.doc"
>
>
>_______________________________________________
>ALAC mailing list
>ALAC at atlarge-lists.icann.org
>http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
>
>At-Large Official Site: http://www.alac.icann.org
>ALAC Independent: http://www.icannalac.org
____________________________________________________________
You received this message as a subscriber on the list:
     governance at lists.cpsr.org
To be removed from the list, send any message to:
     governance-unsubscribe at lists.cpsr.org

For all list information and functions, see:
     http://lists.cpsr.org/lists/info/governance
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN Ensemble.doc
Type: application/msword
Size: 85504 bytes
Desc: not available
URL: <http://lists.igcaucus.org/pipermail/governance/attachments/20070911/b4ffbe75/attachment.doc>