<html>
<body>
Answers embedded below.<br><br>
At 16/08/2017 02:51 AM, Seun Ojedeji wrote:<br><br>
<blockquote type=cite class=cite cite="">Hello Alan,<br><br>
Am not sure I understand why we will be selecting more than 1 person for
Maureen to mentor since only one person will serve as replacement of her.
Selecting more than 1 will also make travel difficult to
allocate.</blockquote><br>
We may not select more than 1, but that will depend on the people who put
their names forward. We don't want to waste people's time or other
resources, but it may not be obvious at the start who the best candidate
is. If there is more than one, travel could be an issue (depending on
whether the person is already funded or not) and that will surely be a
consideration, but only one of them.<br><br>
<blockquote type=cite class=cite cite="">Secondly I think it's important
to be clear from start the maximum number of months that this mentorship
will take so whoever is selected will be able to assume his/her
role.</blockquote><br>
My personal opinion is it will be several months, covering at least one
and perhaps two ICANN meetings. That will depend on whether the initial
selection is made prior to ICANN60, whether the candidates will be in Abu
Dhabi, and just how quickly it goes. I am sure that Maureen will do this
as quickly as practical, and she may have some comments to add. In my
mind, the ABSOLUTE limit is the 2018 AGM, but I surely hope the
transition is complete prior to then. <br><br>
<br>
<blockquote type=cite class=cite cite="">Lastly I hope the selection of
the replacement will be done by/before Abu dhabi so those that were
selected will then have the opportunity to start attending next ICANN
meeting.</blockquote><br>
I am optimistic that we will have completed out initial selection for the
SSAC prior to Abu Dhabi. I cannot address whether the SSAC Membership
Committee and the SSAC will have completed their part by then.<br><br>
For the ccNSO, it is pretty clear it will not be done by then.<br><br>
If we really though that these selections could be made before the
meeting, there would be no need to reappoint Maureen and Julie on an
interim basis.<br><br>
Alan<br><br>
<br>
<blockquote type=cite class=cite cite="">Regards<br>
Sent from my mobile<br>
Kindly excuse brevity and typos<br><br>
On Aug 16, 2017 3:51 AM, "Alan Greenberg"
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
> wrote:<br>
<dl>
<dd>Following consultation with ALAC Members and with our current
Liaisons, this is Consensus Call on how to address our Liaisons to the
GNSO, ccNSO, SSAC and GAC for the year beginning at the end of ICANN60 to
be held in Abu Dhabi.<br><br>
<dd>Our current Liaisons are:<br><br>
<dd>GNSO: Cheryl Langdon-Orr<br>
<dd>GAC: Yrjö Länsipuro<br>
<dd>ccNSO: Maureen Hilyard<br>
<dd>SSAC: Julie Hammer<br><br>
<dd>All four are serving the ALAC well. Cheryl and Yrjö, both having
served just one term (plus several months for Yrjö) and have agreed,
with the support of the ALAC, to continue in their roles. Maureen and
Julie have both indicated that they wish to step down from their Liaison
roles. In the case of the ccNSO, we expect the identification and
training of a replacement to take a significant number of months, during
which time Maureen will stay on as Liaison. In the case of the SSAC, as
Julie will become the new Vice-Chair of the SSAC in January, she would
like to step down as soon as practical, but has agreed to serve for the
first months of the ICANN year if a replacement has not been named by
then.<br><br>
<dd>In all four cases and in accordance with ALAC RoP 18.2 (See
<a href="http://tinyurl.com/ALAC-RoP-2016-09">
http://tinyurl.com/ALAC-RoP-2016-09</a> and reproduced at the end of this
message), I am proposing that the ALAC re-appoint the current
Liaisons.<br><br>
<dd>In parallel with this we will also begin the process of identifying a
replacement for both Maureen and Julie.<br><br>
<dd>ccNSO:<br><br>
<dd>A set of qualifications will be assembled and a call will be issued
for volunteers interested in serving as the ALAC Liaison to the ccNSO.
Depending on the number of candidates, either Maureen will work with the
candidates (with the permission of the ccNSO) and ultimately makes a
recommendation or set of recommendations on the future ccNSO Liaison. If
there are too many candidates, the ALAC Appointee Selection Committee
(AASC) working with Maureen will select a sub-set for Maureen to mentor.
This process will continue into the coming year, but the success we had
with a similar process last time there was a change in ccNSO Liaison
indicates that it is worth the time and effort.<br><br>
<dd>SSAC:<br><br>
<dd>A set of qualifications will be assembled and a call will be issued
for volunteers. The list of candidates will go to the AASC who, with
Julie's assistance, will select no more than two potential candidates.
Those selected will be forwarded to the SSAC (ratified by the ALAC). If
the SSAC decides to admit one person to the SSAC, that person is our SSAC
Liaison. If the SSAC selects more than one, this subset of people returns
the AASC for final selection. Due to the number of steps and the
requirement for the SSAC Membership Committee and the SSAC to meet, this
may or may not happen prior to the end of ICANN60. <br><br>
<dd>With this message, I am initiating a Consensus Call of the ALAC
</u></b>to ratify the above recommendations. <br><br>
<dd>This Consensus Call will end at 23:59 UTC on Monday, 21 August
2017.<br><br>
<dd>If there are any questions of comments, please direct them to either
this list or to me directly. <br><br>
<dd>Although messages indicating support are welcome, they are not
necessary. This Consensus Call will be deemed to have succeeded in the
absence of significant opposition (greater than 20% as specified by ALAC
RoP 12.3.3.1).<br><br>
<dd>Alan<br><br>
<dd>=======================<br><br>
<dd>ALAC Rules of Procedure<br><br>
</b>
<dd>18.1 Appointments of At-Large Appointees to various bodies both
inside and outside of ICANN will be made by the ALAC. Such appointments
will normally be initiated by a call for volunteers, posted by the
Chair/Staff to the Approved Distribution Lists, and on other lists if
appropriate, allowing at least seven days for people to volunteer. The
decision regarding appointments is typically made via Consensus. However,
the Chair will initiate a secret ballot to determine which candidate is
to be appointed if Consensus cannot be reached or if this is requested by
any ALAC Member.<br><br>
<dd>18.2 By the decision of the ALAC, a current Appointee who is willing
to continue in that role may be reconfirmed instead of initiating a new
selection process.<br><br>
<dd>18.3 In the case of selections requiring complex criteria evaluation,
the ALAC may choose to form a sub-committee to carry out the analysis and
to make recommendations to the ALAC based on that analysis.<br><br>
<dd>18.4 For situations where the ALAC is not empowered to make
appointments but rather to endorse one or more candidates, essentially
the same process as described here for appointments should be used, but
with the outcome being an endorsement.<br><br>
<dd>_______________________________________________<br>
<dd>ALAC mailing list<br>
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
<br>
<dd>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>
<br><br>
</dl><br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;DM5PR03MB2714;27:j8abEXqxo1uo9d8H86iikCyhqV8rEmtkun8UrVHYHy+vFvIHi3T/SuqUfrGOJGto99HrI0OClLrp2q0QDgQFPrIKtqz8jfZGs5Z8psSPJ7HfuWq6KaMagRm7v6EvxpDs<br>
X-Microsoft-Antispam-Mailbox-Delivery:<br>
<x-tab> </x-tab>
ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(750103)(520002050)(400001001223)(400125100095)(61617095)(400001002128)(400125200095);<br>
<br>
_______________________________________________<br>
ALAC mailing list<br>
ALAC@atlarge-lists.icann.org<br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" eudora="autourl">
http://www.atlarge.icann.org</a><br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" eudora="autourl">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote></body>
</html>