December 2016 - council - lists.icann.org

Re: [council] Mp3, AC recording and attendance GNSO Review implementation plan webinar is scheduled for Thursday, 08 December 2016 at 14:00 UTC
by James M. Bladel Dec. 8, 2016

Dec. 8, 2016

Thanks, Terri, and all who attended this session. And huge Kudos to Jen and Wolf-Ulrich for their leadership on this effort. Thanks – J. From: <owner-council(a)gnso.icann.org> on behalf of Terri Agnew <terri.agnew(a)icann.org> Date: Thursday, December 8, 2016 at 9:45 To: GNSO Council List <council(a)gnso.icann.org> Cc: "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org> Subject: [council] Mp3, AC recording and attendance GNSO Review implementation plan webinar is scheduled for Thursday, 08 December 2016 at 14:00 UTC Dear all, Please find the attendance of the call attached to this email and the MP3 and Adobe Connect recording below for the GNSO Review implementation plan webinar held on Thursday, 08 December 2016 at 14:00 UTC. MP3: https://audio.icann.org/gnso/gnso-review-08dec16-en.mp3 Adobe Connect Recording: https://participate.icann.org/p9p5iut6zcq/<https://participate.icann.org/p9p5iut6zcq/?OWASP_CSRFTOKEN=cd9a97fa0329f7d6…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> Mailing list archives: http://mm.icann.org/pipermail/gnso-review-wg/ Wiki page: https://community.icann.org/x/ZhmsAw ** Please let me know if your name has been left off the list ** Thank you. Kind regards, Terri ------------------------------- Adobe Connect chat transcript for 08 December 2016 Terri Agnew:Welcome to the GNSO Review implementation plan webinar held on Thursday, 08 December 2016 at 14:00 UTC for 60 minutes. Terri Agnew:agenda wiki page (with slides) https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Julf Helsingius:I am in a pretty noisy office, so I will probably not use the microphone. Terri Agnew:Thank you for this information Julf David Olive:Welcome Everyone Julie Hedlund:As this is a webinar we have no need for statements of interest. Julie Hedlund:That has been removed from the agenda. Stefania Milan:Hello everyone. Thanks for organizing this webminar James Bladel:Good so far! :) Amr Elsadr:My only comment is that this tool/table is incredibly helpful. Thanks. Julf Helsingius:Yes, this is really good for understanding the process. Thanks! James Bladel:Makes sense. Thank you. Julie Hedlund:@James: Also note that this is a suggested timeline. A more precise and likely compressed timeline will be developed in implementation. James Bladel:Got it. Amr Elsadr:I'm assuming that all of this is being communicated to the OEC. James Bladel:Agree, Wolf-Ulrich. We can highlight that in the motion and communicate it to the OEC Julie Hedlund:@Amr: Yes, we are in touch with the OEC and they were invited to attend this webinar also. Amr Elsadr:Thanks. David Olive:Thanks Jen and All Julf Helsingius:Thanks - appreciated! James Bladel:Thank you Jen & Wolf-Ulrich for lending us some of your time & expertise on this. Very helpful! Julie Hedlund:@Thanks Jen and all! Lawrence Olawale-Roberts:Thanks All Julie Hedlund:Happy holidays to all! Wolf-Ulrich Knoben:Thanks and bye Darcy Southwell:Thank you! James Bladel:Thanks all. Amr Elsadr:Thanks Jen..., for seeing this through over the past few years!! :) Amr Elsadr:Thanks all. Bye.

2 1

Updated Draft Minutes Meeting of the GNSO Council 1 December 2016 to review
by Nathalie Peregrine Dec. 8, 2016

Dec. 8, 2016

Dear Councillors, Please find attached the updated draft minutes of the GNSO Council meeting on the 1st December 2016 for your review. Edits by Wolf-Ulrich Knoben to item 7: removal of the mention of Jen Wolfe's apologies and correction of a typo. Thank you, Wolf-Ulrich, for your input. Kind regards, Nathalie From: <owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org>> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>> Date: Thursday, December 8, 2016 at 9:55 AM To: "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Draft Minutes Meeting of the GNSO Council 1 December 2016 to review Dear Councillors, Attached, please find the draft minutes of the GNSO Council meeting on the 1st December 2016 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 18 December 2016. Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Next Steps: IAG Report, and WHOIS Conflicts with local law
by James M. Bladel Dec. 8, 2016

Dec. 8, 2016

Councilors – Having now considered --and withdrawn-- two separate motions on this topic, it is clear that we need to regroup, reassess, and consider our path(s) forward. Per the discussion on our 30 SEP call, I would like to convene a group of interested Councilors to kick off discussions and present options. For context, please see the attached Overview document prepared by Staff. This summary is intended to provide backgrounds, and kick start ideas for resolution, but by no means is it meant to serve as an exhaustive list. I’m hopeful this group can work together to reconcile the diverse opinions on this issue, and come back to Council one or more motions that have sufficient support to pass. Thank you, J.

7 12

Mp3, AC recording and attendance GNSO Review implementation plan webinar is scheduled for Thursday, 08 December 2016 at 14:00 UTC
by Terri Agnew Dec. 8, 2016

Dec. 8, 2016

Dear all, Please find the attendance of the call attached to this email and the MP3 and Adobe Connect recording below for the GNSO Review implementation plan webinar held on Thursday, 08 December 2016 at 14:00 UTC. MP3: https://audio.icann.org/gnso/gnso-review-08dec16-en.mp3 Adobe Connect Recording: https://participate.icann.org/p9p5iut6zcq/<https://participate.icann.org/p9p5iut6zcq/?OWASP_CSRFTOKEN=cd9a97fa0329f7d6…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> Mailing list archives: http://mm.icann.org/pipermail/gnso-review-wg/ Wiki page: https://community.icann.org/x/ZhmsAw ** Please let me know if your name has been left off the list ** Thank you. Kind regards, Terri ------------------------------- Adobe Connect chat transcript for 08 December 2016 Terri Agnew:Welcome to the GNSO Review implementation plan webinar held on Thursday, 08 December 2016 at 14:00 UTC for 60 minutes. Terri Agnew:agenda wiki page (with slides) https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Julf Helsingius:I am in a pretty noisy office, so I will probably not use the microphone. Terri Agnew:Thank you for this information Julf David Olive:Welcome Everyone Julie Hedlund:As this is a webinar we have no need for statements of interest. Julie Hedlund:That has been removed from the agenda. Stefania Milan:Hello everyone. Thanks for organizing this webminar James Bladel:Good so far! :) Amr Elsadr:My only comment is that this tool/table is incredibly helpful. Thanks. Julf Helsingius:Yes, this is really good for understanding the process. Thanks! James Bladel:Makes sense. Thank you. Julie Hedlund:@James: Also note that this is a suggested timeline. A more precise and likely compressed timeline will be developed in implementation. James Bladel:Got it. Amr Elsadr:I'm assuming that all of this is being communicated to the OEC. James Bladel:Agree, Wolf-Ulrich. We can highlight that in the motion and communicate it to the OEC Julie Hedlund:@Amr: Yes, we are in touch with the OEC and they were invited to attend this webinar also. Amr Elsadr:Thanks. David Olive:Thanks Jen and All Julf Helsingius:Thanks - appreciated! James Bladel:Thank you Jen & Wolf-Ulrich for lending us some of your time & expertise on this. Very helpful! Julie Hedlund:@Thanks Jen and all! Lawrence Olawale-Roberts:Thanks All Julie Hedlund:Happy holidays to all! Wolf-Ulrich Knoben:Thanks and bye Darcy Southwell:Thank you! James Bladel:Thanks all. Amr Elsadr:Thanks Jen..., for seeing this through over the past few years!! :) Amr Elsadr:Thanks all. Bye.

1 0

Draft Minutes Meeting of the GNSO Council 1 December 2016 to review
by Nathalie Peregrine Dec. 8, 2016

Dec. 8, 2016

Dear Councillors, Attached, please find the draft minutes of the GNSO Council meeting on the 1st December 2016 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 18 December 2016. Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>

3 3

Draft Agenda GNSO Council Meeting 15 December 2016 at 12:00UTC
by Nathalie Peregrine Dec. 8, 2016

Dec. 8, 2016

Dear Councillors, Please find the Draft Agenda for the GNSO Council Meeting on 15 December 2016 at 12:00UTC. Please bear in mind that it is subject to change pending further review by the GNSO Council Chairs. The links in Agenda item 4 will be provided when available. DRAFT AGENDA FOR GNSO COUNCIL MEETING 15 December 2016 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/IZfDAw This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.2, 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: 12:00 UTC http://tinyurl.com/jmry4q4 04:00 Los Angeles; 07:00 Washington; 12:00 London; 15:00 Istanbul; 23:00 Hobart ___________________________________ Item 1. Administrative Matters (5 mins) 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 meeting of the GNSO Council Part I on 7 November 2016 and posted on 1 December 2016 Minutes of the meeting of the GNSO Council Part II on 7 November 2016 and posted on XXXXX 2016. Minutes of the meeting of the GNSO Council on 1 December 2016 and will be posted on 18 December 2016. Item 2. Opening Remarks / Review of Projects & Action List (5 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3. Consent Agenda (0 mins) Item 4. COUNCIL VOTE – GNSO Council Response to the Board on gTLD Policy Matters related to the GAC Communique from Hyderabad (20 minutes) Beginning in July 2015, the GNSO Council has reviewed each GAC Communiqué for issues relating to gTLD policy, with a view toward providing information to the ICANN Board and the broader community concerning past, present or future GNSO policy activities relating to GAC advice touching on these topics. In the GAC Communique from ICANN57 in Hyderabad, the GAC had provided specific advice on a number of issues, including protections in the domain name system for International Governmental Organization (IGO) names and acronyms as well as identifiers associated with the international Red Cross movement and its National Societies (https://www.icann.org/en/system/files/correspondence/gac-to-icann-08nov16-e…) A placeholder motion was proposed for the 1 December Council meeting, and deferred pending the completion of a draft response being prepared by a small group of Council volunteers. The draft response [INSERT LINK] to the GAC’s Communique from ICANN57 in Hyderabad was circulated to the GNSO Council on [INSERT DATE]. Here the Council will consider whether or not to approve the response to the Board. 4.1 – Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+1+December+…> (Paul McGrady) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE – Adoption of Proposed Implementation Plan for Recommendations relating to the 2014 GNSO Review (10 minutes) Along with the ICANN Board’s adoption in June 2016 of certain recommendations from the 2014 GNSO Review, the GNSO Council requested that ICANN policy staff prepare a discussion paper outlining the possible options for implementation, taking into account past implementation of previous GNSO Reviews as well as existing mechanisms. At ICANN56 in Helsinki in June 2016, the GNSO Council discussed the options outlined in the staff discussion paper (http://gnso.icann.org/en/drafts/review-implementation-recommendations-discu…) On 21 July 2016 the GNSO Council chartered<https://gnso.icann.org/en/drafts/gnso-review-charter-21jul16-en.pdf> the GNSO Review Working Group and directed it to submit a proposed implementation plan to the Council for approval by the ICANN57 meeting. The GNSO Review Working Group circulated its proposed implementation plan to the Council on 21 November. https://gnso.icann.org/en/drafts/review-implementation-recommendations-plan…. A motion to adopt the proposed plan was submitted for the Council’s 1 December meeting but was withdrawn to allow the Council additional time to consider the details. A webinar was also scheduled for 8 December 2016 to go through the plan. Here the Council will consider whether or not to approve the plan for transmission to the ICANN Board. 5.1 – Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+1+December+…> (Wolf-Ulrich Knoben) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – Appointment of GNSO Co-Chair and Members to Cross Community Working Group on New gTLD Auction Proceeds (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, and the DT subsequently submitted a proposed Charter<https://community.icann.org/x/mRuOAw> – a document that was the result of extensive community input to the DT - for a new cross-community working group (CCWG) to all SO/ACs for consideration. At its meeting at ICANN57 in Hyderabad, the GNSO Council approved<https://gnso.icann.org/en/council/resolutions#20161107-4> the Charter and a set of criteria for GNSO-appointed members to the new CCWG. Following the approval of the Charter by the ALAC, SSAC and ccNSO, a Call for Volunteers was issued on [INSERT DATE]. For the GNSO, one nomination was received for the position of CCWG co-chair, and nominations for members were received from the Registries Stakeholder Group and the Commercial Stakeholders Group [UPDATE AS NEEDED]. Here the Council will discuss and vote on the appointment of the GNSO co-chair and nominated members to the new CCWG. 6.1 – Presentation of the motion [INSERT LINK] (James Bladel) 6.2 – Council discussion 6.3 – Council vote (voting threshold: simple majority) Item 7. COUNCIL DISCUSSION – GNSO Council Response to Proposed Scope of the Forthcoming Registration Directory Services (RDS) Review (formerly the Whois Review) (10 minutes) On 4 November 2016 ICANN staff circulated a document to all Supporting Organizations and Advisory Committee (SO/AC) leaders that described a proposed limited scope for the forthcoming RDS (formerly Whois) Review (https://gnso.icann.org/mailing-lists/archives/council/msg19381.html) This topic was also discussed as part of a High Interest Topics Session at ICANN57 in Hyderabad, and certain concerns with the proposal were noted by the GNSO Council during its Wrap Up Session. At its meeting on 1 December, the Council discussed the likely nature of the feedback it may provide to ICANN staff, and Susan Kawaguchi and Keith Drazek volunteered to draft a proposed response. The draft response was circulated to the Council on [INSERT DATE]. Here the Council will discuss the draft response, and decide what to include in the final document to be sent. 7.1 – Summary and update (Susan Kawaguchi / Keith Drazek) 7.2 – Council discussion 7.3 – Next steps Item 8. COUNCIL DISCUSSION – Proposal for a Uniform Selection of GNSO Representatives to Future Review Teams, and Selection of GNSO Representatives to the Second Security, Stability & Resiliency Review Team (20 minutes) At ICANN57 in Hyderabad, SO/AC leaders (including the chairs of several GNSO Stakeholder Groups and Constituencies) met with ICANN staff to discuss the selection process for appointments to the forthcoming Security, Stability & Resiliency (SSR) Review Team (SSR-RT-2). It was agreed that selection of the final slate of Review Team members should be a collective effort by all SO/AC leaders, and that each SO/AC would develop its own internal guidelines for selecting its representatives for consideration (up to a maximum of 3 per SO/AC). The group also discussed how independent experts should be appointed to the Review Team. The current slate of applicants can be viewed at https://community.icann.org/x/xRqsAw. At the Council’s 1 December meeting, Susan Kawaguchi and Ed Morris confirmed that they were working on a proposed set of criteria and a uniform process for selection of GNSO representatives to all future Review Teams. The draft document was circulated to the Council on [INSERT DATE]. Here the Council will discuss the proposal, and confirm its deadline for selecting the GNSO’s representatives on the SSR-RT-2 using the new, agreed criteria and process. 8.1 – Status summary (Susan Kawaguchi / Ed Morris) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION - ICANN Board Letter regarding policy implications of the Final Report of the Internationalized Registration Data (IRD) Expert Working Group (10 minutes) On 11 May 2016, ICANN Board Chair Dr. Steve Crocker sent a letter to the GNSO Council following up on the Board’s 10 March 2016 Resolution (see https://gnso.icann.org/en/correspondence/crocker-to-bladel-11may16-en.pdf) The Board’s request was for the GNSO Council to “review the broader policy implications of the IRD Final Report<http://whois.icann.org/sites/default/files/files/ird-expert-wg-final-23sep1…> as they relate to other GNSO policy development work on WHOIS issues, and, at a minimum, forward the IRD Final Report as an input to the GNSO PDP on the Next Generation Registration Directory Services to Replace WHOIS that is currently underway.” The GNSO Council sought input from the co-chairs and members of the recently completed GNSO Policy Development Process on the Translation and Transliteration of gTLD Contact Data, requesting feedback on several specific points, viz.: (1) how certain recommendations in the IRD Final Report were considered, if at all, in the Final Report<https://gnso.icann.org/en/issues/gtlds/translation-transliteration-contact-…> of the T&T PDP Working Group; (2) how those recommendations could potentially conflict with the T&T PDP Working Group’s recommendations that have been adopted by the GNSO Council and the ICANN Board; and (3) What steps are recommended to the GNSO Council in considering the policy implications of the IRD Final Report. Following input received, the GNSO Council Chairs developed a draft response that was circulated to the Council on 5 December (see https://gnso.icann.org/mailing-lists/archives/council/msg19547.html) Here the Council will discuss the proposed response and agree on next steps, including whether or not to send the response to the Board. 9.1 – Status update (James Bladel) 9.2 – Council discussion 9.3 – Next steps Item 10: COUNCIL DISCUSSION – Planning for ICANN58 (15 minutes) At its Wrap Up Session at ICANN57 in Hyderabad, the Council discussed the need to start planning early for ICANN58. It also agreed that confirming certain sessions (including joint meetings with other SO/ACs and the ICANN Board) as fixed in the overall meeting schedule would be helpful for scheduling purposes, as would facilitating better coordination between and with individual Stakeholder Groups and Constituencies, and ensuring that sufficient time is given over to policy development work. To assist in the Council’s deliberations, staff compiled all GNSO Council input received on the ICANN58 Council Planning Survey: https://gnso.icann.org/en/drafts/icann58-council-planning-survey-30nov16-en…. At the Council’s 1 December meeting, the Council Chairs provided an update on the latest SO/AC leadership call where planning for ICANN58 was discussed. The Council agreed that it would be helpful to create a draft GNSO Block Schedule, to be shared with the other SO/AC leaders ahead of the next SO/AC leadership call. The Council also noted that, with several important Policy Development Processes (PDPs) ongoing, it will be important to ensure that ICANN58 scheduling take into account those PDP Working Groups that will need face to face meeting time. A draft GNSO Block Schedule was prepared by staff and circulated on [INSERT DATE]. Here the Council will discuss the draft schedule and agree on next steps. 10.1 – Status summary (GNSO Council leadership) 10.2 – Council discussion 10.3 – Next steps Item 11: ANY OTHER BUSINESS (10 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_about_…>): 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_council_…>) 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) 12:00 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 +0DST 04:00 San José, Costa Rica UTC--6 +0DST 06:00 Iowa City, USA (CST) UTC--6 +0DST 06:00 New York/Washington DC, USA (EST) UTC-5 +0DST 07:00 Buenos Aires, Argentina (ART) UTC-3+0DST 09:00 Rio de Janiero, Brazil (BRST) UTC-2 +0DST 10:00 London, United Kingdom (GMT) UTC+0DST 12:00 Bonn, Germany (CET) UTC+1+0DST 13:00 Cairo, Egypt, (EET) UTC+2 +0DST 14:00 Istanbul, Turkey (TRT) UTC+3+0DST 15:00 Singapore (SGT) UTC +8 +0DST 20:00 Tokyo, Japan (JST) UTC+9+0DST 21:00 Sydney/Hobart, Australia (AEDT) UTC+11+0DST 23:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2017, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/jmry4q4 Please let me know if you have any questions. Thank you very much Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> http://gnso.icann.org[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_&d=DgMFA…> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses[learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

Re: [council] GNSO Council meetings time rotation tool
by James M. Bladel Dec. 7, 2016

Dec. 7, 2016

Thank you, Nathalie. Colleagues, as you can see from this tool, the “span” of time zones, along with the distribution of Councilors within those time zones, hasn’t changed much since last year. For example, we exchanged Mason for Darcy (Yay Portland!), Volker for Michele, David for Rafik, etc. It was also this time last year when we shifted the rotation from 3 meeting timeslots, down to 2, after having determined that more time slots created significant complexities with little benefit. So if there aren’t any objections, I propose that we keep the current 2 time slots, and adopt the meeting calendar that was previously circulated. Thanks – J. From: <owner-council(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Monday, December 5, 2016 at 17:32 To: GNSO Council List <council(a)gnso.icann.org> Cc: Marika Konings <marika.konings(a)icann.org>, Mary Wong <mary.wong(a)icann.org>, Julie Hedlund <julie.hedlund(a)icann.org>, "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org> Subject: [council] GNSO Council meetings time rotation tool Dear all, From the Council meeting on the 1st December 2016, an action item for staff was to use a time rotation tool to visualise how the current time rotation of Council meetings fits in with Council member locations. The following Google doc covers the 24hr clock with all Council member timezones (row 3) and how many members per said timezone (row 4). Our current times of 12:00 UTC and 21:00 UTC are highlighted in column R. https://docs.google.com/spreadsheets/d/1vY7O_8jOzHc_UZ3AyKryUPbAuGgeNlsFslA… Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>

4 3

REMINDER: Meeting Invite/ GNSO Review implementation plan webinar 08 December 2016 at 14:00 UTC
by Terri Agnew Dec. 7, 2016

Dec. 7, 2016

Dear All, The GNSO Review implementation plan webinar is scheduled for Thursday, 08 December 2016 at 14:00 UTC for 60 minutes. See the plan at: https://gnso.icann.org/en/drafts/review-implementation-recommendations-plan… and the motion at: https://community.icann.org/display/gnsocouncilmeetings/Motions+1+December+… Although the focus of this webinar is to assist GNSO Council members in their deliberations on the implementation plan and motion, if you know others who wish to join, please feel free to forward the invitation. 06:00 PST, 09:00 EST, 14:00 London, 15:00 CEST, 01:00 Sydney (Friday) For other places: http://tinyurl.com/jynesrn Adobe Connect WITH AUDIO enabled: https://participate.icann.org/gnso-review The dial-in details are below - please let us know if you require a dial-out. Please confirm your dial-out requests to GNSO Secretariats: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> _________________________________________________________________________ Participant passcode: GNSO WEBINAR Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL SAO PAULO: 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 EGYPT 0800000-9029 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDIA BANGALORE: 91-80-48030674 INDIA MUMBAI: 91-22-49412807 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7878-2631 0066-33-132439 JAPAN TOKYO: 81-3-6868-2631 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 351-2-10054705 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 VIETNAM 120-11751 Thank you. Kind regards, Terri

1 0

Re: [council] GNSO Council meetings time rotation tool
by James M. Bladel Dec. 7, 2016

Dec. 7, 2016

Thanks Stefania. Let’s give folks another 24 hours to comment or raise concerns, then we’ll fix these dates and times, and Nathalie can publish the schedule. Appreciate everyone’s help in finalizing this calendar! J. From: "Milan, Stefania" <Stefania.Milan(a)EUI.eu> Date: Wednesday, December 7, 2016 at 7:50 To: "James M. Bladel" <jbladel(a)godaddy.com> Cc: Nathalie Peregrine <nathalie.peregrine(a)icann.org>, GNSO Council List <council(a)gnso.icann.org>, Marika Konings <marika.konings(a)icann.org>, Mary Wong <mary.wong(a)icann.org>, Julie Hedlund <julie.hedlund(a)icann.org>, "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org> Subject: Re: [council] GNSO Council meetings time rotation tool Seems very reasonable, James. Thanks, Stefania Sent from my iPhone On Dec 6, 2016, at 15:06, James M. Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> wrote: Thank you, Nathalie. Colleagues, as you can see from this tool, the “span” of time zones, along with the distribution of Councilors within those time zones, hasn’t changed much since last year. For example, we exchanged Mason for Darcy (Yay Portland!), Volker for Michele, David for Rafik, etc. It was also this time last year when we shifted the rotation from 3 meeting timeslots, down to 2, after having determined that more time slots created significant complexities with little benefit. So if there aren’t any objections, I propose that we keep the current 2 time slots, and adopt the meeting calendar that was previously circulated. Thanks – J. From: <owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org>> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>> Date: Monday, December 5, 2016 at 17:32 To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>>, Julie Hedlund <julie.hedlund(a)icann.org<mailto:julie.hedlund@icann.org>>, "'gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>'" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: [council] GNSO Council meetings time rotation tool Dear all, From the Council meeting on the 1st December 2016, an action item for staff was to use a time rotation tool to visualise how the current time rotation of Council meetings fits in with Council member locations. The following Google doc covers the 24hr clock with all Council member timezones (row 3) and how many members per said timezone (row 4). Our current times of 12:00 UTC and 21:00 UTC are highlighted in column R. https://docs.google.com/spreadsheets/d/1vY7O_8jOzHc_UZ3AyKryUPbAuGgeNlsFslA… Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…> The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination, distribution, forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in error, please contact the sender and delete the material from any computer.

1 0

Updated Action Items: GNSO Council meeting on 1 December 2016
by Nathalie Peregrine Dec. 6, 2016

Dec. 6, 2016

Dear all, Please find updated last bullet point of the Action Items which is now “ Update GNSO Calendar for 2017 according to agreed schedule.” instead of the previous “Council to confirm proposed meeting dates and rotating times for GNSO Council meetings during 2017” Updated Action items are also attached to this email. Kind regards, Nathalie From: "owner-gnso-secs(a)icann.org<mailto:owner-gnso-secs@icann.org>" <owner-gnso-secs(a)icann.org<mailto:owner-gnso-secs@icann.org>> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>> Date: Tuesday, December 6, 2016 at 12:00 AM To: "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: [gnso-secs] Action Items: GNSO Council meeting on 1 December 2016 Dear Councillors, Please find the action items, below and as attachment, arising from the GNSO Council meeting on 1 December 2016. Please take note of the action items coming out of the Council meeting last week and the proposed timing for delivering on these actions. The next GNSO Council meeting is on the 15 December 2016. ACTION ITEMS FROM GNSO COUNCIL MEETING 1 December 2016 NOTE: Motion and document deadline for the next GNSO Council meeting – 5 December 2016 Item 4. COUNCIL VOTE – Adoption of Consensus Recommendations from the GNSO Bylaws Drafting Team Voting result: · Motion (as amended – see https://gnso.icann.org/mailing-lists/archives/council/msg19515.html) PASSED unanimously Action items: · Policy staff to draft proposed language for modifications/additions to the GNSO Operating Procedures and, if applicable, those parts of the ICANN Bylaws pertaining to the GNSO (IN PROCESS) · Drafting Team members to be available for consultation by staff as needed · ICANN Legal to evaluate whether the proposed modifications are consistent with the post-transition Bylaws and report to the GNSO Council. · Staff to post the DT Final Report, including the minority report, and all proposed modifications or new procedures for public comment for no less than 40 days (NOTE: following close of public comment forum, Council to review all public comments submitted and decide on next steps; GNSO Council intends to adopt any new/amended procedures by Supermajority vote) · Staff to notify DT of voting result (DONE) Item 5. COUNCIL VOTE – GNSO Council Response to the Board on gTLD Policy Matters related to the GAC Communique from Hyderabad Voting result: · None (Motion DEFERRED to 15 December Council meeting) Action items: · Draft response to be circulated by the group of volunteer Councilors working on the draft in advance of the next Council meeting Item 6: COUNCIL VOTE – Approval of Letter to the ICANN Board concerning Implementation Issues with Part C of the Inter-Registrar Transfer Policy Voting result: · None (Motion WITHDRAWN following Council agreement to send amended (second version of) draft letter circulated by Darcy Southwell to the Board) Action item: · Letter to be sent to ICANN Board (DONE – letter now published on ICANN Correspondence Page) Item 7. COUNCIL VOTE – Adoption of Proposed Implementation Plan for Recommendations relating to the 2014 GNSO Review Voting result: · None (Motion DEFERRED to 15 December Council meeting) Action items: · Webinar to provide overview of proposed plan to be scheduled (DONE – scheduled for Thursday 8 December at 1400 UTC) Item 8. COUNCIL DISCUSSION – GNSO Council Response to Proposed Scope of the Forthcoming Registration Directory Services (RDS) Review (formerly the Whois Review) Action items: · Susan Kawaguchi and Keith Drazek to work on draft response, incorporating points raised during Council discussion (including suggestions to include strategy for coordinating all ongoing Whois-related efforts, consult past Review Team members, and expand membership beyond past Review Team members) and circulate draft to Council list by COB on Monday 5 December · Council leadership and staff to notify responsible ICANN staff that a GNSO Council response should be forthcoming by Monday 12 December Item 9. COUNCIL DISCUSSION – GNSO Council Response to Questions from the CCWG-Accountability Co-Chairs concerning Work Stream 2 Action items: · Councilors to review draft response that was circulated and send comments to Council list; aim to finalize and send the response to the CCWG-Accountability Co-Chairs before the next Council meeting · Staff to contact SG/C chairs to ensure they are clear on the request, and suggest that SG/C responses be sent directly to the CCWG-Accountability Co-Chairs and the relevant rapporteurs Item 10: COUNCIL DISCUSSION – Selection of GNSO Representatives to the Security, Stability & Resiliency Review Team Action items: · Susan Kawaguchi and Ed Morris to circulate draft proposed uniform selection criteria and process to Council list by Friday 9 December · Council to consider using suggested criteria/process to select GNSO representatives to the SSR-RT2 early in the new year · GNSO leadership team to communicate this proposed approach to staff supporting SSR-RT2 as well as other SO/ACs Item 11: COUNCIL DISCUSSION – Planning for ICANN58 Action items: · Council to prepare an initial standard GNSO calendar for Meetings A, B and C (showing what the expected, blocked-out GNSO sessions are and allowing time for PDP face to face meetings) · Council leadership to take that standardized GNSO calendar into the next SO/AC planning meeting Item 12: ANY OTHER BUSINESS Action items: · Council leadership to review rotation of Council meetings based on current geographic location of Council members (DONE – the current two time slots represent the best options to share the pain across the different time zones) · Update GNSO Calendar for 2017 according to agreed schedule. Please let me know if I missed anything or if you have questions. Thank you. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

GNSO Council meetings time rotation tool
by Nathalie Peregrine Dec. 5, 2016

Dec. 5, 2016

Dear all, >From the Council meeting on the 1st December 2016, an action item for staff was to use a time rotation tool to visualise how the current time rotation of Council meetings fits in with Council member locations. The following Google doc covers the 24hr clock with all Council member timezones (row 3) and how many members per said timezone (row 4). Our current times of 12:00 UTC and 21:00 UTC are highlighted in column R. https://docs.google.com/spreadsheets/d/1vY7O_8jOzHc_UZ3AyKryUPbAuGgeNlsFslA… Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<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

Action Items: GNSO Council meeting on 1 December 2016
by Nathalie Peregrine Dec. 5, 2016

Dec. 5, 2016

Dear Councillors, Please find the action items, below and as attachment, arising from the GNSO Council meeting on 1 December 2016. Please take note of the action items coming out of the Council meeting last week and the proposed timing for delivering on these actions. The next GNSO Council meeting is on the 15 December 2016. ACTION ITEMS FROM GNSO COUNCIL MEETING 1 December 2016 NOTE: Motion and document deadline for the next GNSO Council meeting – 5 December 2016 Item 4. COUNCIL VOTE – Adoption of Consensus Recommendations from the GNSO Bylaws Drafting Team Voting result: · Motion (as amended – see https://gnso.icann.org/mailing-lists/archives/council/msg19515.html) PASSED unanimously Action items: · Policy staff to draft proposed language for modifications/additions to the GNSO Operating Procedures and, if applicable, those parts of the ICANN Bylaws pertaining to the GNSO (IN PROCESS) · Drafting Team members to be available for consultation by staff as needed · ICANN Legal to evaluate whether the proposed modifications are consistent with the post-transition Bylaws and report to the GNSO Council. · Staff to post the DT Final Report, including the minority report, and all proposed modifications or new procedures for public comment for no less than 40 days (NOTE: following close of public comment forum, Council to review all public comments submitted and decide on next steps; GNSO Council intends to adopt any new/amended procedures by Supermajority vote) · Staff to notify DT of voting result (DONE) Item 5. COUNCIL VOTE – GNSO Council Response to the Board on gTLD Policy Matters related to the GAC Communique from Hyderabad Voting result: · None (Motion DEFERRED to 15 December Council meeting) Action items: · Draft response to be circulated by the group of volunteer Councilors working on the draft in advance of the next Council meeting Item 6: COUNCIL VOTE – Approval of Letter to the ICANN Board concerning Implementation Issues with Part C of the Inter-Registrar Transfer Policy Voting result: · None (Motion WITHDRAWN following Council agreement to send amended (second version of) draft letter circulated by Darcy Southwell to the Board) Action item: · Letter to be sent to ICANN Board (DONE – letter now published on ICANN Correspondence Page) Item 7. COUNCIL VOTE – Adoption of Proposed Implementation Plan for Recommendations relating to the 2014 GNSO Review Voting result: · None (Motion DEFERRED to 15 December Council meeting) Action items: · Webinar to provide overview of proposed plan to be scheduled (DONE – scheduled for Thursday 8 December at 1400 UTC) Item 8. COUNCIL DISCUSSION – GNSO Council Response to Proposed Scope of the Forthcoming Registration Directory Services (RDS) Review (formerly the Whois Review) Action items: · Susan Kawaguchi and Keith Drazek to work on draft response, incorporating points raised during Council discussion (including suggestions to include strategy for coordinating all ongoing Whois-related efforts, consult past Review Team members, and expand membership beyond past Review Team members) and circulate draft to Council list by COB on Monday 5 December · Council leadership and staff to notify responsible ICANN staff that a GNSO Council response should be forthcoming by Monday 12 December Item 9. COUNCIL DISCUSSION – GNSO Council Response to Questions from the CCWG-Accountability Co-Chairs concerning Work Stream 2 Action items: · Councilors to review draft response that was circulated and send comments to Council list; aim to finalize and send the response to the CCWG-Accountability Co-Chairs before the next Council meeting · Staff to contact SG/C chairs to ensure they are clear on the request, and suggest that SG/C responses be sent directly to the CCWG-Accountability Co-Chairs and the relevant rapporteurs Item 10: COUNCIL DISCUSSION – Selection of GNSO Representatives to the Security, Stability & Resiliency Review Team Action items: · Susan Kawaguchi and Ed Morris to circulate draft proposed uniform selection criteria and process to Council list by Friday 9 December · Council to consider using suggested criteria/process to select GNSO representatives to the SSR-RT2 early in the new year · GNSO leadership team to communicate this proposed approach to staff supporting SSR-RT2 as well as other SO/ACs Item 11: COUNCIL DISCUSSION – Planning for ICANN58 Action items: · Council to prepare an initial standard GNSO calendar for Meetings A, B and C (showing what the expected, blocked-out GNSO sessions are and allowing time for PDP face to face meetings) · Council leadership to take that standardized GNSO calendar into the next SO/AC planning meeting Item 12: ANY OTHER BUSINESS Action items: · Council leadership to review rotation of Council meetings based on current geographic location of Council members (DONE – the current two time slots represent the best options to share the pain across the different time zones) · Council to confirm proposed meeting dates and rotating times for GNSO Council meetings during 2017 Please let me know if I missed anything or if you have questions. Thank you. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<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: Confirmation of GNSO Appointed Members and Co-Chair to CCWG-Auction Proceeds
by James M. Bladel Dec. 5, 2016

Dec. 5, 2016

Councilors – Attached, and copied below, please find a motion to approve the GNSO appointed Members and Co-Chairs to CCWG Auction Proceeds. Note that our co-chair candidate (Jonathan Robinson) and the list of members is listed in brackets, as we are still waiting to finalize these. Please ensure that your SG-designated Member is sent to the list by EOD today. Thank you, J. Motion – Confirmation of GNSO Appointed Co-Chair and Members to the CCWG-Auction Proceeds Whereas, 1. The GNSO Council adopted the charter for the CCWG new gTLD Auction Proceeds during its meeting on 7 November 2016; 2. As a Chartering Organization, the GNSO can appoint a minimum of 2 and a maximum of 5 Members to the CCWG. Members are expected to serve as a liaison between their respective Chartering Organization and the CCWG. Members must, if and when necessary, ensure that the Chartering Organizations are kept up to date on the progress and deliberations of the CCWG as well as sharing any input from the Chartering Organization with the CCWG. 3. The Charter specifies that a chair may be appointed by each Chartering Organizations. Chartering Organizations that do decide to appoint a chair should make reasonable efforts that the proposed chair / co-chair has the necessary experience to manage an effort of this nature by, for example, having actively participated as a member in at least one CCWG or ICANN Working Group throughout its lifecycle in order to have relevant or related experience of the different tasks that come with chairing a CCWG. Prior leadership experience (chair / co-chair / vice-chair) is desirable. 4. The GNSO Council notes that that best efforts have been to ensure that GNSO appointed members: o 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; o Commit to actively participate in the activities of the CCWG on an on-going and long-term basis; o Solicit and communicate (where appropriate) the views and concerns of individuals in the organization that appoints them; o Commit to abide to the charter when participating in the CCWG; o Understand the needs of the Internet communities that ICANN serves (standards, domains and numbers); o 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. Resolved 1. The GNSO Council appoints [Jonathan Robinson] as the GNSO Appointed Co-Chair and Member to the CCWG – Auction Proceeds. 2. The GNSO Council confirms [include names] as GNSO appointed members to the CCWG-Auction Proceeds. 3. The GNSO Council requests the GNSO Appointed Co-Chair and the GNSO appointed members to ensure that the GNSO community is kept up to date on the progress of the deliberations as well as making sure that input from the GNSO community is sought on a regular basis. 4. The GNSO Council encourages other interested in this topic to join this effort as a participant or observer.

1 0

In less than one hour: Document and Motion deadline Monday, 5 December 2016 at 23:59 UTC for the GNSO Council Meeting 15 December 2016 at 12:00 UTC
by Nathalie Peregrine Dec. 5, 2016

Dec. 5, 2016

Dear Councillors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 5 December 2016 at 23:59 UTC) of the GNSO Council Meeting on 15 December 2016 at 12:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+15+December…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Council Resolution Thursday 1 December 2016
by Nathalie Peregrine Dec. 2, 2016

Dec. 2, 2016

Dear Councillors, Please find below the resolution the Council adopted at its meeting on Thursday 1 December 2016. Acceptance of the Report from the GNSO Bylaws Implementation Drafting Team and next steps WHEREAS: 1. On 30 June 2016 the GNSO Council approved the creation of a Drafting Team (DT) that was to work with ICANN staff to "fully identify all the new or additional rights and responsibilities that the GNSO has under the revised Bylaws, including but not limited to participation of the GNSO within the Empowered Community, and to develop new or modified structures and procedures (as necessary) to fully implement these new or additional rights and responsibilities"; 2. In creating the DT, the GNSO Council requested that the DT provide the GNSO Council with an implementation plan "which will have the consensus of the Drafting Team, including any recommendations for needed further changes to ICANN Bylaws and/or GNSO Operating Procedures to enable effective GNSO participation in ICANN activities under the revised ICANN Bylaws, not later than 30 September 2016"; 3. During the course of the DT's work, differing views were expressed on the role of the GNSO Council in the Empowered Community, leading to the production of a Final Report, which included a minority report on the role of the GNSO Council; and 4. The DT submitted its Final Report to the GNSO Council on 12 October 2016 (https://gnso.icann.org/en/drafts/bylaws-drafting-team-final-report-12oct16-…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>). The GNSO Council has reviewed the DT's report. RESOLVED: 1. The GNSO Council accepts the recommendations in the DT's Final Report as submitted. 2. The GNSO Council directs ICANN Policy Staff to draft proposed language for any necessary modifications or additions to the GNSO Operating Procedures and, if applicable, those parts of the ICANN Bylaws pertaining to the GNSO. The GNSO Council requests that ICANN Legal evaluate whether the proposed modifications are consistent with the post-transition Bylaws and report their findings to the GNSO Council. 3. The GNSO Council requests that members of the DT make themselves available for consultation by ICANN Policy Staff as needed. 4. The GNSO Council directs ICANN Policy Staff to post the DT Final Report, including the minority report, and all proposed modifications or new procedures for public comment for no less than 40 days. The GNSO Council expects that any comments received will be given meaningful consideration. 5. As resolved previously, the GNSO Council intends to subject the adoption of the proposed modifications to existing procedures and/or ICANN Bylaws to a GNSO Supermajority vote. 6. The GNSO Council thanks the DT for its collaborative effort, especially in view the limited time frame available Voting results<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> Please let me know if you have any questions. Thank you very much. Kind regards, Nathalie

1 0

Re: [council] Letter from the GNSO Council to ICANN Board re ICANN Transfer Policy posted on website
by James M. Bladel Dec. 2, 2016

Dec. 2, 2016

Thank you, Nathalie. Thanks – J. From: <owner-council(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Friday, December 2, 2016 at 8:24 To: GNSO Council List <council(a)gnso.icann.org> Cc: "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org> Subject: [council] Letter from the GNSO Council to ICANN Board re ICANN Transfer Policy posted on website Dear all, The letter drafted from the GNSO Council to the Chairman of the ICANN Board regarding ICANN’s Transfer Policy, specifically Part C, has been sent to the ICANN Board and posted on the GNSO Website on the Correspondance<https://gnso.icann.org/en/council/correspondence> page. It is available for viewing here: https://gnso.icann.org/en/correspondence/bladel-to-crocker-01dec16-en.pdf Kind regards, Nathalie

1 0

Letter from the GNSO Council to ICANN Board re ICANN Transfer Policy posted on website
by Nathalie Peregrine Dec. 2, 2016

Dec. 2, 2016

Dear all, The letter drafted from the GNSO Council to the Chairman of the ICANN Board regarding ICANN's Transfer Policy, specifically Part C, has been sent to the ICANN Board and posted on the GNSO Website on the Correspondance<https://gnso.icann.org/en/council/correspondence> page. It is available for viewing here: https://gnso.icann.org/en/correspondence/bladel-to-crocker-01dec16-en.pdf Kind regards, Nathalie

1 0

Reminder: Document and Motion deadline Monday, 5 December 2016 at 23:59 UTC for the GNSO Council Meeting 15 December 2016 at 12:00 UTC
by Nathalie Peregrine Dec. 2, 2016

Dec. 2, 2016

Dear Councillors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 5 December 2016 at 23:59 UTC) of the GNSO Council Meeting on 15 December 2016 at 12:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+15+December… Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<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

Meeting Invite/ GNSO Review implementation plan webinar 08 December 2016 at 14:00 UTC
by Terri Agnew Dec. 2, 2016

Dec. 2, 2016

Dear All, The GNSO Review implementation plan webinar is scheduled for Thursday, 08 December 2016 at 14:00 UTC for 60 minutes. See the plan at: https://gnso.icann.org/en/drafts/review-implementation-recommendations-plan… and the motion at: https://community.icann.org/display/gnsocouncilmeetings/Motions+1+December+… Although the focus of this webinar is to assist GNSO Council members in their deliberations on the implementation plan and motion, if you know others who wish to join, please feel free to forward the invitation. 06:00 PST, 09:00 EST, 14:00 London, 15:00 CEST, 01:00 Sydney (Friday) For other places: http://tinyurl.com/jynesrn Adobe Connect WITH AUDIO enabled: https://participate.icann.org/gnso-review The dial-in details are below - please let us know if you require a dial-out. Please confirm your dial-out requests to GNSO Secretariats: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> _________________________________________________________________________ Participant passcode: GNSO WEBINAR Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL SAO PAULO: 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 EGYPT 0800000-9029 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDIA BANGALORE: 91-80-48030674 INDIA MUMBAI: 91-22-49412807 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7878-2631 0066-33-132439 JAPAN TOKYO: 81-3-6868-2631 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 351-2-10054705 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 VIETNAM 120-11751 Thank you. Kind regards, Terri

1 0

MP3 and AC Chat transcript/ GNSO Council Teleconference 01 December 2016
by Terri Agnew Dec. 2, 2016

Dec. 2, 2016

Dear All, Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 01 December 2016 at: http://audio.icann.org/gnso/gnso-council-01dec16-en.mp3 as well as the Adobe chat transcript at : https://gnso.icann.org/en/meetings/transcript-council-01dec16-en.pdf all on page https://gnso.icann.org/en/group-activities/calendar#dec Thank you. Happy listening and reading! With kind regards, Terri Agnew --- Terri Agnew Secretariat Services Coordinator, GNSO & At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann

1 0

Webinar Invite: GNSO Review Implementation Plan 08 Dec 1400 UTC
by Julie Hedlund Dec. 1, 2016

Dec. 1, 2016

Dear GNSO Councilors, Per the request from Councilors during today’s GNSO Council meeting to have a webinar on the GNSO Review implementation plan, a webinar will be held on 08 December at 1400 UTC for 60 minutes. See the plan at: https://gnso.icann.org/en/drafts/review-implementation-recommendations-plan… and the motion at: https://community.icann.org/display/gnsocouncilmeetings/Motions+1+December+…. Although the focus of this webinar is to assist GNSO Council members in their deliberations on the implementation plan and motion, if you know others who wish to join, please feel free to forward the invitation. If you are interested in participating, please confirm your attendance at gnso-secs(a)icann.org. Note that the webinar will be recorded and transcribed. Best regards, Julie Julie Hedlund Policy Director, Internet Corporation for Assigned Names and Numbers (ICANN) Email: Julie.hedlund(a)icann.org Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages.

1 0

RDS Review -- Bylaws Language
by Drazek, Keith Dec. 1, 2016

Dec. 1, 2016

All, for our discussion on the RDS Review Team scope, here's the relevant Bylaws language. Best, Keith (e) Registration Directory Service Review (i) Subject to applicable laws, ICANN shall use commercially reasonable efforts to enforce its policies relating to registration directory services and shall work with Supporting Organizations and Advisory Committees to explore structural changes to improve accuracy and access to generic top-level domain registration data, as well as consider safeguards for protecting such data. (ii) The Board shall cause a periodic review to assess the effectiveness of the then current gTLD registry directory service and whether its implementation meets the legitimate needs of law enforcement, promoting consumer trust and safeguarding registrant data ("Directory Service Review"). (iii) The review team for the Directory Service Review ("Directory Service Review Team") will consider the Organisation for Economic Co-operation and Development ("OECD") Guidelines on the Protection of Privacy and Transborder Flows of Personal Data as defined by the OECD in 1980 and amended in 2013 and as may be amended from time to time. (iv) The Directory Service Review Team shall assess the extent to which prior Directory Service Review recommendations have been implemented and the extent to which implementation of such recommendations has resulted in the intended effect. (v) The Directory Service Review shall be conducted no less frequently than every five years, measured from the date the previous Directory Service Review Team was convened, except that the first Directory Service Review to be conducted after 1 October 2016 shall be deemed to be timely if the applicable Directory Service Review Team is convened on or before 31 October 2016.

1 0

Re: [EXTERNAL] RE: Consolidated input on ICANN58 planning
by Emily Barabas Dec. 1, 2016

Dec. 1, 2016

I have updated the summary document (attached) to include comments from the BC. Kind regards, Emily From: Phil Corwin <psc(a)vlaw-dc.com> Date: Wednesday 30 November 2016 at 18:36 To: Emily Barabas <emily.barabas(a)icann.org>, GNSO Council List <council(a)gnso.icann.org> Subject: [EXTERNAL] RE: Consolidated input on ICANN58 planning Weighing in for the BC: 1. Prefer single Constituency Day 2. One HIT that the community has broad agreement on, and no more than 3 maximum for entire meeting. 3. Staff should create a process for requests for HIT’s that makes it fair and equitable for all who have requested topics and that looks toward achieving SO/AC consensus; and ICANN staff should moderate any HIT and should select panelists to ensure opportunity for each SOAC to be represented. 4. Conflicts will be substantially minimized via early review of draft schedule and limiting HIT sessions to no more than 1-3. We did not discuss whether the A meeting should look more like the B or C. Hope that is useful. 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 Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Emily Barabas Sent: Wednesday, November 30, 2016 3:54 AM To: GNSO Council List Subject: [council] Consolidated input on ICANN58 planning Dear Councilors, Item 11 on the agenda of the December 1 Council meeting is a discussion on planning for ICANN58. On November 23, James sent an email the Council list requesting feedback on several questions related to meeting planning. The attached document provides an overview of responses to the following questions: (1) Do we prefer a Single or Split Constituency Day? (2) What is the right number of High Interest Topics (HIT)? The current Block Schedule drafts contain five HIT sessions. (3) Any thoughts on the best way to solicit topics for HIT sessions, and how to choose the top 5? (4) Similarly, any thoughts on how to address the inevitable conflicts between working sessions and HITs? (5) Any other specific feedback you’d like us to bring to the SO/AC meeting Rubens, Michele, Donna, Rafik, Ed and Carlos provided responses to the above questions. Please reference the attached for full text of the comments, but staff notes a few common threads in the responses that may feed into further discussion in the Council: - There were several responses supporting a single constituency day. Rubens, Michele, and Rafik supported a single constituency day. - Several responses supported either reducing the number of HIT sessions or rethinking the HIT concept. Ed suggested having a single HIT. Rubens supported having 1 or 2 at most. Rafik suggested 3. Michele and Donna recommended taking a step back to look more broadly at goals around the HIT concept and then planning accordingly. - Rubens, Ed, and Carlos all supported the notion that when in doubt, make meeting A more like meeting B than meeting C. The issue of scheduling was also raised in the Council session in Hyderabad (transcript here: http://schd.ws/hosted_files/icann572016/c8/I57%20HYD_Mon07Nov2016-GNSO%20Pu…<https://urldefense.proofpoint.com/v2/url?u=http-3A__schd.ws_hosted-5Ffiles_…>). Several themes came up in the discussion, including: - Improving communication during the planning process - Revisiting the rubric used for scheduling: take a step back, clarify and prioritize objectives for ICANN meetings, develop schedule based on priorities to use the time effectively - Focusing meetings on ICANN’s core, substantive work - Managing and (to the extent possible) avoiding critical scheduling conflicts - Avoiding duplication of content across sessions - Scheduling sessions in a way that maximizes productivity and does not overload participants Please note that the above is not intended to be a full summary. It highlights some of the points that have been raised to support further discussion. Kind regards, Emily Emily Barabas | Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org<mailto:emily.barabas@icann.org> | Phone: +31 (0)6 84507976 ________________________________ No virus found in this message. Checked by AVG - www.avg.com[avg.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.avg.com&d=DgMGaQ&c=…> Version: 2016.0.7859 / Virus Database: 4664/13314 - Release Date: 10/30/16 Internal Virus Database is out of date.

3 3

Review Project List
by Glen de Saint Géry Dec. 1, 2016

Dec. 1, 2016

Dear Councillors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meetings. If there are no comments, the list will be posted on the website on page. http://gnso.icann.org/en/council/project and be directly viewed at: http://gnso.icann.org/meetings/projects-list.pdf Thanks so 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-…>.

4 3

Draft Minutes Meeting of the GNSO Council Part 1 7 November 2016 to review
by Nathalie Peregrine Dec. 1, 2016

Dec. 1, 2016

Dear Councillors, Attached, please find the draft minutes of the Meeting of the GNSO Council Part I on 7 November 2016 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 11 December 2016. Our apologies for the delay, the minutes for the GNSO Council Part II meeting will be sent out shortly. Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<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