<div dir="ltr">+1 Matthew<div>+1 Roelof even better</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><span style="border-collapse:separate;font-family:'Times New Roman';font-variant:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:arial"><b style="font-weight:normal;font-style:normal;font-size:small;color:rgb(0,0,0)"><font size="4">Carlos Raúl Gutiérrez</font></b><div style="font-weight:normal;font-style:normal;font-size:small">_________<div style="color:rgb(0,0,0)">Apartado 1571-1000</div><div style="color:rgb(0,0,0)"><b>COSTA RICA</b></div><div style="color:rgb(0,0,0)"><br></div></div></span></span></div></div></div>
<br><div class="gmail_quote">On Thu, Jan 15, 2015 at 10:19 AM, Roelof Meijer <span dir="ltr"><<a href="mailto:Roelof.Meijer@sidn.nl" target="_blank">Roelof.Meijer@sidn.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div style="font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0)">
Dear Paul, Kavouss, Tijani, Mathieu, all,</div>
<div style="font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0)">
<br>
</div>
<div><font face="Calibri,sans-serif">I think Paul’s „</font><span style="font-family:Calibri,sans-serif;font-size:15px;color:rgb(31,73,125);background-color:rgb(255,255,255)"><i>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.</i></span><span style="background-color:rgb(255,255,255)"><font color="#1f497d" face="Calibri,sans-serif"><span style="font-size:15px">”</span></font><font face="Calibri,sans-serif"><span style="font-size:15px"> clearly
shows the difference between te charter’s version and the „elaborated” one: the latter narrows down on a specific group of mechanisms (that when in place or committed to would etc..). </span></font></span><span style="background-color:rgb(255,255,255)"><font face="Calibri,sans-serif"><span style="font-size:15px">That
can be good, if we agree. On the other side, it might exclude </span></font><font face="Calibri,sans-serif"><span style="font-size:15px">mechanisms that the charter version includes (mechanisms <b>other</b> than </span></font></span><span style="background-color:rgb(255,255,255);font-family:Calibri,sans-serif;font-size:15px">that
when in place or committed to would etc..). </span></div>
<div><span style="background-color:rgb(255,255,255);font-family:Calibri,sans-serif;font-size:15px">To illustrate my point: a review mechanism that has to be in place before IANA stewardship transition is in scope with the
charter phrasing, but does not "</span><i><font color="#1f497d"><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px;background-color:rgb(255,255,255)">provide the community with </span><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px">assurance</span><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px"> that
any accountability <span style="background-color:rgb(255,255,255)">mechanism that would further enhance ICANN's accountability would be implemented if it had consensus support from the community.</span></span></font></i><font color="#1f497d" face="Calibri,sans-serif"><span style="font-size:15px;line-height:17px"><i>”</i></span></font></div>
<div><i><font color="#1f497d"><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px"><span style="background-color:rgb(255,255,255)"><br>
</span></span></font></i></div>
<div><font face="Calibri,sans-serif"><span style="font-size:15px"><span style="background-color:rgb(255,254,254)">It might look like a compromise, but it is not intended to be, how about:</span></span></font></div>
<div><font face="Calibri,sans-serif"><font color="#1f497d"><span style="font-size:15px"><span style="background-color:rgb(255,255,255)"><br>
</span></span></font></font></div>
<div><font face="Calibri,sans-serif"><font color="#1f497d"><span style="font-size:15px"><span style="background-color:rgb(255,255,255)"> </span></span></font></font><span style="font-family:Calibri,sans-serif;font-size:15px;color:rgb(31,73,125);background-color:rgb(255,255,255)"> </span><i><font color="#1f497d"><b style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px">Work
Stream 1</b><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px">: 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-color:rgb(255,255,0)">including</span> </span><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px;background-color:rgb(255,255,255)">mechanisms that, when in place or committed
to, </span><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px;background-color:rgb(255,255,0)"><strike>would
</strike></span><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px;background-color:rgb(255,255,255)">provide the community with
</span><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px;background-color:rgb(255,255,0)">assurance</span><span style="font-family:Calibri,sans-serif;font-size:15px;line-height:17px"><span style="background-color:rgb(255,255,255)">
that any </span><strike style="background-color:rgb(255,255,0)">accountability </strike><span style="background-color:rgb(255,255,255)">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)</span></span></font></i></div>
<div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<font color="#000000"><font face="Calibri"><br>
</font></font></div>
<div>I<font color="#000000"><font face="Calibri,sans-serif" style="font-family:Calibri"> agree, it</font>’<font face="Calibri" style="font-family:Calibri,sans-serif">s one terribly long sentence. </font><font face="Calibri,sans-serif">I</font><font face="Calibri,sans-serif" style="font-family:Calibri"> submit
that we can leave out the bit </font>I<font face="Calibri" style="font-family:Calibri,sans-serif"> put in brackets, because the phrasing already correctly covers the </font><font face="Calibri,sans-serif">„</font><font face="Calibri"><font face="Calibri,sans-serif">even
if</font>”<font face="Calibri,sans-serif"> situations </font></font></font><font face="Calibri,sans-serif">implicitly.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<font color="#000000"><font face="Calibri">Cheers,</font></font></div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<font color="#000000"><font face="Calibri"><br>
</font></font></div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<font color="#000000"><font face="Calibri">Roelof</font></font></div>
</div>
</div>
<div style="font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0)">
<br>
</div>
<span style="font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0)">
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Paul Rosenzweig <<a href="mailto:paul.rosenzweig@redbranchconsulting.com" target="_blank">paul.rosenzweig@redbranchconsulting.com</a>><br>
<span style="font-weight:bold">Date: </span>donderdag 15 januari 2015 15:22<br>
<span style="font-weight:bold">To: </span>'Tijani BEN JEMAA' <<a href="mailto:tijani.benjemaa@fmai.org.tn" target="_blank">tijani.benjemaa@fmai.org.tn</a>>, "<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>" <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><span class=""><br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-Accountability] Work Streams definition<br>
</span></div><div><div class="h5">
<div><br>
</div>
<div>
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="color:#1f497d">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.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Paul<u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><b><span style="color:#c00000">**NOTE: OUR NEW ADDRESS -- EFFECTIVE 12/15/14 ***<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="color:#1f497d">509 C St. NE<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Washington, DC 20002<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Paul Rosenzweig<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="mailto:paul.rosenzweigesq@redbranchconsulting.com" target="_blank"><span style="color:#0563c1">paul.rosenzweig@redbranchconsulting.com</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">O: <a href="tel:%2B1%20%28202%29%20547-0660" value="+12025470660" target="_blank">+1 (202) 547-0660</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">M: <a href="tel:%2B1%20%28202%29%20329-9650" value="+12023299650" target="_blank">+1 (202) 329-9650</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Skype: <a href="tel:%2B1%20%28202%29%20738-1739" value="+12027381739" target="_blank">+1 (202) 738-1739</a> or paul.rosenzweig1066<u></u><u></u></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="color:#1f497d"><a href="http://www.redbranchconsulting.com/index.php?option=com_content&view=article&id=19&Itemid=9" target="_blank"><span style="color:#0563c1">Link to my PGP Key</span></a><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Tijani BEN JEMAA [<a href="mailto:tijani.benjemaa@fmai.org.tn" target="_blank">mailto:tijani.benjemaa@fmai.org.tn</a>]
<br>
<b>Sent:</b> Thursday, January 15, 2015 4:53 AM<br>
<b>To:</b> <a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a><br>
<b>Subject:</b> [CCWG-Accountability] Work Streams definition<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="line-height:115%"><span lang="FR" style="color:#1f497d">Dear all,<u></u><u></u></span></p>
<p class="MsoNormal" style="line-height:115%"><span lang="FR" style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="line-height:115%"><span style="color:#1f497d">I read again the new proposed definition of the Work Streams, and I found it too different from the one in our charter:<u></u><u></u></span></p>
<p class="MsoNormal" style="line-height:115%"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="line-height:115%"><span style="color:#1f497d">In the charter:<u></u><u></u></span></p>
<p style="margin-bottom:0in;margin-bottom:.0001pt">
<span style="color:rgb(1,1,1)"><span>·<span style="font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</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="font-family:Cambria,serif;color:rgb(1,1,1);background-color:white;background-repeat:initial initial"><u></u><u></u></span></p>
<p style="margin-bottom:0in;margin-bottom:.0001pt">
<span style="color:rgb(1,1,1)"><span>·<span style="font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</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:#1f497d"></span><span style="font-family:Cambria,serif;color:rgb(1,1,1);background-color:white;background-repeat:initial initial"><u></u><u></u></span></p>
<p class="MsoNormal" style="line-height:115%"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="line-height:115%"><span style="color:#1f497d">The new proposal:<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:35.45pt;margin-bottom:.0001pt;background:white">
<span><span>·<span style="font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</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. <u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:35.45pt;margin-bottom:.0001pt;background:white">
<span><span>·<span style="font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</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.<u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">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
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">I would prefer stay with the charter definition for all those reasons<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#17365d">--------------------------------------------------------------------------------<u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="color:#17365d">Tijani BEN JEMAA<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="color:#17365d">Executive Director<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#17365d">Mediterranean Federation of Internet Associations
</span><span style="font-size:12.0pt;color:#17365d">(<b>FMAI</b>)</span><span style="font-size:13.0pt;color:#17365d"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#17365d">Phone: <a href="tel:%2B%20216%2041%20649%20605" value="+21641649605" target="_blank">+ 216 41 649 605</a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#17365d">Mobile: <a href="tel:%2B%20216%2098%20330%20114" value="+21698330114" target="_blank">+ 216 98 330 114</a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#17365d">Fax: <a href="tel:%2B%20216%2070%20853%C2%A0376" value="+21670853376" target="_blank">+ 216 70 853 376</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#17365d">--------------------------------------------------------------------------------<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="FR" style="color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="FR" style="font-size:12pt;font-family:'Times New Roman',serif;color:windowtext"><u></u> <u></u></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="FR" style="font-size:12pt;font-family:'Times New Roman',serif;color:windowtext">
<hr size="1" width="99%" noshade style="color:#909090" align="center">
</span></div>
<table border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td style="padding:0in 11.25pt 0in 6.0pt">
<p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif;color:windowtext"><a href="http://www.avast.com/" target="_blank"><span style="text-decoration:none"><img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png"></span></a><u></u><u></u></span></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p><span style="font-family:Calibri,sans-serif;color:rgb(61,77,90)">Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection
<a href="http://www.avast.com/" target="_blank">Antivirus avast!</a> est active. <u></u><u></u></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span lang="FR" style="font-size:12pt;font-family:'Times New Roman',serif;color:windowtext"><u></u> <u></u></span></p>
</div>
</div>
</div>
</div></div></span>
</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">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>