November 2016 - council - lists.icann.org

GNSO Council resolutions - Hyderabad 7 November 2016
by Glen de Saint Géry Nov. 17, 2016

Nov. 17, 2016

Dear Councillors, Please find the resolutions passed at the GNSO Council Public meeting in Hyderabad on 7 November 2016. Consent Agenda 1. Adoption of the GAC-GNSO Consultation Group on GAC Early Engagement in GNSO Policy Development Processes Final Status Report & Recommendations WHEREAS: 1. In March 2014 the GNSO and GAC formed a joint consultation group (CG) to explore mechanisms to facilitate GAC early engagement in GNSO Policy Development Processes. 2. As per its charter, the CG's deliberations have focused on two tracks, namely 1) a mechanism for day-to-day ongoing cooperation and 2) a mechanism for GAC early engagement in the GNSO PDP (see https://community.icann.org/display/gnsogcgogeeipdp/3.+Charter) 3. A number of recommendations, such as the Quick Look Mechanism and the GNSO Liaison to the GAC have already been piloted and subsequently implemented. 4. Following ICANN56, the CG reviewed the charter and noted a number of outstanding items that it considered, factoring in the input received as part of the survey amongst the GAC and GNSO to obtain input on the experiences to date with the Quick Look Mechanism as well as additional suggestions and ideas for opportunities for early engagement in the other phases of the PDP (see https://www.surveymonkey.com/results/SM-6ZLVM39T/) 5. As a result of this review, the CG submitted its Final Status Update and Proposed Recommendations to the GNSO and GAC on 10 October 2016 (see https://gnso.icann.org/en/drafts/gac-status-report-rec-10oct16-en.pdf) 6. The GNSO Council reviewed the Final Status Update and Proposed Recommendations and discussed it with the GAC during its joint session at ICANN57. RESOLVED: 1. The GNSO Council adopts the Final Status Update and Proposed Recommendations (see https://gnso.icann.org/en/drafts/gac-status-report-rec-10oct16-en.pdf) 2. The GNSO Council instructs staff to work with the GNSO Council, the GAC Leadership team as well as the GNSO Liaison to the GAC on the implementation of these recommendations. An implementation status update is expected to be provided in time for the next joint GNSO-GAC meeting. 3. The GNSO Council thanks the members of the Consultation Group for all their efforts and considers the work of the CG hereby complete. 4. The GNSO Council requests that the GNSO Secretariat informs the GAC Secretariat of this decision. Voting results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-1-07nov16-e…> Consent Agenda 2. Approval of the appointment of Carlos Raúl Gutiérrez 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, a GNSO liaison to the GAC was piloted during FY15 and FY16. 2. Based on the review of the GAC-GNSO Consultation Group (see http://gnso.icann.org/en/drafts/review-liaison-gac-pilot-29feb16-en.pdf) and discussions between the GAC and GNSO during their joint session at the ICANN meeting in Marrakesh, the GNSO Council confirmed on 14 April 2016 role and process for a GNSO Liaison to the Governmental Advisory Committee as a permanent feature (see https://gnso.icann.org/en/drafts/request-liaison-gac-30mar16-en.pdf) 3. Following a call for candidates (https://gnso.icann.org/mailing-lists/archives/council/msg19176.html) three applications were received all of which were evaluated by the GNSO Council Leadership based on the criteria outlined in the call for candidates. 4. Carlos Gutiérrez was unanimously recommended by the GNSO Council Leadership as the preferred candidate. RESOLVED: 1. The GNSO Council hereby appoints Carlos Gutiérrez to the role of GNSO Liaison to the Governmental Advisory Committee until the end of the ICANN AGM 2017. 2. The GNSO Council will review the role and is expected to annually reconfirm the appointment, unless the review indicates otherwise and/or the Liaison has indicated that he/she is no longer available to continue in this role in which case a new selection process will take place and/or the review indicates. 3. The GNSO Council Leadership Team will co-ordinate with Carlos Gutiérrez as well as the GAC Leadership Team and GAC Secretariat on next steps and the successful implementation of this role. 4. The GNSO Council thanks all who expressed an interest in this role, and noting that all candidates met or exceeded the published requirements for the position. Voting results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-1-07nov16-e…> Main Agenda 3. Conditional participation of the GNSO as a Chartering Organization for the Cross Community Working Group to discuss Internet governance (CWG-IG) issues affecting ICANN WHEREAS: a) The GNSO Council adopted the charter for a Cross Community Working Group to discuss Internet governance (CWG-IG) issues affecting ICANN and make recommendations to the chartering organization on these issues on 15 October 2014, and as such became a Chartering Organization. b) The Charter foresees that "At each ICANN Annual General Meeting, starting 2014, the Charter and deliverables of the WG shall be reviewed by the participating SO's and AC's to determine whether the WG should continue, or, close and be dissolved. Consistent with ICANN community practices, the WG will continue if at least two of the participating SO's or AC's extend the Charter of the WG and notify the other participating SO's and AC's accordingly one month after the annual review date". c) The CWG-IG provided its first written status update on 23 June 2016 (see https://gnso.icann.org/en/drafts/ccwg-internet-governance-23jun16-en.pdf[gn…) d) The GNSO Council recently adopted the "Uniform Framework of Principles and Recommendations for Cross Community Working Groups" (CWG Framework) which details the lifecycle of a CCWG including initiation, formation, operation, decision-making, adoption of Final Report by Chartering Organizations and closure of CCWG, and post-closure of CCWG. e) The GNSO Council has observed that the CWG-IG does not follow this lifecycle, nor has it established or adopted an initial work plan and associated schedule as foreseen in its Charter. f) The GNSO Council recognizes the importance of a continued dialogue and discussion in relation to the topic of Internet Governance within an ICANN context. g) The GNSO Council has shared its concerns with the ccNSO Council and representatives of other SO/ACs on the subject of this CWG and its future. RESOLVED: a) The GNSO Council will continue to participate as a Chartering Organization for the CWG-IG. However, this participation is conditioned upon a comprehensive review of the CWG-IG Charter by the CWG-IG, in accordance with the CWG Framework (http://gnso.icann.org/en/drafts/uniform-framework-principles-recommendation…. In particular, the GNSO Council expects future work to be subject to a clear work plan, with regular updates and clear deliverables. b) The GNSO Council expects that the CWG-IG will present by ICANN58 a report on its findings, which may include a revised charter or a recommendation to reconstitute the group under a new structure. c) Following the submission of the CWG-IG report, the GNSO Council will consider the recommendations and decide whether or not it will continue as a Chartering Organization. d) The GNSO Secretariat will communicate this decision to the CWG-IG Chairs as well as the other Chartering Organizations. Voting results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-1-07nov16-e…> Main Agenda 4. Adoption of the Charter for a Cross-Community Working Group on new gTLD Auction Proceeds WHEREAS: 1. Following a number of sessions on the topic of new gTLD Auction proceeds during the ICANN53 in Buenos Aires (see https://buenosaires53.icann.org/en/schedule/mon-soac-high-interest[buenosai… and https://buenosaires53.icann.org/en/schedule/wed-cwg-new-gtld-auction[buenos…) a discussion paper was published in September 2015 to solicit further community input on this topic as well as the proposal to proceed with a CCWG on this topic. 2. As the feedback received on the discussion paper confirmed the support for moving forward with a CCWG, James Bladel, GNSO Chair, reached out to all the ICANN Supporting Organizations and Advisory Committees to ask for volunteers to participate in a drafting team to develop a charter for a CCWG on this topic. All ICANN SO/ACs, apart from the ccNSO, responded to this request and put forward volunteers to participate in the drafting team. 3. The GNSO Council appointed Jonathan Robinson to chair the Drafting Team ('DT'), which commenced its deliberations on Tuesday 23 February 2016. 4. The DT published a draft charter for community discussion in advance of ICANN 56 which was discussed during the cross-community session held at ICANN56. Following ICANN56, the DT reviewed all the input received and updated the proposed charter accordingly. On 13 September, this proposed charter was shared with all ICANN SO/ACs with the request to review it and identify any pertinent issues that would prevent adoption of the charter, if any. 5. Subsequently, a webinar was held on 13 October to allow for some additional time and information to undertake this review (see https://community.icann.org/x/gh_4Aw[community.icann.org]) 6. As no pertinent issues were raised, the DT submitted the proposed CCWG charter (see https://community.icann.org/x/mRuOAw[community.icann.org]) for consideration to all ICANN SO/ACs on 17 October 2016. RESOLVED: 1. The GNSO Council approves the Charter. 2. Each GNSO Stakeholder Group will identify one member for the CCWG by 5 December 2016 taking into account the charter requirement that best efforts should be made to ensure that members: a. Have sufficient and appropriate motivation (and ideally expertise) to participate in the substance of the work of the CCWG. Appropriate experience could, for example, include experience with allocation and final disbursement of funds; b. Commit to actively participate in the activities of the CCWG on an on-going and long-term basis; c. Solicit and communicate (where appropriate) the views and concerns of individuals in the organization that appoints them; d. Commit to abide to the charter when participating in the CCWG; e. Understand the needs of the Internet communities that ICANN serves (standards, domains and numbers); f. Understand the broader ecosystem (the Internet Community) in which ICANN operates and the needs of those working on other aspects of the Internet industry, including those not yet connected. 3. The GNSO Council expects to select a GNSO Co-Chair for the CCWG from the slate of GNSO appointed members to the CCWG during its meeting on 15 December 2016. 4. Furthermore, in addition to a Statement of Interest, all members and participants will be required to provide a declaration on intention to apply for (or in any way support the application for) new gTLD Auction Proceeds, either as an individual or through the entity you are representing or employed by or are otherwise funded by or affiliated with or support/endorse. It will be mandatory to report any changes in relation to these intentions throughout the CCWG life-cycle. 5. The GNSO will collaborate with the other SOs and ACs to issue a call for participants and observers to join the CCWG, each in accordance with its own rules. 6. The GNSO Council thanks the members of the Auction Proceeds Drafting Team for their contributions developing this Draft Charter. Voting results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-1-07nov16-e…> Thank you. Please let us know if you have any questions. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Motion RE: GAC Communique
by policy＠paulmcgrady.com Nov. 15, 2016

Nov. 15, 2016

1 0

FW: [Soac-infoalert] ICANN57 Meeting Survey
by Marika Konings Nov. 14, 2016

Nov. 14, 2016

Dear All, FYI, please see message below. Please make sure to participate in the survey as it will help inform planning for future meetings (note that the ICANN Meeting Structure Survey includes a question on the future of Constituency Day). Best regards, Marika From: <soac-infoalert-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Friday, November 11, 2016 at 3:49 AM To: "soac-infoalert(a)icann.org" <soac-infoalert(a)icann.org> Subject: [Soac-infoalert] ICANN57 Meeting Survey Please join in in taking these two surveys. One is on ICANN57 and the other is on the structure of ICANN. Soon we will be send additional information about the Community planning for ICANN58. Thank you for your participation on ICANN57. Regards. David https://meetingapp.icann.org/icann57/surveys/196636[meetingapp.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__meetingapp.icann.org_i…> Sent from my iPhone David A. Olive Senior Vice President, Policy Development Support General Manager, ICANN Regional Headquarters –Istanbul Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349<tel:10%2034349> Fulya, Besiktas, Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212<tel:+90.212.999.6212> Mobile: + 1. 202.341.3611<tel:+%201.%20202.341.3611> Mobile: +90.533.341.6550<tel:+90.533.341.6550>

1 0

RE: [council] FW: [CCWG-ACCT] Fwd: ICANN's US jurisdiction
by policy＠paulmcgrady.com Nov. 14, 2016

Nov. 14, 2016

4 3

RE: [council] [CCWG-ACCT] Fwd: ICANN's US jurisdiction
by policy＠paulmcgrady.com Nov. 14, 2016

Nov. 14, 2016

1 0

RE: [council] FW: [CCWG-ACCT] Fwd: ICANN's US jurisdiction
by policy＠paulmcgrady.com Nov. 13, 2016

Nov. 13, 2016

3 2

Thank you Staff!
by James M. Bladel Nov. 10, 2016

Nov. 10, 2016

(Please forward to anyone I’ve missed) Huge thanks to Glen, Rob, Marika and Mary for arranging the tour this afternoon! It was a welcome change from another day trapped in a meeting room. Safe travels home, and see you in Copenhagen! Thanks— J.

6 7

FW: [CCWG-ACCT] Fwd: ICANN's US jurisdiction
by James M. Bladel Nov. 9, 2016

Nov. 9, 2016

Council colleagues – See below for a statement published on the CCWG-ACCT mailing list. Thank you, J. From: <accountability-cross-community-bounces(a)icann.org> on behalf of parminder <parminder(a)itforchange.net> Date: Wednesday, November 9, 2016 at 7:31 To: CCWG Accountability <accountability-cross-community(a)icann.org> Subject: [CCWG-ACCT] Fwd: ICANN's US jurisdiction All I thought this may be relevant to those on this list. Regard, parminder -------- Forwarded Message -------- Subject: ICANN's US jurisdiction Date: Wed, 9 Nov 2016 07:23:40 +0530 From: parminder <parminder(a)itforchange.net><mailto:parminder@itforchange.net> To: governance(a)lists.igcaucus.org<mailto:governance@lists.igcaucus.org> <governance(a)lists.igcaucus.org><mailto:governance@lists.igcaucus.org>, BestBitsList <bestbits(a)lists.bestbits.net><mailto:bestbits@lists.bestbits.net>, Forum@Justnetcoalition. Org <forum(a)justnetcoalition.org><mailto:forum@justnetcoalition.org> All As you know, the issue of jurisdiction of ICANN is under consideration at ICANN's community process (in the accountability track where there is a sub group discussing this issue). ICANN is currently meeting in Hyderabad, India, from 3rd to 9th November. Today, on the last day of ICANN's Hyderabad meeting, the enclosed statement was issued by key Indian civil society organisations engaged with Internet governance issues, supported by two key global networks involved in this area. The statement expresses the urgent need for transiting ICANN from being under the jurisdiction of one country, presenting the rationale of why this is important to do. It also lists some possible options of doing so, towards beginning a serious action-oriented deliberation on this very important matter. Unlike what is often understood, the jurisdiction issue is not just a matter of sovereign prestige and self respect of the states but concerns vital matters impacting people's rights. This is especially so as the society gets more and more digitised in all areas. We welcome comments and feedback. The statement has been issued by the following Indian civil society organisations. Centre for Internet and Society<http://cis-india.org/>, Bangalore IT for Change<http://www.itforchange.net/>, Bangalore Free Software Movement of India<https://en.wikipedia.org/wiki/Free_Software_Movement_of_India>, Hyderabad Society for Knowledge Commons<http://www.knowledgecommons.in/>, New Delhi Digital Empowerment Foundation<http://defindia.org/>, New Delhi Delhi Science Forum<http://www.delhiscienceforum.net/>, New Delhi Software Freedom Law Center India, New Delhi Third World Network - India<https://twnetwork.org/>, New Delhi It is supported by the following global networks: Association For Progressive Communications<https://www.apc.org/> Just Net Coalition <http://justnetcoalition.org/> <http://justnetcoalition.org/>We will soon expand this effort to enlist more global support. Best, Parminder <http://justnetcoalition.org/> <http://justnetcoalition.org/> <http://justnetcoalition.org/> <http://justnetcoalition.org/>

1 0

Re: [council] Thank you Staff!
by Michele Neylon - Blacknight Nov. 9, 2016

Nov. 9, 2016

+1 It was wonderful to get out of windowless rooms for a few hours -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains http://www.blacknight.host/ http://blacknight.blog/ http://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845 From: <owner-council(a)gnso.icann.org> on behalf of James Bladel <jbladel(a)godaddy.com> Date: Wednesday 9 November 2016 at 14:05 To: GNSO Council List <council(a)gnso.icann.org>, Paul Diaz <pdiaz(a)pir.org>, Steve DelBianco <sdelbianco(a)netchoice.org>, Greg Shatan <gregshatanipc(a)gmail.com>, Becky Burr <Becky.Burr(a)neustar.biz>, 'Tobias Sattler' <sattler(a)united-domains.de> Subject: [council] Thank you Staff! (Please forward to anyone I’ve missed) Huge thanks to Glen, Rob, Marika and Mary for arranging the tour this afternoon! It was a welcome change from another day trapped in a meeting room. Safe travels home, and see you in Copenhagen! Thanks— J.

1 0

FW: GAC Communique - ICANN57
by Phil Corwin Nov. 9, 2016

Nov. 9, 2016

In regard to the GAC advice concerning IGOs appearing at pages 9-11 of the Communique, as Co-Chair of the IGO CRP WG, and noting this language-- III. That, to facilitate the implementation of the above advice, the GAC invites the GNSO Working Group on Curative Rights Protection Mechanisms to take the small group proposal into account. --I would like Council members to be aware that the WG spent two one hour working sessions analyzing and discussing the SG Proposal, so we have complied with this request. In regard to the rest of the GAC advice concerning IGOs, I will confer with my Co-Chair after returning home and we shall prepare a more detailed response to share with Council. Best regards, Philip 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 "Luck is the residue of design" -- Branch Rickey ________________________________ From: soac-infoalert-bounces(a)icann.org [soac-infoalert-bounces(a)icann.org] on behalf of David Olive [david.olive(a)icann.org] Sent: Tuesday, November 08, 2016 12:46 PM To: soac-infoalert(a)icann.org Subject: [Soac-infoalert] GAC Communique - ICANN57 https://gacweb.icann.org/download/attachments/27132037/GAC%20ICANN%2057%20C…

1 0