[At-Large] Fwd: ATLASIII Participation

Tue Oct 15 12:57:37 UTC 2019

On Thu, Aug 1, 2019, 2:40 PM Wolfgang Kleinwächter <
wolfgang at kleinwaechter.info> wrote:

> Hi,
>
> let me join the discussion. ATLAS can have an impact. It is indeed an
> opportunity, but the poutcome has to be very carefully designed (and
> realistic).
>
> I was involved in the Mexico Summit (inter alia by creating the acronym
> :-))) ). In my opinion the Mexcio summit did have an impact. We worked on
> short "Resolutions" which were handed over to the Board. One resolution was
> on At Large representation in the ICANN Board. We were calling for two
> voting seats in the Board. We did not get the two voting seats, but as a
> result of the Mexico ATLAS resolution the non-voting At Large liaison in
> the board was upgraded into one voting seat for At Large in the Board
> (picked by At Large itself). Since that Sebastian, Rinalia and now Leon
> have voting rights. All other ACs have only non-voting liaisons.Before
> Mexico  there was also a discussion to change the At-Large AC into an
> At-Large SO. This make no sense anymore. But to ask for a second voting
> seat (to have the same the representation like an SO in the Board) could
> make sense. This could contribute to more diversity.
>
> My proposal for Montreal is to define three or four very concrete issues
> and to work on language for short resolutions.
>
I am not sure if I have understood it well, but the signals we receive seem
to (mis)lead me to think that there is an (un)intentional flaw in the
design of ATLAS 3.  It is possible that ATLAS 3 is about to make a point
that At Large is lesser than other ACs/SOs. ATLAS III appears more focused
on educating the participants than expecting the participants to contribute
to policy. An 'Important NOTICE: to the Atlas III participants' says "The
program has been designed carefully to develop your knowledge. Attending
all ATLAS III sessions is crucial in order for you to gain the knowledge
and skills needed to work on behalf of the At-Large Community following
ATLAS III." Following, not during.

In Mexico there was a separation of ATLAS from mainstream ICANN, but in the
nature of an early start which somewhat converged into main ICANN sessions
from Monday. During London At Large was a little more equal somehow, but I
am not sure if we are careful about our stature during and after Montreal.

Sivasubramanian M

P. S.  Carlton made his excellent observations during ATLAS II.  Is there
even an acknowledgement of his notions of the value of volunteer time
dwarfing the cost of necessary, basic arrangements such as travel and a bed
to sleep?

This could include issues discussed under PDPs or WS2, but also more
> general issues as cyberstability, DNS market development or human rights
>
> Two cents
>
> Wolfgang
>
>
> Vanda Scartezini <vanda at etges.com.br> hat am 31. Juli 2019 um 22:07
> geschrieben:
>
> Maureen, agree with your points. However it is not my opinion that Mexico
> or London Summit can be perceived as no impact. Anytime we shall analyze
> anything with the perspective of the occasion in time. Like in History
> anyone can criticize any AC/SOs and their constituencies about the poor
> work done if we look to the past with the experiences and demands of the
> present.
>
> Mexico was an quite interesting experience to have all ALS from around the
> world experiment work together with their different cultural behavior,
> views of the world and ICAnn etc..
>
> London experience was richer with policy discussion going deeply discussed.
>
> Certainly reducing the number of participants is positive to achieve a
> more focus content and results.
>
> ALAC is the only group embracing the whole world and sometimes is
> difficult for anyone with a more focused approach to understand its
> impact.  What is quite important is the touched community has appropriated
> ALAC spread of knowledge and improved the participation after both summits.
>
> Thanks all for sharing different views, we can always enrich the process.
>
>
>
> *Vanda Scartezini*
>
> *Polo Consultores Associados*
>
> *Av. Paulista 1159, cj 1004*
>
> *01311-200- Sao Paulo, SP, Brazil*
>
> *Land Line: +55 11 3266.6253*
>
> *Mobile: + 55 11 98181.1464 *
>
> *Sorry for any typos.  *
>
>
>
>
>
>
>
>
>
>
>
> *From: *At-Large <at-large-bounces at atlarge-lists.icann.org> on behalf of
> Maureen Hilyard <maureen.hilyard at gmail.com>
> *Date: *Saturday, July 13, 2019 at 21:09
> *To: *"karl at cavebear.com" <karl at cavebear.com>
> *Cc: *'At-Large Worldwide' <at-large at atlarge-lists.icann.org>
> *Subject: *Re: [At-Large] Fwd: ATLASIII Participation
>
>
>
> Karl, I am very grateful that you can see what the ALAC is trying to do
> with regards to ATLASIII - developing a roadmap for the future.
>
>
>
> I cannot imagine that ALAC and At-Large is going to miraculously change
> overnight when it has been perceived that we made no positive impacts from
> our previous Summits. However, this time I believe that we are truly
> attempting to offer an event where participants can get a better
> understanding not only of why it is important we take the end-users
> perspective to all discussions that take place in ICANN, but also why it is
> important that we all share common messages to minimise the confusion that
> people have about At-Large. This is being supported already by the weekly
> CPWG meetings and members of this WG who are already committed to this
> model.
>
>
>
> I am thankful that the Board made the decision to reduce the ATLAS
> funding, and made us change the way we view Summits and what should aim to
> achieve. This has made us also look not only at what we should do, but also
> how we should go about doing it.
>
>
>
> Evan is correct, we are not providing a SUMMIT in the traditional sense.
> This was something that had to change with the reduced funding and thus the
> reduced number for whom we could offer travel sponsorship.  We have
> retained the name ATLAS this time because it is still a gathering of
> At-Large members.
>
>
>
> However, the reductions forced us to deal with challenges, especially with
> regards to our selection process and the programme.  One of the positives
> that has come out of this is that the ideas for the development of both
> emerged from discussions with our ATLAS volunteers. The selection process
> came about through some robust discussion by the members which was endorsed
> by the five representatives of the ALAC Leadership Team.  Even though there
> are still the inevitable complaints about inequities, the majority of those
> who were selected, are looking at this as an opportunity to learn more
> about At-Large and to work on its behalf in the future. This is a primary
> goal for this ATLAS - the work for these participants will not end with
> ATLAS in Montreal. There is an expectation of continued engagement even
> after ATLAS - in their regions, in At-Large and in ICANN.  This is where we
> see that ICANN will get value out of this event.
>
>
>
> Because this is a new experience for us, we are still finding our way, but
> I thank the Staff and the Selection Committee for the hard work they
> contributed to the selection of those ATLAS participants that ICANN will
> sponsor for the ATLAS. The ATLAS programme will be more than "just capacity
> building". The five pre-application modules were to ensure that there was
> at least a benchmark that had been achieved by all. And while they were
> basic for many of our experienced members, it was important that everyone
> was at least starting on the same page, albeit at different levels.
>
>
>
> The proposed ATLAS programme will require this knowledge as the groups
> become involved in the main activity which I believe will help them not
> only learn more about how At-Large thinking fits into that of the rest of
> ICANN but also what all the discussions mean to us as end-users.  This is
> the gap of learning we want to close for those newer members of the ATLAS
> group, supported by our more experienced participants. There is no way you
> could offer the same level of learning on a webinar and you wouldn’t be
> able to encourage as much individual participation as will be possible at
> this event.
>
>
>
> Our greatest numbers of participants are justifiably coming from our
> underdeveloped regions. Evan's complaints that there are few NARALO members
> in the ATLAS, yet they are the best served of all the regions with regards
> to ongoing capacity building and updating on latest issues - check out the
> Community Skype chat just about every week. I thank NARALO members for
> opening up the opportunity for other less advantaged At-Large members to
> attend.
>
>
>
> I am looking forward not only to what we will achieve at our ATLAS but the
> new thinking we can inject into our RALOs and our regions and the work that
> these selected participants will contribute to our At-Large of the future.
>
>
>
> My 2c
>
> Maureen
>
>
>
> On Sun, Jul 14, 2019 at 7:24 AM Karl Auerbach <karl at cavebear.com> wrote:
>
> I agree with your dim assessment in many ways, but not all.
>
> There is something that the ALAC can do, and relatively easily.
>
> The issue of naming is beginning to move beyond the domain name system -
> there will be (and are) issues of naming of "topics" for IoT networking;
> there are issues in cloud computing of entities as they split, move, and
> merge; etc.
>
> Now on one hand there is a lot of technological issues in there - which
> are better left to the IETF and similar groups.
>
> On the other hand there are major non-technical lessons to be learned from
> ICANN of what ought to be done in the world of governance including issues
> of whether-or-not-to-govern, what-to-do, what-not-to-do, ownership
> information access (the whois issue again), etc.
>
> The ALAC of all the bodies in ICANN, is in the best position to step back
> and give an unbiased (at least, commercially unbiased) assessment and
> roadmap for that future.
>
>     --karl--
>
>
>
> On 7/13/19 2:46 PM, Evan Leibovitch wrote:
>
> As ICANN enters a period of austerity while it panics its way to
> re-opening the gTLD floodgates, ALAC is at a crossroads. Ridiculed wherever
> it is not written off for its navel-gazing and complete ineffectiveness at
> bringing forth any useful input unique to end users, ALAC struggles for
> legitimacy whether it knows it or not. No wonder ATLAS 3 was so poorly
> funded; ICANN suspects that nothing useful (for its purposes) will come out
> of the current direction of yet more process and more capacity building.
> They think it's a waste of money so they give the minimum they can get away
> with. Who can blame them?
>
>
>
> ALAC had the chance to prove them wrong this time and to do something
> different, to take the time necessary to have the mortally necessary debate
> within ALAC of how it can be relevant to ICANN and revisit how to serve its
> bylaw-stated mission. It needed to counter the awful external ALAC review
> with a thoughtful internal one.
>
>
>
> But no.
>
>
>
> Based on the published objectives of ATLAS 3
> <https://community.icann.org/download/attachments/71605234/ATLASIII%20Overview%20-%206%20Feb.png?version=1&modificationDate=1549471752000&api=v2>,
> we are in for more of the same:
>
> ·         Leadership Development: another way to say "capacity building",
> training that could be easily be done by webinars and/or the same CBT used
> to deliver "what is ICANN" that would be accessible by anyone, not just the
> 60 attendees
>
> ·         Programming: what are the tasks? "Define and structure",
> "Develop meeting processes". And the outcomes of programming? Reports,
> video interviews, and "fully functional next generation leaders".
>
> IOW, continued navel gazing that seems to be focused most on the
> succession plans of existing leadership. Policy doesn't even get lip
> service, the word isn't mentioned once.
>
>
>
> Nothing in the objectives points to how ALAC can actually work better to
> understand what end users need from ICANN and then to communicate those
> needs to the greater community. So why not stop calling it a Summit and
> call it what it is -- Leadership training? Probably because, presented that
> way, it wouldn't have been funded. Let's just say it's unlikely there will
> be an ATLAS 4 once ICANN sees how its money was spent this time.
>
>
>
> - Evan
>
>
>
>
>
> _______________________________________________
>
>
> At-Large mailing list
>
>
> At-Large at atlarge-lists.icann.org
>
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
>
>
>
>
> At-Large Official Site: http://atlarge.icann.org
>
> _______________________________________________
>
>
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
>
>
> _______________________________________________
> At-Large mailing list
> At-Large at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
> At-Large Official Site: http://atlarge.icann.org
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
> _______________________________________________ At-Large mailing list
> At-Large at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large
> Official Site: http://atlarge.icann.org
> _______________________________________________ By submitting your personal
> data, you consent to the processing of your personal data for purposes of
> subscribing to this mailing list accordance with the ICANN Privacy Policy (
> https://www.icann.org/privacy/policy) and the website Terms of Service (
> https://www.icann.org/privacy/tos). You can visit the Mailman link above
> to change your membership status or configuration, including unsubscribing,
> setting digest-style delivery or disabling delivery altogether (e.g., for a
> vacation), and so on.
>
>
>
>
> _______________________________________________
> At-Large mailing list
> At-Large at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
> At-Large Official Site: http://atlarge.icann.org
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
>
> _______________________________________________
> At-Large mailing list
> At-Large at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
> At-Large Official Site: http://atlarge.icann.org
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/at-large/attachments/20191015/0e543747/attachment-0001.html>