<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Excellent advice Kieren - thank you.<br>
<br>
<div class="moz-cite-prefix">On 28/09/2015 15:06, Kieren McCarthy
wrote:<br>
</div>
<blockquote
cite="mid:CAA4fB=07+sYcVS3NQGG+XM1yjAutTpvtzMmvJwopjfxQXUDyvg@mail.gmail.com"
type="cite">
<div dir="ltr">To get back to the initial theme of this email
thread: communications.
<div><br>
</div>
<div>Yes, the CCWG report as it currently stands is severely
lacking in clear communications.</div>
<div><br>
</div>
<div>I doubt that clear communications will resolve the current
impasse but I have yet to see a single situation where clear
communications has not helped.</div>
<div><br>
</div>
<div>Here is my advice to this group, based on having been a
comms professional for 20 years.</div>
<div><br>
</div>
<div><br>
</div>
<div>1. Keep your report. It is how this group works. Trying to
bend it into clear communications for the rest of the world
will be a tiring and pointless task.</div>
<div><br>
</div>
<div>2. Write a second report specifically designed for
non-ICANNers to read. Think: Congressmen, your own senior VPs
whose eyes rollover whenever you mention the word "ICANN".
Smart people who couldn't care less about ICANN but do want to
be up-to-date and informed about important developments.</div>
<div><br>
</div>
<div>3. Create a sub-group of people who actually write those
kinds of reports for a living to produce the second report.</div>
<div><br>
</div>
<div>4. Here is what is missing in what the CCWG is currently
proposing:</div>
<div><br>
</div>
<div>* This is no clear rationale for why these changes are
needed</div>
<div>* There is no clear explanation for why these solutions
were chosen</div>
<div>* There is no clear explanation for what happens if these
things aren't done</div>
<div><br>
</div>
<div>5. Here are the components of the current CCWG plans that
undermine it:</div>
<div><br>
</div>
<div>* It is both too vague and too detailed</div>
<div>* Too vague: the overall scaffolding is not explained
sufficiently or clearly.</div>
<div>* Too detailed: no one but not one outside the 50 GNSO
obsessives in this world want anything to do with obscure
voting procedures that they will never participate in. And no
one but no one wants to read pages about the process you
followed except in the most enormously general terms.</div>
<div><br>
</div>
<div>* It is too complex</div>
<div>* If you want the internet community to override the Board,
then it needs to be clear to people outside ICANN how that
works. Just imagine a completely different organization. </div>
<div><br>
</div>
<div>Imagine you are reading a report about how the car industry
is allowed to overrule the international body that regulates
emissions. If you are faced with a dozen pages over how a
specific subgroup of the car industry, under a weighted voting
system, is able to overrule a decision not withstanding a
challenge from a specific group of plant union workers who
would then be expected to enter an as-yet unspecified
arbitration process whose final result would require a
separate process, also under weighted voting, that would
reconsider the results of the report and decides whether to
empower a new group....</div>
<div><br>
</div>
<div>You see that and you say: this is a mess and won't ever
work.</div>
<div><br>
</div>
<div>But if you read: an override would require all groups from
the manufacturers to the dealers to the pant worker union to
agree... well then you can have some confidence in it.</div>
<div><br>
</div>
<div>The shorter version of this point is: the GNSO needs to
pull its head out its ass.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Now to get to the nub of it:</div>
<div><br>
</div>
<div>There are several very, very good reasons why there should
be a "member" of ICANN. Focus on them (at least in the second,
clear comms, report).</div>
<div><br>
</div>
<div>Two of the biggest I would say are:</div>
<div><br>
</div>
<div>* Without a member, the internet community will never be
able to legally separate IANA from ICANN. That is the one,
single, unquestionable power that the NTIA currently has: to
cut that contract. Under the Board's MEM plan, that
unquestionable right does not and will not exist.</div>
<div><br>
</div>
<div>* Without a member, the Board can pass a two-thirds
resolution to move its headquarters to Beijing and there is
nothing the rest of the internet community can do about it.
The Board's MEM approach is so convoluted that it could be
tied up in pseudo-legislation for the next decade. The member
approach provides a legal, unassailable right to reject that
and at the same time kick the Board off for good measure.</div>
<div><br>
</div>
<div><br>
</div>
<div>These are clear scenarios that would currently never happen
because the NTIA is in charge. When the NTIA is gone, they
have to become impossible. And the member model is the clear
path, written into existing US corporate law i.e. not some
special hodge-podge of ideas dreamed up in the penthouse suite
of an LA hotel. </div>
<div><br>
</div>
<div>Tell that to Congress and then let ICANN Corporate explain
why their approach is better.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>* Last suggestion: stop calling it the "single member
model". Call it something that makes immediate sense to
everyone and has a positive feel to it. That way people can
understand it. And you give the Board a way to save face.</div>
<div><br>
</div>
<div><br>
</div>
<div>Hope this is helpful.</div>
<div><br>
</div>
<div><br>
</div>
<div>Kieren</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Sep 27, 2015 at 3:23 PM, Dr
Eberhard W Lisse <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:el@lisse.na"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:el@lisse.na">el@lisse.na</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div>Paul,</div>
<div><br>
</div>
<div>to be precise, categoric and emphatic, we want the
reasons (WHY).</div>
<div><br>
</div>
<div>We have seen shared the understanding of WHAT the
Board is saying.</div>
<div><br>
</div>
<div>And apparently we need to find out how to ask the
Board, because they seem to have issues with it.</div>
<span class="">
<div><br>
</div>
<div>el<br>
<br>
--
<div>Sent from Dr Lisse's iPad mini</div>
</div>
</span>
<div>
<div class="h5">
<div><br>
On 27 Sep 2015, at 15:15, Paul Rosenzweig <<a
moz-do-not-send="true"
href="mailto:paul.rosenzweig@redbranchconsulting.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@redbranchconsulting.com</a></a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p style="margin-top:0px" dir="ltr">Yes oracle
of Delphi. What is the Board view? Nobody
asked you say. We are asking now?</p>
<p dir="ltr">--<br>
Paul<br>
Sent from myMail app for Android</p>
Sunday, 27 September 2015, 06:09PM -04:00 from
Dr Eberhard W Lisse <<a
moz-do-not-send="true"
href="mailto:epilisse@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:epilisse@gmail.com">epilisse@gmail.com</a></a>>:<br>
<br>
<blockquote style="border-left:1px solid
#fc2c38;margin:0px 0px 0px 10px;padding:0px
0px 0px 10px"
cite="http://14433917980000079312">
<div>
<div>
<div>
<div>Than what is it, what you are
stating?</div>
<div><br>
</div>
<div><br>
</div>
<div>el<br>
<br>
--
<div>Sent from Dr Lisse's iPad mini</div>
</div>
<div>
<div><br>
On 27 Sep 2015, at 14:14, Chris
Disspain <<a
moz-do-not-send="true"
href="https://e-aj.my.com/compose/?mailto=mailto%3aceo@auda.org.au"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:ceo@auda.org.au">ceo@auda.org.au</a></a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span
style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)">No
El, that is emphatically,
categorically and precisely not
what I am stating.<br>
<div>
<p
style="margin:0px;font-style:normal;font-variant:normal;font-weight:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px;color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br>
<br>
</p>
<p
style="margin:0px;font-style:normal;font-variant:normal;font-weight:normal;font-size:13px;line-height:normal;font-family:Verdana;color:rgb(148,67,251);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Cheers,</p>
<p
style="margin:0px;font-style:normal;font-variant:normal;font-weight:normal;font-size:13px;line-height:normal;font-family:Verdana;color:rgb(148,67,251);min-height:16px;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br>
</p>
<p
style="margin:0px;font-style:normal;font-variant:normal;font-weight:normal;font-size:13px;line-height:normal;font-family:Verdana;color:rgb(148,67,251);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Chris</p>
</div>
<br>
<div>
<blockquote type="cite">
<div>On 28 Sep 2015, at
07:06 , Dr Eberhard W
Lisse <<a
moz-do-not-send="true"
href="https://e-aj.my.com/compose/?mailto=mailto%3aepilisse@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:epilisse@gmail.com">epilisse@gmail.com</a></a>>
wrote:</div>
<br>
<div>
<div>
<div
name="messageBodySection">Chris,<br>
<br>
are you seriously
stating that the Board
does not have to give
reasons because it was
unaware we would like
to unserstand why, or
are are saying "You
gotta ask me nicely"?
(Jack Nicholson as Col
Jessup in "A few good
men")<br>
<br>
greetings, el</div>
<div
name="messageSignatureSection"><br>
--<br>
Sent from Dr Lisse's
iPhone 5s<br>
</div>
<div
name="messageReplySection"><br>
On 27 Sep 2015, 13:31
-0700, Chris Disspain
<<a
moz-do-not-send="true"
href="https://e-aj.my.com/compose/?mailto=mailto%3aceo@auda.org.au"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:ceo@auda.org.au">ceo@auda.org.au</a></a>>,
wrote:<br>
<blockquote
type="cite"><font
size="2"
color="#666666"
face="Verdana">[...]</font><br>
<div><span
style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)"><br>
</span></div>
<div><span
style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)">But
you did not ask
the Board to
expand on its
comments or
explain why it
had a problem
with anything in
the CCWG report.<br>
</span>
<div><span
style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)"></span>
<div
style="margin:0px;font-style:normal;font-variant:normal;font-weight:normal;font-size:12px;line-height:normal;font-family:Helvetica;min-height:14px;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span
style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)"><br>
<br>
</span></div>
<div
style="margin:0px;font-style:normal;font-variant:normal;font-weight:normal;font-size:13px;line-height:normal;font-family:Verdana;color:rgb(148,67,251);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span
style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)">Cheers,</span></div>
<div
style="margin:0px;font-style:normal;font-variant:normal;font-weight:normal;font-size:13px;line-height:normal;font-family:Verdana;color:rgb(148,67,251);min-height:16px;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span
style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)"><br>
</span></div>
<div
style="margin:0px;font-style:normal;font-variant:normal;font-weight:normal;font-size:13px;line-height:normal;font-family:Verdana;color:rgb(148,67,251);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span
style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)">Chris</span></div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</span></div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Matthew Shears
Director - Global Internet Policy and Human Rights
Center for Democracy & Technology
<a class="moz-txt-link-abbreviated" href="mailto:mshears@cdt.org">mshears@cdt.org</a>
+ 44 771 247 2987 </pre>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="https://www.avast.com/antivirus">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br />
</body>
</html>