[council] Motion - GAC Liaison

Phil Corwin psc at vlaw-dc.com
Mon Apr 4 21:40:07 UTC 2016


I'm in full support of converting this to a permanent role, and very much appreciate Mason's efforts over the past two years.

Is it possible to circulate the 'Request for Candidates - GNSO Liaison to the GAC' so that we may review the requirements, process and procedures for this role? Thanks

Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/Cell

Twitter: @VlawDC

"Luck is the residue of design" -- Branch Rickey

From: owner-council at gnso.icann.org [mailto:owner-council at gnso.icann.org] On Behalf Of Jennifer Gore Standiford
Sent: Monday, April 04, 2016 3:55 PM
To: James M. Bladel
Cc: GNSO Council List
Subject: Re: [council] Motion - GAC Liaison

Thanks James. I second the motion.

Jennifer

On Apr 4, 2016, at 3:36 PM, James M. Bladel <jbladel at godaddy.com<mailto:jbladel at godaddy.com>> wrote:

Council Colleagues -

Following the discussion on the list, I am now submitting this motion (attached and copied below) for our next meeting. This motion calls for making the GAC Liaison a permanent role, and begins the process for selecting Mason Cole's replacement.  For your review, I have also attached the selection process that was used previously.

Thank you,

J.

________________________________



Motion to confirm the role and process for a GNSO Liaison to the Governmental Advisory Committee

Whereas:


1.      As part of the discussions within ICANN between the GNSO and GAC, on how to facilitate early engagement of the GAC in GNSO policy development activities, the option of appointing a GNSO liaison to the GAC was proposed as one of the mechanisms to explore and implemented as a one-year pilot program in FY15 on the recommendation of the GAC-GNSO Consultation Group.

2.      The GAC and GNSO Council agreed that additional time was needed to fully evaluate this pilot program and as such requested, and received, support for continuing the pilot program in FY16.

3.      The GAC-GNSO Consultation Group reviewed the pilot project (see http://gnso.icann.org/en/drafts/review-liaison-gac-pilot-29feb16-en.pdf) and has recommended to the GAC and GNSO that 'the GNSO Liaison to the GAC, in conjunction with the other improvements recommended by the GAC-GNSO Consultation Group, has positively contributed to the GAC engagement with the GNSO, and recommends that the GNSO Liaison to the GAC is transformed from a pilot project to a permanent role'.

4.      The GAC and GNSO discussed the review of the pilot project during their joint session at the ICANN meeting in Marrakesh.

5.      The GNSO Council reviewed the 'Request for Candidates - GNSO Liaison to the GAC' which includes the proposed call for volunteers, application and evaluation process (see [include link].

Resolved:


1.      The GNSO Council hereby confirms that the GNSO Liaison to the GAC is to become a permanent role at the start of FY17 (1 July 2016) and adopts the 'Request for Candidates - GNSO Liaison to the GAC' as the requirements, process and procedures for this role (see [include link]).

2.      The GNSO Council instructs the GNSO Secretariat to distribute the request for candidates to the GNSO Stakeholder Groups and Constituencies in accordance with the timeline outlined in the 'Request for Candidates - GNSO Liaison to the GAC'.

3.      The Council thanks Mason Cole who has been fulfilling this role for the last two years and looks forward to working with him during the remainder of his term.
<Motion to confirm the role and process of GNSO Liaison to the GAC - 30 March 2016[1].docx>
<GNSO Liaison to the GAC - call for candidates - updated 30 March 2016.doc>
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7497 / Virus Database: 4545/11942 - Release Date: 04/02/16
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20160404/71f7db48/attachment.html>


More information about the council mailing list