<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394">I see the issue of accountability as one of a few that keep At-Large obsessed with its own internal processes to the detriment of its actually being able to affect change within ICANN.<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394">Consider that:</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394"><ul><li>Fully one-third of ALAC, assigned to it by the Nominating Committee is unaccountable to anyone <u>by design</u></li><li>The rest is elected from At-Large Structures, a self-selected group of organizations that themselves are accountable, at best, to a membership that usually doesn't care -- or by self-selected individuals accountable only to themselves</li><li>No mechanisms have ever been contemplated -- let alone put in place -- to enable accountability to the mainstream of Internet users</li><li>After decades of debate At-Large is far from resolution of whether its constituency is registrants or non-registrant end-users. A distressing amount of ALAC commentary is in service to registrants, rather than non-registrant end-users who really couldn't care less about, for instance, registrar-registry relationships.</li></ul></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394">Out of all the qualities that have come to define At-Large's aspirational vision of itself -- accountable, transparent, diverse -- the component that gets the least attention is effective. We spend far more time on internal processes than policy, and over my decades of involvement I have come to the belief that this is deliberate. That is, so long as ALAC continues to consume itself with ... itself ... it will forever be retarded in its bylaw-given mandate. As such, the vested interests maintain a clear path to inflict their path without any resistance from the public interest.<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394"><br clear="all"></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div style="text-align:center"><div style="text-align:left">Evan Leibovitch, <span style="font-size:12.8px">Toronto Canada</span></div><div style="text-align:left"><span style="font-size:12.8px">@evanleibovitch / </span><span style="font-size:12.8px">@el56</span></div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 19, 2023 at 9:49 AM David Mackey via CPWG <<a href="mailto:cpwg@icann.org">cpwg@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">Hi Hadia,</font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal;min-height:14px"><font face="arial, sans-serif"><br></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">Thank you for your cogent analysis by taking the original research and applying it for relevance to the At-Large community. I benefit from your analysis. It definitely adds to the conversation originally triggered by Joanna.<span> </span></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal;min-height:14px"><font face="arial, sans-serif"><br></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">I concur with you about the need to promote and encourage research within At-Large, but I think it might be wise to broaden the scope to include ICANN, At-Large & Global End Users. The idea of encouraging research may align with some of Evan’s ideas, although the pragmatic hurdle of funding research cannot be avoided.<span> </span></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal;min-height:14px"><font face="arial, sans-serif"><br></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">In addition to the need for more academic research, I believe Maureen’s contribution yesterday highlights an important dimension of the environment in which At-Large exists. Specifically, Maureen’s quote which follows caught my attention … “You can't compare the work that is done by volunteers in the ALAC and the GAC who don't come to the ICANN table with the technical knowledge and expertise of the SO community, so that AC end-user interests are dismissed as insignificant.”<span> </span></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal;min-height:14px"><font face="arial, sans-serif"><br></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">Hadia,I think the role you identify at the end of your analysis which addresses Quiet Politics aligns with Maureen’s statement. My experience with technology tells me this is a non-trivial and never-ending task. However, At-Large can be successful in this task with support from staff plus constant effort by ALSs & individual members. The need for appropriate funding, again, cannot be avoided.<span> </span></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal;min-height:14px"><font face="arial, sans-serif"><br></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">I finish with a question to the At-Large community, which was triggered from your statement … “Promoting and ensuring effective accountability mechanisms are in place”.<span> </span></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal;min-height:14px"><font face="arial, sans-serif"><br></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">I’m not familiar with the term “accountability mechanisms”. Maybe someone with more governance experience and knowledge of At-Large history can share their ideas<span> </span>and/or views of past conversations on the topic of accountability mechanisms within ICANN & At-Large. Accountability mechanisms seem to be an important issue which could be linked to the legitimacy of At-Large, and ICANN as an institution.</font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal;min-height:14px"><font face="arial, sans-serif"><br></font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">Cheers,</font></p>
<p style="margin:0px;font-stretch:normal;line-height:normal"><font face="arial, sans-serif">David</font></p></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 18, 2023 at 6:30 PM Hadia El Miniawi via CPWG <<a href="mailto:cpwg@icann.org" target="_blank">cpwg@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:"times new roman","new york",times,serif;font-size:13px"><div></div>
<div dir="ltr">Dear Joanna,</div><div dir="ltr"><br></div><div dir="ltr">Thank you for sharing this interesting read. I briefly tried to look at the study from an At-Large perspective and how we could use some of the learnings to benefit the work that we do. But first let me share some notes and observations from the study which could be of interest to At-Large:</div><div dir="ltr"><br></div><div dir="ltr"><ul dir="ltr"><li>The study looked into which stakeholder groups have a high influence in shaping the language tone of GNSO meetings, the transcripts analyzed were of the nine GNSO stakeholders, thus the study in that regard is basically an analysis of the language influence and power within the GNSO and not at ICANN in general</li><li>ICANN was seen as focusing on technical efficiencies and customer satisfaction, failing to address political and public policy implications </li><li>The length of ICANN multi-stakeholder policy development could hinder effective participation of some stakeholders, most probably those who are lesser resourced. </li><li>The lack of capacity of lesser resourced stakeholders to understand the complexity of " technically opaque policy fields" can lead to asymmetric power that threatens equal participation. </li><li>The importance of an effective accountability mechanism </li><li>The Hegemonic discourse analysis focused on GNSO meetings and the role played by language, however the conclusion extends the findings to the entire ICANN multi-stakeholder practice. Extending the findings to the entire ICANN multi-stakeholder practice requires considering stakeholder groups other than the GNSO and other processes and technical considerations. </li><li>The quite politics part generally speaking applies to all multi-stakeholder practices, thus it is neither limited specifically to the GNSO nor generally to ICANN</li><li>The participatory evangelism part is quite interesting because it speaks to the difference between participation and influence over the decision.</li></ul><div dir="ltr">As an At-large community I see a role for us in </div><div dir="ltr"><ul dir="ltr"><li><b>Addressing the Quite Politics Part: </b>Continue to develop skill development programs that help stakeholders with lesser resources understand the policy issues, this would help address the issue of more dominant and skilled groups being in control.</li><li><b>Addressing Participants Evangelism Part: </b>Promoting and ensuring effective accountability mechanisms are in place, which would ensure both participation and influence over decision.<b> </b></li><li>Promote and encourage research within the At-large community in order to know more about At-large participation and how we could improve it.</li></ul></div></div><div dir="ltr">Kind regards</div><div dir="ltr">Hadia</div><div dir="ltr"><br></div><div dir="ltr"> </div><div><br></div>
</div><div id="m_8788712038454696972m_2097989676288895787ydp7469e145yahoo_quoted_2654919180">
<div style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px;color:rgb(38,40,42)">
<div>
On Tuesday, April 18, 2023 at 01:54:39 PM EDT, jkuleszaicann--- via CPWG <<a href="mailto:cpwg@icann.org" target="_blank">cpwg@icann.org</a>> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="m_8788712038454696972m_2097989676288895787ydp7469e145yiv4702086189"><div><div><p><span lang="EN-US">Hi all,</span></p><p><span lang="EN-US"> </span></p><p><span lang="EN-US">Thanks for the rich and informative feedback. Indeed, Bill, I thought that comparing and contrasting the three papers (two studies, if you will) was interesting and worthy of an e-mail exchange. It is thought-provoking that, as you observe, an ICANN PDP study fully abstracts from any end-user input. I do share David and Evan’s concerns that the end user community falls largely outside the research scope, regardless of whether its an ICANN-commissioned legitimacy study (J.A. Scholte) or an independent, young researcher’s work with the telling typo in our constituency’s name (van Klyton et al). The quiet politics section is particularly interesting. Referring to the ICANN MSM (not just the GNSO) it notes “a lack of sufficient specialized knowledge“ that “might result in an inability of lesser-resourced stakeholders to sustain high salience for an issue over an extended period, which facilitates control by dominant and more skilled groups”, which is what Maureen points to if I’m reading her message correctly. These are particularly interesting in light of the MSM plenary in Cancun, where we found it difficult to identify specific challenges and offer solutions. This and similar research work might help us – the ICANN community – address these needs, adjust, and evolve, if that’s what we truly wish to see happen. Not that these observations are particularly novel or revolutionary, but they do give us the background to use in our policy and advocacy work. </span></p><p><span lang="EN-US"> </span></p><p><span lang="EN-US">Any further thoughts are most welcome, thanks for all the feedback received thus far. </span></p><p><span lang="EN-US"> </span></p><p><span lang="EN-US">With all best wishes,</span></p><p><span lang="EN-US">Joanna </span></p><p><span lang="EN-US"> </span></p><div id="m_8788712038454696972m_2097989676288895787ydp7469e145yiv4702086189yqt11571"><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0cm 0cm"><p><b>From:</b> CPWG <<a href="mailto:cpwg-bounces@icann.org" target="_blank">cpwg-bounces@icann.org</a>> <b>On Behalf Of </b>Bill Jouris via CPWG<br clear="none"><b>Sent:</b> Tuesday, April 18, 2023 7:27 PM<br clear="none"><b>To:</b> <a href="mailto:cpwg@icann.org" target="_blank">cpwg@icann.org</a><br clear="none"><b>Subject:</b> Re: [CPWG] Suggested reading: "Hegemonic practices in multistakeholder Internet governance: Participatory evangelism, quiet politics, and glorification of status quo at ICANN meetings"</p></div><p> </p><div id="m_8788712038454696972m_2097989676288895787ydp7469e145yiv4702086189"><div><p>Hi Joanna, </p></div><div><p> </p></div><div><p>Thanks for this. </p></div><div><p> </p></div><div><p>I note that the study looks (if I'm reading it correctly) at practices *within* the GNSO, rather than across ICANN generally. </p></div><div><p> </p></div><div><p>There are certainly similarities in the practices. But which ICANN stakeholders dominate the overall organization is, unfortunately, not addressed. And that is something we should be concerned with. </p></div><div><p> </p></div><div><p>Bill Jouris </p></div><div><p style="margin-bottom:12pt"> </p><div id="m_8788712038454696972m_2097989676288895787ydp7469e145yiv4702086189ymail_android_signature"><p><a shape="rect" href="https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature" rel="nofollow" target="_blank">Sent from Yahoo Mail on Android</a></p></div><p> </p><blockquote style="margin-left:0cm;margin-right:0cm;margin-bottom:15pt"><div><div id="m_8788712038454696972m_2097989676288895787ydp7469e145yiv4702086189yqtfd65308"><div><p><span style="font-family:sans-serif;color:rgb(109,0,246)">On Tue, Apr 18, 2023 at 2:17 AM, jkuleszaicann--- via CPWG</span></p></div><div><p><span style="font-family:sans-serif;color:rgb(109,0,246)"><<a shape="rect" href="mailto:cpwg@icann.org" rel="nofollow" target="_blank">cpwg@icann.org</a>> wrote:</span></p></div></div></div><div id="m_8788712038454696972m_2097989676288895787ydp7469e145yiv4702086189yqtfd62845"><div style="border-style:none none none solid;border-left:1pt solid rgb(109,0,246);padding:0cm 0cm 0cm 15pt;margin-top:7.5pt"><p>_______________________________________________<br clear="none">CPWG mailing list<br clear="none"><a shape="rect" href="mailto:CPWG@icann.org" rel="nofollow" target="_blank">CPWG@icann.org</a><br clear="none"><a shape="rect" href="https://mm.icann.org/mailman/listinfo/cpwg" rel="nofollow" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br clear="none"><br clear="none">_______________________________________________<br clear="none">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 (<a shape="rect" href="https://www.icann.org/privacy/policy" rel="nofollow" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a shape="rect" href="https://www.icann.org/privacy/tos" rel="nofollow" target="_blank">https://www.icann.org/privacy/tos</a>). 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. </p></div></div></blockquote></div></div></div></div></div></div><div id="m_8788712038454696972m_2097989676288895787ydp7469e145yqt78879">_______________________________________________<br clear="none">CPWG mailing list<br clear="none"><a shape="rect" href="mailto:CPWG@icann.org" rel="nofollow" target="_blank">CPWG@icann.org</a><br clear="none"><a shape="rect" href="https://mm.icann.org/mailman/listinfo/cpwg" rel="nofollow" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br clear="none"><br clear="none">_______________________________________________<br clear="none">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 (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</div></div>
</div>
</div></div>_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</blockquote></div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</blockquote></div>