December 2019 - council - lists.icann.org

Documents for GNSO Council review
by Nathalie Peregrine Dec. 16, 2019

Dec. 16, 2019

Dear all, A reminder that there are deadlines approaching for GNSO Council input on documents. You may find them itemized here<https://community.icann.org/display/gnsocouncilmeetings/Documents+for+GNSO+…>. Thank you, Kind regards, Nathalie Nathalie Peregrine Manager, Operations 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 visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Re: [council] [gnso-chairs] FW: NomCom 2020 Timeline and Request for description of GNSO Council positions and requirements
by Steve Chan Dec. 15, 2019

Dec. 15, 2019

Dear Jay and NomCom Support Staff, On behalf of the GNSO Council, please find the revised description for the NomCom to use in filling the GNSO Council position in 2020. Please note that the revised description takes into account consideration of the suggested questions. If you have any questions or concerns, please let us know. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar From: NomCom Operations Team <nomcom-ops-team(a)icann.org> Date: Friday, November 15, 2019 at 17:41 To: "kdrazek(a)verisign.com" <kdrazek(a)verisign.com> Cc: "jay(a)handynetworks.com" <jay(a)handynetworks.com>, "olejacobsen(a)me.com" <olejacobsen(a)me.com>, "dashcraft(a)swlaw.com" <dashcraft(a)swlaw.com>, Marika Konings <marika.konings(a)icann.org>, NomCom Operations Team <nomcom-ops-team(a)icann.org> Subject: NomCom 2020 Timeline and Request for description of GNSO Council positions and requirements Dear Mr. Drazek, I’m writing you today to notify you about an important timing change with respect to our Nominating Committee (NomCom) processes, and to request your input about the skillsets and traits that the GNSO Council seek in a NomCom appointed individual. During this NomCom cycle, we will appoint a single non-voting member to the GNSO Council, who is not affiliated with a specific house. First, from a process perspective, this NomCom intends to open this year’s NomCom application cycle mid-December 2019 and the cycle will close mid-February 2020. Doing so will allow us to conduct full committee interviews of GNSO Council, ccNSO, and ALAC candidates under consideration for selection during May and June, prior to ICANN68. Please note this is a substantial change in timing as compared to previous years, where the application period has historically closed at the end of March. Additionally, we welcome and appreciate any updates to the GNSO Council skill-set criteria and position description that you may have provided us in the past. It is important that you provide the NomCom with these suggested skill sets and criteria so that the NomCom can consider them when making its selections. We are curious to learn your preferences around themes such as: Does GNSO Council have a preference on if the NomCom appointed representatives are from within the ICANN community, or should they be outsiders? Does GNSO Council have a preference on NomCom appointed representatives who are from within GNSO? For example, the ccNSO has specifically indicated to the NomCom in previous years that they do not want us to appoint any candidates who currently are affiliated with a ccTLD operator. Does GNSO Council have a preference on candidates who have previous policy development experience? In preparation of the upcoming application period, any updates/changes to the GNSO Council skill set criteria and position description should be returned to NomCom Staff Support: nomcom-ops-team(a)icann.org by 14 December 2019. Please note that this year’s NomCom is not able to consider submissions of skill sets/criteria from prior years unless you affirmatively contact us this year by the 14th December deadline and request that the NomCom do so. As reference, previous guidance we have received from the ICANN Board, PTI Board, GNSO Council, ccNSO Council, and ALAC can be found at: https://www.icann.org/nomcom2019-positions [icann.org] Please let me know if you have any questions. I can be reached by e-mail at jay(a)handynetworks.com or by phone at 720-544-1485. Kindest regards, Sent by the NomCom Staff on behalf of Jay Sudowski Chair, ICANN 2020 Nominating Committee

1 0

Re: [council] [Ext] RE: NomCom Request for the GNSO Council to Review Selection Criteria
by Steve Chan Dec. 13, 2019

Dec. 13, 2019

Thanks for the heads up Marie, as well as the timely reminder to all about the deadline. The deadline is today, but getting feedback returned no later than tomorrow will hopefully still allow for adequate time to incorporate everything into a single document that all can agree upon. Best, Steve From: Marie Pattullo <marie.pattullo(a)aim.be> Date: Wednesday, December 11, 2019 at 12:04 PM To: Steve Chan <steve.chan(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [Ext] RE: [council] NomCom Request for the GNSO Council to Review Selection Criteria Steve, all We’re talking with the BC but with apologies, we won’t be able to get our feedback to you today. Will do our utmost to ensure that it reaches you tomorrow. Sorry Marie From: council <council-bounces(a)gnso.icann.org> On Behalf Of Steve Chan Sent: Tuesday, December 3, 2019 7:54 PM To: council(a)gnso.icann.org Subject: [council] NomCom Request for the GNSO Council to Review Selection Criteria Dear Councilors, The GNSO Council has been invited by the Nominating Committee (NomCom) to review the skillsets and traits that the GNSO Council seeks in NomCom appointees. For this particular cycle, the NomCom will appoint a single non-voting member to the GNSO Council, who is not affiliated with a specific house. Staff has extracted the criteria used by the NomCom in 2019 for GNSO appointees (here: https://www.icann.org/nomcom2019-positions [icann.org] and created a Google document for the Council to suggest changes (here: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCE… [docs.google.com] Note that the NomCom has suggested three additional questions to consider in reviewing the criteria – those have also been included in the Google doc. Council leadership has already reviewed and made some suggested edits, which you will find in suggestion mode. The deadline to return the Council’s selection criteria to the NomCom is 14 December. As such, Council leadership would like to set a deadline of 11 December for you all to consult with your respective groups and return feedback as applicable. While perhaps obvious, ensuring the NomCom has criteria that are consistent with the expectations of the GNSO Council is extremely important, so Council leadership greatly appreciates your review and input. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

3 3

FW: [Ext] Re: Draft SOAC Leadership Meeting Agenda for January 2020_v2.docx
by Drazek, Keith Dec. 13, 2019

Dec. 13, 2019

FYI From: David Olive <david.olive(a)icann.org> Sent: Friday, December 13, 2019 2:08 PM To: Katrina Sataki <katrina(a)nic.lv>; Drazek, Keith <kdrazek(a)verisign.com>; Aftab Siddiqui <aftab.siddiqui(a)gmail.com>; manal(a)tra.gov.eg; Maureen Hilyard <maureen.hilyard(a)gmail.com>; Rod Rasmussen <rod(a)rodrasmussen.com>; Fred Baker <fred(a)isc.org> Subject: [EXTERNAL] FW: [Ext] Re: Draft SOAC Leadership Meeting Agenda for January 2020_v2.docx Dear SO-AC Chairs: Just wish to convey to you a note from the ICANN Board Chair with some comments on the current draft agenda for the LA meeting. I will be sending some comment on the agenda from Goran and the org shortly. Best regards, David David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) Washington, D.C. From: "maarten.botterman(a)board.icann.org<mailto:maarten.botterman@board.icann.org>" <Maarten.Botterman(a)board.icann.org<mailto:Maarten.Botterman@board.icann.org>> Date: Friday, December 13, 2019 at 9:26 AM To: David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>, Goran Marby <goran.marby(a)icann.org<mailto:goran.marby@icann.org>> Cc: León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx<mailto:leonfelipe@sanchez.mx>>, Cassia Oliveira <cassia.oliveira(a)icann.org<mailto:cassia.oliveira@icann.org>>, Susie Johnson <susie.johnson(a)icann.org<mailto:susie.johnson@icann.org>>, Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>> Subject: RE: [Ext] Re: Draft SOAC Leadership Meeting Agenda for January 2020_v2.docx Dear David, Good to have the agenda focus on the “Three Big Plans”. Driving these forward is very most a joint effort. In this I would like to add to the discussion the need to seek excellence in everything we do by committing to “continuous improvement”. This means that up and beyond the Reviews we do according to our Bylaw commitments (and the discussions we have on further rationalizing this, as well as the recommendations ATRT3 may come with) it is important for all in the multistakeholder system to realize we are all responsible for our own functioning. And there is several examples already from the Community on how this is taken forward. In fact, one could consider PDP3.0 one of those, and there are other examples. The point I would want to make is that the Board is also committed to “continuous improvement” of: * our internal processes and way of working; * our interaction with the Organization and Organization-led processes; * our interaction with the Community and Community-led processes. Great if all SO’s and AC’s also take a look at their focus in this – and how this can be improved, further. Happy to talk about some of the activities the Board has set up for this purpose in the past (e.g. Board Operational Priorities formulation and communication; pre- and post workshop blogs; etc.), and is working on right now (e.g. skills matrix to ensure balance of skills in the Board; focus on role of liaisons to improve Board – community interaction; etc.) – when you feel that may be useful for this meeting. Best regards Maarten From: David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>> Sent: Thursday, 12 December 2019 22:49 To: Goran Marby <goran.marby(a)icann.org<mailto:goran.marby@icann.org>> Cc: Maarten Botterman <maarten.botterman(a)board.icann.org<mailto:maarten.botterman@board.icann.org>>; León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx<mailto:leonfelipe@sanchez.mx>>; Cassia Oliveira <cassia.oliveira(a)icann.org<mailto:cassia.oliveira@icann.org>>; Susie Johnson <susie.johnson(a)icann.org<mailto:susie.johnson@icann.org>>; Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>> Subject: Re: [Ext] Re: Draft SOAC Leadership Meeting Agenda for January 2020_v2.docx Great. Thanks. I will share any updates on the agenda. Please send me any comments so I can convey them to the SOAC Chairs. Best regards. David Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

FYI: [ICANN Community Leaders] 12 December Update
by Michelle DeSmyter Dec. 12, 2019

Dec. 12, 2019

FYI: [http://r20.rs6.net/on.jsp?ca=685048cb-5a44-415c-8725-fedc65dfd281&a=1122025…] Thursday, 12 December 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents Information Sharing · NEW: .ORG Update · NEW: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 · DUE ON MONDAY: NextGen@ICANN Community Consultation · REMINDER: FY21 SO/AC Additional Budget Request Process · REMINDER: ICANN Fellowship Program Mentors ICANN67 Planning · REMINDER: ICANN67 Publication Support · REMINDER: CROP Deadline for ICANN67 Public Comment · CLOSES TODAY: Registration Directory Service (WHOIS2) Review Team Final Report · CLOSES THIS WEEK: Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names · Proposal for Future Root Zone KSK Rollovers Information Sharing NEW: .ORG Update Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Read an update about .ORG in a blog post [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> by ICANN President and CEO Göran Marby and ICANN Board Chair Maarten Botterman. NEW: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING ICANN org will hold Strategic Outlook Trends Identification sessions with the community at ICANN67. To prepare for that exercise, ICANN org will be seeking community feedback on possible formats and arrangements which will be sent through each community group’s leadership. The Strategic Outlook program [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> is a joint effort among ICANN org, the community, and ICANN Board to identify and track trends that relate to ICANN and its mission and to make sure that relating opportunities and challenges are incorporated into ICANN's current and future strategy. New trends or shifts in existing trends impacting the operating plans (five-year or annual), and/or budget, will be factored into the annual iteration of those plans as appropriate. Significant shifts could also result in adjustments to the strategic plan. DUE ON MONDAY: NextGen@ICANN Community Consultation Executive: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The NextGen@ICANN program is currently undergoing a community consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. One request from the preliminary feedback received to-date was for ICANN org to explore the feasibility of having community volunteer representatives from Supporting Organizations (SOs), Advisory Committees (ACs), Stakeholder Groups (SGs), and Constituencies (Cs) to nominate individuals for the following two roles: 1. NextGen Selection Committee members 2. NextGen mentors For the Selection Committee, a time commitment of approximately 20 hours over three weeks is required (for each application round). Selection Committee members will typically serve for two years (or six application rounds). Mentors are expected to devote approximately 24 hours to pre-ICANN Public Meeting preparation with their mentees, to offer advice, networking support, and regular check-ins on-site, and to complete evaluations following the ICANN Public Meeting. Based on previous estimates, mentors spend about two hours per week during the six-week preparation period in advance of the meeting and about two hours per day providing on-site support at the ICANN Public Meeting. Mentors will typically serve for one year (or three meetings). Is your group interested in nominating individuals for either of these roles? By Monday, 16 December 2019, please take the following poll [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to help ICANN org can gauge the level of community interest. The findings of this poll will inform the proposed NextGen program approach that will be published for Public Comment. Note: You will not be asked to submit the names of potential volunteers for roles at this time. REMINDER: FY21 SO/AC Additional Budget Request Process Executive: Xavier Calvez, Chief Financial Officer FOR: All Community Leaders INFORMATION SHARING The Fiscal Year 2021 (FY21) Supporting Organization and Advisory Committee (SO/AC) Additional Budget Request process has begun. This additional budget approval process is part of the overall ICANN annual budgeting process that is for the review of specific requests from the community that are not already included in the budget but serve to further the key objectives of the requesting community group. Your active participation and adherence to procedural guidelines is greatly appreciated. Information concerning the FY21 SO/AC Additional Budget Request process, including timeline and request template can be found on the finance community wiki [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Additional Budget Requests are due Friday, 31 January 2020. Please email any questions that you may have to planning(a)icann.org<mailto:planning@icann.org>. We look forward to your continued engagement on the SO/AC Additional Budget Request process for FY21. REMINDER: ICANN Fellowship Program Mentors From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. SOs/ACs should first select their respective Fellowship Program mentor by Friday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. ICANN67 Planning REMINDER: ICANN67 Publication Support From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN67 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 3 January 2020. Please ensure that all materials, new or updated, are evergreen. Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. REMINDER: CROP Deadline for ICANN67 From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN67, requests must be submitted no later than Friday, 17 January 2020. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: Trip requests must be approved by the respective community leadership team. For FY20, the trip request must be filled in by the CROP participant via the CROP workspace [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. In order to access it, applicants must first have an account; please let the CROP coordinator know if you need an account. All individuals requesting CROP funding must also review the CROP Guidelines [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> prior to submitting a request. Please contact crop-staff(a)icann.org with any questions. Public Comment Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSES TODAY: Thursday, 12 December 2019 Registration Directory Service (WHOIS2) Review Team Final Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> EXTENDED: Monday, 23 December 2019 Proposal for Future Root Zone KSK Rollover [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Volume 1, Issue 73 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 16 December 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

NomCom Request for the GNSO Council to Review Selection Criteria
by Steve Chan Dec. 11, 2019

Dec. 11, 2019

Dear Councilors, The GNSO Council has been invited by the Nominating Committee (NomCom) to review the skillsets and traits that the GNSO Council seeks in NomCom appointees. For this particular cycle, the NomCom will appoint a single non-voting member to the GNSO Council, who is not affiliated with a specific house. Staff has extracted the criteria used by the NomCom in 2019 for GNSO appointees (here: https://www.icann.org/nomcom2019-positions) and created a Google document for the Council to suggest changes (here: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCE…) Note that the NomCom has suggested three additional questions to consider in reviewing the criteria – those have also been included in the Google doc. Council leadership has already reviewed and made some suggested edits, which you will find in suggestion mode. The deadline to return the Council’s selection criteria to the NomCom is 14 December. As such, Council leadership would like to set a deadline of 11 December for you all to consult with your respective groups and return feedback as applicable. While perhaps obvious, ensuring the NomCom has criteria that are consistent with the expectations of the GNSO Council is extremely important, so Council leadership greatly appreciates your review and input. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

2 1

Final Proposed Agenda GNSO Council Meeting - 19 December 2019 at 21:00 UTC
by Andrea Glandon Dec. 10, 2019

Dec. 10, 2019

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 19 December 2019 at 21:00 UTC. Draft GNSO Council Agenda 19 December 2019 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/D5IzBw This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf> v3.3, updated on 30 January 2018 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. GNSO Council meeting held at 21:00 UTC Coordinated Universal Time: 21:00 UTC: https://tinyurl.com/w82k6rn 13:00 Los Angeles; 13:00 Washington; 21:00 London; (Friday) 02:00 Islamabad; (Friday) 06:00 Tokyo; (Friday) 08:00 Melbourne GNSO Council Meeting Audio Cast Listen in browser: http://stream.icann.org:8000/stream0<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…>1 Listen in application such as iTunes: http://stream.icann.org:8000/stream01.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 (10 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<https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-coun…> of the GNSO Council meeting on the 24 October 2019 were posted on 13 November 2019 Minutes Part 1<https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-gnso…> Part 2 <https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-gnso…> of the GNSO Council meetings on the 06 November 2019 were posted on 26 November 2019 Item 2: Opening Remarks / Review of Projects & Action List (20 minutes) 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 (10 minutes) * Motion<https://community.icann.org/x/DZIzBw> to adopt the GNSO Council response to the GAC Communique. * Motion<https://community.icann.org/x/DZIzBw> for the confirmation of GNSO representative to the Empowered Community Administration * Confirmation of Anne Aikman-Scalese as one of the GNSO appointees to the CCWG Auction Proceeds Item 4: COUNCIL VOTE - Approval of the Supplemental Recommendation Related to the Non-Adopted EPDP Phase 1 Recommendations (recommendation #12) (15 minutes) On 15 May, the ICANN Board informed<https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-t…> the GNSO Council of the Board’s action in relation to the GNSO’s EPDP Phase 1 policy recommendations. The Board did not adopt two of the recommendations in full, where the Board has identified that portions of those recommendations are not in the best interests of the ICANN Community or ICANN and is initiating the consultation process between the Board and the GNSO Council. This concerns recommendation #1, purpose 2 and recommendation #12, deletion of data in the Organization field. As required under the ICANN Bylaws at Annex A-1,Section 6.b, a Board Statement is attached as Annex A to the letter, articulating the reasons for the Board’s non-adoption of these two items. As per the Bylaw requirements (Annex A-1, Section 6.c), “the Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement.” During the Council’s Extraordinary Meeting on 28 May 2019, it reviewed the Board Statement and conducted a lengthy discussion on the best path forward. On 30 May 2019, Keith Drazek, the GNSO Chair provided an update to the EPDP Team on the expected next steps in relation to the ICANN Board’s action on Phase 1 recommendations and requested that the EPDP Team provide input to identify any questions, comments or concerns in relation to ICANN Board’s action on the EPDP Phase 1 Recommendations. Subsequently, on 9 June 2019, Janis Karklins, Chair of the EPDP, informed the GNSO Chair of the following preliminary input noting that there was not sufficient time to formalize and agree on an EPDP Team response: “• In relation to purpose 2, there is a general understanding for why the Board decided to not adopt this purpose and the EPDP Team confirms that it considers it firmly within its scope for phase 2 to further review this purpose in the context of the System for Standardized Access / Disclosure (SSAD); • For recommendation #12, some additional context has been provided that may help explain the thinking behind the EPDP Team’s original recommendation. However, there is no agreement at this stage on whether or not the Board’s non-adoption should be supported.” During the Council’s June 2019 meeting, it continued to consider the next steps<https://mm.icann.org/pipermail/council/2019-May/022754.html>, taking into account a discussion with the ICANN Board at ICANN65. The reasoning and intent of the deletion part of recommendation #12 was explained to the Board, as well as the intent of purpose 2 and it was agreed that a letter should be drafted and sent to the ICANN Board as well as the EPDP Team to provide an update on the current thinking of the GNSO Council and likely next steps. The Council discussed a draft response on its 18 July 2019 meeting, subsequent discussion on the mailing list, and additional dialogue on the 22 August 2019 meeting. On 9 September 2019, the GNSO Council sent its response<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> to the ICANN Board. On 14 October 2019, the ICANN Board provided its response<https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-t…> to the GNSO Council’s update. On the Council’s October 2019 meeting, the Council considered the Board’s response and discussed next steps. The Council consulted with the EPDP Team regarding some potential ways of addressing Board’s concerns (i.e., including implementation guidance), in preparation for discussions with the ICANN Board at ICANN66. At ICANN66, the GNSO Council conducted dialogue with the ICANN Board to share the proposed approach. Here, the Council will vote to approve Supplemental Recommendation reaffirming the part of the original Recommendation #12 and the Implementation Advice. See also Annex A-1, Section 6. Board Approval Process below for further details. Section 6. Board Approval Processes The Board will meet to discuss the EPDP recommendation(s) as soon as feasible, but preferably not later than the second meeting after receipt of the Recommendations Report from the Staff Manager. Board deliberation on the EPDP Recommendations contained within the Recommendations Report shall proceed as follows: a. Any EPDP Recommendations approved by a GNSO Supermajority Vote shall be adopted by the Board unless, by a vote of more than two-thirds (2/3) of the Board, the Board determines that such policy is not in the best interests of the ICANN community or ICANN. If the GNSO Council recommendation was approved by less than a GNSO Supermajority Vote, a majority vote of the Board will be sufficient to determine that such policy is not in the best interests of the ICANN community or ICANN. b. In the event that the Board determines, in accordance with paragraph a above, that the proposed EPDP Recommendations are not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council. c. The Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement. The Board shall determine the method (e.g., by teleconference, email, or otherwise) by which the Council and Board will discuss the Board Statement. At the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board, including an explanation for the then-current recommendation. In the event that the Council is able to reach a GNSO Supermajority Vote on the Supplemental Recommendation, the Board shall adopt the recommendation unless more than two-thirds (2/3) of the Board determines that such guidance is not in the interests of the ICANN community or ICANN. For any Supplemental Recommendation approved by less than a GNSO Supermajority Vote, a majority vote of the Board shall be sufficient to determine that the guidance in the Supplemental Recommendation is not in the best interest of the ICANN community or ICANN. 4.1 – Presentation of motion (Council leadership) 4.2 – Council discussion 4.3 – Council vote (voting threshold: Supermajority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A: GNSO Policy Development Process of the ICANN Bylaws. Item 5: COUNCIL DISCUSSION – Discussion on the Addendum to the Review of All Rights Protection Mechanisms in All gTLDs Charter to Integrate Recommendation 5 From IGO-INGO Access to Curative Rights Protection Mechanisms Final Report (20 minutes) On 18 April 2019, the Council voted<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+April+20…> to approve recommendations 1-4 of Final Report from the IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG. The Council also resolved to not approve Recommendation 5 and, ” directs the Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP to consider, as part of its Phase 2 work, whether an appropriate policy solution can be developed that is generally consistent with Recommendations 1, 2, 3 & 4 of the PDP Final Report and: * accounts for the possibility that an IGO may enjoy jurisdictional immunity in certain circumstances; * does not affect the right and ability of registrants to file judicial proceedings in a court of competent jurisdiction; * preserves registrants’ rights to judicial review of an initial UDRP or URS decision; and * recognizes that the existence and scope of IGO jurisdictional immunity in any particular situation is a legal issue to be determined by a court of competent jurisdiction.” The GNSO Council resolved also to, “amend the charter for the RPMs PDP Working Group to reflect this new instruction accordingly.” Some members of the GNSO Council met with certain members of the GAC and IGOs at ICANN65, where there appeared to be agreement from the GAC/IGOs to support the chartering of this separate work. A small team of Councilors was convened to prepare a draft Addendum to the RPMs PDP charter, which was discussed during the Council’s September 2019 meeting. After integrating Councilor feedback, the revised Addendum<https://gnso.icann.org/en/drafts/rpms-charter-addendum-09oct19-en.pdf> was shared with the GAC and IGOs for their consideration. The Council considered GAC/IGO feedback<https://gnso.icann.org/sites/default/files/file/field-file-attach/ismail-to…> received on 1 November 2019, as well as feedback from the meeting with the GAC at ICANN66. Taking into account GAC and IGO feedback received and balancing with the goals of the GNSO Council, leadership prepared a revised draft for GNSO Council consideration. Here, the Council will discuss the draft revisions to the Addendum to the RPMs PDP charter, as well as additional steps that need to be taken prior to Council consideration for adoption. 5.1 – Introduction of topic (Council leadership) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL UPDATE - Expedited PDP on the Temporary Specification for gTLD Registration Data - Phase 2 Work (15 minutes) As noted in the charter<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter> for the Expedited PDP on the Temporary Specification for gTLD Registration Data, work on a System for Standardized Access to Non-Public Registration Data (SSAD) commenced after the work on a series of gating questions are complete. With the EPDP Team’s delivery of its Final Report to the GNSO Council, the work on the gating questions was considered completed and the work on the SSAD, or otherwise known as phase 2 of the EPDP, commenced. In March of 2019, the GNSO Council resolved to indicate its non-objection to the EPDP Phase 2 work beginning; the Team commenced its Phase 2 deliberations on 2 May 2019. The Team has worked diligently in developing draft “building blocks” and policy principles that can serve as components of the SSAD. Leveraging ICANN meetings and a dedicated face-to-face meeting in September 2019, as well as remote meetings twice a week, the Team has made substantial progress towards its goal of publishing its Initial Report for public comment by mid-December of 2019. However, the EPDP Team collectively agreed to delay publication from December until a target date of 7 February 2020, noting it would prefer more time to ensure the overall quality and comprehensiveness of its draft recommendations; accordingly, the Team submitted a Project Change Request (PCR<https://community.icann.org/download/attachments/105388008/EPDP-P2_Project_…>) to the GNSO Council. The EPDP Leadership presented the ramifications of delayed publication to the EPDP Team, noting, specifically, if the EPDP Team delays publication at this stage, no slack remains in the project plan to deliver a Final Report by June. In the event the EPDP Team does not meet the June deadline, any remaining resources allocated will be returned to conclude fiscal year 2020. Therefore, if the EPDP were to determine additional resources will be necessary to complete its work, the GNSO Council will be required to request more resources from the Board. Here, the Council will receive an update on the status of the EPDP Phase 2. 6.1 – Introduction of topic (Council leadership; Rafik Dammak - Council Liaison) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - GNSO Council Strategic Planning Session (15 minutes) From 22-24 January of 2020, the GNSO Council will hold its third Strategic Planning Session (SPS), which is a result of previous GNSO Councils realizing the benefit of holding dedicated sessions to plan and prepare for the coming year of work; the primary objective of these sessions is to develop a work plan for the year ahead and beyond. However, the sessions also help the GNSO Council to better understand its responsibilities and remit and how to more effectively perform its role. Council leadership and staff have collaborated on planning the upcoming SPS. Here, the Council will discuss the draft agenda, expectations for Councilors, and review action items from previous SPSs. 7.1 - Introduction of topic (Council leadership) 7.2 - Council discussion 7.3 - Next steps Item 8: ANY OTHER BUSINESS (10 minutes) 8.1 - Consideration of previous GNSO Council Additional Budget Requests (ABRs) and whether they should be pursued in the future, as well as if other ABRs should be submitted. FY20 ABRs included: * GNSO Council Strategic Planning Session<https://community.icann.org/download/attachments/102146823/FY20%20ABR_SPS.p…> (similar ABRs submitted in FY18, FY19, and FY20) * PDP Leadership Travel Pilot<https://community.icann.org/download/attachments/102146823/FY20%20ABR_Trave…> (similar ABRs submitted submitted in FY18, FY19, and FY20) * Consensus Building Playbook<https://community.icann.org/download/attachments/102146823/FY20%20ABR_Conse…> (submitted in FY20 only, as an element of PDP 3.0) _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 21:00 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EST) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRST) UTC-2 20:00 London, United Kingdom (GMT) UTC+0 21:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CET) UTC+1 22:00 Islamabad, Pakistan (PKT) (+1 day) UTC+5 02:00 Singapore (SGT) (+1 day) UTC+8 05:00 Tokyo, Japan (JST) (+1 day) UTC+9 06:00 Melbourne, Australia (AEDT) (+1 day) UTC+11 08:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 29 of March 2020, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 08 of March 2020 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/w82k6rn

1 0

FW: [gnso-secs] RrSG GNSO Councilor
by Drazek, Keith Dec. 10, 2019

Dec. 10, 2019

Hi all, We have been informed that Greg DiBiase from Amazon Registrar has been elected by the Registrars Stakeholder Group to replace Darcy Southwell on the GNSO Council. Once he’s added to the Council mailing list, please join me in welcoming Greg! Regards, Keith From: Gnso-chairs <gnso-chairs-bounces(a)icann.org> On Behalf Of Andrea Glandon Sent: Friday, December 06, 2019 11:30 AM To: gnso-chairs(a)icann.org Cc: gnso-secs(a)icann.org Subject: [EXTERNAL] [gnso-chairs] FW: [gnso-secs] RrSG GNSO Councilor Dear GNSO Council Leadership, Please see below the announcement of Darcy Southwell’s replacement to the GNSO Council. Would you be so kind to inform the rest of the council? Thank you! Kind Regards, Andrea From: Gnso-secs <gnso-secs-bounces(a)icann.org<mailto:gnso-secs-bounces@icann.org>> on behalf of Graeme Bunton <gbunton(a)tucows.com<mailto:gbunton@tucows.com>> Date: Friday, December 6, 2019 at 10:15 AM To: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>> Cc: "DiBiase, Gregory" <dibiase(a)amazon.com<mailto:dibiase@amazon.com>>, "James M. Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Subject: [gnso-secs] RrSG GNSO Councilor Yo GNSO, We've completed (in record time) our election process to replace Darcy Southwell, and have elected Greg DiBiase from Amazon Registrar. Is it possible to rescind my temporary alternate designation of James Bladel, and get Greg in there Permanently? Thanks Graeme -- ____________________________ Graeme Bunton Director, Analytics & Policy Tucows Inc. PH: 416 535 0123 ext 1634

4 3

EPDP phase update & Project Change request
by Rafik Dammak Dec. 10, 2019

Dec. 10, 2019

Hi all, I am sending this to share update from EPDP phase 2 with regard to progress and timeline. You will find attached the project package which includes the adjusted timeline (page #2), project status and summary (page #3) and formal project change request (page #4), which are tools coming from the PDP 3.0 improvements, reflecting the timeline change, explaining the rationale behind it and the impact. You can also see the documents used in prior EPDP call for the timeline discussion and a rough plan to get the initial report published with the new target date in early February instead of Mid December. We will have EPDP update as agenda item for the next GNSO Council meeting and I am planning to give more details there. Best Regards, Rafik

1 0

For your review: Updated GNSO project list
by Terri Agnew Dec. 10, 2019

Dec. 10, 2019

Dear all, Ahead of the upcoming GNSO Council meeting, please find attached the updated GNSO Project List for your review. This will be posted shortly on the GNSO website [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>. Thank you! With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0