February 2021 - council - lists.icann.org

Re: [council] [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart - EPDP on the Temp Spec for gTLD Registration Data Phase 2
by philippe.fouquart＠orange.com 22 Feb '21

22 Feb '21

Dear Councillors, In preparation for our call with the board on Monday, please have a thought the specific aspects you would like to raise in relation to the launch of the ODP for the SSAD, and share them with the list if you can. For example, as it relates to the Maarten’s letter below, there seems to be a difference of appreciation on the aspects which the operational assessment is expected to cover, as identified in Council’s previous letter https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…. The Council suggests that the operational impact assessment would cover, at a minimum, the following aspects: · Expected costs / resources; · Expected benefits; · Expected time-to-market; · Possible business risks; · Possible legal risks; · Possible reputational risks; · Implementation considerations (e.g., outsourcing or phased deployment of the solution); · Opportunity Costs (e.g., what projects, if any, would be put on hold or not move forward to implement the SSAD). Thanks. Regards, Philippe From: FOUQUART Philippe TGI/OLN Sent: Friday, February 19, 2021 4:29 PM To: council(a)gnso.icann.org Subject: FW: [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart - EPDP on the Temp Spec for gTLD Registration Data Phase 2 Dear Councillors, Please note the attached response on our EPDP phase 2 letter to the board in advance of our call next week. This is mostly relative to how we approach the discussion, but I’ll quote the part that deals with the remit of this ODP. The Board also would like to remind the Council that the purpose of the ODP is to assess the operational impact of the SSAD-related policy recommendations on ICANN org and to inform the Board of these impacts prior to the Board's consideration of the policy recommendations. The ODP is not intended to determine whether the concept of the SSAD accounts for the cost and effort required to implement the proposed system. We believe this specific question has been addressed by the Council in approving the recommendations and forwarding them to the Board. Best regards, Philippe From: Gnso-chairs [mailto:gnso-chairs-bounces@icann.org] On Behalf Of Wendy Profit via Gnso-chairs Sent: Friday, February 19, 2021 2:50 AM To: gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>; gnso-secs(a)icann.org<mailto:gnso-secs@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>>; Board Ops Team <board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart - EPDP on the Temp Spec for gTLD Registration Data Phase 2 Dear Philippe Fouquart, Please find the attached letter from Maarten Botterman regarding the EPDP on the Temporary Specification for gTLD Registration Data Phase 2. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

5 9

FW: [Ext] Monday, 22 February 2021
by Andrea Glandon 22 Feb '21

22 Feb '21

[http://r20.rs6.net/on.jsp?ca=8ab50c44-38d7-459d-b375-7763c3aff857&a=1122025…] Monday, 22 February 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents Information Sharing · HAPPENING TODAY: ICANN Board Consultation with the GNSO Council on the SSAD · REMINDER: FY23 Strategic Outlook Program: Trend Identification Sessions · REMINDER: ICANN Nominating Committee Application Period Now Open · REMINDER: ICANN Community Excellence Award Nomination Period Now Open ICANN70 Planning · DUE THIS WEEK: ICANN Board Interactions with Stakeholders during ICANN70 · DUE THIS WEEK: ICANN org Finance and Planning Updates during ICANN70 · REMINDER: ITI Demonstrations during ICANN70 · REMINDER: ICANN70 Publication Support · REMINDER: Participate in "Newcomers Introduction to ICANN Communities" Webinar · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program ICANN70 Resources · Registration · Virtual Backgrounds Public Comment · Second Security, Stability, and Resiliency (SSR2) Review Team Final Report · Additional Reference Label Generation Rulesets (LGRs) for the Second Level · IANA Naming Function Review: Recommendation for an IANA Naming Function Contract Amendment · EPDP Phase 2 Policy Recommendations for Board Consideration Information Sharing HAPPENING TODAY: ICANN Board Consultation with the GNSO Council on the SSAD From: David Olive, Senior Vice President, Policy Development Support The ICANN Board will be meeting with the GNSO Council to discuss the Standardized System for Access/Disclosure ("SSAD"). The consultation is to support ICANN Board consideration of SSAD-related recommendations. Observers are welcome to attend but will not have speaking or chat capabilities during the meeting. Monday, 22 February 2021 | 19:00 UTC Zoom room [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> Passcode: AqUyLw#=1s REMINDER: FY23 Strategic Outlook Program: Trend Identification Sessions From: Xavier Calvez, Senior Vice President, Planning and Chief Financial Officer ICANN is kicking off the FY23 Strategic Outlook trend identification process. ICANN community members will have the opportunity to participate in trend identification sessions via their Supporting Organization (SO) or Advisory Committee (AC). ICANN org will collaborate with SO and AC chairs and support teams to schedule their sessions over the next few weeks. We are targeting to complete the trend sessions by the end of March. All strategic outlook sessions will be conducted virtually. ICANN community members are encouraged to join this important discussion. Once complete, ICANN org will conduct a trend analysis and impact assessment. The Strategic Outlook Program is a joint effort of ICANN org, community, and Board to identify and track trends that are related to ICANN. This ensures that these opportunities and challenges are incorporated into current and future planning. Every year, new trends or shifts in existing trends impacting the operating plans (five-year or annual) and/or budget are factored into the annual iteration of those plans as appropriate. Significant shifts could also result in adjustments to the strategic plan. We look forward to your participation in this dialogue about ICANN planning and strategy. REMINDER: ICANN Nominating Committee Application Period Now Open The ICANN Nominating Committee invites interested individuals to submit applications for key leadership positions. Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the Internet's technical coordination and policy development. The deadline to submit applications is Thursday, 18 March 2021 at 23:59 UTC. Applications should be submitted via the online [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…>candidate portal [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…>. All applications are confidential. Learn more. [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> REMINDER: ICANN Community Excellence Award Nomination Period Now Open From: David Olive, Senior Vice President, Policy Development Support The nomination period for the ICANN Community Excellence Award 2020 is now open. The winner(s) will be announced during ICANN71. The ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within ICANN’s multistakeholder model. Learn more about the nomination process [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> and submit your nominations here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> by Monday, 29 March 2021. ICANN70 Planning DUE THIS WEEK: ICANN Board Interactions with ICANN Communities during ICANN70 From: ICANN Board Chair Maarten Botterman Dear ICANN community chairs, First of all, let me take the opportunity to reiterate on behalf of the ICANN Board, our best wishes to you and your families for a healthy 2021. We have all been very affected (and still are) by this long-lasting pandemic and will never spread enough of those positive thoughts and messages of hope for a brighter future! We very much look forward to seeing you in person, hopefully later this year, even if today it is not possible to predict when it will be responsible to do so again. The ICANN Board has recently been briefed thoroughly on your input to the ICANN Public Meetings Strategy and wanted to thank you all for your constructive contribution to this important survey. The suggested changes will be implemented by ICANN org, and the ICANN Board will of course actively participate in the dialogue to find the best possible way forward in this, together. ICANN70 will mark the next step. In line with the decision to organize ICANN70 virtually and considering the current global situation with regard to the pandemic, various communities are arranging different times to engage the ICANN Board, either before, during or after ICANN70. We have learned to appreciate the opportunity to have this conversation during ICANN Public Meetings, and the survey conducted after ICANN69 confirmed that you do as well. Up until ICANN69, the ICANN Board has proposed a subject to you to discuss during our joint meetings. For ICANN70, we would like to invite you to propose questions for the ICANN Board to answer, or a subject to engage in an open discussion during our time together. Please note that we are not changing the current total time allotted per community. Please send your single topic or list of questions in order of priority to the Board Operations team, board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>, no later than Friday, 26 February 2021. Your suggested questions or topic for discussion will be published and circulated in this digest, which will facilitate transparency and allow all communities to deepen their understanding of community issues and different points of view. We look forward to hearing your thoughts, questions, or topics of interest and to exchange with you constructively. Best regards, Maarten Botterman ICANN Board Chair DUE THIS WEEK: ICANN70 Publication Support Translation-only Deadline For translation, please provide the final material(s) by Friday, 26 February 2021. This ensures that there is enough time to translate the publication. If the publication requires 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. Please work directly with your support team to submit these requests to evin.erdogdu(a)icann.org<mailto:evin.erdogdu@icann.org> and liana.teo(a)icann.org<mailto:liana.teo@icann.org>. REMINDER: ICANN org Finance and Planning Updates during ICANN70 From: Xavier Calvez, Senior Vice President, Planning and Chief Financial Officer The ICANN org Finance and Planning teams seek opportunities to engage with the ICANN communities during ICANN70 or via webinars to present a short updates on finance- and planning-related topics: Finance · Financial Results: FY20 and FY21 Year-to-Date · Accountability and transparency reporting Planning · Draft FY22-FY26 Five-Year Operating Plan and Financial Plan · Draft FY22 Operating Plan and Budget · Review of Public Comment submissions and next steps in the planning process · FY23 Planning Process and Strategic Outlook Trends Please contact becky.nash(a)icann.org to request a briefing and please let us know if you have any other finance and planning topics. Thank you in advance for your support, and we appreciate your assistance. REMINDER: ITI Demonstrations during ICANN70 The Information Transparency Initiative (ITI) Team invites ICANN communities to request a demonstration of upcoming improvements to https://icann.org [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> during ICANN70. ITI is an operational activity to improve content governance and infrastructure at ICANN. Since its inception, the ITI team has sought community input through the feedback website [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…>, sessions during ICANN Public Meetings, webinars, and smaller, informal sessions targeted to specific user groups. This feedback is vital to ensuring ITI delivers the improvements needed to more easily find content on https://icann.org [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…>. The ITI team has implemented changes based on community feedback. Please contact carlos.reyes(a)icann.org to request a demonstration. Thank you. REMINDER: Participate in "Newcomers Introduction to ICANN Communities" Webinar The Public Responsibility Support function seeks speakers from ICANN communities to participate in an introductory webinar for newcomers. Each each speaker will have 5-10 minutes to provide an overview of their ICANN community. The webinar will take place Monday, 8 March 2021, 17:30-19:00 UTC. Sign up [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> by Monday, 1 March 2021. Please contact deborah.escalera(a)icann.org with any questions. Thank you. REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program The Pandemic Internet Access Reimbursement Program aims to facilitate participation in ICANN Public Meetings during the COVID-19 pandemic, including the upcoming ICANN70 Virtual Community Forum. It offers financial assistance to ICANN community members who have limited Internet capacity to increase their Internet bandwidth. ICANN community members interested in the Pandemic Internet Access Reimbursement Program must apply in advance of ICANN70. Those who meet the eligibility requirements will be selected to participate. Nominations ICANN community leaders will have the opportunity to nominate recipients. This includes up to five nominees from each of the three Supporting Organizations, four Advisory Committees, four GNSO Stakeholder Groups and five GNSO Constituencies, and five RALOs from At-Large. In order to be reimbursed, all applicants must: · Require additional bandwidth at home to facilitate their active participation during ICANN70. · Have a valid personal bank account for ICANN org to wire the reimbursement funds. · Register [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> for ICANN70. · Attend a minimum of four official ICANN70 sessions. Once ICANN community leaders have established their nominees, they can inform their nominees to apply for the program here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> beginning Monday, 8 February 2021. Chairs should send their list to travelsupport(a)icann.org<mailto:travelsupport@icann.org> so that ICANN org can verify the applications. Chairs and community leaders will have until Monday, 1 March 2021 to complete this nomination process. All applications are due by Friday, 5 March 2021. Learn more. [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> ICANN70 Resources Registration [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> Public Comment Second Security, Stability, and Resiliency (SSR2) Review Team Final Report [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> Close Date: Tuesday, 9 March 2021 Additional Reference Label Generation Rulesets (LGRs) for the Second Level [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> Close Date: Thursday, 11 March 2021 IANA Naming Function Review: Recommendation for an IANA Naming Function Contract Amendment [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> Close Date: Monday, 22 March 2021 EPDP Phase 2 Policy Recommendations for Board Consideration [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> Close Date: Tuesday, 30 March 2021 Volume 3, Issue 15 | Archive [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001f9R4467_CXbJt1nYH…> | Next Issue: Thursday, 25 February 2021

1 0

FW: [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart - EPDP on the Temp Spec for gTLD Registration Data Phase 2
by philippe.fouquart＠orange.com 19 Feb '21

19 Feb '21

Dear Councillors, Please note the attached response on our EPDP phase 2 letter to the board in advance of our call next week. This is mostly relative to how we approach the discussion, but I’ll quote the part that deals with the remit of this ODP. The Board also would like to remind the Council that the purpose of the ODP is to assess the operational impact of the SSAD-related policy recommendations on ICANN org and to inform the Board of these impacts prior to the Board's consideration of the policy recommendations. The ODP is not intended to determine whether the concept of the SSAD accounts for the cost and effort required to implement the proposed system. We believe this specific question has been addressed by the Council in approving the recommendations and forwarding them to the Board. Best regards, Philippe From: Gnso-chairs [mailto:gnso-chairs-bounces@icann.org] On Behalf Of Wendy Profit via Gnso-chairs Sent: Friday, February 19, 2021 2:50 AM To: gnso-chairs(a)icann.org; gnso-secs(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: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart - EPDP on the Temp Spec for gTLD Registration Data Phase 2 Dear Philippe Fouquart, Please find the attached letter from Maarten Botterman regarding the EPDP on the Temporary Specification for gTLD Registration Data Phase 2. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

GNSO Council resolutions 18 February 2021
by Nathalie Peregrine 18 Feb '21

18 Feb '21

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday 18 February 2021 which will be posted shortly on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> page. 20210218 – 1 Consent agenda * Confirmation of Philippe Fouquart to serve as the GNSO Council liaison to the EPDP 2A. * Non-objection from the Council for the EPDP Team to appoint a non-EPDP Team member as vice-chair. * Confirmation of the Recommendations Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/council-r…> to the ICANN Board regarding adoption of all recommendations from the Phase 1 Final Report of the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs PDP. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> Initiation of a Policy Development Process to Review the Transfer Policy Submitted by: Pam Little Seconded by: Carlton Samuels Whereas, 1. The GNSO Council issued a call for volunteers for a Transfer Policy Review Scoping Team on October 3, 2019<https://mm.icann.org/pipermail/council/2019-October/023097.html>. The Scoping Team was tasked with providing recommendations on the approach to a potential review and future policy work related to the Transfer Policy; composition of the review team or PDP working group; and scope of the review; 2. The Transfer Policy Review Scoping Team delivered aTransfer Policy Initial Scoping Paper<https://gnso.icann.org/sites/default/files/file/field-file-attach/transfer-…> on April 6, 2020 in which it recommended the GNSO Council instruct ICANN Policy staff to draft a Preliminary Issue Report, outlining, et. , the issues described within the Transfer Policy Initial Scoping Paper; 3. On 24 June 2020 the GNSO Council requested preparation of a Preliminary Issue Report, for delivery as expeditiously as possible, on the issues identified in the Transfer Policy Initial Scoping Paper<https://gnso.icann.org/sites/default/files/file/field-file-attach/transfer-…>, to assist in determining whether a PDP or series of PDPs should be initiated regarding changes to the Transfer Policy; 4. On 20 August 2020, the GNSO Council agreed to extend the timeline for delivery of the Issue Report to 10 October 2020; 5. ICANN staff published the Preliminary Issue Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/prelimina…> on a Policy Development Process to Review the Transfer Policy for public comment on 12 October 2020, with the public comment forum closing on 30 November 2020; 6. ICANN staff have reviewed the public comments<https://www.icann.org/public-comments/transfer-policy-pdp-review-2020-10-12…> received, published a Report of Public Comments<https://www.icann.org/en/system/files/files/report-comments-transfer-policy…> on 14 December 2020 and updated the Issue Report accordingly; 7. The Final Issue Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-iss…> on a Policy Development Process to Review the Transfer Policy was delivered to the GNSO Council on 12 January 2021; 8. The Final Issue Report includes a recommendation that the GNSO Council proceed with a two-phased Policy Development Process (PDP) that will address the following topic areas in sequence: * Phase 1(a): Form of Authorization (including Rec. 27, Wave 1 FOA issues) and AuthInfo Codes * Phase 1(b): Change of Registrant (including Rec. 27, Wave 1 Change of Registrant issues) * Phase 2: Transfer Emergency Action Contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy (including Rec. 27, Wave 1 TDRP issues), NACKing transfers, ICANN-approved transfers 9. The General Counsel of ICANN has indicated that the topics recommended for review are properly within the scope of the ICANN policy process and the GNSO. RESOLVED: 1. The GNSO Council hereby initiates a two-phased PDP to Review the Transfer Policy which will determine if changes to the policy are needed to improve the ease, security, and efficacy of inter-registrar and inter-registrant transfers. 2. The GNSO Council requests that the PDP Working Group be convened as soon as possible after the adoption of the PDP Working Group Charter in order to fulfill the requirements of this PDP. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> Adoption of the Policy Development Process on New gTLD Subsequent Procedures Final Report Submitted by: Flip Petillion Seconded by: Kurt Pritz WHEREAS 1. On 17 December 2015 the GNSO Council resolved to initiate<https://gnso.icann.org/en/council/resolutions#201512> a PDP to consider and analyze issues discussed in the Final Issue Report on New gTLD Subsequent Procedures (SubPro PDP) to determine whether changes or adjustments to the existing policy recommendations in the Final Report on the Introduction of New Generic Top-Level Domains from 08 August 2007 are needed. 2. On 21 January 2016 the GNSO Council approved<https://gnso.icann.org/en/council/resolutions#201601> the Charter for the SubPro PDP and directed ICANN staff to issue a call for volunteers for the SubPro PDP Working Group. 3. After initiating a call for community comment in June of 2016 (Community Comment 1), the SubPro PDP divided its work into four Work Tracks culminating in a second call for community comment (Community Comment 2) in March of 2017, that provided an insight into the work of each of the initial four Work Tracks, and asked a series of questions of the community for further consideration. 4. In November of 2017, a fifth Work Track (WT5) was created solely for the purpose of examining the issues related to Geographic Names as the Top Level. In recognition of the broad interest in the topic and to encourage participation from the ICANN community, it was set up to include four WT5 leaders, one each from the GNSO, ccNSO, GAC and At-Large. 5. The SubPro PDP has followed the prescribed PDP steps as stated in the Bylaws, including the publication of the following Reports for public comment: * an Initial Report<https://www.icann.org/public-comments/gtld-subsequent-procedures-initial-20…> on 08 July 2018 for public comment. * a Supplemental Initial Report<https://www.icann.org/public-comments/new-gtld-subsequent-procedures-supp-i…> on 30 October 2018, covering certain issues not included in the Initial Report. * a Supplemental Initial Report <https://www.icann.org/public-comments/geo-names-wt5-initial-2018-12-05-en> on Geographic Names at the Top Level on 5 December 2018. * a Draft Final Report<https://www.icann.org/public-comments/gnso-new-gtld-subsequent-draft-final-…> on 20 August 2020. 6. On 18 January 2021, the SubPro PDP Working Group submitted its Final Report to the Council for its consideration. 7. On 21 January 2021, the GNSO Council received a high-level briefing of the Final Report by the GNSO Council Liaison to the SubPro PDP Working Group. 8. On 28 January 2021, the GNSO Council Liaison to the SubPro PDP Working Group and its Co-Chairs held a webinar, directed at the GNSO Council, to discuss the Final Report’s 41 Topics, which included hundreds of Affirmations, Recommendations and Implementation Guidance (Collectively referred to as “Outputs”) in more detail. 9. Each of the Outputs in the following topics obtained a Full Consensus designation (Topics 1, 5, 6, 7, 8, 10, 11, 13, 14, 16, 19, 20, 22, 23, 25, 26, 28, 31, 32, 33, 36, 37, 38, 39, and 40). 10. Each of the following topics received an overall designation of Consensus, with all of the Outputs obtaining at least a Consensus designation (Topics 2, 3, 4, 9, 12, 15, 17, 18, 21, 24, 27, 29, 30, 34, and 41). 11. One Topic obtained a Strong Support but Significant Opposition designation (#35); However, within that one Topic, three of the five Outputs obtained a Consensus designation, and two of the five Outputs, Recommendations 35.2 and 35.4, obtained the designation Strong Support but Significant Opposition. 12. While not seeking to affirm that the status quo prevails in any particular instance, the GNSO Council notes that the Working Group operated under the assumption that, in the event the Working Group was unable to reach consensus in recommending an alternate course of action, the “status quo” should remain in place as a default position, with the status quo consisting of the 2007 policy, the final Applicant Guidebook, and any implementation elements that were put into practice in the 2012 application round. 13. The GNSO Council notes that Topic 23: Closed Generics was identified as an Output category of No Agreement, which did achieve Full Consensus. However, the GNSO Council believes No Agreement is functionally equivalent to the designation of Divergence as detailed in the GNSO Working Group Guidelines, meaning that the Working Group was unable to reach consensus in recommending an alternate course of action. The GNSO Council further notes that especially as it relates to Topic 23: Closed Generics, there were diverging interpretations within the Working Group of what constitutes the “status quo”. 14. Given the large number of topics and the interdependency of many of the subjects, the SubPro PDP Working Group recommends that all Outputs be considered as one package by the GNSO Council and subsequently the ICANN Board, notwithstanding any Outputs that did not achieve Consensus or Full Consensus. RESOLVED 1. The GNSO Council approves, and recommends that the ICANN Board adopt, the Affirmations, Recommendations, and Implementation Guidance (Collectively referred to as “Outputs”) that were determined to have received either Full Consensus or Consensus designations as documented in the SubPro PDP Working Group's Final Report 2. Recognizing that nearly a decade has passed since the opening of the 2012 round of new gTLDs, the GNSO Council requests that the ICANN Board consider and direct the implementation of the Outputs adopted by the GNSO Council without waiting for any other proposed or ongoing policy work unspecific to New gTLD Subsequent Procedures to conclude, while acknowledging the importance of such work. 3. Further, the GNSO Council requests that the ICANN Board initiate an Operational Design Phase on the Final Report of the SubPro Working Group and its Outputs as soon as possible, to perform an assessment of GNSO Council recommendations in order to provide the Board with relevant operational information to facilitate the Board’s determination, in accordance with the Bylaws, on the impact of the operational impact of the implementation of the recommendations, including whether the recommendations are in the best interests of the ICANN community or ICANN. 4. The GNSO Council requests that the ICANN Board convene an Implementation Review Team to work on the implementation of these Outputs. The Implementation Review Team will be tasked with assisting ICANN org in developing the implementation details for the New gTLD Program, evaluating the proposed implementation of the Outputs as approved by the Board, and working with ICANN staff to ensure that the resultant implementation conforms to the intent of the approved Outputs. The Implementation Review Team shall operate in accordance with the Implementation Review Team Principles and Guidance approved by the GNSO Council in June 2015. 5. The GNSO Council extends its sincere appreciation to the Co-Chairs, Cheryl Langdon-Orr and Jeffrey Neuman, as well as past Co-Chair Avri Doria, the SubPro PDP Work Track leaders, the SubPro Working Group members and support staff of the SubPro PDP for their tireless efforts these past five years to deliver this Final Report. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> Kind regards, Nathalie

1 1

Recordings, attendance & Zoom chat | GNSO Council meeting | Thursday, 18 February 2021 at 19:00 UTC
by Terri Agnew 18 Feb '21

18 Feb '21

Dear all, Please find below the audio recording, zoom recording (audio, visual, rough transcript) and chat of the GNSO Council meeting held on Thursday, 18 February 2021 at 19:00 UTC. Audio only: https://icann.zoom.us/rec/play/p5_Hwjm57UL9Zq_8j0AsJwJ_4WhFExEO_Gcuo8DljfVT… Zoom Recording (includes visual and rough transcript. To access the rough transcript, select the Audio Transcript tab): https://icann.zoom.us/rec/share/AkVM9z73pAhnsOIehLA49UM5UbEYv6-kPwU1CweypUL… Zoom chat: https://icann.zoom.us/rec/sdownload/4BV1VMkHTVqJ9Ds0_f-XIWBGe8ZSkTiYHc--1TM… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page<https://gnso.icann.org/en/group-activities/calendar>. With kind regards, Terri

1 0

SubPro Resolution Second and Amendment 2
by Flip Petillion 18 Feb '21

18 Feb '21

Dear Kurt and Councilors, Thank you, Kurt, for seconding the motion. Also, I consider the proposed amendments to be friendly. I have discussed some additional clarifications with Council Leadership and I hereby attach an amendment to the Motion. I attach a version with and a version without track changes (including Kurt’s and the additional amendments). Respectfully submitted, Flip Flip Petillion fpetillion(a)petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law [id:image001.png@01D3691D.DA7539C0]<https://www.petillion.law/> Attorneys – Advocaten – Avocats

2 1

FW: [Ext] Thursday, 18 February 2021
by Julie Bisland 18 Feb '21

18 Feb '21

FYI From: ICANN Community Leadership Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, February 18, 2021 at 10:01 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 18 February 2021 [http://r20.rs6.net/on.jsp?ca=640470d6-1fb1-4907-b975-e4ad1621deef&a=1122025…] Thursday, 18 February 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents Information Sharing · NEW: ICANN Board Consultation with the GNSO Council on the SSAD · REMINDER: FY23 Strategic Outlook Program: Trend Identification Sessions · REMINDER: ICANN Nominating Committee Application Period Now Open · REMINDER: ICANN Community Excellence Award Nomination Period Now Open ICANN70 Planning · REMINDER: ICANN Board Interactions with Stakeholders during ICANN70 · REMINDER: ICANN org Finance and Planning Updates during ICANN70 · REMINDER: ITI Demonstrations during ICANN70 · REMINDER: ICANN70 Publication Support · REMINDER: Participate in "Newcomers Introduction to ICANN Communities" Webinar · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program ICANN70 Resources · Registration · Virtual Backgrounds Public Comment · Second Security, Stability, and Resiliency (SSR2) Review Team Final Report · Additional Reference Label Generation Rulesets (LGRs) for the Second Level · IANA Naming Function Review: Recommendation for an IANA Naming Function Contract Amendment · EPDP Phase 2 Policy Recommendations for Board Consideration Information Sharing NEW: ICANN Board Consultation with the GNSO Council on the SSAD From: David Olive, Senior Vice President, Policy Development Support The ICANN Board will be meeting with the GNSO Council to discuss the Standardized System for Access/Disclosure ("SSAD"). The consultation is to support ICANN Board consideration of SSAD-related recommendations. Observers are welcome to attend but will not have speaking or chat capabilities during the meeting. Monday, 22 February 2021 | 19:00 UTC Zoom room [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> Passcode: AqUyLw#=1s REMINDER: FY23 Strategic Outlook Program: Trend Identification Sessions From: Xavier Calvez, Senior Vice President, Planning and Chief Financial Officer ICANN is kicking off the FY23 Strategic Outlook trend identification process. ICANN community members will have the opportunity to participate in trend identification sessions via their Supporting Organization (SO) or Advisory Committee (AC). ICANN org will collaborate with SO and AC chairs and support teams to schedule their sessions over the next few weeks. We are targeting to complete the trend sessions by the end of March. All strategic outlook sessions will be conducted virtually. ICANN community members are encouraged to join this important discussion. Once complete, ICANN org will conduct a trend analysis and impact assessment. The Strategic Outlook Program is a joint effort of ICANN org, community, and Board to identify and track trends that are related to ICANN. This ensures that these opportunities and challenges are incorporated into current and future planning. Every year, new trends or shifts in existing trends impacting the operating plans (five-year or annual) and/or budget are factored into the annual iteration of those plans as appropriate. Significant shifts could also result in adjustments to the strategic plan. We look forward to your participation in this dialogue about ICANN planning and strategy. REMINDER: ICANN Nominating Committee Application Period Now Open The ICANN Nominating Committee invites interested individuals to submit applications for key leadership positions. Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the Internet's technical coordination and policy development. The deadline to submit applications is Thursday, 18 March 2021 at 23:59 UTC. Applications should be submitted via the online [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…>candidate portal [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…>. All applications are confidential. Learn more. [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> REMINDER: ICANN Community Excellence Award Nomination Period Now Open From: David Olive, Senior Vice President, Policy Development Support The nomination period for the ICANN Community Excellence Award 2020 is now open. The winner(s) will be announced during ICANN71. The ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within ICANN’s multistakeholder model. Learn more about the nomination process [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> and submit your nominations here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> by Monday, 29 March 2021. ICANN70 Planning REMINDER: ICANN Board Interactions with ICANN Communities during ICANN70 From: ICANN Board Chair Maarten Botterman Dear ICANN community chairs, First of all, let me take the opportunity to reiterate on behalf of the ICANN Board, our best wishes to you and your families for a healthy 2021. We have all been very affected (and still are) by this long-lasting pandemic and will never spread enough of those positive thoughts and messages of hope for a brighter future! We very much look forward to seeing you in person, hopefully later this year, even if today it is not possible to predict when it will be responsible to do so again. The ICANN Board has recently been briefed thoroughly on your input to the ICANN Public Meetings Strategy and wanted to thank you all for your constructive contribution to this important survey. The suggested changes will be implemented by ICANN org, and the ICANN Board will of course actively participate in the dialogue to find the best possible way forward in this, together. ICANN70 will mark the next step. In line with the decision to organize ICANN70 virtually and considering the current global situation with regard to the pandemic, various communities are arranging different times to engage the ICANN Board, either before, during or after ICANN70. We have learned to appreciate the opportunity to have this conversation during ICANN Public Meetings, and the survey conducted after ICANN69 confirmed that you do as well. Up until ICANN69, the ICANN Board has proposed a subject to you to discuss during our joint meetings. For ICANN70, we would like to invite you to propose questions for the ICANN Board to answer, or a subject to engage in an open discussion during our time together. Please note that we are not changing the current total time allotted per community. Please send your single topic or list of questions in order of priority to the Board Operations team, board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>, no later than Friday, 26 February 2021. Your suggested questions or topic for discussion will be published and circulated in this digest, which will facilitate transparency and allow all communities to deepen their understanding of community issues and different points of view. We look forward to hearing your thoughts, questions, or topics of interest and to exchange with you constructively. Best regards, Maarten Botterman ICANN Board Chair REMINDER: ICANN org Finance and Planning Updates during ICANN70 From: Xavier Calvez, Senior Vice President, Planning and Chief Financial Officer The ICANN org Finance and Planning teams seek opportunities to engage with the ICANN communities during ICANN70 or via webinars to present a short updates on finance- and planning-related topics: Finance · Financial Results: FY20 and FY21 Year-to-Date · Accountability and transparency reporting Planning · Draft FY22-FY26 Five-Year Operating Plan and Financial Plan · Draft FY22 Operating Plan and Budget · Review of Public Comment submissions and next steps in the planning process · FY23 Planning Process and Strategic Outlook Trends Please contact becky.nash(a)icann.org to request a briefing and please let us know if you have any other finance and planning topics. Thank you in advance for your support, and we appreciate your assistance. REMINDER: ITI Demonstrations during ICANN70 The Information Transparency Initiative (ITI) Team invites ICANN communities to request a demonstration of upcoming improvements to https://icann.org [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> during ICANN70. ITI is an operational activity to improve content governance and infrastructure at ICANN. Since its inception, the ITI team has sought community input through the feedback website [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…>, sessions during ICANN Public Meetings, webinars, and smaller, informal sessions targeted to specific user groups. This feedback is vital to ensuring ITI delivers the improvements needed to more easily find content on https://icann.org [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…>. The ITI team has implemented changes based on community feedback. Please contact carlos.reyes(a)icann.org to request a demonstration. Thank you. REMINDER: ICANN70 Publication Support Translation-only Deadline For translation, please provide the final material(s) by Friday, 26 February 2021. This ensures that there is enough time to translate the publication. If the publication requires 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. Please work directly with your support team to submit these requests to evin.erdogdu(a)icann.org<mailto:evin.erdogdu@icann.org> and liana.teo(a)icann.org<mailto:liana.teo@icann.org>. REMINDER: Participate in "Newcomers Introduction to ICANN Communities" Webinar The Public Responsibility Support function seeks speakers from ICANN communities to participate in an introductory webinar for newcomers. Each each speaker will have 5-10 minutes to provide an overview of their ICANN community. The webinar will take place Monday, 8 March 2021, 17:30-19:00 UTC. Sign up [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> by Monday, 1 March 2021. Please contact deborah.escalera(a)icann.org with any questions. Thank you. REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program The Pandemic Internet Access Reimbursement Program aims to facilitate participation in ICANN Public Meetings during the COVID-19 pandemic, including the upcoming ICANN70 Virtual Community Forum. It offers financial assistance to ICANN community members who have limited Internet capacity to increase their Internet bandwidth. ICANN community members interested in the Pandemic Internet Access Reimbursement Program must apply in advance of ICANN70. Those who meet the eligibility requirements will be selected to participate. Nominations ICANN community leaders will have the opportunity to nominate recipients. This includes up to five nominees from each of the three Supporting Organizations, four Advisory Committees, four GNSO Stakeholder Groups and five GNSO Constituencies, and five RALOs from At-Large. In order to be reimbursed, all applicants must: · Require additional bandwidth at home to facilitate their active participation during ICANN70. · Have a valid personal bank account for ICANN org to wire the reimbursement funds. · Register [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> for ICANN70. · Attend a minimum of four official ICANN70 sessions. Once ICANN community leaders have established their nominees, they can inform their nominees to apply for the program here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> beginning Monday, 8 February 2021. Chairs should send their list to travelsupport(a)icann.org<mailto:travelsupport@icann.org> so that ICANN org can verify the applications. Chairs and community leaders will have until Monday, 1 March 2021 to complete this nomination process. All applications are due by Friday, 5 March 2021. Learn more. [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> ICANN70 Resources Registration [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> Public Comment Second Security, Stability, and Resiliency (SSR2) Review Team Final Report [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> Close Date: Tuesday, 9 March 2021 Additional Reference Label Generation Rulesets (LGRs) for the Second Level [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> Close Date: Thursday, 11 March 2021 IANA Naming Function Review: Recommendation for an IANA Naming Function Contract Amendment [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> Close Date: Monday, 22 March 2021 EPDP Phase 2 Policy Recommendations for Board Consideration [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> Close Date: Tuesday, 30 March 2021 Volume 3, Issue 14 | Archive [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001bxO2CXYRSmtx8CiZR…> | Next Issue: Monday, 22 February 2021

1 0

Final Proposed Agenda | GNSO Council Meeting 18 February 2021 at 19:00 UTC
by Nathalie Peregrine 17 Feb '21

17 Feb '21

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 18 February 2021 at 19:00 UTC. Draft GNSO Council Agenda 18 February 2021 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/QwtACQ This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 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 19:00 UTC Coordinated Universal Time: 19:00 UTC: https://tinyurl.com/yxdh3opz 11:00 Los Angeles; 14:00 Washington; 19:00 London; 20:00 Paris; 22:00 Moscow; (Friday) 06:00 Melbourne GNSO Council Meeting Remote Participation: 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/2020/minutes/minutes-gnso…> of the GNSO Council meeting on 17 December 2020 were posted on 3 January 2021. Minutes of the GNSO Council meeting on 21 January 2021 were posted on 4 February 2021. Item 2: Opening Remarks / Review of Projects & Action List (10 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 (5 minutes) 3.1 - Confirmation of of SSC selection processes: * Confirmation of Philippe Fouquart to serve as the GNSO Council liaison to the EPDP 2A. * Non-objection from the Council for the EPDP Team to appoint a non-EPDP Team member as vice-chair. * Confirmation of the Recommendations Report [LINK TO BE ADDED UPON RECEIPT] to the ICANN Board regarding adoption of all recommendations from the Phase 1 Final Report of the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs PDP. * Per the incoming letter [LINK TO BE ADDED UPON RECEIPT] from the IANA Naming Function Review Team (IFRT), approval of the IFRT’s Recommendation that would require an amendment to the IANA Naming Function Contract. Item 4: COUNCIL VOTE - Approval to Initiate a Two-Phased Policy Development Process on the Transfer Policy (15 minutes) The GNSO Council established a Transfer Policy Review Scoping Team to provide recommendations on the approach to a potential review and future policy work related to the Transfer Policy, including composition of the review team or PDP working group and scope of the review. The Transfer Policy Review Scoping Team delivered a Transfer Policy Initial Scoping Paper<https://gnso.icann.org/sites/default/files/file/field-file-attach/transfer-…> on April 6, 2020 in which it recommended the GNSO Council instruct ICANN Policy staff to draft a Preliminary Issue Report. On 24 June 2020, the Council requested the preparation of a Preliminary Issue Report. The Preliminary Issue Report was published for public comment on 12 October 2020 and after the report was adjusted to take into account public comments as appropriate, the Final Issue Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-iss…> was delivered to the GNSO Council on 12 January 2021. The Final Issue Report includes a recommendation that the GNSO Council proceed with a two-phased Policy Development Process (PDP) that will address the following topic areas in sequence: * Phase 1(a): Form of Authorization (including Rec. 27, Wave 1 FOA issues) and AuthInfo Code * Phase 1(b): Change of Registrant (including Rec. 27, Wave 1 Change of Registrant issues) * Phase 2: Transfer Emergency Action Contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy (including Rec. 27, Wave 1 TDRP issues), NACKing transfers, ICANN-approved transfers The General Counsel of ICANN has indicated that the topics recommended for review are properly within the scope of the ICANN policy process and the GNSO. On 1 February 2021, policy staff shared a pre-recorded webinar<https://community.icann.org/x/J4FeCQ> to help Councilors prepare for this agenda item. Here, the Council will vote to initiate a two-phased PDP to review the Transfer Policy, as recommended in the Final Issue Report. 4.1 - Presentation of motion<https://community.icann.org/x/SAtACQ> (TBD) 4.2 – Council discussion 4.3 – Council vote (voting threshold: an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House) 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 VOTE - Final Report and Outputs From the New gTLD Subsequent Procedures PDP (20 minutes) The New gTLD Subsequent Procedures (SubPro) PDP was chartered in January 2016 to review the 2012 New gTLD Program round to determine what, if any changes may need to be made to the existing 2007 Introduction of New Generic Top-Level Domains policy recommendations. After extensive WG deliberations and a number of community consultations, the WG delivered its Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…> to the GNSO Council on 18 January 2021. Because of the volume of outputs(e.g., affirmations, recommendations, implementation guidance, etc.) and length of the report, the PDP Co-Chairs believed that similar to the Final Report for the All Rights Protection Mechanisms (RPMs) in All gTLDs PDP WG, a preliminary briefing would be beneficial and therefore, scheduled a briefing during the January 2020 Council meeting. Subsequently, and again similar to the RPMs PDP, the GNSO Council liaison to the PDP and the Co-Chairs held a detailed webinar and discussion on the report, to better prepare the Council for a vote during a subsequent Council meeting. Here, the Council will vote to adopt the Final Report of the SubPro WG. 5.1 - Presentation of motion<https://community.icann.org/x/SAtACQ> (GNSO Council liaison to the PDP, Flip Petillion) 5.2 – Council discussion 5.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 6: COUNCIL DISCUSSION – Charter for the Transfer Policy PDP (20 minutes) In connection to item 4, if the Council initiates a PDP on the Transfer Policy, it will subsequently need to adopt a charter. The Preliminary Issue Report included a draft charter, which was included in the public comment proceeding. That draft charter is also included in the Final Issue Report. Comment on the draft charter was solicited from Councilors via a pre-recorded webinar <https://community.icann.org/x/J4FeCQ> prior to this Council meeting. Here, the Council will discuss whether there are substantive changes needed for the draft charter and determine next steps as appropriate. 6.1 – Introduction of topic (Council leadership) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL UPDATE - Update from the Internationalized Domain Names (IDNs) EPDP Charter Drafting Team (15 minutes) During the Council’s October 2020 meeting, the Council agreed to launch a call for volunteers and to establish a drafting team to develop a draft charter and an EPDP initiation request for the IDN Policy Track 2. That drafting team met for the first time on 5 January 2021 and since then has steadily made progress, recently agreeing for the most part to a set of principles and underlying assumptions to help make its work more efficient. Previous to that agreement, making progress was challenging, resulting in an extension of the expected completion date from the March Council meeting to the May Council meeting (see workplan here<https://docs.google.com/spreadsheets/d/1mD0soQAd-OfPQCiY5aHls3HVltq0CtSu8aA…>). Here, the Council will receive an update from the drafting team. 7.1 – Introduction of topic (Chair of the drafting team, Dennis Tan) 7.2 – Council discussion 7.3 – Next steps Item 8: ANY OTHER BUSINESS (20 minutes) 8.1 - EPDP-P2A Project and Work Plan commitment 8.2 - Update from the GNSO Council liaison to the GAC, including his discussion with the GAC point of contact to the GNSO, Jorge Cancio. 8.3 - ICANN70 GNSO sessions _______________________________ 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 19:00 UTC Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 11:00 San José, Costa Rica (CST) UTC-6 13:00 New York/Washington DC, USA (EDT) UTC-5 14:00 Buenos Aires, Argentina (ART) UTC-3 16:00 Rio de Janeiro, Brazil (BRST) UTC-3 16:00 London, United Kingdom (GMT) UTC+0 19:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 20:00 Paris, France (CEST) UTC+1 20:00 Moscow, Russia (MST) UTC+3 22:00 Singapore (SGT) (+1 day) UTC+8 03:00 Melbourne, Australia (AEDT)(+1 day) UTC+11 06:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 28 March 2021, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 14 March 2021 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/yxdh3opz

2 1

SubPro Resolution Second and Amendment
by Kurt Pritz 17 Feb '21

17 Feb '21

Dear Flip and fellow Councillors: Thanks very much for the work done on the motion (recognizing that is a small percentage of the multi-year effort that has been put in). I’d be pleased to second the motion. I also wish to offer two amendments supported by the RrSG and RySG Leadership that should, I think, be considered separately. The first amendment removes the second portion of this part of the resolution: The GNSO Council adopts the Final Report of the SubPro Working Group and recommends the implementation of each of the Outputs that have obtained either Consensus or Full Consensus designations by the ICANN Board of Directors. The GNSO Council requests that the ICANN Board take note of Recommendations 35.2 and 35.4, the two Outputs that have obtained Strong Support but Significant Opposition, including the rationale and the minority statements associated with those Outputs. The reasons for this were described in an earlier email. Briefly, we think the Board will have an easier time approving the SubPro recommendations if they are not put in the position of considering policy that is not supported by a consensus of the working group. In addition, we think it is important to draw a bright line that is congruent with the working group's agreement that only consensus-level recommendations would become part of the next program round. The second amendment adapts the first portion of the same amendment to more assertively fulfill the Council’s policy role: The GNSO Council adopts the Final Report of the SubPro Working Group and recommends the implementation of each of the Outputs that have obtained either Consensus or Full Consensus designations by the ICANN Board of Directors. Becomes, The GNSO Council approves, and recommends that the ICANN Board adopt, all the Outputs Affirmations, Recommendations and Implementation Guidance that were determined to have received either Full Consensus or Consensus designations as documented in the SubPro PDP Working Group's Final Report. The reason for this is that the Council is in the business of making (through its delegated Working Groups) and approving specific policy and associated recommendations — and not reports generally. Again, we think that refining this portion of the resolution will facilitate acceptance by the Board and better focus the role fo the Council. I and other RrSG and RySG Council representatives can answer questions or requests for additional information. An edited version of the amendment is attached. Best regards, Kurt .

2 1

In preparation for the GNSO Council meeting 18 February 2021
by Nathalie Peregrine 17 Feb '21

17 Feb '21

Dear all, A few reminders in preparation for the GNSO Council meeting on Thursday 18 February 2021 at 19:00 UTC. * Please remember to update your Zoom application, steps as to how to do this can be found here<https://urldefense.com/v3/__https:/support.zoom.us/hc/en-us/articles/201362…>. * Please review the agenda<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+GNSO…> and motions<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+February…> as well as supporting documents<https://community.icann.org/display/gnsocouncilmeetings/Documents+18+Februa…>. * Please review all updated Program Management Tools<https://community.icann.org/display/gnsocouncilmeetings/Program+Management+…>: Action Item list<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>, Project List<https://community.icann.org/display/gnsocouncilmeetings/Project+List> , Action Decision Radar<https://community.icann.org/display/gnsocouncilmeetings/Action+Decision+Rad…>. * There are three votes on the GNSO Council agenda, if you cannot make the call, or are worried about connectivity issues, please use the GNSO Council Absence Notification form<https://forms.icann.org/en/gnso-council-absence-notification-form> to assign a proxy. Thank you, Kind regards, Nathalie

1 0