<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Evan</p>
<p>Thanks for your frank description of the phenomenon that ICANN
is, and its new age governance model, which is basically a
neoliberal capture. it is a governance model run by big business,
and openly so. <br>
</p>
<p>I think people here see it but dont do anything bec perhaps they
think that the potential of damage by ICANN isnt that much, and
then Internet debates are still framed by that gov/UN takeover
threat, while the context today is hugely if not entirely changed.</p>
<p>Read this piece in CirleID
<a class="moz-txt-link-freetext" href="http://www.circleid.com/posts/20170420_usa_pharma_sector_extending_dysfunctional_pricing_to_cyberspace/">http://www.circleid.com/posts/20170420_usa_pharma_sector_extending_dysfunctional_pricing_to_cyberspace/</a>
to see how ICANN by allocating crucial digital name-posts to
vested interests and big business (largely US based) can cause
enormous damage that we have not even begun to think about, lost
that we remain in petty issues that ICANN throws at us, and for
which even it doesnt listen to us.</p>
<p>In the above you will read how by inappropriately allocating a
key sectoral gLTD to a small group of big business which is known
to have geo-economic interests at variance with much of the world,
and whose interests hit at crucial global health concerns, ICANN
has made that group a de facto sector regulator -- in an area as
socially crucial as health and pharmaceuticals!</p>
<p>And it is not that people havent raised concerns about such
possibilities. See <a
href="https://www.itforchange.net/sites/default/files/Jurisdiction%20of%20ICANN.pdf">this
civil society statement </a>of a few months back which raised
exactly this prospect of .pharmacy's ownership being used for de
facto pharma sector regulation by US's big pharma. <br>
</p>
<p>This will also happen with automobile industry (.cars), and
every .sector.... you name it!</p>
<p>Would then the section of global civil society that was supposed
to be protecting public interest wrt issues pertaining to ICANN
not be called upon to account for how it let all this happen? Does
such a prospect bother anyone here?</p>
<p>parminder <br>
</p>
<br>
<blockquote
cite="mid:25450C8A50114192BF7D05ABB689FC1D@LENOVOC0574B68"
type="cite">
<div> </div>
<blockquote style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT:
5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir="ltr">
<div style="FONT: 9pt 宋体">----- Original Message ----- </div>
<div style="FONT: 9pt 宋体; BACKGROUND: #e4e4e4; font-color:
black"><b>From:</b> <a moz-do-not-send="true"
title="evan@telly.org" href="mailto:evan@telly.org">Evan
Leibovitch</a> </div>
<div style="FONT: 9pt 宋体"><b>To:</b> <a moz-do-not-send="true"
title="kankaili@gmail.com" href="mailto:kankaili@gmail.com">Kan
Kaili</a> </div>
<div style="FONT: 9pt 宋体"><b>Cc:</b> <a moz-do-not-send="true"
title="at-large@atlarge-lists.icann.org"
href="mailto:at-large@atlarge-lists.icann.org">ICANN
At-Large list</a> </div>
<div style="FONT: 9pt 宋体"><b>Sent:</b> Monday, May 15, 2017 6:53
AM</div>
<div style="FONT: 9pt 宋体"><b>Subject:</b> Re: [At-Large] Auction
Proceeds - where we are and what you can help</div>
<div><br>
</div>
<div dir="ltr">
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR: #0b5394"
class="gmail_default"><span style="FONT-FAMILY:
arial,sans-serif; COLOR: rgb(34,34,34)">On 14 May 2017 at
16:55, Kan Kaili </span><span style="FONT-FAMILY:
arial,sans-serif; COLOR: rgb(34,34,34)" dir="ltr"><<a
moz-do-not-send="true" href="mailto:kankaili@gmail.com"
target="_blank">kankaili@gmail.com</a>></span><span
style="FONT-FAMILY: arial,sans-serif; COLOR:
rgb(34,34,34)"> wrote:</span><br>
</div>
<div class="gmail_extra">
<div class="gmail_quote"><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN:
0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class="gmail_quote">
<div bgcolor="#ffffff">
<div><span style="FONT-FAMILY: 宋体">I fully agree with
you that certain sections of ICANN, primarily from
the registry/registrar side, may resist
discouraging domain parking out of their own
financial interests. However, ICANN, according to
its mandate as defined by the Bylaws, is to
protect the "public interest". As I understand
it, this means foremost to protect the end-users'
interest.</span></div>
</div>
</blockquote>
<div><br>
</div>
<div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">Your perception
is a minority view. While ICANN may be considered to
be acting in the public service as an organization,
the role and voice of the end-user is expressly stated
(and limited) in the ICANN bylaws. Only a single
member of the entire ICANN Board is chosen by
representatives of the end-user viewpoint; even a
Board review that recommended two Board spots was cut
back down.</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default"><br>
</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">Furthermore,
ICANN stands back while the vested interests
constantly assail the legitimacy of ALAC. The At-Large
Review is a perfect recent example, with the reviewers
commenting at length on perceptions by other
communities (who want to silence us) at the expense of
the intrinsic value of having anyone speaking for the
end-user interests.</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default"><br>
</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">When I was
NARALO chair we were trolled frequently by people from
the domain industry imploring "aren't I part of the
public too?" And any time you go to an ALAC session
with the term "public interest" in the title, no
matter what the original intent the meeting devolves
into an hour-long talk-fest without outcome agonizing
about "what is the public interest?".</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default"><br>
</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">Welcome to
ICANN, where the vested interests have an effective
game plan to keep any potential obstacles divisive and
ineffective.</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default"><br>
</div>
</div>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN:
0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class="gmail_quote">
<div bgcolor="#ffffff">
<div><span style="FONT-FAMILY: 宋体">Otherwise, ICANN
will become a DNS industry association and
advocator, no longer to be trusted by the public.</span></div>
</div>
</blockquote>
<div><br>
</div>
<div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">Some would
argue that this has already happened, and that
At-Large is a mainly cosmetic appendage that ICANN
indulges to give it an outward appearance of public
input. It funds competent and well-meaning staff for
At-Large, and (within strict and arbitrary limits)
funds its outreach and capacity-building dreams. But
when it comes time for At-Large to actually affect
ICANN's grand direction the wins are minor.</div>
<br>
</div>
<div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">At the first
At-Large Summit in Mexico City, our final report said
that the gTLD expansion was "unacceptable" in its
proposed state at the time. Very little had changed
when the program finally rolled out, and I remind that
the position has never officially been rescinded. I
highly doubt that the Summit report was even read by
the President and Board Chair to whom it was
presented.</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default"><br>
</div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">There have been
a number of changes at senior management, all in turn
publicly telling At-Large how important we are. Yet I
invite you to find concrete evidence of our actual
big-picture influence.</div>
<br>
</div>
<div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">Everyone should
ask themselves: we may have tweaked some things and
have produced plenty of volume -- but <b>how has
ICANN better, in its management of domain names,
because of At-Large</b>?</div>
</div>
<div><br>
</div>
<div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">At our best we
have helped with course corrections which can be seen
more as damage control than forward-thinking. We have
produced white papers and policy statements that were
painstakingly developed yet received not a word of
official reply (let alone action!) beyond gratitude
for the effort.</div>
<br>
</div>
<div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">Yes, I'm
cynical. I have some right to be, I've helped develop
some of the advice, endorsed by ALAC, which has been
ignored. I've witnessed a lot of the insults,
dismissals and rejections first-hand. I stay involved
in the hope that my successors will have better luck
than I. But based on current activity, such as the
inevitable march towards new gTLD rounds despite the
problems with the last round, the challenges remain as
much as ever. And the At-Large Review, if all of it
is implemented, will make the situation even worse.</div>
<br>
</div>
<div>
<div style="FONT-FAMILY: tahoma,sans-serif; COLOR:
rgb(11,83,148)" class="gmail_default">- Evan</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
At-Large mailing list
<a class="moz-txt-link-abbreviated" href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/at-large">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a>
At-Large Official Site: <a class="moz-txt-link-freetext" href="http://atlarge.icann.org">http://atlarge.icann.org</a></pre>
</blockquote>
<br>
</body>
</html>