<div dir="ltr"><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-10-05 15:38 GMT+02:00 Matthew Shears <span dir="ltr"><<a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
+ 1 also <br><div><div class="h5">
<br>
<div>On 05/10/2015 13:54, James M. Bladel
wrote:<br>
</div>
<blockquote type="cite">
<div>+1. </div>
<div><br>
</div>
<div>Any claims that we must abbreviate
accountability reforms in order to fit the IANA transition
timeline has those two priorities reversed. <br>
<br>
Sent via iPhone. Blame Siri.
<div><br>
</div>
</div>
<div><br>
On Oct 2, 2015, at 19:44, Jordan Carter <<a href="mailto:jordan@internetnz.net.nz" target="_blank"><a href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a>>
wrote:<br>
<br>
</a></div>
<blockquote type="cite">
<div>
<div dir="ltr">Thanks Avri for this nice statement of one of
the key dilemmas facing this group.
<div><br>
</div>
<div>The divergence between:</div>
<div><br>
</div>
<div>- the transition can't happen until accountability is
sustainable, and so that requires the member model as a
foundation</div>
<div><br>
</div>
<div>and</div>
<div><br>
</div>
<div>- the transition can't happen if there is a significant
change such as that to a member model, and so that
requires ruling out the member model</div>
<div><br>
</div>
<div><br>
</div>
<div>is quite stark.</div>
<div><br>
</div>
<div>FWIW my instincts are in line with Avri's. If ICANN's
current level of accountability was acceptable, the
community would not have demanded an accountability
process alongside the transition process, and NTIA would
not have agreed the two had to be intertwined and
interrelated.</div>
<div><br>
</div>
<div><br>
</div>
<div>cheers</div>
<div>Jordan</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 1 October 2015 at 10:38, Avri
Doria <span dir="ltr"><<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
Hi,<br>
<br>
The Board's critique rests on a notion that the
introduction of<br>
anything new in the ICANN system will be a destabilizing
factor and most<br>
be avoided.<br>
<br>
This ignores the fact that by removing the NTIA backstop
we destabilize<br>
the current system. It might have been possible to find
a new balance<br>
(not that the old worked that well given the amount of
discontent that<br>
existed prior to the CCWG process) by tweaking the
system. The early<br>
work of the CCWG, however, showed that this was not
enough. So we<br>
decided to bring back a notion that existed in the early
ICANN design,<br>
the idea of membership. Membership has always been part
of the kit that<br>
was available to ICANN in the multistakeholder model.
An initial<br>
experiment met with some issues and instead of fixing
that then, they<br>
threw the notion away without exploring possible tweaks
to the system.<br>
As a result we are living in ICANN 2.0, a system that
was imposed in a<br>
top down manner and one that was never fully accepted by
those at the<br>
bottom.<br>
<br>
Now, albeit in a very different configuration, the CCWG
is proposing to<br>
establish a community consensus based idea of
membership. I believe that<br>
this should be given a fair analysis before rejecting
it. It is also<br>
important to remember that the NTIA requirements were
not a prohibition<br>
of new mechanisms or structures, but rather evidence
that these<br>
structure did not increase the current risk, or fact, of
capture and<br>
that they could be held to account.<br>
<br>
The Board criticism is important to look at for
arguments that show the<br>
areas in which the CCWG plan either does not explain its
protections<br>
against capture and its accountability checks and
balances or may have<br>
gaps in these areas. If we cannot explain what we
propose, or cannot<br>
close the gaps, then it becomes time to consider
variations on the model<br>
or another model altogether. In my opinion, we are not
there.<br>
<br>
avri<br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast
antivirus software.<br>
<a href="https://www.avast.com/antivirus" target="_blank" rel="noreferrer">https://www.avast.com/antivirus</a><br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div style="font-size:small" dir="ltr">Jordan
Carter<br>
<br>
Chief Executive <br>
<b>InternetNZ</b><br>
</div>
<div style="font-size:small" dir="ltr"><br>
<a href="tel:%2B64-4-495-2118" target="_blank" value="+6444952118">+64-4-495-2118</a> (office) | <a href="tel:%2B64-21-442-649" target="_blank" value="+6421442649">+64-21-442-649</a>
(mob)<br>
Email: <a style="color:rgb(17,85,204)" href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a> <br>
Skype: jordancarter<br>
</div>
<div style="font-size:small">Web: <a href="http://www.internetnz.nz" target="_blank">
<a href="http://www.internetnz.nz" target="_blank">www.internetnz.nz</a> </a></div>
<div style="font-size:small" dir="ltr"><br>
<i>A better world through a better
Internet </i></div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Accountability-Cross-Community mailing list</span><br>
<span><a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br>
</div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Accountability-Cross-Community mailing list
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
</div></div><pre cols="72">--
Matthew Shears
Director - Global Internet Policy and Human Rights
Center for Democracy & Technology
<span><a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>
<a href="tel:%2B%2044%20771%20247%202987" target="_blank" value="+447712472987">+ 44 771 247 2987</a> </span></pre>
<br><br>
<hr style="border:currentColor;width:99%;color:rgb(144,144,144);min-height:1px;background-color:rgb(176,176,176)">
<table style="border:currentColor;border-collapse:collapse">
<tbody><tr>
<td style="padding:0px 15px 0px 8px;border:currentColor">
<a href="https://www.avast.com/antivirus" target="_blank">
<img alt="Avast logo" src="http://static.avast.com/emails/avast-mail-stamp.png" border="0">
</a>
</td>
<td>
<p style="color:rgb(61,77,90);font-family:"Calibri","Verdana","Arial","Helvetica";font-size:12pt"><span>
This email has been checked for viruses by Avast antivirus software.
<br></span><a href="https://www.avast.com/antivirus" target="_blank">www.avast.com</a>
</p>
</td>
</tr>
</tbody></table>
<br>
</div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>