January 2020 - council - lists.icann.org

Re: [council] [gnso-secs] Welcome to the GNSO Council Strategic Planning Session!
by Nathalie Peregrine 21 Jan '20

21 Jan '20

Update (and thank you to Gregory for reminding me!): the agenda for the Strategic Planning Session can be found in the SPS 2020 Google drive, in the General Information folder. Thank you! Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Tuesday, January 21, 2020 at 10:02 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Welcome to the GNSO Council Strategic Planning Session! Dear councilors, Welcome to Los Angeles for the GNSO Council Strategic Planning Session! A few reminders: * At LAX, upon retrieving your luggage, please book your Uber to the Doubletree and make your way towards the LAXit (Uber and taxi zone). You will receive a pin code upon booking your Uber which you will be required to show your driver. * At the Doubletree, upon check-in please ensure you are provided with breakfast coupons covering your stay. * All our meetings will take place at the Doubletree, in the Pacifica room (above the lobby) * Breakfast and lunch are provided all three days. * Please join the GNSO Council leadership at the Doubletree bar this evening from 7pm onwards for informal welcome drinks. * Please ensure you have familiarized yourselves with the reading materials posted on the GNSO SPS 2020 Google drive. The agenda for the SPS has been built on the expectation that councilors have read the materials in advance of the session. Please do not hesitate to email me if you have any questions or concerns. Looking forward to seeing you this evening! 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

FW: [ICANN Community Leaders] 20 January 2020
by Julie Bisland 20 Jan '20

20 Jan '20

[http://r20.rs6.net/on.jsp?ca=5fe8b867-85ac-4456-8631-c8201a29edbb&a=1122025…] Monday, 20 January 2020 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 · REMINDER: Register for ICANN67 Prep Week Webinars · REMINDER: FY21 SO/AC Additional Budget Request Process · REMINDER: ICANN Fellowship Program Mentors ICANN67 Planning · REMINDER: ICANN67 Publication Support · REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Public Comment · Proposal for Future Root Zone KSK Rollovers · Third Accountability and Transparency Review Team (ATRT3) Draft Report · Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022 · Proposed Amendment 3 to the .COM Registry Agreement · Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group · Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget Information Sharing REMINDER: Register for ICANN67 Prep Week Webinars Executive: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING ICANN org released the schedule for ICANN67 Prep Week [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>, which features a series of nine webinars to prepare the community ahead of the upcoming Community Forum. Register and submit questions by Friday, 14 February 2020. REMINDER: FY21 SO/AC Additional Budget Request Process Executive: Xavier Calvez, Chief Financial Officer 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 Executive: Sally Costerton, Senior Vice President, Global Stakeholder Engagement 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 Executive: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING IN ONE WEEK: 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 required design assistance, 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: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives 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. Public Comment 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 Third Accountability and Transparency Review Team (ATRT3) Draft Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 11 February 2020 Proposed Amendment 3 to the .COM Registry Agreement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 14 February 2020 Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 14 February 2020 Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 25 February 2020 Volume 2, Issue 6 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 23 January 2020 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

IDN Scoping Team Final Report - GNSO Council Meeting Agenda #7 (23 January 2020)
by Ariel Liang 17 Jan '20

17 Jan '20

Dear All, On behalf of GNSO Council’s IDN Scoping Team, please find attached its Final Report, which serves as a conclusion of the scoping exercise of IDN issues. For Council’s consideration, the Scoping Team’s proposed mechanisms to address IDN variant TLD management and other related IDN issues are contained in “Section 6. Overall Conclusions” (pages 9-11) of the document. This document is expected to be discussed during the GNSO Council meeting on 23 January 2020, under Item 7: Council Update – IDN Scoping Small Team. Thank you, Ariel From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Wednesday, January 15, 2020 at 11:36 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Final Proposed Agenda GNSO Council Meeting - 23 January 2020 at 22:00 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 23 January 2020 at 22:00 UTC. Draft GNSO Council Agenda 23 January 2020 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/7gCJBw This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> 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 22:00 UTC Coordinated Universal Time: 22:00 UTC: https://tinyurl.com/vjx8bub [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_vjx8bub&d=…> 14:00 Los Angeles; 17:00 Washington DC; 22:00 London; (Friday) 03:00 Islamabad; (Friday) 07:00 Tokyo; (Friday) 09: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 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> of the GNSO Council meeting on the 24 October 2019 were posted on 13 November 2019 Minutes [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> of the GNSO Council meeting on the 19 December 2019 were posted on 02 January 2020 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>and Action Item List<https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (10 minutes) * Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+23+January+…> to approve the nomination of Amr Elsadr to serve as the ICANN Fellowship Program mentor. * Confirmation of Johan Helsingius as the Chair and Carlton Samuels as Vice-Chair for the GNSO Standing Selection Committee (SSC). Item 4: COUNCIL VOTE – Vote 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 the 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> was shared with the GAC and IGOs for their consideration. The Council considered GAC/IGO feedback [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> for GNSO Council consideration. The GNSO Council reviewed and discussed the draft at the December 2019 Council meeting. A revised draft was prepared and shared on the Council mailing list. Here, the Council will vote to adopt the Addendum to the RPMs PDP charter. 4.1 – Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+23+January+…> (Council leadership) 4.2 – Council discussion 4.3 – Council vote (voting threshold: Simple majority) 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 UPDATE – Review of All Rights Protection Mechanisms in All gTLDs PDP (15 minutes) Chartered in March 2016 to review all the RPMs that have been developed by ICANN, the PDP is focused on RPMs developed for the 2012 New gTLD Program (i.e., Trademark Clearing House, Sunrise, Claims, and Uniform Rapid Suspension). The WG is tasked with considering the overarching issue as to whether or not the RPMs collectively fulfil their purposes or whether additional policy recommendations will be necessary. The PDP has worked diligently since launch and is preparing to publish its Initial Report for public comment. As of ICANN64, the WG had expected to be able to publish its Initial Report at the beginning of 2020. The WG is currently revisiting sub team and individual URS proposals and, when completed, will proceed to the development of its Phase One Initial Report, with a plan to publish in March of 2020. As a result of this delay in timeline, the PDP has submitted a Project Change Request [INSERT LINK] and this update is intended to both inform and gain approval from the GNSO Council. Here, the Council will consider the Project Change Request. 5.1 – Introduction of topic (Council leadership; John McElwaine, GNSO Council liaison to the PDP) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL UPDATE – Cross-Community Working Group on new gTLD Auction Proceeds (15 minutes) This CCWG was chartered to develop a mechanism to allocate new gTLD Auction Proceeds. The CCWG is expected to consider the scope of fund allocation, due diligence requirements that preserve ICANN’s tax status as well as how to deal with directly related matters such as potential or actual conflicts of interest. The CCWG will not make any recommendations or determinations with regards to specific funding decisions (i.e. which specific organizations or projects are to be funded or not). The CCWG published its Initial Report for public comment on 8 October 2018 that later closed 11 December 2018 after requests for extension. 37 community submissions were received (see https://www.icann.org/en/system/files/files/report-comments-new-gtld-auctio… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>). After additional deliberations, a decision was made to publish the CCWG’s Proposed Final Report for public comment [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> to ensure that the community can review and provide input on changes that have been made since publication of the Initial Report. Input received through the second public comment period will be reviewed and incorporated as appropriate before the Final Report is published. The purpose of this update is to ensure that the GNSO Council, as a Chartering Organization, is familiar with the expected recommendations, but also to determine whether it might make sense for the Council to submit a public comment (14 February 2020 deadline). Here, the Council will consider the proposed final recommendations and consider whether a public comment on behalf of the Council is warranted. 6.1 – Introduction of topic (Council leadership; Erika Mann, Chair of the CCWG) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL UPDATE – IDN Scoping Small Team (15 minutes) The ICANN Board resolved in 2010 that IDN variant TLDs will not be delegated until relevant work is completed and directed ICANN org to develop a report identifying what needs to be done with the evaluation, possible delegation, allocation and operation of generic top-level domains (gTLDs) containing variant characters IDNs, in order to facilitate the development of workable approaches to the deployment of gTLDs containing variant characters IDNs. Based on analysis, ICANN org and the community identified two gaps to address: 1) that there is no definition of IDN variant TLDs, and; 2) that there is no IDN variant TLD management mechanism. The Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> (RZ-LGR Procedure) has been developed by the community to define the IDN variant TLDs and, following the Board resolution [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> in 2013 which approved the RZ-LGR Procedure, has been implemented to incrementally develop the Root Zone Label Generation Rules to address the first gap. ICANN org has developed the Recommendations for Managing IDN Variant TLDs [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> (the Variant TLD Recommendations), a collection of six documents finalized after incorporating the public comment feedback and published them as mechanisms for addressing the second gap identified by the community in the implementation of IDN variant TLDs. On 14 March 2019, the ICANN Board resolved [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>: The Board approves the Variant TLD Recommendations and requests that the ccNSO and GNSO take into account the Variant TLD Recommendations while developing their respective policies to define and manage the IDN variant TLDs for the current TLDs as well as for future TLD applications. The Board requests that the ccNSO and GNSO keep each other informed of the progress in developing the relevant details of their policies and procedures to ensure a consistent solution, based on the Variant TLD Recommendations, is developed for IDN variant ccTLDs and IDN variant gTLDs. Additionally, and separately, the ICANN Board anticipated adopting the IDN Guidelines v. 4.0 as part of its consent agenda for the 3 May 2019 meeting, but the GNSO Council requested [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> that the vote be deferred, due in part to concerns around the process, as well as specific requirements within the guidelines (e.g.,“same entity” requirement on second level registrations, which are in both the guidelines and the Variant TLD Recommendations). The ICANN Board agreed [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> to the deferral, allowing the GNSO Council additional time to consider the matter. The Council convened an IDN Scoping Team, comprised of Councilors and other GNSO members, to consider the scope of issues (e.g., IDN Guidelines and IDN Variant Management solutions) related to IDNs and accordingly, recommend a mechanism to address those issues (e.g., leverage existing PDPs, convene new PDP/EPDP, other). The IDN Scoping Team has thoroughly considered the scope of work that needs to be undertaken and accordingly, what mechanisms make the most sense to address. Most members of the IDN Scoping Team believe that two tracks of work can be undertaken: * Operational Track 1: In brief, a Contracted Party working/negotiation/implementation team would focused on IDN Implementation Guidelines 4.0 operational issues * Policy Track 2: In brief, a PDP/EPDP should be initiated and would have a scope including the definitions, management, and coordination issues related to IDN Variant TLDs, as well as IDN variants at the second-level. Additionally, this track would consider the related issue of how the IDN Implementation Guidelines, which Contracted Parties are required to comply with, should be revised in the future. The IDN Scoping Team shared the report [INSERT LINK} with the Council mailing list on [date]. Here, the Council will discuss the IDN Scoping Team’s recommendations report. 7.1 – Introduction of topic (Council Leadership; Edmon Chung, Scoping Team Lead) 7.2 – Update and council discussion 7.3 – Next step Item 8: ANY OTHER BUSINESS (10 minutes) 8.1 - ICANN67 Planning 8.2 - Council response [INSERT LINK] to the NomCom Review Implementation Working Group’s request for input on 27 recommendations. 8.3 - Council consideration of proposed GNSO Council Additional Budget Requests (ABRs) for FY21; review draft ABRs for the FY21 Strategic Planning Session [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> and Travel support for PDP Leadership to ICANN Public Meetings. [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> _______________________________ 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 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. 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… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> References for Coordinated Universal Time of 22:00 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 14:00 San José, Costa Rica (CST) UTC-6 16:00 New York/Washington DC, USA (EST) UTC-5 17:00 Buenos Aires, Argentina (ART) UTC-3 19:00 Rio de Janeiro, Brazil (BRST) UTC-2 21:00 London, United Kingdom (GMT) UTC+0 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 23:00 Paris, France (CET) UTC+1 23:00 Islamabad, Pakistan (PKT) (+1 day) UTC+5 03:00 Singapore (SGT) (+1 day) UTC+8 06:00 Tokyo, Japan (JST) (+1 day) UTC+9 07:00 Melbourne, Australia (AEDT) (+1 day) UTC+11 09: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 [timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_&d=…> and https://tinyurl.com/vjx8bub [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_vjx8bub&d=…>

1 0

Proposed GNSO Council Response to NomComRIWG Outreach Questions
by Ariel Liang 17 Jan '20

17 Jan '20

Dear GNSO Councilors, Kindly find attached the proposed GNSO Council response to the NomCom Review Implementation Working Group’s request for input. The proposed response was drafted by the GNSO Council Small Team consisting of Tom Dale, Carlton Samuels, and Marie Pattullo. Please note this item is expected to be discussed during the GNSO Council meeting on 23 January, under Item 8: Any Other Business: https://community.icann.org/x/8ACJBw Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) From: council <council-bounces(a)gnso.icann.org> on behalf of "Drazek, Keith via council" <council(a)gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek(a)verisign.com> Date: Monday, December 16, 2019 at 8:21 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] FW: NomComRIWG: Outreach questions Hi all, Please see the email below from the NomCom Review Implementation Working Group. They have posed a set of questions to the GNSO Council, with a response deadline of January 31. I suggest we form a small team to coordinate the Council’s answers and reply. If anyone would like to volunteer, please let me know. Best, Keith From: Jean-Baptiste Deroulez <jean-baptiste.deroulez(a)icann.org> Sent: Friday, December 13, 2019 8:13 AM To: Drazek, Keith <kdrazek(a)verisign.com>; pam.little(a)alibaba-inc.com; rafik.dammak(a)gmail.com Cc: Tom Barrett <tbarrett(a)encirca.com>; Cheryl Langdon-Orr <langdonorr(a)gmail.com>; Zahid Jamil-IG <internet(a)jamilandjamil.com>; Lars Hoffmann <lars.hoffmann(a)icann.org>; Steve Chan <steve.chan(a)icann.org>; gnso-secs(a)icann.org Subject: [EXTERNAL] NomComRIWG: Outreach questions Dear Keith, Dear Pam, Dear Rafik, As the leaders of the NomCom Review Implementation Working Group (NomComRIWG), we are contacting you following the ICANN Board’s acceptance of our Detailed Implementation Plan [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. The NomComRIWG has been directed to commence implementation of the twenty-seven (27) recommendations, and we are seeking the GNSO Council’s responses to a number of questions via the following google form: https://forms.gle/vrs95jrp9akK5sSRA [forms.gle]<https://urldefense.proofpoint.com/v2/url?u=https-3A__forms.gle_vrs95jrp9akK…> by 31 January 2020. Feel free to also seek input from the GNSO Council’s supporting staff if you believe this might add value to the implementation. If we have not received the GNSO Council’s response or a request for an extension by the deadline, we will proceed with the implementation without your input. If you prefer, feel free to respond separately to individual questions that you are able to answer, rather than wait until you are able to answer all of the questions at once. Please note this is the first round of several outreaches, we will be continuously outreaching to you throughout the implementation phase (over the next twenty-four to thirty-six months) due to the nature of this review. In particular, many members of the NomComRIWG will attend ICANN67 and plan to hold an update session for the entire community. If your group has time on your internal agenda and would like to meet with us for a short in-person update, do not hesitate to reach out to us via mssi-secretariat(a)icann.org<mailto:mssi-secretariat@icann.org> and we will happily coordinate. Finally, if you have any questions or concerns, either about the questions, or about any other aspect of the NomCom Review implementation, please, do not hesitate to reach out to us. Many thanks and best wishes, Tom Barrett, Chair NomComRIWG Cheryl Langdon-Orr, Vice-Chair NomComRIWG Zahid Jamal, Vice-Chair NomComRIWG NomComRIWG wiki: https://community.icann.org/x/aBpIBg Detailed Implementation Plan: PDF [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> Rec. 14: Formalize communication between the NomCom and the Board, SOs/ACs, and the PTI Board to understand needed competencies and experience. * Is there additional information that could be shared between the NomCom and the GNSO so that the NomCom can better target its selection to the needs of the GNSO Council? Rec. 16: Implement and codify a system for providing feedback to the NomCom regarding the contributions and participation of members up for re-appointment by the NomCom. * What information do you currently share with the NomCom about its NomCom appointees, and what is the timing of these communications? * In your opinion, what additional information should be shared between you and the NomCom? Rec. 21: The NomCom should use a standardized tool to evaluate and prioritize candidates, based on desired competencies and experience as determined annually. This tool will not replace qualitative assessments of candidates. * In your opinion, what tools, assessments and skills analysis should be used by the NomCom to make the best possible selection. Rec. 22: The NomCom should provide consistent interview questions and an interviewer evaluation form for the candidates interviewed during the deep-dive phase and the final face-to-face interviews. * In your opinion, which questions should be part of the "interview question library" and which would then be used by every NomCom? Rec. 25: Improve NomCom selection decisions by assessing the performance and needs of all bodies receiving NomCom appointees. * Is the GNSO Council performing any self-assessments, or third-party assessments? * If yes, are there any identified skills needed for future NomCom appointees to your organization? * If applicable, how do you communicate this to the NomCom? * What performance assessment, if any, do you think is feasible by the GNSO Council to improve future NomCom selection decisions.

1 0

Amendment to Motion - Nomination of a Mentor to the ICANN Fellowship Program
by Carlton Samuels 17 Jan '20

17 Jan '20

Dear GNSO Councillors: I would like to make a minor amendment to the motion I submitted for the upcoming Council meeting to nominate a mentor for the ICANN Fellowship Program. The purpose of this amendment is to clarify that the SSC’s recommendation was delivered via the motion and not through a separate communication to the GNSO Council mailing list. Whereas 5 currently states, “The SSC submitted its full consensus recommendation to the GNSO Council on 13 January 2019.” I would like to amend the text to read, “The SSC submitted its full consensus recommendation to the GNSO Council on 13 January 2020, by way of submission of the relevant motion.” This revision also corrects a typo in the date of submission. Kind regards, Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

2 1

FW: [Correspondence] Maarten Botterman to GNSO Chair Keith Drazek RE: ICANN Transfer Policy-Gaining Registrar Form of Authorization
by Drazek, Keith 16 Jan '20

16 Jan '20

FYI From: Wendy Profit <wendy.profit(a)icann.org> Sent: Thursday, January 16, 2020 5:03 PM To: Drazek, Keith <kdrazek(a)verisign.com>; gnso-secs(a)icann.org; Andrea Glandon <andrea.glandon(a)icann.org> Cc: Maarten Botterman <maarten.botterman(a)board.icann.org>; Secretary <secretary(a)icann.org>; Correspondence <Correspondence(a)icann.org>; Board Ops Team <board-ops-team(a)icann.org> Subject: [EXTERNAL] Re: [Correspondence] Maarten Botterman to GNSO Chair Keith Drazek RE: ICANN Transfer Policy-Gaining Registrar Form of Authorization …with attachment. From: Wendy Profit <wendy.profit(a)icann.org<mailto:wendy.profit@icann.org>> Date: Thursday, January 16, 2020 at 2:01 PM To: Keith Drazek <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, Andrea Glandon <andrea.glandon(a)icann.org<mailto:andrea.glandon@icann.org>> Cc: Maarten Botterman <maarten.botterman(a)board.icann.org<mailto:maarten.botterman@board.icann.org>>, Secretary <secretary(a)icann.org<mailto:secretary@icann.org>>, Correspondence <Correspondence(a)icann.org<mailto:Correspondence@icann.org>>, ICANN Board Ops <board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>> Subject: [Correspondence] Maarten Botterman to GNSO Chair Keith Drazek RE: ICANN Transfer Policy-Gaining Registrar Form of Authorization Dear Keith Drazek, On behalf of Maarten Botterman and the ICANN Board, please find the attached response to your letter of 31 October 2019 regarding ICANN’s Transfer Policy-Gaining Registrar Form of Authorization. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094

1 0

RPMs PDP WG Update Re: Final Proposed Agenda GNSO Council Meeting - 23 January 2020 at 22:00 UTC
by Julie Hedlund 16 Jan '20

16 Jan '20

Dear GNSO Councilors, Per the following agenda item: Item 5: COUNCIL UPDATE – Review of All Rights Protection Mechanisms in All gTLDs PDP (15 minutes) On behalf of Brian Beckham, Phil Corwin, and Kathy Kleiman, RPMs PDP WG Co-Chairs, and John McElwaine, GNSO Council Liaison to the WG, please see the attached slides and related Project Change Request for your consideration. Kind regards, Julie Hedlund Policy Director From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Wednesday, January 15, 2020 at 11:36 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Final Proposed Agenda GNSO Council Meeting - 23 January 2020 at 22:00 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 23 January 2020 at 22:00 UTC. Draft GNSO Council Agenda 23 January 2020 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/7gCJBw This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> 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 22:00 UTC Coordinated Universal Time: 22:00 UTC: https://tinyurl.com/vjx8bub [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_vjx8bub&d=…> 14:00 Los Angeles; 17:00 Washington DC; 22:00 London; (Friday) 03:00 Islamabad; (Friday) 07:00 Tokyo; (Friday) 09: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 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> of the GNSO Council meeting on the 24 October 2019 were posted on 13 November 2019 Minutes [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> of the GNSO Council meeting on the 19 December 2019 were posted on 02 January 2020 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>and Action Item List<https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (10 minutes) * Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+23+January+…> to approve the nomination of Amr Elsadr to serve as the ICANN Fellowship Program mentor. * Confirmation of Johan Helsingius as the Chair and Carlton Samuels as Vice-Chair for the GNSO Standing Selection Committee (SSC). Item 4: COUNCIL VOTE – Vote 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 the 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> was shared with the GAC and IGOs for their consideration. The Council considered GAC/IGO feedback [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> for GNSO Council consideration. The GNSO Council reviewed and discussed the draft at the December 2019 Council meeting. A revised draft was prepared and shared on the Council mailing list. Here, the Council will vote to adopt the Addendum to the RPMs PDP charter. 4.1 – Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+23+January+…> (Council leadership) 4.2 – Council discussion 4.3 – Council vote (voting threshold: Simple majority) 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 UPDATE – Review of All Rights Protection Mechanisms in All gTLDs PDP (15 minutes) Chartered in March 2016 to review all the RPMs that have been developed by ICANN, the PDP is focused on RPMs developed for the 2012 New gTLD Program (i.e., Trademark Clearing House, Sunrise, Claims, and Uniform Rapid Suspension). The WG is tasked with considering the overarching issue as to whether or not the RPMs collectively fulfil their purposes or whether additional policy recommendations will be necessary. The PDP has worked diligently since launch and is preparing to publish its Initial Report for public comment. As of ICANN64, the WG had expected to be able to publish its Initial Report at the beginning of 2020. The WG is currently revisiting sub team and individual URS proposals and, when completed, will proceed to the development of its Phase One Initial Report, with a plan to publish in March of 2020. As a result of this delay in timeline, the PDP has submitted a Project Change Request [INSERT LINK] and this update is intended to both inform and gain approval from the GNSO Council. Here, the Council will consider the Project Change Request. 5.1 – Introduction of topic (Council leadership; John McElwaine, GNSO Council liaison to the PDP) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL UPDATE – Cross-Community Working Group on new gTLD Auction Proceeds (15 minutes) This CCWG was chartered to develop a mechanism to allocate new gTLD Auction Proceeds. The CCWG is expected to consider the scope of fund allocation, due diligence requirements that preserve ICANN’s tax status as well as how to deal with directly related matters such as potential or actual conflicts of interest. The CCWG will not make any recommendations or determinations with regards to specific funding decisions (i.e. which specific organizations or projects are to be funded or not). The CCWG published its Initial Report for public comment on 8 October 2018 that later closed 11 December 2018 after requests for extension. 37 community submissions were received (see https://www.icann.org/en/system/files/files/report-comments-new-gtld-auctio… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>). After additional deliberations, a decision was made to publish the CCWG’s Proposed Final Report for public comment [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> to ensure that the community can review and provide input on changes that have been made since publication of the Initial Report. Input received through the second public comment period will be reviewed and incorporated as appropriate before the Final Report is published. The purpose of this update is to ensure that the GNSO Council, as a Chartering Organization, is familiar with the expected recommendations, but also to determine whether it might make sense for the Council to submit a public comment (14 February 2020 deadline). Here, the Council will consider the proposed final recommendations and consider whether a public comment on behalf of the Council is warranted. 6.1 – Introduction of topic (Council leadership; Erika Mann, Chair of the CCWG) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL UPDATE – IDN Scoping Small Team (15 minutes) The ICANN Board resolved in 2010 that IDN variant TLDs will not be delegated until relevant work is completed and directed ICANN org to develop a report identifying what needs to be done with the evaluation, possible delegation, allocation and operation of generic top-level domains (gTLDs) containing variant characters IDNs, in order to facilitate the development of workable approaches to the deployment of gTLDs containing variant characters IDNs. Based on analysis, ICANN org and the community identified two gaps to address: 1) that there is no definition of IDN variant TLDs, and; 2) that there is no IDN variant TLD management mechanism. The Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> (RZ-LGR Procedure) has been developed by the community to define the IDN variant TLDs and, following the Board resolution [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> in 2013 which approved the RZ-LGR Procedure, has been implemented to incrementally develop the Root Zone Label Generation Rules to address the first gap. ICANN org has developed the Recommendations for Managing IDN Variant TLDs [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> (the Variant TLD Recommendations), a collection of six documents finalized after incorporating the public comment feedback and published them as mechanisms for addressing the second gap identified by the community in the implementation of IDN variant TLDs. On 14 March 2019, the ICANN Board resolved [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>: The Board approves the Variant TLD Recommendations and requests that the ccNSO and GNSO take into account the Variant TLD Recommendations while developing their respective policies to define and manage the IDN variant TLDs for the current TLDs as well as for future TLD applications. The Board requests that the ccNSO and GNSO keep each other informed of the progress in developing the relevant details of their policies and procedures to ensure a consistent solution, based on the Variant TLD Recommendations, is developed for IDN variant ccTLDs and IDN variant gTLDs. Additionally, and separately, the ICANN Board anticipated adopting the IDN Guidelines v. 4.0 as part of its consent agenda for the 3 May 2019 meeting, but the GNSO Council requested [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> that the vote be deferred, due in part to concerns around the process, as well as specific requirements within the guidelines (e.g.,“same entity” requirement on second level registrations, which are in both the guidelines and the Variant TLD Recommendations). The ICANN Board agreed [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> to the deferral, allowing the GNSO Council additional time to consider the matter. The Council convened an IDN Scoping Team, comprised of Councilors and other GNSO members, to consider the scope of issues (e.g., IDN Guidelines and IDN Variant Management solutions) related to IDNs and accordingly, recommend a mechanism to address those issues (e.g., leverage existing PDPs, convene new PDP/EPDP, other). The IDN Scoping Team has thoroughly considered the scope of work that needs to be undertaken and accordingly, what mechanisms make the most sense to address. Most members of the IDN Scoping Team believe that two tracks of work can be undertaken: * Operational Track 1: In brief, a Contracted Party working/negotiation/implementation team would focused on IDN Implementation Guidelines 4.0 operational issues * Policy Track 2: In brief, a PDP/EPDP should be initiated and would have a scope including the definitions, management, and coordination issues related to IDN Variant TLDs, as well as IDN variants at the second-level. Additionally, this track would consider the related issue of how the IDN Implementation Guidelines, which Contracted Parties are required to comply with, should be revised in the future. The IDN Scoping Team shared the report [INSERT LINK} with the Council mailing list on [date]. Here, the Council will discuss the IDN Scoping Team’s recommendations report. 7.1 – Introduction of topic (Council Leadership; Edmon Chung, Scoping Team Lead) 7.2 – Update and council discussion 7.3 – Next step Item 8: ANY OTHER BUSINESS (10 minutes) 8.1 - ICANN67 Planning 8.2 - Council response [INSERT LINK] to the NomCom Review Implementation Working Group’s request for input on 27 recommendations. 8.3 - Council consideration of proposed GNSO Council Additional Budget Requests (ABRs) for FY21; review draft ABRs for the FY21 Strategic Planning Session [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> and Travel support for PDP Leadership to ICANN Public Meetings. [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> _______________________________ 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 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. 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… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> References for Coordinated Universal Time of 22:00 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 14:00 San José, Costa Rica (CST) UTC-6 16:00 New York/Washington DC, USA (EST) UTC-5 17:00 Buenos Aires, Argentina (ART) UTC-3 19:00 Rio de Janeiro, Brazil (BRST) UTC-2 21:00 London, United Kingdom (GMT) UTC+0 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 23:00 Paris, France (CET) UTC+1 23:00 Islamabad, Pakistan (PKT) (+1 day) UTC+5 03:00 Singapore (SGT) (+1 day) UTC+8 06:00 Tokyo, Japan (JST) (+1 day) UTC+9 07:00 Melbourne, Australia (AEDT) (+1 day) UTC+11 09: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 [timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_&d=…> and https://tinyurl.com/vjx8bub [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_vjx8bub&d=…>

1 0

For your review: Updated GNSO project list
by Andrea Glandon 16 Jan '20

16 Jan '20

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! Andrea Glandon GNSO SO/AC Support Internet Corporation for Assigned Names and Numbers (ICANN) Email: andrea.glandon(a)icann.org<mailto:andrea.glandon@icann.org> Skype ID: acglandon76 Find out more about the GNSO by visiting: https://learn.icann.org/ [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 [twitter.com]<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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global Calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 0

FYI: 16 January 2020
by Michelle DeSmyter 16 Jan '20

16 Jan '20

FYI: [http://r20.rs6.net/on.jsp?ca=2ea6dc8c-d01d-4d38-9209-86555d62b00e&a=1122025…] Thursday, 16 January 2020 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: Register for ICANN67 Prep Week Webinars · REMINDER: FY21 SO/AC Additional Budget Request Process · REMINDER: ICANN Fellowship Program Mentors ICANN67 Planning · TOMORROW: CROP Deadline for ICANN67 · REMINDER: ICANN67 Publication Support · REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Public Comment · Proposal for Future Root Zone KSK Rollovers · Third Accountability and Transparency Review Team (ATRT3) Draft Report · Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022 · Proposed Amendment 3 to the .COM Registry Agreement · Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group · Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget Information Sharing NEW: Register for ICANN67 Prep Week Webinars Executive: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING ICANN org released the schedule for ICANN67 Prep Week [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>, which features a series of nine webinars to prepare the community ahead of the upcoming Community Forum. Register and submit questions by Friday, 14 February 2020. REMINDER: FY21 SO/AC Additional Budget Request Process Executive: Xavier Calvez, Chief Financial Officer 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 Executive: Sally Costerton, Senior Vice President, Global Stakeholder Engagement 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 TOMORROW: CROP Deadline for ICANN67 Executive: David Olive, Senior Vice President, Policy Development Support 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. REMINDER: ICANN67 Publication Support Executive: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING 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 required design assistance, 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: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives 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. Public Comment 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 Third Accountability and Transparency Review Team (ATRT3) Draft Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 11 February 2020 Proposed Amendment 3 to the .COM Registry Agreement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 14 February 2020 Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 14 February 2020 Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 25 February 2020 Volume 2, Issue 5 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 20 January 2020 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

Final Proposed Agenda GNSO Council Meeting - 23 January 2020 at 22:00 UTC
by Nathalie Peregrine 15 Jan '20

15 Jan '20

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 23 January 2020 at 22:00 UTC. Draft GNSO Council Agenda 23 January 2020 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/7gCJBw 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 22:00 UTC Coordinated Universal Time: 22:00 UTC: https://tinyurl.com/vjx8bub 14:00 Los Angeles; 17:00 Washington DC; 22:00 London; (Friday) 03:00 Islamabad; (Friday) 07:00 Tokyo; (Friday) 09: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<https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-gnso…> of the GNSO Council meeting on the 19 December 2019 were posted on 02 January 2020 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/display/gnsocouncilmeetings/Motions+23+January+…> to approve the nomination of Amr Elsadr to serve as the ICANN Fellowship Program mentor. * Confirmation of Johan Helsingius as the Chair and Carlton Samuels as Vice-Chair for the GNSO Standing Selection Committee (SSC). Item 4: COUNCIL VOTE – Vote 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 the 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<https://gnso.icann.org/sites/default/files/file/field-file-attach/rpms-char…> for GNSO Council consideration. The GNSO Council reviewed and discussed the draft at the December 2019 Council meeting. A revised draft was prepared and shared on the Council mailing list. Here, the Council will vote to adopt the Addendum to the RPMs PDP charter. 4.1 – Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+23+January+…> (Council leadership) 4.2 – Council discussion 4.3 – Council vote (voting threshold: Simple majority) 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 UPDATE – Review of All Rights Protection Mechanisms in All gTLDs PDP (15 minutes) Chartered in March 2016 to review all the RPMs that have been developed by ICANN, the PDP is focused on RPMs developed for the 2012 New gTLD Program (i.e., Trademark Clearing House, Sunrise, Claims, and Uniform Rapid Suspension). The WG is tasked with considering the overarching issue as to whether or not the RPMs collectively fulfil their purposes or whether additional policy recommendations will be necessary. The PDP has worked diligently since launch and is preparing to publish its Initial Report for public comment. As of ICANN64, the WG had expected to be able to publish its Initial Report at the beginning of 2020. The WG is currently revisiting sub team and individual URS proposals and, when completed, will proceed to the development of its Phase One Initial Report, with a plan to publish in March of 2020. As a result of this delay in timeline, the PDP has submitted a Project Change Request [INSERT LINK] and this update is intended to both inform and gain approval from the GNSO Council. Here, the Council will consider the Project Change Request. 5.1 – Introduction of topic (Council leadership; John McElwaine, GNSO Council liaison to the PDP) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL UPDATE – Cross-Community Working Group on new gTLD Auction Proceeds (15 minutes) This CCWG was chartered to develop a mechanism to allocate new gTLD Auction Proceeds. The CCWG is expected to consider the scope of fund allocation, due diligence requirements that preserve ICANN’s tax status as well as how to deal with directly related matters such as potential or actual conflicts of interest. The CCWG will not make any recommendations or determinations with regards to specific funding decisions (i.e. which specific organizations or projects are to be funded or not). The CCWG published its Initial Report for public comment on 8 October 2018 that later closed 11 December 2018 after requests for extension. 37 community submissions were received (see https://www.icann.org/en/system/files/files/report-comments-new-gtld-auctio…). After additional deliberations, a decision was made to publish the CCWG’s Proposed Final Report for public comment<https://www.icann.org/public-comments/new-gtld-auction-proceeds-final-2019-…> to ensure that the community can review and provide input on changes that have been made since publication of the Initial Report. Input received through the second public comment period will be reviewed and incorporated as appropriate before the Final Report is published. The purpose of this update is to ensure that the GNSO Council, as a Chartering Organization, is familiar with the expected recommendations, but also to determine whether it might make sense for the Council to submit a public comment (14 February 2020 deadline). Here, the Council will consider the proposed final recommendations and consider whether a public comment on behalf of the Council is warranted. 6.1 – Introduction of topic (Council leadership; Erika Mann, Chair of the CCWG) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL UPDATE – IDN Scoping Small Team (15 minutes) The ICANN Board resolved in 2010 that IDN variant TLDs will not be delegated until relevant work is completed and directed ICANN org to develop a report identifying what needs to be done with the evaluation, possible delegation, allocation and operation of generic top-level domains (gTLDs) containing variant characters IDNs, in order to facilitate the development of workable approaches to the deployment of gTLDs containing variant characters IDNs. Based on analysis, ICANN org and the community identified two gaps to address: 1) that there is no definition of IDN variant TLDs, and; 2) that there is no IDN variant TLD management mechanism. The Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels<https://www.icann.org/en/system/files/files/lgr-procedure-20mar13-en.pdf> (RZ-LGR Procedure) has been developed by the community to define the IDN variant TLDs and, following the Board resolution<https://www.icann.org/resources/board-material/resolutions-2013-04-11-en#2.a> in 2013 which approved the RZ-LGR Procedure, has been implemented to incrementally develop the Root Zone Label Generation Rules to address the first gap. ICANN org has developed the Recommendations for Managing IDN Variant TLDs<https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-…> (the Variant TLD Recommendations), a collection of six documents finalized after incorporating the public comment feedback and published them as mechanisms for addressing the second gap identified by the community in the implementation of IDN variant TLDs. On 14 March 2019, the ICANN Board resolved<https://www.icann.org/resources/board-material/prelim-report-2019-03-14-en#…>: The Board approves the Variant TLD Recommendations and requests that the ccNSO and GNSO take into account the Variant TLD Recommendations while developing their respective policies to define and manage the IDN variant TLDs for the current TLDs as well as for future TLD applications. The Board requests that the ccNSO and GNSO keep each other informed of the progress in developing the relevant details of their policies and procedures to ensure a consistent solution, based on the Variant TLD Recommendations, is developed for IDN variant ccTLDs and IDN variant gTLDs. Additionally, and separately, the ICANN Board anticipated adopting the IDN Guidelines v. 4.0 as part of its consent agenda for the 3 May 2019 meeting, but the GNSO Council requested<https://gnso.icann.org/sites/default/files/file/field-file-attach/drazek-to…> that the vote be deferred, due in part to concerns around the process, as well as specific requirements within the guidelines (e.g.,“same entity” requirement on second level registrations, which are in both the guidelines and the Variant TLD Recommendations). The ICANN Board agreed<https://www.icann.org/en/system/files/correspondence/chalaby-to-drazek-04ju…> to the deferral, allowing the GNSO Council additional time to consider the matter. The Council convened an IDN Scoping Team, comprised of Councilors and other GNSO members, to consider the scope of issues (e.g., IDN Guidelines and IDN Variant Management solutions) related to IDNs and accordingly, recommend a mechanism to address those issues (e.g., leverage existing PDPs, convene new PDP/EPDP, other). The IDN Scoping Team has thoroughly considered the scope of work that needs to be undertaken and accordingly, what mechanisms make the most sense to address. Most members of the IDN Scoping Team believe that two tracks of work can be undertaken: * Operational Track 1: In brief, a Contracted Party working/negotiation/implementation team would focused on IDN Implementation Guidelines 4.0 operational issues * Policy Track 2: In brief, a PDP/EPDP should be initiated and would have a scope including the definitions, management, and coordination issues related to IDN Variant TLDs, as well as IDN variants at the second-level. Additionally, this track would consider the related issue of how the IDN Implementation Guidelines, which Contracted Parties are required to comply with, should be revised in the future. The IDN Scoping Team shared the report [INSERT LINK} with the Council mailing list on [date]. Here, the Council will discuss the IDN Scoping Team’s recommendations report. 7.1 – Introduction of topic (Council Leadership; Edmon Chung, Scoping Team Lead) 7.2 – Update and council discussion 7.3 – Next step Item 8: ANY OTHER BUSINESS (10 minutes) 8.1 - ICANN67 Planning 8.2 - Council response [INSERT LINK] to the NomCom Review Implementation Working Group’s request for input on 27 recommendations. 8.3 - Council consideration of proposed GNSO Council Additional Budget Requests (ABRs) for FY21; review draft ABRs for the FY21 Strategic Planning Session<https://gnso.icann.org/sites/default/files/file/field-file-attach/fy21-abr-…> and Travel support for PDP Leadership to ICANN Public Meetings.<https://gnso.icann.org/sites/default/files/file/field-file-attach/fy21-abr-…> _______________________________ 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 22:00 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 14:00 San José, Costa Rica (CST) UTC-6 16:00 New York/Washington DC, USA (EST) UTC-5 17:00 Buenos Aires, Argentina (ART) UTC-3 19:00 Rio de Janeiro, Brazil (BRST) UTC-2 21:00 London, United Kingdom (GMT) UTC+0 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 23:00 Paris, France (CET) UTC+1 23:00 Islamabad, Pakistan (PKT) (+1 day) UTC+5 03:00 Singapore (SGT) (+1 day) UTC+8 06:00 Tokyo, Japan (JST) (+1 day) UTC+9 07:00 Melbourne, Australia (AEDT) (+1 day) UTC+11 09: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/vjx8bub

1 0