September 2016 - council - lists.icann.org

Call for candidates: GNSO Liaison to the GAC
by Glen de Saint Géry Sept. 28, 2016

Sept. 28, 2016

Dear All, As a follow up to the reminder for the revised timeline adopted in Helsinki for the GNSO Liaison to the GAC attached please the call for candidates. Thank you very much. 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-…>. From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Glen de Saint Géry Sent: Sunday, September 25, 2016 11:45 PM To: GNSO Council List (council(a)gnso.icann.org) <council(a)gnso.icann.org> Subject: [council] REMINDER: GNSO Liaison to the GAC - Revised timeline Dear Councillors, We would like to remind you of the revised timeline as adopted in Helsinki for the GNSO Liaison to the GAC and that we will be sending a call for candidates early in September 2016. We would like to draw your attention to the slight adjustment in the timeline which has come about as a result of the change in the date of the Council meeting at ICANN57 (see: http://gnso.icann.org/en/drafts/meeting-c-schedule-11jul16-en.pdf[gnso.ican…<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_draft…>) 1. The leadership of each Stakeholder Group / Constituency may submit the application of its candidate(s), which should include at a minimum a link to a completed and current statement of interest as well as a brief note explaining why the candidate has applied for this role and how the candidate meets the specific requirements by 1 October 2016 at the latest to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org)<mailto:gnso.secretariat@gnso.icann.org)>. Candidates will be requested to complete an application template. 2. The GNSO Council Chairs will review the applications received and rank these taking into account the skills and experience required as outlined in this call for volunteers by 20 October 2016. 3. Based on the outcome of the ranking process, the GNSO Council Chairs will contact the nr 1 candidate to confirm the selection by 20 October 2016. 4. GNSO Council Chairs will submit motion for confirmation of GNSO Liaison to the GAC to the GNSO Council by 28 October 2016 at the latest. 5. Consideration of motion and approval of candidate by GNSO Council during GNSO Council meeting on 7 November 2016. 6. Confirmation of candidate to GAC leadership (by 9 November 2016). 7. GNSO Liaison to the GAC officially takes up its role (by 10 November 2016). Please note that the name of applicants will be made public unless an applicant specifically states in his/her application that his/her name should be kept confidential. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> Internet Corporation for Assigned Names & Numbers - ICANN http://gnso.icann.org/en/<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_&d=Cw…>

1 0

CWG-Internet Governance and Next Steps
by James M. Bladel Sept. 27, 2016

Sept. 27, 2016

Dear Councilors- Unfortunately, we ran short of time during the last Council meeting to discuss agenda item 7 (Council Discussion – Next Steps for the Cross Community Working Group on Internet Governance). Some Councilors questioned why this item was on the agenda at all. Therefore, I thought it might be helpful to explain why the leadership added this topic to the agenda and our expected next steps: * As you may recall, the CWG-IG provided a status update that was reviewed and discussed by the Council in Helsinki (see https://gnso.icann.org/en/drafts/ccwg-internet-governance-23jun16-en.pdf) Note that the CWG-IG charter foresees that ‘The Co-Chairs of the WG shall update the participating SO’s and AC’s at least monthly on the activities of the WG’ and ‘The Co-Chairs will be responsible for maintaining and updating the work plan and schedule and for informing the Chairs of the participating SO’s and AC’s of changes made to the work plan and schedule’. * In light of the work of the CWG Principles, which foresees CWGs having a clear start and end, many have questioned whether a CWG is the appropriate vehicle for dealing with IG issues, as the current objective of the CWG (as described in its charter) is ‘to coordinate, facilitate, and increase the participation of the ICANN community in discussions and processes pertaining to Internet Governance’. * The CWG-IG 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’. * The GNSO is therefore expected to review and decide by ICANN57 whether to extend its support for the charter of the CWG-IG. * In order to be in a position to make this determination by ICANN57, this item was added to the Council agenda to obtain feedback from Councilors/SG/Cs on what further information, if any, is needed from the CWG-IG. I propose that this final bullet point become the focal point of our discussions (list or teleconference) on this topic. If Councilors are satisfied that they, along with the leadership of their respective SGs and Cs, are capable of deciding on continued GNSO support for the CCWG-IG charter by ICANN57, then it may not be necessary to revisit this topic again until our sessions in Hyderabad. If not, we should include this discussion on our next Council agenda to ensure that all open questions are addressed. Regards, J.

1 1

Summary of input received: ICANN Board Letter on New gTLD Subsequent Procedures
by Emily Barabas Sept. 27, 2016

Sept. 27, 2016

Dear Councillors, In the upcoming September 29th Council meeting, there will be a discussion regarding the ICANN Board Letter on New gTLD Subsequent Procedures and community input on this letter. Please find attached a draft document created by staff to facilitate the review of input on this topic received to date. A full list of documents related to this agenda item can be found on the wiki, including all input received to date: https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Meetin…. We welcome any additional suggestions on ways staff can further support this review. Kind regards, Emily Emily Barabas | Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

Revised Motion - GSNO Validation of CCWG-Accountability Budget Request
by James M. Bladel Sept. 26, 2016

Sept. 26, 2016

Colleagues – Attached and copied below, please find a modified version of this Motion. As the maker of the original, I accept all changes as friendly amendments. Many thanks to Phil, Ed, Paul, and Keith for working out the new language, and positioning us for a more efficient Council meeting on Thursday. Thank you, J. Draft Motion - GNSO Validation of CCWG-Accountability Budget Request WHEREAS, 1. Per its Charter, the Project Cost Support Team (PCST) has supported the CCWG-Accountability in developing a draft budget and cost-control processes for the CCWG-Accountability activities for FY17, and has also developed a historical analysis of all the transition costs to date (see https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf) 2. The CCWG-Accountability FY17 budget was presented at its plenary meeting of June 21st and approved for transmission to the Chartering Organizations for validation as per the process agreed with the PCST. This request for validation was received on 23 June. 3. Following review and discussion during ICANN56, the GNSO Council requested<https://gnso.icann.org/en/correspondence/bladel-to-bfc-ccwg-accountability-…> a webinar on this topic which was held on 23 August (see transcript at https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-2…, recording at http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3 and AC recording at https://icann.adobeconnect.com/p8fu99qpt7d/) 4. The GNSO Council notes that many members of the GNSO community have expressed the view that the projected budget does not likely support revisiting the topic of the jurisdiction of ICANN’s organization in that such exploration would likely require substantial independent legal advice on alternative jurisdictions and their potential impact on the text and structure of ICANN’s Bylaws. 5. The GNSO Council has discussed and reviewed all the relevant materials. RESOLVED, 1. The GNSO Council hereby accepts the proposed CCWG-Accountability FY17 budget, as well as the cost-control processes presented in conjunction with the CCWG budget, expects the working groups to be restrained and judicious in their use of outside legal assistance, and believes that the Legal Committee should exercise reasonable and effective controls in evaluating requests for outside legal assistance and should approve them only when deemed essential to assist a working group to fully and objectively understand and develop a particular course of action for which the group has reached a substantial degree of consensus and requires legal advice on its risks and feasibility. 2. The GNSO Council expects to receive regular updates on actual expenditures as tracked against this adopted budget, and reserves the right to provide further input on the budget allocation in relation to the CCWG-Accountability related activities. 3. The GNSO Council expects ICANN staff, including its office of General Counsel, to provide the assistance requested by the CCWG and its working groups in an expeditious, comprehensive, and unbiased manner. 4. The GNSO Council expects the CCWG-Accountability and staff to work within the constraints of this approved budget, and that excess costs or request for additional funding beyond said budget should be recommended by the Legal Committee only when deemed essential to completion of the CCWG’s work and objectives. . 5. It is the position of the GNSO Council that revisiting the jurisdiction or organization of the ICANN legal entity, as established by CCWG-Accountability Work Stream 1, would not likely be supported by this projected budget and, further, that such inquiry should not be undertaken at this time because the new accountability measures are all premised and dependent on California jurisdiction for their effective operation, and any near-term changes in organizational jurisdiction could be extremely destabilizing for ICANN and its community. 6. The GNSO Council requests the GNSO Secretariat to communicate this resolution to the CCWG-Accountability Chairs, and to the office of the ICANN CFO.

2 1

[Council] FW: New gTLD Subsequent Procedures PDP WG - Response to 12 Sept 2016 Council Letter
by Steve Chan Sept. 26, 2016

Sept. 26, 2016

Dear Councilors, Attached, please find the New gTLD Subsequent Procedure PDP WG’s response to the GNSO Council’s letter. Best, Steve From: <owner-gnso-chairs(a)icann.org> on behalf of Steve Chan <steve.chan(a)icann.org> Date: Sunday, September 25, 2016 at 11:00 AM To: "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org> Cc: avri doria <avri(a)apc.org>, Jeff Neuman <jeff.neuman(a)comlaude.com>, Paul McGrady <policy(a)paulmcgrady.com>, Julie Hedlund <julie.hedlund(a)icann.org>, Emily Barabas <emily.barabas(a)icann.org> Subject: [gnso-chairs] - New gTLD Subsequent Procedures PDP WG - Response to 12 Sept 2016 Council Letter Dear James, Donna, and Heather, Attached, please find the New gTLD Subsequent Procedures PDP WG’s response to the Council’s letter, sent to the WG on 12 September. If you have any questions, please let the co-chairs or staff know. Best, Steve Steven Chan  Sr. Policy Manager   ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org direct: +1.310.301.3886  mobile: +1.310.339.4410 tel: +1.310.301.5800 fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://twitter.com/ICANN_GNSO http://gnso.icann.org/en/

1 0

FW: RySG inputs for the Subsequent Procedures PDP WG
by Emily Barabas Sept. 26, 2016

Sept. 26, 2016

Dear All, Please find attached input from the RySG regarding the Subsequent Procedures PDP WG. Kind regards, Emily On 26/09/16 22:07, "Paul Diaz" <pdiaz(a)pir.org> wrote: Attached please find the RySG's initial input for the Subsequent Procedures PDP WG. As noted in the document, the RySG has identified a small number of initial areas in which the GNSO Policy either did not address an issue that arose during the 2012 round, or where it became clear that the GNSO Policy needed to be revised. Please note that in the interest of time we did not conduct a vote on these comments. We did, however, debate them on our mailing list and during a recent biweekly call. No RySG member expressed opposition to submitting these comments. Please feel free to contact me with questions or concerns. Best, P Paul Diaz Chair, gTLD Registries Stakeholder Group

1 0

Draft Motion - GNSO Validation of CCWG-Accountability Budget Request
by James M. Bladel Sept. 26, 2016

Sept. 26, 2016

Council Colleagues - Attached and copied below, please find a draft motion for consideration during our next GNSO Council call (29 SEP), that examines the subject of the proposed budget & cost control mechanisms for CCWG-ACCT and Work Stream 2. In particular, I would like to draw your attention to WHEREAS #4 and RESOLVED #4, in which I attempted to capture the concerns raised by Phil and Paul and others regarding revisiting the subject of ICANN Jurisdiction in WS2. Please review these provisions closely, and make sure that they accurately reflect these points. Thank you, J. Draft Motion - GNSO Validation of CCWG-Accountability Budget Request WHEREAS, 1. Per its Charter, the Project Cost Support Team (PCST) has supported the CCWG-Accountability in developing a draft budget and cost-control processes for the CCWG-Accountability activities for FY17, and has also developed a historical analysis of all the transition costs to date (see https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf) 2. The CCWG-Accountability FY17 budget was presented at its plenary meeting of June 21st and approved for transmission to the Chartering Organizations for validation as per the process agreed with the PCST. This request for validation was received on 23 June. 3. Following review and discussion during ICANN56, the GNSO Council requested<https://gnso.icann.org/en/correspondence/bladel-to-bfc-ccwg-accountability-…> a webinar on this topic which was held on 23 August (see transcript at https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-2…, recording at http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3 and AC recording at https://icann.adobeconnect.com/p8fu99qpt7d/) 4. The GNSO Council notes that many members of the GNSO community have expressed the view that the projected budget does not support revisiting the topic of the jurisdiction of ICANN"s organization. 5. The GNSO Council has discussed and reviewed all the relevant materials. RESOLVED, 1. The GNSO Council hereby accepts the proposed CCWG-Accountability FY17 budget, as well as the cost-control processes presented in conjunction with the CCWG budget (see https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf) 2. The GNSO Council expects to receive regular updates on actual expenditures as tracked against this adopted budget, and reserves the right to provide further input on the budget allocation in relation to the CCWG-Accountability related activities. 3. The GNSO Council expects the CCWG-Accountability and staff to work within the constraints of this approved budget, and that excess costs or request for additional funding will be considered only in extraordinary circumstances. 4. It is the position of the GNSO Council that revisiting the jurisdiction or organization of the ICANN legal entity, as established by CCWG-Accountability Work Stream 1, is not supported by this projected budget. 5. The GNSO Council requests the GNSO Secretariat to communicate this resolution to the CCWG-Accountability Chairs, and to the office of the ICANN CFO.

7 22

REMINDER: GNSO Liaison to the GAC - Revised timeline
by Glen de Saint Géry Sept. 25, 2016

Sept. 25, 2016

Dear Councillors, We would like to remind you of the revised timeline as adopted in Helsinki for the GNSO Liaison to the GAC and that we will be sending a call for candidates early in September 2016. We would like to draw your attention to the slight adjustment in the timeline which has come about as a result of the change in the date of the Council meeting at ICANN57 (see: http://gnso.icann.org/en/drafts/meeting-c-schedule-11jul16-en.pdf) 1. The leadership of each Stakeholder Group / Constituency may submit the application of its candidate(s), which should include at a minimum a link to a completed and current statement of interest as well as a brief note explaining why the candidate has applied for this role and how the candidate meets the specific requirements by 1 October 2016 at the latest to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org)<mailto:gnso.secretariat@gnso.icann.org)>. Candidates will be requested to complete an application template. 2. The GNSO Council Chairs will review the applications received and rank these taking into account the skills and experience required as outlined in this call for volunteers by 20 October 2016. 3. Based on the outcome of the ranking process, the GNSO Council Chairs will contact the nr 1 candidate to confirm the selection by 20 October 2016. 4. GNSO Council Chairs will submit motion for confirmation of GNSO Liaison to the GAC to the GNSO Council by 28 October 2016 at the latest. 5. Consideration of motion and approval of candidate by GNSO Council during GNSO Council meeting on 7 November 2016. 6. Confirmation of candidate to GAC leadership (by 9 November 2016). 7. GNSO Liaison to the GAC officially takes up its role (by 10 November 2016). Please note that the name of applicants will be made public unless an applicant specifically states in his/her application that his/her name should be kept confidential. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> Internet Corporation for Assigned Names & Numbers - ICANN http://gnso.icann.org/en/<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_&d=Cw…>

1 0

FW: [Correspondence] Letter from Steve Crocker to James Bladel, Chair, GNSO Council
by James M. Bladel Sept. 22, 2016

Sept. 22, 2016

Councilors - Attached, please find a letter form Steve Crocker/ICANN Board to the Council, regarding the work on subsequent rounds of New gTLDs. (Per Wendy's note, the letter has not yet been posted on the ICANN Correspondence page, but expected soon). Note that the letter contains a specific request to the GNSO: 'For example, assuming all other review activities are completed, it would be helpful to understand whether the GNSO believes that the entirety of the current Subsequent Procedures PDP must be completed prior to advancing a new application process under the current policy recommendations. The Board is cognizant that it may be difficult to provide a firm answer at this stage of the process as the reviews are still underway and the PDP is in its initial stages of work, but if any consideration has been given in relation to whether a future application process could proceed while policy work continues and be iteratively applied to the process for allocating new gTLDs, or that a set of critical issues could be identified to be addressed prior to a new application process, the Board would welcome that input. The Board would also welcome any elaboration on the expected time frame outlined in the PDP Work Plan, as well as any additional points the GNSO might wish to clarify for the Board in its efforts to support the various areas of work underway in the multistakeholder community'. I propose that we add this question/topic, and the letter itself, to our 1 SEP meeting agenda as a discussion item, and that we examine ideas on how to proceed on responding to this question. If this is amenable, I would also ask Staff to draft a brief note to Steve, acknowledging the receipt of this letter and noting that it would be discussed during our next meeting. Thoughts on this approach? Thank you, J. From: Wendy Profit <wendy.profit(a)icann.org<mailto:wendy.profit@icann.org>> Date: Friday, August 5, 2016 at 14:19 To: James Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>, Glen de Saint Géry <gnso-secretariat(a)gnso.icann.org<mailto:gnso-secretariat@gnso.icann.org>>, Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Cc: Steve Crocker <steve.crocker(a)board.icann.org<mailto:steve.crocker@board.icann.org>>, Icann-board ICANN <icann-board(a)icann.org<mailto:icann-board@icann.org>>, board-support <board-support(a)icann.org<mailto:board-support@icann.org>>, Akram Atallah <akram.atallah(a)icann.org<mailto:akram.atallah@icann.org>>, Erika Randall <erika.randall(a)icann.org<mailto:erika.randall@icann.org>>, Daniel Halloran <daniel.halloran(a)icann.org<mailto:daniel.halloran@icann.org>>, Eleeza Agopian <eleeza.agopian(a)icann.org<mailto:eleeza.agopian@icann.org>>, Jamie Hedlund <jamie.hedlund(a)icann.org<mailto:jamie.hedlund@icann.org>>, Karen Lentz <karen.lentz(a)icann.org<mailto:karen.lentz@icann.org>>, Cyrus Namazi <cyrus.namazi(a)icann.org<mailto:cyrus.namazi@icann.org>>, Cristina Flores <cristina.flores(a)icann.org<mailto:cristina.flores@icann.org>> Subject: [Correspondence] Letter from Steve Crocker to James Bladel, Chair, GNSO Council Dear James Bladel, Please find the attached letter from Steve Crocker, Chair, ICANN Board of Directors regarding subsequent New gTLD rounds. The letter will be posted shortly to the ICANN Correspondence and New gTLD Correspondence pages: https://www.icann.org/resources/pages/correspondence https://newgtlds.icann.org/en/program-status/correspondence With warm regards, Wendy Profit ICANN Board Operations Specialist

8 7

Proposed GNSO Council Meeting Agenda 29 September 2016 at 21:00 UTC.
by Glen de Saint Géry Sept. 22, 2016

Sept. 22, 2016

Dear Councillors, Please find the proposed Agenda for the GNSO Council Meeting on 29 September 2016 at 21:00 UTC. Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/owu4Aw This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf>, v3.2<https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf> updated on 01 September 2016. For convenience: · An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. · An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 21:00 UTC (http://tinyurl.com/hxoe7sh) 14:00 Los Angeles; 17:00 Washington; 22:00 London; 00:00 Istanbul; 07:00 Hobart - next day GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/gnso.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________________ Item 1: Administrative matters (5 minutes) 1.1 - Roll call 1.2 - Updates to Statements of Interest 1.3 - Review/amend agenda. 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes of the GNSO Council Meeting on 1 September 2016 to be posted on xx xxxxx 2016. Item 2: Opening Remarks / Review of Projects & Action List (5 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> Item 3: Consent agenda (0 minutes) Item 4: COUNCIL VOTE - GNSO Validation of the FY17 Budget and Cost-Control Processes for the CCWG-Accountability (20 minutes) A draft budget and cost-control processes for the CCWG-Accountability activities for FY17 was presented at the group's plenary meeting of 21 June 2016. In accordance with the process agreed with the Project Cost Support Team (PCST) that supported the CCWG-Accountability, a request for validation of the proposed budget and cost-control processes was transmitted to the CCWG-Accountability's Chartering Organizations on 23 June. The GNSO Council discussed the validation request during ICANN56 in Helsinki at the end of June, and a webinar on the topic was held at the Council's request on 23 August. Here the Council will consider approving the request to validate the FY17 budget and cost-control processes as well as a number of related topics that have been highlighted for discussion by various Councilors. . 4.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+29+Septembe…> (James Bladel) 4.2 - Discussion 4.3 - Council vote (voting threshold: simple majority) Item 5: COUNCIL VOTE - Approval of Appointment of an Interim GNSO Representative to the Empowered Community Administration (20 minutes) Section 1.1(a) of Article 6 of the new ICANN Bylaws concerning the composition and organization of the Empowered Community (EC) states that the EC is to be "a nonprofit association formed under the laws of the State of California consisting of the ASO, the ccNSO, the GNSO, the ALAC and the GAC (each a "Decisional Participant" or "associate," and collectively, the "Decisional Participants")." Section 6.3 provides that, as a Decisional Participant in the EC, the GNSO "shall act through its respective chair or such other person as may be designated by the GNSO". Each Decisional Participant must deliver annually a written certification from its chair or co-chairs to the ICANN Secretary designating the individual representing that Decisional Participant in the EC Administration. On 30 June 2016, the GNSO Council created a Drafting Team (DT) to work with ICANN staff to identify the GNSO's new rights and obligations, and prepare an implementation plan to address any needed changes by 30 September (https://gnso.icann.org/en/council/resolutions#20160630-2) Upon the completion of the DT's work, the GNSO is expected to finalize its process for appointing its EC representative going forward. Here the Council will consider the appointment of the GNSO Chair as an interim representative to the EC Administration to ensure that a GNSO representative is designated as soon as the new Bylaws come into effect, pending the completion and approval of the DT's work. 5.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+29+Septembe…> (James Bladel) 5.2 - Discussion 5.3 - Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE - Adoption of Implementation Advisory Group Recommendations to Update Procedure on WHOIS Conflicts with National Laws (20 minutes) The GNSO's 2005 Policy on WHOIS Conflicts with National Laws (see http://gnso.icann.org/en/issues/whois-privacy/council-rpt-18jan06.htm) had recommended the creation of a procedure to address conflicts between a contracted party's WHOIS obligations and local/national privacy laws or regulations. Under the existing procedure dating from January 2008, a contracted party that credibly demonstrates that it is legally prevented from complying with its WHOIS obligations can invoke the procedure, which defines a credible demonstration as one in which the contracted party has received "notification of an investigation, litigation, regulatory proceeding or other government or civil action that might affect its compliance." The procedure has never been invoked. In May 2014, ICANN launched a review of the procedure. An Implementation Advisory Group (IAG) was formed and began its work in January 2015. The IAG's Initial Report was published for public comment in November 2015 (see https://www.icann.org/public-comments/iag-whois-conflicts-privacy-2015-10-0…) On 25 May 2016, the IAG's Final Report<http://gnso.icann.org/mailing-lists/archives/council/pdf1nt18yPBer.pdf>, accompanying Appendices<http://gnso.icann.org/mailing-lists/archives/council/pdfC9Dr9B5OBO.pdf> and a summary Memo<https://gnso.icann.org/en/drafts/iag-review-whois-conflicts-procedure-26may…> to the GNSO Council was delivered to the GNSO Council. The IAG proposed modifications to the procedure that it believes do not contradict the underlying policy recommendations. The Council received an update on the proposed modifications at ICANN56 and discussed the matter further at its meetings on 21 July and 2 September. Here the Council will confirm whether or not the IAG's proposed modifications conform with the intent of the underlying GNSO Policy. 6.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+29+Septembe…> (Stephanie Perrin) 6.2 - Discussion 6.3 - Council vote (voting threshold: simple majority) Item 7: COUNCIL DISCUSSION - Proposed Draft Charter for a New Cross Community Working Group concerning Auction Proceeds from the 2012 New gTLD Program (15 minutes) The 2012 New gTLD Program established auctions as a mechanism of last resort to resolve string contention. Although most string contention sets have been resolved through other means prior to reaching the stage of an auction conducted by ICANN's authorized auction service provider, it was recognized from the outset that significant funds could accrue as a result of several auctions. As such, any and all auction proceeds have been reserved and earmarked until the Board authorizes a plan for the appropriate use of the funds. The Board, staff, and community are expected to work together in designing the appropriate processes for addressing the use of the new gTLD auction proceeds.To this end, a cross-community Drafting Team (DT) was formed which has now submitted a proposed Charter for a cross-community working group to all SO/ACs for consideration. As outlined by the DT, the proposed charter is the result of extensive input and deliberations and represents a careful balance between the different viewpoints and perspectives, including from both the DT Members and the ICANN Board liaisons to the DT. As such, the DT has requested that the GNSO Council review the proposed charter with this careful balance in mind and only flag to the DT any pertinent issues that would prevent the GNSO from adopting this charter. The DT has requested to receive the GNSO's feedback by 30 September 2016 at the latest, including an indication of when the GNSO anticipates to be in a position to consider the charter for adoption following 30 September, provided that no pertinent issues have been identified by any of the ICANN SO/ACs. Here the Council will discuss the DT's proposed Charter, with a view toward providing its input by 30 September. 7.1 - Summary and update (Jonathan Robinson (DT chair)) 7.2 - Council discussion 7.3 - Next steps Item 8: COUNCIL DISCUSSION - ICANN Board Letter on New gTLD Subsequent Procedures (15 minutes) On 5 August 2016, ICANN Board Chair Dr. Steve Crocker sent a letter to the GNSO Council concerning work on the GNSO Policy Development Process (PDP) on New gTLD Subsequent Procedures (https://gnso.icann.org/en/correspondence/crocker-to-bladel-05aug16-en.pdf) The Board wished to know the GNSO Council's view of the current work in light of the existing GNSO policy and ongoing parallel review work on the 2012 New gTLD Program. The Board letter specifically asked for information on the PDP timeline and whether the GNSO believes that the current PDP must be completed prior to advancing a new application process under the current policy recommendations, including whether any consideration has been given in relation to whether a future application process could proceed while policy work continues and be iteratively applied to the process for allocating new gTLDs. On 16 August the GNSO Chairs sent a reply to the Board on behalf of the Council, acknowledging the Board's request (https://gnso.icann.org/en/correspondence/council-leadership-to-crocker-16au…) At its meeting on 2 September, the GNSO Council agreed to seek input from all GNSO Stakeholder Groups and Constituency leaders, as well as the New gTLD Subsequent Procedures Policy Development Process Working Group. Here the Council will discuss feedback received from the various groups and determine next steps. 8.1 - Status update (GNSO Council chairs / Paul McGrady (for the PDP Working Group)) 8.2 - Discussion 8.3 - Next steps Item 9: COUNCIL DISCUSSION - Proposed Final Framework for Future Cross Community Working Groups (5 minutes) In March 2014, the ccNSO and GNSO Councils jointly chartered a Cross Community Working Group to develop a framework of principles to guide the formation, chartering, operations and closure for future cross community working groups (CCWG-Principles). The CCWG-Principles published an initial proposed framework for public comment in February 2016, and following a review of all public comments received and further community discussion at ICANN56 in Helsinki at the end of June, completed a proposed Final Framework which it has since submitted to both its Chartering Organizations. Here the Council will receive a brief update on the Final Framework, with a view toward its possible adoption at the next Council meeting in October. 9.1 - Summary and update (Mary Wong / Steve Chan) 9.2 - Next steps Item 10: COUNCIL DISCUSSION - GNSO Meeting Schedule for ICANN57 (5 minutes) ICANN57 will take place in Hyderabad, India, from 3-9 November 2016. This will be the first "Meeting C" under the new ICANN Meeting Strategy as well as the Annual General Meeting for ICANN. A draft GNSO schedule<http://gnso.icann.org/en/drafts/meeting-c-schedule-11jul16-en.pdf> for the meeting was circulated to the GNSO Council on 11 July 2016 and reviewed at the Council meetings on 21 July and 2 September. GNSO Stakeholder Groups and Constituencies wishing to hold sessions at ICANN57 were requested to submit meeting requests by the agreed deadline. Here the Council will discuss the GNSO's meeting schedule for ICANN57, including the Council sessions and Working Group and other meetings. 10.1 - Overview of the proposed schedule (GNSO Council Chairs / Glen de St Gery) 10.2 - Discussion 10.3 - Next steps Item 11: Any Other Business (5 minutes) Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting's adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) Reference (Coordinated Universal Time) UTC 21:00 Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+0DST 14:00 San José, Costa Rica UTC-5+0DST 16:00 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+0DST 16:00 New York/Washington DC, USA (EST) UTC-4+0DST 17:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 18:00 Rio de Janiero, Brazil (BRST) UTC-3+0DST 18:00 London, United Kingdom (BST) UTC+0DST 22:00 Bonn, Germany (CET) UTC+1+0DST 23:00 Cairo, Egypt, (EET) UTC+2+0DST 23:00 Istanbul, Turkey (EEST) UTC+3+0DST 00:00 (next day) Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 05:00 00 (next day) Singapore (SGT) UTC +8 +0DST 05:00 00 (next day) Sydney/Hobart, Australia (AEDT) UTC+11+0DST 07:00 00 (next day) ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2016, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> http://tinyurl.com/hxoe7sh Glen de Saint Géry Manager Supporting Organisations Advisory Committees Internet Corporation for Assigned Names & Numbers - ICANN glen(a)icann.org<mailto:glen@icann.org> http://www.icann.org<http://www.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