I would love for us to get a better picture of the ways each of us, both individually, and though our organizations, are undertaking the tasks below and other related tasks. We need to map the talents, capacities and passions across the NA ALS's... and build stronger ties amongst us.
I believe that such mapping should extend beyond the scope of what defines us as ALSs, and what will define the RALO in relation to ICANN.
Of course my perspective is that of Community Networking and Network Weaving... and my passion is for communications policy and how it intersects with daily life. That is where we need to be doing outreach and education. I dont think the Internet is principally about arcane issues, and I dont think our role is limited to such arcana either.
-MM
On 2/3/07, Luc Faubert <LFaubert@conceptum.ca> wrote:
> [...] The only thing an NARALO has to do is to select
> ALAC committee members, [...]
John, again, the RALO can do much more than that if we want it to (see bylaws below). It's our call. From the perspective where we are trying to bring people on board the NARALO to influence ICANN's processes and outcomes and make their voice heard within ICANN, I'm not sure we're serving these constituents well by limiting NARALO's role to selecting 2 ALAC members. Granted, we should not entertain unrealistic expectations on the impact we can have within ICANN, but this is no reason to lobotomize NARALO.
We've all agreed I think, that we want something light in structure.
On NARALO's role, in addition to selecting 2 ALAC members, ICANN's bylaws at
http://www.icann.org/general/archive-bylaws/bylaws-02jun03.htm#XI-2.4g state that:
j. The ALAC is also responsible, working in conjunction with the RALOs, for coordinating the following activities:
1. Keeping the community of individual Internet users informed about the significant news from ICANN;
2. Distributing (through posting or otherwise) an updated agenda, news about ICANN, and information about items in the ICANN policy-development process;
3. Promoting outreach activities in the community of individual Internet users;
4. Developing and maintaining on-going information and education programs, regarding ICANN and its work;
5 Establishing an outreach strategy about ICANN issues in each RALO's Region;
6. Making public, and analyzing, ICANN's proposed policies and its decisions and their (potential) regional impact and (potential) effect on individuals in the region;
7. Offering Internet-based mechanisms that enable discussions among members of At-Large structures; and
8. Establishing mechanisms and processes that enable two-way communication between members of At-Large Structures and those involved in ICANN decision-making, so interested individuals can share their views on pending ICANN issues.
_________________________________________
Luc Faubert
Conseiller en gouvernance TI et en gestion du changement /
IT governance and change management consulting
GFI Solutions
+1 514 236 5129
www.GFISolutions.com
www.LucFaubert.com
www.isoc.qc.ca
www.ccig.ca
www.maillons.qc.ca
> -----Original Message-----
> From: na-discuss-bounces@atlarge-lists.icann.org
> [mailto:na-discuss-bounces@atlarge-lists.icann.org] On Behalf
> Of John R Levine
> Sent: 2 février 2007 18:10
> To:
na-discuss@atlarge-lists.icann.org
> Subject: Re: [NA-Discuss] Potential Meeting in Vancouver
>
> >> 1) Have a meeting space at the larger meeting, which if there's a
> >> cost ICANN could fund, to allow those of the ALS / candidate ALS
> >> community to meet in-person. Those present could also
> invite others
> >> at the PCNA who are interested in ICANN and At-Large to attend.
>
> This is what we recommended. Like, or moreso than, most
> organizations, ICANN works largely via informal personal
> contacts. It will be vastly more useful to come to a real
> ICANN meeting where you can meet the board, staff,
> registries, registrars, and other constituencies than to a
> meeting of people with no ICANN experience. There is an
> ICANN meeting in Puerto Rico in June which would be good for
> people to attend.
>
> I believe I speak for the other U.S. ALS that have been
> around for a while, when I point out that there has been more
> than one attempt to build an ambitious at large organization,
> all of which quickly failed and live on as, at most, dusty
> web sites. The only thing an NARALO has to do is to select
> ALAC committee members, and the route most likely to lead to
> success is the smallest, lightest weight structure that can
> accomplish that, with no budget, no staff, and no meetings of
> its own. To the extent that we can get an MOU that commits
> ICANN to providing us with the stuff that a RALO is supposed
> to get, so much the better, but that still doesn't require a
> complicated structure.
>
> Also, as Wendy pointed out, if you want to participate in
> ICANN discussions and offer them advice, you can and should
> do so now. I was rather surprised that none of the groups
> who were asking for an in-person meeting submitted advice on
> the proposed WHOIS changes after I sent out a note
> encouraging it. CAUCE CA and CAUCE US did (we worked up a joint
> statement) even though neither of us have any interest in a
> RALO meeting.
>
> R's,
> John
>
> _______________________________________________
> NA-Discuss mailing list
> NA-Discuss@atlarge-lists.icann.org
> http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atl
arge-lists.icann.org
>
_______________________________________________
NA-Discuss mailing list
NA-Discuss@atlarge-lists.icann.org
http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists.icann.org
--
-----------------------------------------------------------------
Executive Director, CTCNet Chicago Chapter
Co-Founder, Chicago Digital Access Alliance
Co-Chair, Illinois Community Technology Coalition
President, Association For Community Networking
Support the efforts of the Chicago Digital Access Alliance: http://www.digitalaccessalliance.org