<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif">Thanks. Excellent
material. It goes a long way to addressing the shifting ground
that has got ICANN to this point. I think that some of the white
paper on future challenges does and should be used in our
current discussions re the MS model. Currently, there is a
proposal in the intergroup issues that suggests that power
imbalances need to be addressed -- but it could be put in a
larger frame as something that cuts across structural and
process issues as well.<br>
</font></p>
<p>Marita</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 5/21/2019 3:46 PM, Evan Leibovitch
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMguqh2v-qC0iYadPj_W+heh_j2-FonUgNjq-z+Qix4GQrhFug@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default"
style="font-family:tahoma,sans-serif;color:rgb(11,83,148)"><a
href="https://atlarge.icann.org/correspondence/future-challenges-white-paper-17sep12-en.pdf"
moz-do-not-send="true">https://atlarge.icann.org/correspondence/future-challenges-white-paper-17sep12-en.pdf</a></div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;color:rgb(11,83,148)"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;color:rgb(11,83,148)"><a
href="https://docs.google.com/document/d/1GIWLITB63MNZcG769aceEpTZc23UASdKA5ZS3MUx2WI/edit?usp=sharing"
moz-do-not-send="true">https://docs.google.com/document/d/1GIWLITB63MNZcG769aceEpTZc23UASdKA5ZS3MUx2WI/edit?usp=sharing</a><br>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, 21 May 2019 at 14:06,
Marita Moll <<a href="mailto:mmoll@ca.inter.net"
moz-do-not-send="true">mmoll@ca.inter.net</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 bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif">If anyone
would point me to the two white papers that Evan
mentions in his message below, it would be a useful
addition to our submission to be able to reference
these.</font></p>
<p><font face="Times New Roman, Times, serif">Marita</font><br>
</p>
<div class="gmail-m_4577485599135182954moz-cite-prefix">On
5/18/2019 4:37 PM, Alan Greenberg wrote:<br>
</div>
<blockquote type="cite"> Evan, as much as some people (and I
count myself among them) feel that the overall ICANN model
needs to be changed to address the types of issues you
list in your bullet points below, that is not what this
exercise is about. <br>
<br>
As the name implies, this is <u>evolution</u> to increase
the effectiveness of the current model and not a complete
reorg. That may make it less than useful in the minds of
some, but that is what it is.<br>
<br>
It is not the only such exercise going on. There is one
purely within the GNSO which addresses some of these same
problems but has the potential for worsening some things
(including participation of non-GNSO groups/entities which
some view as impeding the PDP process).<br>
<br>
Is this current process sufficient to address the larger
problems? No (in my mind). But can it provide useful
change without increasing the overall structural problems?
I hope so.<br>
<br>
Alan<br>
<br>
At 18/05/2019 01:58 PM, Evan Leibovitch wrote:<br>
<blockquote type="cite"
class="gmail-m_4577485599135182954cite">Hi Marita,<br>
<br>
I apologize for not making the call. I am very
interested in this topic, but even more interested in
not having my time wasted.<br>
<br>
As has been expressed before, I am extremely skeptical
that the status quo can be disrupted purely from the
inside. There have been quite a few exercises of this
kind before, even high profile moves such as the ATRT
and independence from the US government have been
tortuous but led to little real change in the way
decisions are made. I could even make the case that the
IANA transition has worsened the status of stakeholders
outside the compact of domain buyers and domain sellers.
What is the assurance (or even broad confidence) that
the results of any new work would be heeded? What are
the consequences to ICANN of yet again ignoring the
calls to distribute power more broadly or address its
many fundamental breeches of public trust?<br>
<br>
There are a few key components of ICANN governance that,
so long as they exist, render all talk of real change
aspirational at best.
<ul>
<li>So long as GNSO consensus policy binds the ICANN
Board, the rest of us are essentially powerless. </li>
<li>So long as ICANN's revenue comes solely from
domain acquisition, it is by definition in a
conflict of interest in setting domain policy. </li>
<li>So long as domain sellers sit on both sides of the
negotiating table in development of the RAA and
other instruments of domain regulation, ICANN cannot
be trusted to act impartially. </li>
<li>So long ICANN is accountable to nobody but its
core conflicted community, it will successfully
resist change. "Empowered" my eye. </li>
</ul>
ALAC has diligently participated in multiple previous
"fix the MSM" efforts which have yielded no significant
result. Two white papers produced by ALAC members were
ignored without so much as acknowledgement of their
existence. In this context, exactly how serious is this
latest iteration? A new turnover of ALAC members
provides fresh hope and maybe even new insights, but
lack of institutional memory simply indicates new
iterations of old efforts that have proven to fail. We
hit the most solid of walls whenever intention tries to
turn to execution.<br>
<br>
This just feels so much like ICANN is Lucy and ALAC is
Charlie Brown. Maybe if we try kicking the football
again, this time it will work.....<br>
<br>
What's different this time?<br>
<br>
- Evan<br>
<br>
_______________________________________________<br>
CPWG mailing list<br>
<a
class="gmail-m_4577485599135182954moz-txt-link-abbreviated"
href="mailto:CPWG@icann.org" target="_blank"
moz-do-not-send="true">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg"
target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<br>
_______________________________________________<br>
registration-issues-wg mailing list<br>
<a
class="gmail-m_4577485599135182954moz-txt-link-abbreviated"
href="mailto:registration-issues-wg@atlarge-lists.icann.org"
target="_blank" moz-do-not-send="true">registration-issues-wg@atlarge-lists.icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/registration-issues-wg"
target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/registration-issues-wg</a>
</blockquote>
</blockquote>
</div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank"
moz-do-not-send="true">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
_______________________________________________<br>
GTLD-WG mailing list<br>
<a href="mailto:GTLD-WG@atlarge-lists.icann.org"
target="_blank" moz-do-not-send="true">GTLD-WG@atlarge-lists.icann.org</a><br>
<a
href="https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg</a><br>
<br>
Working Group direct URL: <a
href="https://community.icann.org/display/atlarge/New+GTLDs"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://community.icann.org/display/atlarge/New+GTLDs</a></blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr" class="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 or </span><span
style="font-size:12.8px">@el56</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>