Dear all, This is a final reminder, that we are seeking 2 councillors as members of the Rejection Action Petition Review Committee. To date, nobody has stepped forward. The Guideline: ccNSO Procedure for the Exercise of the Empowered Community’s rights to Reject Specified Actions, as adopted on 24 May 2018, can be consulted here: https://ccnso.icann.org/sites/default/files/field-attached/guideline-rejecti... [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_d...> Paragraph 3.3: The Rejection Action Petition Review Committee consists of the Rejection Action Petition Manager, the deputy Rejection Action Petition Manager and two (2) additional ccNSO Council members appointed by the ccNSO Council for a term of one (1) year as part of and in accordance of the annual assignment of roles and responsibilities of Councillors. The Rejection Action Petition Review Committee will evaluate any Rejection Action Petition received by the Rejection Action Petition Manager to ensure that it meets the requirements for a Rejection Action Petition as set forth in Annex D of the Bylaws and advise the ccNSO Council accordingly. The Rejection Action Petition Manager will be the Chair of the Rejection Action Petition Review Committee and will be responsible for organising the work of the Rejection Action Petition Review Committee and for all communication between the Rejection Action Petition Review Committee and the ccTLD community. If you are interested in this position, kindly send an email to joke.braeken@icann.org<mailto:joke.braeken@icann.org>, latest on Tue, 5 June 2018 COB. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=DwM...> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso_...> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGaQ...> From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Joke Braeken <joke.braeken@icann.org> Date: Tuesday, 29 May 2018 at 12:58 To: "ccnso-council@icann.org" <ccnso-council@icann.org> Subject: [ccnso-council] call for volunteers: Rejection Action Petition Review Committee Dear all, Following a discussion during the 24 May ccNSO Council call, I am hereby sending you a call for volunteers. We seek 2 councillors as members of the Rejection Action Petition Review Committee. If you are interested in this position, kindly send an email to joke.braeken@icann.org<mailto:joke.braeken@icann.org>, latest on Tue, 5 June 2018 COB. Background During its 24 May meeting, the ccNSO council adopted the Guideline on Rejection Action Procedures. (https://community.icann.org/download/attachments/84219624/Item%204.1%2024%20... [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_dow...> ) The Rejection Action Petition Review Committee will evaluate any Rejection Action Petition received by the Rejection Action Petition Manager to ensure that it meets the requirements for a Rejection Action Petition as set forth in Annex D of the Bylaws[1] and advise the ccNSO Council accordingly. The Rejection Action Petition Manager and its alternate are ex-officio members of the Rejection Action Petition Review Committee. Thank you. Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=DwM...> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso_...> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGaQ...> ________________________________ ________________________________ ________________________________ [1] ICANN Bylaws, Annex D Section 2.2(c)(i)(A-B)