<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Not to belabor this much more, and I may be being pedantic...<br>
<br>
It appears to read as if WS1 is about putting in place mechanisms
that <span lang="EN-US">"provide the community with confidence"</span>
but not specifically about putting in place accountability
mechanisms or measures. There is a big difference between putting
in in place process mechanisms to provide confidence (as it now
seems to imply) and putting in place actual accountability
mechanisms which is what the original definition suggested. The
second definition is fine for so long as it explicitly includes the
first as well. <br>
<br>
It might be better if it read something like:<br>
<br>
<b><span lang="EN-US">Work Stream 1</span></b><span lang="EN-US">:
is focused on mechanisms that 1) enhance ICANN's accountability
and must be in place or committed to within the time frame of the
IANA Stewardship Transition</span>, and 2) <span lang="EN-US">that
provide the community with confidence that any accountability
measures that would further enhance ICANN's accountability would
be implemented if it had consensus support from the community,
even if it were to encounter ICANN management resistance or if it
were against the interest of ICANN as a corporate entity.</span><br>
<br>
Matthew<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/15/2015 10:40 AM, Jordan Carter
wrote:<br>
</div>
<blockquote
cite="mid:CAK2bTy8yK3KvMG=kgk-mhvmVuzBLt9Rwk9YSeUfK6ptghA=Cog@mail.gmail.com"
type="cite">
<div dir="ltr">I agree with Paul, Mathieu etc - the Charter
language is the skeleton. The language proposed sets out to
characterise why we would select items - i.e. why they have to
be done before the transition.
<div><br>
</div>
<div>We have to set out transparently the criteria we are using
to decide what has to be in place. This language helps do
that. </div>
<div><br>
</div>
<div>best</div>
<div>Jordan</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 16 January 2015 at 04:17, Kavouss
Arasteh <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div><font color="#1f497d"> Dear All,</font></div>
<div><font color="#1f497d">I do not understand who agreed
with whom</font></div>
<div><font color="#1f497d">What has been changed from the
Charter.</font></div>
<div><font color="#1f497d">I personally fully agree with
the following</font></div>
<div><font color="#1f497d">Quote</font></div>
<div><font color="#1f497d">"<strong><em><u> in the absence
“</u></em></strong></font><strong><em><u>mechanisms
[that] would provide the community with confidence
that any accountability mechanism that would
further enhance ICANN's accountability ( in
relation with work stream 1 of CCWG ,for three
distinct areas , Naming, Numbers and Protocols,
including parameter ) could be implemented if it
had consensus support from the community” the IANA
Functions transition should not occur." </u></em></strong></div>
<div><strong><em><u>Unquote</u></em></strong></div>
<span class="HOEnZb"><font color="#888888">
<div><u><br>
</u></div>
<div><u>Kavouss </u></div>
</font></span></div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="h5">2015-01-15 16:06 GMT+01:00 Edward
Morris <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:emorris@milk.toast.net"
target="_blank">emorris@milk.toast.net</a>></span>:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
<div>
<div
style="color:rgb(0,0,0);font-family:Tahoma;font-size:13px;font-style:normal;font-weight:400;background-image:none;background-repeat:repeat
repeat;background-color:rgba(0,0,0,0)">+1</div>
<div
style="color:rgb(0,0,0);font-family:Tahoma;font-size:13px;font-style:normal;font-weight:400;background-image:none;background-repeat:repeat
repeat;background-color:rgba(0,0,0,0)"> </div>
<div
style="color:rgb(0,0,0);font-family:Tahoma;font-size:13px;font-style:normal;font-weight:400;background-image:none;background-repeat:repeat
repeat;background-color:rgba(0,0,0,0)">
<div>Paul has eloquently expressed my views in
a manner far superior to anything I could
write. Thanks. </div>
<div> </div>
<div>One could argue that our current system
of accountability and transparency
(reconsideration, Appeal, CEP, IR, DIDP),
with some tweaks, should actually be
sufficient going forward. It looks great: on
paper. The problem is that a system designed
for redress (per Bruce) actually functions
as a system of review (per Robin), and a
rather cursory review system at that. We
simply must have mechanisms designed to
ensure that we have real systems of
accountability, ones that does not rely on
the good faith and open-mindedness of any
particular Board or staff member or group,
in place before the transition can be
allowed to occur. </div>
<div>
<div>
<blockquote
style="padding-right:0px;padding-left:5px;margin-right:0px;margin-left:5px;border-left-color:rgb(0,0,0);border-left-width:2px;border-left-style:solid">-----Original
Message-----<br>
From: "Paul Rosenzweig" <<a
moz-do-not-send="true"
href="mailto:paul.rosenzweig@redbranchconsulting.com"
target="_blank">paul.rosenzweig@redbranchconsulting.com</a>><br>
To: "'Tijani BEN JEMAA'" <<a
moz-do-not-send="true"
href="mailto:tijani.benjemaa@fmai.org.tn"
target="_blank">tijani.benjemaa@fmai.org.tn</a>>,
<<a moz-do-not-send="true"
href="mailto:accountability-cross-community@icann.org"
target="_blank">accountability-cross-community@icann.org</a>><br>
Date: Thu, 15 Jan 2015 09:22:26 -0500<br>
Subject: Re: [CCWG-Accountability] Work
Streams definition<br>
<div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">Respetful
disagreement. I think the way it
describes types of mechanisms in
the “new” definition is exactly
what needs to be in place before
the Stewardship transition takes
place. Put another way, I think
that the exposition in WS1
precisely describes the
commitments that MUST be made
before a transition is allowed to
occur. More importantly, I think
there is growing consensus across
the community that this is so. To
state it affirmatively – in the
absence “</span>mechanisms [that]
would provide the community with
confidence that any accountability
mechanism that would further
enhance ICANN's accountability would
be implemented if it had consensus
support from the community” the IANA
Functions transition should not
occur.</div>
<div class="MsoNormal"> </div>
<div class="MsoNormal">Paul</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span>
</div>
<div>
<div class="MsoNormal"><b><span
style="color:rgb(192,0,0)">**NOTE:
OUR NEW ADDRESS -- EFFECTIVE
12/15/14 ***</span></b></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">509
C St. NE
</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">Washington,
DC 20002
</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span>
</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">Paul
Rosenzweig
</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"><a
moz-do-not-send="true"
href="mailto:paul.rosenzweigesq@redbranchconsulting.com"
target="_blank"><span
style="color:rgb(5,99,193)">paul.rosenzweig@redbranchconsulting.com</span></a>
</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">O:
<a moz-do-not-send="true"
href="tel:%2B1%20%28202%29%20547-0660"
value="+12025470660"
target="_blank">+1 (202)
547-0660</a>
</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">M:
<a moz-do-not-send="true"
href="tel:%2B1%20%28202%29%20329-9650"
value="+12023299650"
target="_blank">+1 (202)
329-9650</a>
</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">Skype:
<a moz-do-not-send="true"
href="tel:%2B1%20%28202%29%20738-1739"
value="+12027381739"
target="_blank">+1 (202)
738-1739</a> or
paul.rosenzweig1066</span></div>
<div class="MsoNormal"
style="text-align:justify"><span
style="color:rgb(31,73,125)"><a
moz-do-not-send="true"
href="http://www.redbranchconsulting.com/index.php?option=com_content&view=article&id=19&Itemid=9"
target="_blank">
<span
style="color:rgb(5,99,193)">Link
to my PGP Key</span></a></span>
</div>
</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span>
</div>
<div>
<div style="border-width:1pt medium
medium;border-style:solid none
none;border-color:rgb(225,225,225)
currentColor
currentColor;padding:3pt 0in 0in">
<div class="MsoNormal"><b><span
style="color:windowtext">From:</span></b>
<span style="color:windowtext">
Tijani BEN JEMAA [mailto:<a
moz-do-not-send="true"
href="mailto:tijani.benjemaa@fmai.org.tn"
target="_blank">tijani.benjemaa@fmai.org.tn</a>]<br>
<b>Sent:</b> Thursday, January
15, 2015 4:53 AM<br>
<b>To:</b> <a
moz-do-not-send="true"
href="mailto:accountability-cross-community@icann.org"
target="_blank">accountability-cross-community@icann.org</a><br>
<b>Subject:</b>
[CCWG-Accountability] Work
Streams definition
</span></div>
</div>
</div>
<div class="MsoNormal"> </div>
<div class="MsoNormal"
style="line-height:115%"><span
style="color:rgb(31,73,125)"
lang="FR">Dear all,</span></div>
<div class="MsoNormal"
style="line-height:115%"><span
style="color:rgb(31,73,125)"
lang="FR"> </span></div>
<div class="MsoNormal"
style="line-height:115%"><span
style="color:rgb(31,73,125)">
I read again the new proposed
definition of the Work Streams,
and I found it too different from
the one in our charter:</span></div>
<div class="MsoNormal"
style="line-height:115%"><span
style="color:rgb(31,73,125)">
</span></div>
<div class="MsoNormal"
style="line-height:115%"><span
style="color:rgb(31,73,125)">
In the charter:</span></div>
<div style="margin-bottom:0pt"><span
style="color:rgb(1,1,1);font-family:Symbol"><span>
·<span style="font:7pt/normal
"Times New
Roman";font-size-adjust:none;font-stretch:normal">
</span></span></span>
<b>Work Stream 1</b>: focused on
mechanisms enhancing ICANN
accountability that must be in place
or committed to within the time
frame of the IANA Stewardship
Transition;<span
style="background:white;color:rgb(1,1,1);font-family:"Cambria",serif"></span></div>
<div style="margin-bottom:0pt"><span
style="color:rgb(1,1,1);font-family:Symbol"><span>
·<span style="font:7pt/normal
"Times New
Roman";font-size-adjust:none;font-stretch:normal">
</span></span></span>
<b>Work Stream 2</b>: focused on
addressing accountability topics for
which a timeline for developing
solutions and full implementation
may extend beyond the IANA
Stewardship Transition<span
style="color:rgb(31,73,125)"> </span><span
style="background:white;color:rgb(1,1,1);font-family:"Cambria",serif">
</span></div>
<div class="MsoNormal"
style="line-height:115%"><span
style="color:rgb(31,73,125)">
</span></div>
<div class="MsoNormal"
style="line-height:115%"><span
style="color:rgb(31,73,125)">
The new proposal:</span></div>
<div
style="background:white;margin-right:0in;margin-bottom:0pt;margin-left:35.45pt"><span
style="font-family:Symbol"><span>·<span
style="font:7pt/normal
"Times New
Roman";font-size-adjust:none;font-stretch:normal">
</span></span></span>
<b>Work Stream 1</b> mechanisms are
those that, when in place or
committed to, would provide the
community with confidence that any
accountability mechanism that would
further enhance ICANN's
accountability would be implemented
if it had consensus support from the
community, even if it were to
encounter ICANN management
resistance or if it were against the
interest of ICANN as a corporate
entity.
</div>
<div
style="background:white;margin-right:0in;margin-bottom:0pt;margin-left:35.45pt"><span
style="font-family:Symbol"><span>·<span
style="font:7pt/normal
"Times New
Roman";font-size-adjust:none;font-stretch:normal">
</span></span></span>
All other consensus items could be
in <b>Work Stream 2</b>, provided
there are mechanisms in WS1 adequate
to force implementation of WS2 items
despite resistance from ICANN
management and board.</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span>
</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">I
don’t believe that we are allowed
to change any part of the charter
without going back to the
chartering organizations and ask
for their approval.</span>
</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span>
</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">On
the other hand, the separation of
WS 1 and WS 2 was for the purpose
of having the accountability
mechanisms necessary before the
transition done in time, and the
new definition doesn’t satisfy
this requirement </span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span>
</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)">I
would prefer stay with the charter
definition for all those reasons</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"
lang="FR">
</span></div>
<div class="MsoNormal"><span
style="color:rgb(23,54,93)">
--------------------------------------------------------------------------------
</span></div>
<div class="MsoNormal"><b><span
style="color:rgb(23,54,93)">Tijani
BEN JEMAA
</span></b></div>
<div class="MsoNormal"><span
style="color:rgb(23,54,93)">Executive
Director
</span></div>
<div class="MsoNormal"><span
style="color:rgb(23,54,93)">Mediterranean
Federation of Internet
Associations </span><span
style="color:rgb(23,54,93);font-size:12pt">
(<b>FMAI</b>)</span><span
style="color:rgb(23,54,93);font-size:13pt">
</span></div>
<div class="MsoNormal"><span
style="color:rgb(23,54,93)"
lang="FR">Phone: + 216 41 649 605</span></div>
<div class="MsoNormal"><span
style="color:rgb(23,54,93)"
lang="FR">Mobile: + 216 98 330 114</span></div>
<div class="MsoNormal"><span
style="color:rgb(23,54,93)"
lang="FR">
Fax: <a
moz-do-not-send="true"
href="tel:%2B%20216%2070%20853%C2%A0376"
value="+21670853376"
target="_blank">+ 216 70 853 376</a>
</span></div>
<div class="MsoNormal"><span
style="color:rgb(23,54,93)">
--------------------------------------------------------------------------------
</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span><span
style="color:rgb(31,73,125)"
lang="FR"></span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"
lang="FR">
</span></div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span>
</div>
<div class="MsoNormal"><span
style="color:rgb(31,73,125)"> </span>
</div>
<div class="MsoNormal"
style="margin-bottom:12pt"><span
lang="FR"> </span></div>
<div class="MsoNormal"
style="text-align:center"
align="center">
<hr style="color:rgb(144,144,144)"
align="center" noshade="noshade"
size="1" width="99%"></div>
<table
style="border-collapse:collapse"
border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<td style="padding:0in 11.25pt
0in 6pt">
<div class="MsoNormal"><span><a
moz-do-not-send="true"
href="http://www.avast.com/"
target="_blank"><span
style="text-decoration:none"><img
moz-do-not-send="true"
src="http://static.avast.com/emails/avast-mail-stamp.png"
border="0"></span></a>
</span></div>
</td>
<td style="padding:0.75pt">
<div><span
style="color:rgb(61,77,90);font-family:"Calibri",sans-serif">Ce
courrier électronique ne
contient aucun virus ou
logiciel malveillant parce
que la protection <a
moz-do-not-send="true"
href="http://www.avast.com/"
target="_blank">Antivirus
avast!</a> est active. </span></div>
</td>
</tr>
</tbody>
</table>
<div class="MsoNormal"><span lang="FR"> </span></div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
<span class="">_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org"
target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br>
</span></blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
Ccwg-accountability2 mailing list<br>
<a moz-do-not-send="true"
href="mailto:Ccwg-accountability2@icann.org">Ccwg-accountability2@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/ccwg-accountability2"
target="_blank">https://mm.icann.org/mailman/listinfo/ccwg-accountability2</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">Jordan Carter<br>
<br>
Chief Executive <br>
<b>InternetNZ</b><br>
<br>
04 495 2118 (office) | +64 21 442 649 (mob)<br>
<a moz-do-not-send="true"
href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a>
<br>
Skype: jordancarter<br>
<br>
<i>To promote the Internet's benefits and uses, and protect
its potential.</i><br>
<br>
</div>
</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 (CDT)
<a class="moz-txt-link-abbreviated" href="mailto:mshears@cdt.org">mshears@cdt.org</a>
+ 44 771 247 2987</pre>
</body>
</html>