[council] Call for Volunteers - GNSO Selection Committee

Tue May 24 14:34:35 UTC 2016

Hi Donna,

I have another question regarding the “GNSO Council Selection Process” (section 1.2 of the document attached to your original email). I appreciate the time constraint creating the need for a hasty set-up for this committee, so I am not suggesting we extend the deadline. I am not however sure why its membership needs to be limited to Councillors. Why can’t Councillors make nominations from our SGs/Cs.

It seems to me (at least from an NCSG perspective) that there are members of our stakeholder group who may serve the GNSO well in making a recommendation to the Council on a non gTLD-registry GNSO appointee to the CSC.

Thanks.

Amr

> On May 24, 2016, at 6:20 AM, Austin, Donna <Donna.Austin at neustar.biz> wrote:
> 
> Yes! I did mean 27 May 2016.
> 
> Thanks Heather
> 
> Sent from my iPhone
> 
> On May 23, 2016, at 7:45 PM, Heather Forrest <Heather.Forrest at acu.edu.au <mailto:Heather.Forrest at acu.edu.au>> wrote:
> 
>> Dear Donna,
>> 
>> 
>> 
>> Just checking - by the deadline, did you mean Friday, 27 May? I suspect so, and it's a tight deadline to work to but we will do our best from the NCPH side.
>> 
>> 
>> 
>> Best wishes,
>> 
>> 
>> 
>> Heather
>> 
>> From: owner-council at gnso.icann.org <mailto:owner-council at gnso.icann.org> <owner-council at gnso.icann.org <mailto:owner-council at gnso.icann.org>> on behalf of Austin, Donna <Donna.Austin at neustar.biz <mailto:Donna.Austin at neustar.biz>>
>> Sent: Tuesday, May 24, 2016 11:51:08 AM
>> To: council at gnso.icann.org <mailto:council at gnso.icann.org>
>> Subject: [council] Call for Volunteers - GNSO Selection Committee
>>  
>> Dear Councilors
>>  
>> During the last Council meeting I provided a brief overview of some of the GNSO Council obligations associated with the implementation of the CWG’s Transition Proposal and in particular, those related to establishing a Customer Standing Committee (CSC). The CSC is intended to monitor the performance of IANA post-transition and NTIA has requested that the CSC be established by 15 August 2016, in order to be ready to undertake its role upon transition.
>>  
>> The CSC will comprise the following:
>> Members
>> 2 x gTLD registry operators to be selected by the RySG (mandatory)
>> 2 x ccTLD registry operators to be selected by the ccNSO (mandatory)
>> 1 x registry operator not considered to be a ccTLD or gTLD (optional)
>>  
>> Liaisons (all are non-mandatory with the exception of IANA)
>> 1 x IANA 
>> 1 x GNSO (non-registry) 
>> 1 x ALAC
>> 1 x GAC
>> 1 x ASO
>> 1 x RSSAC
>> 1 x SSAC
>>  
>> The GNSO Council is responsible for selecting the GNSO Liaison, and also approving the final composition of the CSC in conjunction with the ccNSO Council. To that end, we are seeking volunteers to serve as the GNSO Council Selection Committee to select the GNSO Liaison for the CSC and to also review the proposed final composition of the CSC and make a recommendation to the Council for approval. The optimal number would be somewhere between 3 to 5 members, representing a cross-section of the Council. In the event that we have no volunteers, James, Heather and I have agreed to serve as the Selection Committee.
>>  
>> It was anticipated that ICANN would post a call for Expressions of Interest last week, but this has been delayed pending approval of the CWG. However, given the timeline, it would be helpful if those interested could respond to this email by Friday 27 June 2016, 23:59 UTC.
>>  
>> More detail regarding the GNSO Council obligations regarding the CSC is provided in the attached documents.
>>  
>> Please let me know if you have any questions.
>>  
>> Thanks
>>  
>> Donna
>>  
>> Donna Austin: Neustar, Inc.
>> Policy and Industry Affairs Manager
>> Cell: +1.310.890.9655 Email: donna.austin at neustar.biz <mailto:donna.austin at neustar.biz>
>>  
>> The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify me immediately and delete the original message.
>> Follow Neustar:   <image001.png> Facebook <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_neustarinc&d=DQMFAg&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=Jb-iYQ1rs-UZ3lSfng4uwj4hGeI901A8sqSs8uXNHUY&s=-vF9dg7THZk1OqanLDPrFrkI1pGg4ZCji9A9tZK-rI4&e=>   <image002.png> LinkedIn <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_5349&d=DQMFAg&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=Jb-iYQ1rs-UZ3lSfng4uwj4hGeI901A8sqSs8uXNHUY&s=c0kduDBXZSqHFZLHBeN3gm0-1D15eTAspySgVskTXgw&e=>   <image003.png> Twitter <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_neustar&d=DQMFAg&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=Jb-iYQ1rs-UZ3lSfng4uwj4hGeI901A8sqSs8uXNHUY&s=k8BGQnVZInL7q6dPDaKySjy9S6QDtjpPP6QXrryzo38&e=>
>> P Please consider the environment before printing this e-mail.
>>  
>>  
>>  
>>  
>>  
>>  
> <image003.png><image002.png><image001.png>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20160524/84ddaf9c/attachment.html>