<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Make sense your proposal Tijani<br><br>Vanda Scartezini<div>Sent from my iPhone</div><div>Sorry for typos </div></div><div><br>On 18 de ago de 2016, at 09:53, Tijani BEN JEMAA <<a href="mailto:tijani.benjemaa@topnet.tn">tijani.benjemaa@topnet.tn</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><font color="#002e7a" class="">Alan,</font><div class=""><font color="#002e7a" class=""><br class=""></font></div><div class=""><font color="#002e7a" class="">There are 3 small corrections that I propose:</font></div><div class=""><font color="#002e7a" class="">2. Defined Terms: Empowered Community (EC): I think that the definition is not that accurate</font></div><div class=""><font color="#002e7a" class="">32.1 There is an « of » missing between « expiration » and « the IANA » </font></div><div class=""><font color="#002e7a" class="">23.2 the SO/AC comprised in the EC are not selected. They chose themselves to participate in the EC or not.</font></div><div class=""><font color="#002e7a" class=""><br class=""></font></div><div class=""><font color="#002e7a" class="">So I propose to make the following modifications:</font></div><div class=""><font color="#002e7a" class=""><br class=""></font></div><div class=""><ul class="MailOutline"><li class=""><font color="#002e7a" class="">2. Definition of the Empowered Community (EC):</font></li></ul><div class=""><font color="#002e7a" class=""><span class="Apple-tab-span" style="white-space:pre"> </span><b class=""><i class="">As part of the accountability mechanisms accompanying the transition of the IANA Functions stewardship from the NTIA to the multi-stakeholder community, the Empowered Community is the sole designator of ICANN and which is composed of the SOs and Acs that accepted to participate in the ICANN new decision making system.</i></b></font></div><div class=""><font color="#002e7a" class=""><br class=""></font></div><div class=""><ul class="MailOutline"><li class=""><font color="#002e7a" class="">23.1 </font></li></ul><div class=""><font color="#002e7a" class=""><span class="Apple-tab-span" style="white-space: pre;"> </span><i class="">The provisions of Section 23 will only come into effect if and when the ICANN
Bylaws adopted by the ICANN Board on 27 May 2016 are deemed to be effective as
per ICANN Board Resolutions 2016.05.27.01-2016.05.27.04. This will occur upon
the expiration <b class="">of </b>the IANA Functions Contract between ICANN and United States
Department of Commerce National Telecommunications and Information Agency
(NTIA).</i></font> </div></div><div class=""><br class=""></div><div class=""><ul class="MailOutline"><li class=""><font color="#002e7a" class="">23.2</font></li></ul><div class=""><font color="#002e7a" class=""><span class="Apple-tab-span" style="white-space:pre"> </span></font><i class=""><font color="#002e7a" class="">The revised ICANN Bylaws bring into existence the Empowered Community (EC)
comprised of <b class="">the </b>ICANN Supporting Organizations and Advisory Committees <b class="">that accepted to participate in the new new decision making system</b>.</font></i></div><div class=""><i class=""><font color="#002e7a" class=""> </font></i></div></div><div class=""><br class=""></div><div apple-content-edited="true" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="orphans: auto; text-align: start; text-indent: 0px; widows: auto; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="orphans: auto; text-align: start; text-indent: 0px; widows: auto; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="orphans: auto; text-align: start; text-indent: 0px; widows: auto; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div apple-content-edited="true" style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="color: rgb(54, 95, 145);" class="">-----------------------------------------------------------------------------</span></div><div apple-content-edited="true" style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><b class=""><span style="color: rgb(54, 95, 145);" class="">Tijani BEN JEMAA</span></b></div><div apple-content-edited="true" style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="color: rgb(54, 95, 145);" class="">Executive Director</span></div><div apple-content-edited="true" style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="color: rgb(54, 95, 145);" class="">Mediterranean Federation of Internet Associations (</span><b style="color: rgb(54, 95, 145);" class="">FMAI</b><span style="color: rgb(54, 95, 145);" class="">)</span></div><div apple-content-edited="true" style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="color: rgb(54, 95, 145);" class="">Phone: +216 98 330 114</span></div><div apple-content-edited="true" style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="color: rgb(54, 95, 145);" class=""> </span> <span style="color: rgb(54, 95, 145);" class="">+216 52 385 114</span></div><div apple-content-edited="true" class=""><span style="color: rgb(54, 95, 145);" class="">-----------------------------------------------------------------------------</span></div><br class=""></div></div></div></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">Le 18 août 2016 à 05:54, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" class="">alan.greenberg@mcgill.ca</a>> a écrit :</div><br class="Apple-interchange-newline"><div class="">
<div class="">
In Helsinki, the ALAC approved a number of changes to its Rules of
Procedure (RoP) related to the selection of the At-Large Director (ICANN
Board Seat 15). Due to lack of time, a number of other changes were not
discussed or approved. These we discussed during the ALAC teleconference
on 26 July. Most of these changes elicited no negative comments but one,
a formalization of current ALAC Leadership Team (ALT) practices, did
result in a number of comments.<br class=""><br class="">
Also discussed in Helsinki and briefly on the July ALA teleconference
were changes that are required to support the ICANN Empowered Community
(EC). The EC will come into being when and if the ICANN Bylaws adopted by
the Board on 27 May go into effect. This will happen when and if the IANA
transition is completed with the expiration of the IANA Functions
Contract between the NTIA and ICANN. The NTIA announced this week that it
intended to let the contract expire at the end of September. Presuming
this process is not halted due to some extraordinary action within the US
Government, the contract will expire on 30 September, the new Bylaws will
be triggered and the EC will exist, and the ALAC must be able to function
within it.<br class=""><br class="">
As discussed, I convened a small group composed of those within our
community most knowledgeable about the EC and its accountability
measures. This group was comprised of the five ALAC Members of the
CCWG-Accountability (me, Tijani, Cheryl, Sébastien and Leon) as well as
Seun and Olivier, both of who devoted much time to participating in the
CCWG and understanding all of the issues. It was agreed that we would use
a minimalist approach to ensure that the ALAC could fulfill its duties.
It may be that at some point in the future we revisit these rules, but
for the moment, and given the tight time lines, a simple approach was the
wisest path to follow.<br class=""><br class="">
The group did discuss whether the Chair or someone else should represent
the ALAC on the EC. It was felt that the default should be the Chair
because: a) there is no real power associated with the position; b) there
is are already detailed measures in the RoP to control the accountability
of the Chair, and to remove the Chair if there is some gross misuse of
the EC power (as implied in the CCWG_ACCT recommendations)<br class=""><br class="">
The RoP revision includes three sets of changes.<br class=""><br class="">
1. The revisions previously presented for the Helsinki meeting, deferred,
and then discussed on 26 July. The section on ALT practices has been
largely re-written to address the issues raised. In particular: a) there
is no longer any reference to past ALAC Chairs, but a more generic
reference to other who might be invited to participate; b) there is no
longer a reference to guests invited at the "sole discretion"
of the Chair - this decision like all other ALT decision will be made
collegially; c) it is clarified for the purposes of full transparency,
that any ALT decisions are made solely by the five regional
representatives and not by the Liaisons or other invited people.
<br class=""><br class="">
2. Two small changes to the Director selection section to address a
possible case of a tied vote that had been accidentally omitted, and to
clarify that the BMSPC is composed of ten regional representatives plus a
Chair (it previously was not clear if the Chair was one of the
ten).<br class=""><br class="">
3. The changes associate with the EC.<br class=""><br class="">
According to the RoP section 13.1.1, a motion to amend the rules must be
made 21 days in advance. Accordingly, I am opening this discussion of the
proposed RoP Revision. Subject to the discussion, a vote of the ALAC will
be taken after the 21 day period elapses (09 September).<br class=""><br class="">
I am proposing that we adopt these changes in a single vote. However, if
any ALAC Member wishes that we segregate out particular changes for a
separate vote, that will be done (presuming each package of revisions can
stand on its own).<br class=""><br class="">
<br class="">
<font color="#0000FF" class=""><b class="">I hereby make the following motion and ask that
another ALAC Member second it.<br class=""><br class="">
Whereas the At-Large Advisory Committee is currently operating under
Rules of Procedure (RoP) approved on 20 June 2016;<br class=""><br class="">
Whereas a number of changes to these (RoP) have been recommended to
correct errors, clarify specific rules, enhance transparency and
implement the ICANN Empowered Community;<br class=""><br class="">
Therefore;<br class=""><br class="">
The ALAC adopts the attached revisions to the ALAC Rules of
Procedure.<br class=""><br class="">
-----------------------------<br class="">
Also attached is a detailed log describing each change and the rationale
for it.<br class=""><br class="">
This motion and the final RoP adopted by the ALAC may be amended as
agreed to by the ALAC prior to final adoption. Final adoption will
require a super-majority (2/3) vote of the ALAC.<br class=""><br class="">
<br class=""><br class="">
</b></font></div>
<span id="cid:5D251042-E9B6-4395-B60A-2969FBCFAF57@home"><ALAC RoP-Revision3-DRAFT_2.0-20160817.pdf></span><span id="cid:E0DCEE31-482B-4278-B97F-009C0DA2AB2D@home"><ALAC RoP-Revision_3-Log.pdf></span>_______________________________________________<br class="">ALAC mailing list<br class=""><a href="mailto:ALAC@atlarge-lists.icann.org" class="">ALAC@atlarge-lists.icann.org</a><br class=""><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br class=""><br class="">At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a><br class="">ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></div></blockquote></div><br class=""></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>ALAC mailing list</span><br><span><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br><span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br><span></span><br><span>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a></span><br><span>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></span></div></blockquote></body></html>