<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
Hi,<br>
<br>
Personally, I am fine with the sitting nomcom doing it. <br>
<br>
The reason I wrote it that way is that several people had stated in
conversation that it could not be done by the same nomcom. I
therefore started with that premise, in fact it was that premsie
which reminded me of the IETF example.<br>
<br>
As for why people argued it could not be the sitting nomcom, I will
let them comment for themselves if they wish. The possible reason
that occurs to me is that it would not only disrupt their carefully
scheduled work, but that it might cause a perspective change that
could also be disruptive. Also there might be a tendancy to review
the recall petition in the light of available replacement
candidates. Having the sitting nomcom do it would require its
members to be people who were good at compartmentalization. <br>
<br>
avri<br>
<br>
<br>
<div class="moz-cite-prefix">On 17-Apr-15 12:38,
<a class="moz-txt-link-abbreviated" href="mailto:olivier.muron@orange.com">olivier.muron@orange.com</a> wrote:<br>
</div>
<blockquote
cite="mid:19639_1429288688_553136F0_19639_8287_1_48B80F60C8D1494BBD9EC2913CCCC87D0ED58AA6@PEXCVZYM11.corporate.adroot.infra.ftgroup"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"Préformaté HTML Car";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:703284534;
mso-list-type:hybrid;
mso-list-template-ids:1814465808 274620304 67895299 67895301 67895297 67895299 67895301 67895297 67895299 67895301;}
@list l0:level1
{mso-level-start-at:3;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l1
{mso-list-id:1034888540;
mso-list-type:hybrid;
mso-list-template-ids:-47827526 274620304 67895299 67895301 67895297 67895299 67895301 67895297 67895299 67895301;}
@list l1:level1
{mso-level-start-at:3;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">Avri,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">Thank you for your suggestion. I agree with the
petition mechanism.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">I think however that building a new adhoc
NomCom is quite complex, and, in fact, I dont fully
understand the rationale for it:</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span
style="font-family:"Calibri","sans-serif""
lang="EN-US"><span style="mso-list:Ignore">-<span
style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span lang="EN-US">for
directors appointed by SO or AC, that same organisation
would decide the director’s removal,<o:p></o:p></span></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span
style="font-family:"Calibri","sans-serif""
lang="EN-US"><span style="mso-list:Ignore">-<span
style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span lang="EN-US">for
directors nominated by the NomCom, one would have to create
that new adhoc NomCom to decide. Why such a difference? The
simplest is to keep the same NomCom (BTW NomCom composition
is partially renewed every year…). <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The comparaison with
IETF is interesting but one must keep in mind that the
selection of their NomCom members is a complex, random
process (detailed in RFC 3797) while our NomCom members are
directly selected by SO/AC/Constituencies in a transparent
process. That makes quite a difference.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In conclusion, I feel
fine with the petition process you are proposing, but I
would leave the recall decision to the NomCom, with the
composition it will have when the situation arises,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Olivier</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US">De :</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:wp1-bounces@icann.org">wp1-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:wp1-bounces@icann.org">mailto:wp1-bounces@icann.org</a>]
<b>De la part de</b> Steve Crocker<br>
<b>Envoyé :</b> jeudi, avril 16, 2015 23:14<br>
<b>À </b></span><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a class="moz-txt-link-abbreviated" href="mailto:avri@acm.org">avri@acm.org</a><br>
<b>Cc :</b> <a class="moz-txt-link-abbreviated" href="mailto:wp1@icann.org">wp1@icann.org</a><br>
<b>Objet :</b> Re: [WP1] 6.5.5. Nomcom Recall Procedure
- suggestion<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">:) Well, although the NomCom is indeed
composed of people appointed by the SOs and ACs, the
composition is quite different from the composition of the
Board, and I think the dynamics are quite different from the
likely effect of having SOs and ACs act as members.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Steve<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Apr 16, 2015, at 5:10 PM, Avri
Doria <<a moz-do-not-send="true"
href="mailto:avri@acm.org">avri@acm.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi,<br>
<br>
I do not think it affects the independence of Board
members. It is a Nomcom activity, composed of the same
mix of members as the appointing Nomcom. It is
patterned on the IETF Nomcom Recall process in RFC 7437,
a model that requires only 20 eligible qualified
petitioners to initiate a Nomcom recall process.<br>
<br>
BTW: I would have no problem with requiring a higher
threshold of SOAC to initiate, but figured that the 3
SOAC requirements was already rather more strict than 20
qualified IETF participants.<br>
<br>
But what is most important to remember is that is is a
properly constituted nomcom that makes the decision and
it needs to meet a high threshold. So if a Nomcom
process composed of AC/SO members can pick independent
Directors, then they should be able to remove them.<br>
<br>
Now if you want to disagree with the antecedent of that
last sentence you might find me in agreement (as I am
still a fan of elected Directors as in ICANN 1.0), but
given that we institutionally trust an ACSO constituted
Nomcom to appoint independent Directors, an ACSO
constituted Nomcom should be able to recall them.<br>
<br>
avri<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On 16-Apr-15 15:00, Steve Crocker
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Doesn’t this move us even further
toward giving the SOs and ACs control of Board members
and thereby reduce, if not eviscerate, the
independence of board members appointed by the NomCom?
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Steve<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Apr 16, 2015, at 2:55 PM,
Avri Doria <<a moz-do-not-send="true"
href="mailto:avri@acm.org">avri@acm.org</a>>
wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi,<br>
<br>
Apologies for being so last minute about this.<br>
<br>
<br>
In order to remove an individual director(s)
appointed by the Nominating Committee, a Nomcom
recall process will be added to the Bylaws
section on Nomcom. The recall process would be
initiated by a petition by 3 AC/SO, including at
least 1 SO and 1 AC. The petition must include a
description of the case for removal. The Recall
process would be chaired by an emeritus chair of
a previous Nominating Committee selected by the
ICANN Board. The Recall Committee will be made
up of appointees from the various AC/SO
according to the same formula used by the
Nominating Committee and will use the same
processes and procedures. The members of the
current nominating committee will not be
qualified for participation. The single focus
of the Recall Committee will be to review the
case for removal presented by the petitioners
and decision on removal of of Board Member(s)
refered to in the AC/SO petition. the Board
Members(s) under consideration for removal will
be givin an opportunity to respond to any issues
in the petition. Decision will be by 3/4 vote of
the Recall Committee. The Recall Committee will
be disbanded after completing its task.<br>
<br>
<br>
avri<br>
<br>
<o:p></o:p></p>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr style="color:#909090" align="center"
noshade="noshade" size="1" width="99%">
</div>
<table class="MsoNormalTable"
style="border-collapse:collapse" border="0"
cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="padding:0in 7.5pt 0in 4.0pt">
<p class="MsoNormal"><a
moz-do-not-send="true"
href="http://www.avast.com/"><span
style="text-decoration:none"><img
moz-do-not-send="true"
id="_x0000_i1070"
src="http://static.avast.com/emails/avast-mail-stamp.png"
alt="Avast logo" border="0"></span></a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p><span
style="font-family:"Calibri","sans-serif";color:#3D4D5A">This
email has been checked for viruses by
Avast antivirus software.
<br>
<a moz-do-not-send="true"
href="http://www.avast.com/">www.avast.com</a>
<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">_______________________________________________<br>
WP1 mailing list<br>
<a moz-do-not-send="true"
href="mailto:WP1@icann.org">WP1@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>WP1 mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:WP1@icann.org">WP1@icann.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<o:p></o:p></p>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr style="color:#909090" align="center"
noshade="noshade" size="1" width="99%">
</div>
<table class="MsoNormalTable"
style="border-collapse:collapse" border="0"
cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="padding:0in 7.5pt 0in 4.0pt">
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://www.avast.com/"><span
style="text-decoration:none"><img
moz-do-not-send="true" id="_x0000_i1072"
src="http://static.avast.com/emails/avast-mail-stamp.png"
alt="Avast logo" border="0"></span></a><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p><span
style="font-family:"Calibri","sans-serif";color:#3D4D5A">This
email has been checked for viruses by Avast
antivirus software.
<br>
<a moz-do-not-send="true"
href="http://www.avast.com/">www.avast.com</a>
<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">_______________________________________________<br>
WP1 mailing list<br>
<a moz-do-not-send="true" href="mailto:WP1@icann.org">WP1@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<pre>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
WP1 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:WP1@icann.org">WP1@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a>
</pre>
</blockquote>
<br>
<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="http://www.avast.com/">
<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="http://www.avast.com/">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br />
</body>
</html>