[ALAC-LT] For Review: DRAFt ALAC Liaison appointments for 2016-17
alan.greenberg at mcgill.ca
Wed Sep 21 02:02:47 UTC 2016
Please review this call for nominations. I would
like to send it out on Thursday.
The ALAC Appointment Selection Committee
recommended for a full call for nominations for
ALAC Liaisons for the 2016-2017 term.
Thus, this is a call for nominations for the
following ALAC Liaisons. The current Liaison is shown in brackets.
- GNSO (Olivier Crepin-Leblond)
- ccNSO (Maureen Hilyard)
- SSAC (Julie Hammer)
- GAC (Yrjö Länsipuro)
-.MOBI (Murray McKercher)
The one year terms will start at the close of
ICANN 57 and end at the close of ICANN 60.
The schedule for this call for Liaisons is:
Call issued Thursday, 22 September
Call closes: Saturday, 1 October (10 days)
Acceptances due: Saturday, 8 October
ALAC Selection Committee Teleconference: week of 10 October
ALAC Vote (if multiple candidates from Selection Committee): 17-21 October
Please review the General Liaison requirements
and responsibilities located in the
RoPs Section 7.
Of particular importance, please note the following:
- (As per RoP 7.3) Liaisons to AC/SOs need not be
ALAC Members, but they will normally be current
or past ALAC Members, or otherwise familiar with
the ALAC and At-Large and the TG to whom they will liaise.
- (As per RoP 7.8) When representing the ALAC,
Appointees have an obligation to solicit ALAC and
At-Large views on the matter where practical and
possible. Appointees should be selected knowing
that in many instances such consultation may not
be possible or practical and thus the ALAC needs
to select people who understand the philosophies
or guiding values and principles of the ALAC and At-Large.
- Liaisons should be selected based on their
familiarity with the group to which they are
appointed. Having worked extensively with them
before in some capacity (such as on multiple WGs) is a strong asset.
- A level of trust between a Liaison and the
group to which they are appointed is mandatory
for success and must already exist or it should
be demonstrable how or why it may exist in the future.
- Liaisons to AC/SOs require a MAJOR time
commitment over and above other At-Large responsibilities.
- For the SSAC Liaison position, the ALAC only
makes a recommendation. The Liaison is a full
SSAC Member and must satisfy SSAC criteria and
follow SSAC processes for admission to the AC.
- For the GAC Liaison position, the potential
candidate must be approved by GAC Leadership.
- For .MOBI, the prime issue not as much mutual
respect and trust, but ensuring that the Liaison
understands the business of .MOBI and is well versed in mobile technologies.
Liaison reports may be seen
Liaisons are asked to provide monthly reports
which summarize activities in the organization to which they are the Liaison.
Process for Nomination and Selection:
Nominations should be sent to the
<mailto:alac at atlarge-lists.icann.org>ALAC list
<mailto:Alan%20Greenberg%20%3calan.greenberg at mcgill.ca%3e>Alan
<mailto:staff at atlarge.icann.org>At-Large staff by
Friday, 21 October at 23:59 UTC. For nominations
made by people without access to the ALAC list,
Staff will post to the ALAC list.
All Nominees, in their acceptance or
self-nomination, must provide an Expression of
Interest including sufficient information about
their background and experience to allow the ALAC
Appointment Selection Committee to review the
nominations and decide on whether to forward their candidacy to the ALAC.
The Selection Committee may choose to forward one
or more candidates to the ALAC for each position.
The Selection Committee or its Chair may choose
to ask follow-up questions, but it is not obliged
to, so submissions should be as complete as possible.
Heidi Ullrich, Silvia Vivanco, Ariel Liang,
Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeºim Nazlar
ICANN Policy Staff in support of the At-Large Community
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ALAC-ExCom