Dear Councillors Please review the two motions in text below which are also published on page https://community.icann.org/x/DQObAw that will be voted on by email ballot on 6-9 August 2016. In motion 1 the link is still to be added when available 6. The GNSO and ccNSO CSC Selection Committees sent to the ccNSO and GNSO Councils their recommended list [INSERT LINK TO LIST WHEN AVAILABLE] of CSC liaisons and members. Please note that both motions need to be seconded. If you have any comments please send these to the Council mailing list, otherwise the motions will appear, as they stand, to be voted on by email ballot on 6 through to 9 August 2016. 1. MOTION TO APPROVE THE LIAISONS AND MEMBERS OF THE CUSTOMER STANDING COMMITTEE (CSC) - 25 July 2016 Made by: Wolf-Ulrich Knoben Seconded by: WHEREAS: 1. The package of proposals<https://www.icann.org/en/system/files/files/iana-stewardship-transition-pack...> that was developed by the community in relation to the IANA Stewardship Transition called for the creation of a new structure, the Customer Standing Committee (CSC) to provide operational oversight of the performance of the IANA naming function, a role currently performed by the United States government through the National Telecommunications and Information Authority (NTIA). 2. On 02 June 2016, the GNSO Council confirmed a Selection Committee to evaluate the candidates for the GNSO CSC liaison. The GNSO Council approved James Gannon as the CSC Liaison. 3. The GNSO Council provided to ICANN the liaison name along with his Expression of Interest by the deadline of 22 July 2016. 4. The GNSO Council requested that the Selection Committee shall engage, if requested, with the ccNSO Selection Committee to evaluate the full slate of CSC members and liaisons. 5. The GNSO and ccNSO CSC Selection Committees met on 02 August to consider the CSC liaisons and members. 6. The GNSO and ccNSO CSC Selection Committees sent to the ccNSO and GNSO Councils their recommended list [INSERT LINK TO LIST WHEN AVAILABLE] of CSC liaisons and members. RESOLVED: 1. The GNSO Council has reviewed the list of CSC liaisons and members and approves the full list. 2. The GNSO Council requests that the GNSO Secretariat shall notify ICANN no later than 10 August that the GNSO has approved the full list of CSC liaisons and members. 2. Adoption of the GNSO Review of GAC Communiqué for submission to the ICANN Board - deferred to Electronic Voting 6-9 August 2016 Made by: James Bladel Seconded by: Whereas, 1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC. 4. The GNSO Council developed a template to facilitate this process, which was completed following the publication of the Helsinki GAC Communiqué by a volunteer and shared with the GNSO Council for its review. 5. The GNSO hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Review of the Helsinki GAC Communiqué (see http://gnso.icann.org/en/drafts/review-gac-communique-27jul16-en.pdf<http://mailer.samanage.com/wf/click?upn=KTB340yHI8DoUtMP4BGJnuFT4taHix-2FWCICVaGtUyTdYM9WfnyW-2F-2BY-2BYBi6-2FsfH7na32o3JEji3-2FbvePwaEIwC4vUN6RH3Z7EAvNsN5YwXA-3D_r-2BdYbSjRm9r0i9vSiPZtW-2BX-2BAwnBbxYJcYft8cAni3iLz7nHdH1TO6yId4yJ1X5bCjn7UQ8ekPGWrKZXzU-2FB1vqqq7KS-2BMznRij3m3ZEI87WW3StxS8dTPOoQSB9krb-2FFJK2QHBzOYchxlxB81-2FrQgEKCZwhIWmFeV3hThjRR7ogCkshuA-2FPie9e6zmA6P8LBAvHnSXnsQVaZYyeAkdwlvV9YAurQoSnhfNSE481ppaFGGeo4XVZzuAlQQE5OohOhyShcm32qhe02MWLmS1vB9uV5E3Q0mlnfpOneiew5okrv7atRnu1ozTk9GEIXPpuNBhHs4QcNBIgea65L80hOQxcxE9UDQ-2FHqn5jnGTXTmTSp9ULY15uQfn5h8O-2Fr4H2YwhGLygXgMEXo4e0CroXxGJYz9i4-2B-2FVJ4mFOlFS5lXeT0pOQvwJChy4eb40N5iXHQUrg7XAcf3rMPaJEOViYNfhj3HySNMQBNIeD2CpxzPU-3D>) and requests that the GNSO Council Chair communicate the GNSO Review of the Helsinki GAC Communiqué to the ICANN Board. 2. Following the communication to the ICANN Board, the GNSO Council requests that the GNSO Council Chair informs the GAC Chair as well as the GAC-GNSO Consultation Group of the communication between the GNSO Council and the ICANN Board. Thank you Kind regards, Glen Glen de Saint Géry GNSO Secretariat