February 2024 - council - lists.icann.org

Document and Motion deadline | Sunday, 25 February 2024 at 23:59 UTC for GNSO Council Meeting 06 March 2024 at 17:15 UTC
by Terri Agnew 15 Feb '24

15 Feb '24

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 25 February 2024 at 23:59 UTC) of the GNSO Council Meeting on Wednesday, 06 March 2024 at 17:15 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Motions Wiki at: https://community.icann.org/x/9IAvEQ Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Recordings | GNSO Council Meeting | Thursday, 15 February 2024
by Terri Agnew 15 Feb '24

15 Feb '24

Dear all, Please find below the audio recording and zoom recording (audio, visual, rough transcript, and chat) of the GNSO Council Meeting that took place on Thursday, 15 February 2024 at 21:00 UTC. Audio only: https://icann.zoom.us/rec/play/qgm2ep8BueDpHFIUVjjM1hOzRxkwq8UCODQvGRX8lBoY… Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/share/8YbrlngOWD_A4EiYRzr8Pt0Slx3DYZKmHZtInO89YjN… The recordings and transcriptions of the calls are posted on the GNSO Calendar page. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

3rd UPDATE - added 9.7 - Update on diacritic study request| Re: Proposed Agenda | GNSO Council Meeting | Thursday, 15 February 2024
by Terri Agnew 15 Feb '24

15 Feb '24

Hi all, The presentation slides are now posted on both agenda<https://community.icann.org/x/6oAvEQ> & documents<https://community.icann.org/x/8IAvEQ> wiki’s in addition on the GNSO presentation website<https://gnso.icann.org/en/council/presentations> for Item 5: COUNCIL DISCUSSION - Update on SubPro Small Team Progress. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: Terri Agnew <terri.agnew(a)icann.org> Date: Wednesday, February 14, 2024 at 2:52 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: 2nd UPDATE - added 9.7 - Update on diacritic study request| Re: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 15 February 2024 Hi all, Another item has been added in AOB: 9.7 - Update on diacritic study request. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: liaison6c <liaison6c-bounces(a)gnso.icann.org> on behalf of Terri Agnew via liaison6c <liaison6c(a)gnso.icann.org> Reply-To: Terri Agnew <terri.agnew(a)icann.org> Date: Tuesday, February 6, 2024 at 5:00 PM To: 陳曼茹 Manju Chen <manju(a)nii.org.tw> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [liaison6c] UPDATED - added 9.6 - CCOICI Survey Reminder| Re: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 15 February 2024 HI all, We have added this item in AOB: 9.6 - CCOICI Survey Reminder. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: 陳曼茹 Manju Chen <manju(a)nii.org.tw> Date: Monday, February 5, 2024 at 8:40 PM To: Terri Agnew <terri.agnew(a)icann.org> Cc: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] Re: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 15 February 2024 Hi all, I'd like to add CCOICI survey as an AOB to the Agenda. It'd be a brief introduction of the survey and a reminder for all to discuss your response within your SG/Cs. I did suggest it in the Council Meeting Agenda Planning [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> document, but it was not picked up probably because I added too late. Thank you! Best, Manju On Tue, Feb 6, 2024 at 5:09 AM Terri Agnew via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear all, Please find below the final proposed agenda for the GNSO Council Meeting taking place on Thursday, 15 February 2024 at 21:00 UTC for 2 hours This has been posted on the agenda wiki page<https://community.icann.org/x/6oAvEQ>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO Draft GNSO Council Agenda 15 February 2024 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/8IAvEQ. This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> v3.5, updated on 15 March 2023. 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 on Thursday, 15 February 2024 at 21:00 UTC: http://tinyurl.com/42vy5duf [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/42vy5duf__;!!PtGJab4!99g_M5Ib…> 13:00 Los Angeles; 16:00 Washington DC; 21:00 London; 22:00 Paris; 00:00 Moscow (Friday); 08:00 Melbourne (Friday) GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (5 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council Meeting on 21 December 2023 were posted on 02 January 2024 Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council Meeting on 18 January 2023 were posted on 02 February 2024 Item 2: Opening Remarks / Review of Projects & Action List (0 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.com/v3/__https:/gnso.icann.org/en/council/project__;!!Pt…> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Confirm Leadership of Standing Selection Committee (“SSC”) * Confirm GNSO-Nominated ICANN Fellowship Program Mentor Item 4: COUNCIL VOTE - Registration Data Accuracy (20 minutes) The Registration Data Accuracy (RDA) Scoping Team was initiated by the GNSO Council in July 2021 per the formation instructions [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>. The Scoping Team was tasked with considering a number of accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations are to help inform the team’s deliberations and development of recommendations to the GNSO Council on whether any changes are recommended to improve accuracy levels, and, if so, how and by whom these changes would need to be developed (for example, if changes to existing contractual requirements are recommended, a PDP or contractual negotiations may be necessary to effect a change). The Scoping Team completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up<https://mm.icann.org/pipermail/council/2022-September/025950.html> to the Council on 5 September 2022. In its write up, the Scoping Team suggested moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3). ICANN org provided an update to the Council during the 20 April meeting [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/gx322OsdypGMHjYVM…>. During its meeting on 20 June 2023, the Council voted to extend the deferral of the consideration of recommendations #1 and #2, pending resolution of recommendation #3 (pausing the work on proposals that require access to registration data until there is clarity from ICANN org on if/how it anticipates the requesting and processing of registration data to be undertaken in the context of measuring accuracy). On 19 October 2023, ICANN org provided an update<https://mm.icann.org/pipermail/council/2023-October/027397.html> on Registration Data Accuracy efforts, and the Council discussed the update during its 16 November 2023 meeting. During that meeting, some Councilors noted that, barring (i) completion of the Data Processing Agreement, (ii) implementation of the NIS2 directive, or (iii) publication of the Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study, it may not be the appropriate time to reconvene the Accuracy Scoping Team. Now that six months have passed since the Council’s deferral of the accuracy scoping work, the Council will need to consider next steps. Here, the Council will vote on deferring the consideration of the accuracy scoping work for an additional six months or potentially sooner if there is a passage of a significant event, e.g., completion of the Data Processing Agreement, implementation of the NIS2 directive, or publication of the INFERMAL study. 4.1 - Introduction of Topic (Greg DiBiase, GNSO Council Chair) 4.2 - Council Vote (Voting Threshold: Simple Majority) 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Update on SubPro Small Team Progress (20 minutes) In March 2023, the ICANN Board approved the majority of the recommendations contained in the Final Report on the new gTLD Subsequent PDP, but also placed some recommendations into a pending status. The Council convened a small team that worked collaboratively with the ICANN Board to resolve all pending recommendations. While the majority of the pending recommendations were able to be adopted by the ICANN Board, recommendations across six Topics were non adopted by the ICANN Board. With the primary task of addressing the pending recommendations now complete, the Council has tasked the Small Team Plus with an updated assignment form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1yDgWIwKZqKk0…>. The Small Team Plus has committed to a work plan [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1IhxKi0dvkS-a…> to address the recommendations not adopted by the Board. Following that plan, the Small Team has completed initiation steps (i.e., developed background materials, preliminary Supplemental Recommendation language, and issued a call for volunteers for the Small Team Plus). The Small Team Plus has come to preliminary Supplemental Recommendation language (i.e., stable text) for most of the six Topic. Here, the Council will receive an update on the progress of the Small Team Plus. 5.1 - Introduction of Topic (Paul McGrady, Small Team Plus Lead) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Next Steps for Consideration of Expired Domain Deletion Policy (“EDDP”) and Expired Registration Recovery Policy (“ERRP”) (15 minutes) The GNSO Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the EDDP and the ERRP. In November 2020, given concerns about its capacity and no known issues with the policies, the Council agreed to delay the request for the Policy Status Report (PSR) for a period of 24 months. After 24 months had passed, the Council reconsidered whether it was an appropriate time to request a Policy Status Report. To that end, in July 2022, the Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. ICANN org shared a report<https://mm.icann.org/pipermail/council/2022-November/026164.html> from Contractual Compliance colleagues on 1 November 2022, and GNSO Councilors from the Registrar Stakeholder Group shared feedback from registrars on previous Council calls. During its meeting on 17 November 2022<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>, representatives from ICANN org’s Contractual Compliance Team provided a briefing of the report<https://mm.icann.org/pipermail/council/2022-November/026164.html>, and the Council briefly considered potential next steps. Following its review of the report, the Council agreed that both the EDDP and ERRP may benefit from further work, though the timing for the work requires further consideration. In particular, as the Compliance report noted, the language of the policy is ambiguous in parts and has caused confusion for registrants. As the ERRP was implemented in part to ensure that “expiration-related provisions in typical registration agreements are clear and conspicuous enough” and to ensure that “adequate notice exists to alert registrants of upcoming expirations,” the continuing registrant confusion warrants further consideration. Additionally, some of the existing language has become obsolete due to intervening data protection law requirements and will require updates. To that end, the Council requested further information from ICANN org on what expiration-related educational materials are currently published and whether additional information can be provided (whether as registrant educational material referenced in Section 4.3 or elsewhere on ICANN’s website). The Council noted receipt of this information would be helpful to the Council in determining if updates to these materials or additional material in other forms could be helpful to combat the ongoing registrant confusion. Here, the Council will receive an update from ICANN org on the published materials. 6.1 - Introduction of Topic (Nacho Amadoz, Council Vice-Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - ICANN79 Preparation (20 minutes) Pre-ICANN79 GNSO Policy Webinar: * Monday, 26 February 2024 at 21:00 UTC Note: Mandatory for GNSO Council members During ICANN79, the GNSO Council has the following meetings and events scheduled (times listed in AST): Saturday, 2 March * 09:00-10:00 - IDNs EPDP Team Working Session * 13:15-14:30 - Transfer Policy Review PDP Working Group Session 1 of 2 * 15:00-16:00 - Transfer Policy Review PDP Working Group Session 2 of 2 * Time TBD: GNSO Council dinner Sunday, 3 March * 09:00-10:00 - GNSO Working Session 1 of 2 * 10:30-12:00 - GNSO Working Session 2 of 2 * 13:15-14:30 - GNSO Working Session 3 of 3 Monday, 04 March * 15:00-16:00 Joint ICANN Board and GNSO Council Tuesday, 05 March * 17:30-18:30 - GNSO Council Informal meeting [closed] Wednesday, 6 March * 09:00-10:00 - Joint GNSO Council & GAC * 10:30-12:00 - SubPro Supplemental Recommendations Community Consultation * 13:15-15:15- GNSO Council Meeting Thursday, 7 March * 09:00-10:00 - GNSO Council SubPro Small Team Plus Meeting * 15:00-16:00 - GNSO Council Wrap-Up During its Strategic Planning Session the Council agreed to conduct a triannual detailed review of the Program Management Tool. The action item coming from the SPS provided, “During a session at ICANN79, Council to prepare for a careful review of work captured in the Program Management Tool (PMT) that will conclude or initiate prior to the next AGM, or continue beyond the next AGM. Paul McGrady to coordinate with staff to plan for this inaugural effort.” Here, the Council will receive an overview of the current block schedule and plan for its in-person meetings. 7.1 - Introduction of Topic (Greg DiBiase, GNSO Council Chair) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL UPDATE: Draft NCAP Study 2 Report (15 minutes) The Name Collision Analysis Project Discussion Group (NCAP) is currently seeking input on its draft Study 2 report [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/name-collisio…> and responses to a series of questions from the ICANN Board regarding name collisions as outlined in resolution 2017.11.02.30<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> and reaffirmed in resolution 2021.03.25.13<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…>. The draft Study 2 report [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/name-collisio…> is structured to guide the reader through the methodology and significant findings of three pivotal research studies, as well as the analysis of the NCAP Discussion Group's extensive work activities. This material is what informs the eleven strategic recommendations provided at the end of the report. One of the key recommendations is the establishment of a new workflow, the Name Collision Risk Assessment Workflow, designed to enhance the assessment process of new generic top-level domains (gTLDs). This recommendation underscores the NCAP Discussion Group’s belief that name collisions should be approached not merely as a technical challenge but as a critical risk management issue. Here, the Council will receive an overview of the draft Study 2 report [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/name-collisio…> and have the opportunity to ask questions. 8.1 - Introduction of Topic (Greg DiBiase, GNSO Council Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: ANY OTHER BUSINESS (20 minutes) 9.1 - ccNSO & GAC Liaison updates (every three months) 9.2 - Board letter on Closed Generics 9.3 - Standing Predictability Implementation Review Team (“SPIRT”) Charter Drafting Team Update 9.4 - Status Update on Council Requests 9.5 - Update from Contracted Party House Abuse Subgroup’s Meeting with the Non-Commercial Stakeholder Group 9.6 - CCOICI Survey Reminder 9.7 - Update on diacritic study request. _______________________________ 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… [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> References for Coordinated Universal Time of 21:00 UTC Local time between November and March in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ [timeanddate.com]<https://urldefense.com/v3/__https:/www.timeanddate.com/time/change/__;!!PtG…> for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PST) UTC-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EST) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CET) UTC+1 22:00 Moscow, Russia (MSK) UTC+3 00:00 Singapore (SGT) UTC+8 05:00 Melbourne, Australia (AEDT) UTC+11 08:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.com/v3/__http:/www.timeanddate.com/__;!!PtGJab4!99g_M5Ib…> and http://tinyurl.com/42vy5duf [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/42vy5duf__;!!PtGJab4!99g_M5Ib…> _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

GNSO Council resolutions 15 February 2024
by Terri Agnew 15 Feb '24

15 Feb '24

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday, 15 February 2024, which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. 20240215-1 CONSENT AGENDA Motion to Confirm GNSO Standing Selection Committee (SSC) Members and Leadership for 2024 Submitted by: Tomslin Samme-Nlar Seconded by: Lawrence Olawale-Roberts Whereas, 1. The GNSO Standing Selection Committee (SSC) is tasked, as requested by the GNSO Council, to 1) where applicable, prepare and issue calls for applications related to the selection or nomination of candidates for ICANN structures such as ICANN review teams, 2) review and evaluate all relevant applicants/candidates, 3) rank candidates and make selection/appointment recommendations for review and approval by Council, and 4) communicate selections to all interested parties. 2. The membership<https://community.icann.org/pages/viewpage.action?pageId=64077781> of the SSC (9 members not including the ex-officio members) is reconfirmed annually and needs to be appointed and/or reconfirmed by the leadership of the appointing Stakeholder Groups and/or Constituencies. 3. Following reconfirmation each year, the SSC selects a Chair and one or two Vice-Chair(s) from its membership. 4. The SSC selected a leadership team for 2024, which is submitted for confirmation to the GNSO Council by way of this motion: * Karen Day to serve for a first term as Chair. * Segunfunmi Olajide to serve for a first term as Vice-Chair. Resolved, 1. The GNSO Council confirms the SSC membership and leadership team for 2024: * Chair: Karen Day * Vice-Chair: Segunfunmi Olajide 2.The GNSO Council requests the ICANN org Support Staff to inform SSC that the membership and leadership team has been confirmed. 3.The GNSO Council thanks the members, Chair, and Vice-Chair for volunteering to serve on the SSC. Vote results<https://gnso.icann.org/sites/default/files/policy/2024/vote-result/gnso-cou…> 20240215-2 CONSENT AGENDA Motion to Confirm the GNSO-Nominated Mentor for the 2024 ICANN Fellowship Program Submitted by: Tomslin Samme-Nlar Seconded by: Lawrence Olawale-Roberts Whereas, 1. On 13 December 2023, the GNSO announced<https://gnso.icann.org/en/announcements/announcement-03jan24-en.htm%20https…> that it was launching an Expression of Interest (EOI) process to solicit volunteers to serve in the capacity of a GNSO-nominated Fellowship Program Mentor for three consecutive ICANN meetings, beginning with ICANN81. 2. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with reviewing mentor applications and recommending one individual for the GNSO to nominate. 3. The SSC reviewed the applications received, taking into account the selection criteria outlined in the EOI announcement. 4. The SSC submitted its full consensus recommendation to the GNSO Council on 05 February 2024, by way of submission of the relevant motion. 5. The GNSO Council considered the recommendation of the SSC. Resolved, 1. The GNSO confirms the nomination of Mark Datysgeld to serve as an ICANN Fellowship Program Mentor for three consecutive ICANN meetings, beginning with ICANN81. 2. The GNSO Council asks the GNSO Secretariat to communicate the resolved #1 to the staff supporting the ICANN Fellowship Program. 3. The GNSO Council asks the GNSO Secretariat to inform the nominated candidate that he has been selected. 4. The GNSO Council asks the GNSO Secretariat to send a response to those applicants who were not nominated, thanking them for their interest and encouraging them to apply for future opportunities as they arise. Vote results<https://gnso.icann.org/sites/default/files/policy/2024/vote-result/gnso-cou…> 20240215-3 Registration Data Accuracy Scoping Team Recommendations #1 and #2 – extending deferral of consideration by six months Submitted by Greg DiBiase Seconded by Prudence Malinki Whereas, The GNSO Council resolved<https://gnso.icann.org/en/council/resolutions/2020-current#20221117-4> on 17 November 2022 to defer consideration of recommendations #1 and #2 of the Registration Data Accuracy Scoping Team write up<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/palag…> until such time as the Data Processing Agreement (DPA) negotiations between ICANN org and Contracted Parties have completed and there is feedback from ICANN org on if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy, or for six months, whichever is the shorter; Whereas, The GNSO Council wrote<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/gnso-…> to ICANN org to obtain this feedback and received a response<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/gutte…> providing a status update on 14 March 2023 which was also presented during its April 2023 meeting; 1. ICANN org’s work on the scenarios that have been identified to review the accuracy of registration data and the data protection questions that arise from these scenarios is still ongoing; 2. Negotiations between ICANN org and Contracted Parties on a DPA have not completed yet. Whereas, ICANN org conducted a comprehensive assessment of the four scenarios and provided an update<https://mm.icann.org/pipermail/council/2023-October/027397.html> on Registration Data Accuracy efforts on 19 October 2023, noting specifically: 1. it is unclear whether [the scenarios] would provide useful data to inform the Accuracy Scoping Team’s efforts; 2. the scenarios are not expected to provide data as it relates to identity verification of the registrant or veracity of the contact information (i.e., the data belongs to the data subject); 3. the costs associated with a full-scale registrar audit may be prohibitive when taking into account the relatively low level of insight the audit may yield; 4. ICANN does not have the authority to mandate collection of nonpublic registration data necessary to conduct reviews outside of auditing current contractual requirements; and 5. ICANN may not be able to demonstrate the purpose of some of the data processing outweighs the rights of the impacted data subject. Whereas, The GNSO Council discussed ICANN org’s update<https://mm.icann.org/pipermail/council/2023-October/027397.html> during its meeting on 16 November 2023<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> and noted that, barring (i) completion of the Data Processing Agreement, (ii) implementation of the NIS2 directive, or (iii) publication of the Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study, it may not be the appropriate time to consider the Accuracy Scoping Team’s recommendations. Resolved, 1. The GNSO Council extends the deferral of consideration of recommendations #1 and #2 of the Registration Data Accuracy Scoping Team write up<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/palag…> for an additional six months. 2. The GNSO Council commits to considering the Scoping Team recommendations at an earlier date if DPA negotiations have been completed before six months have passed or another significant event, such as the implementation of the NIS2 directive or the publication Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study, occurs before six months have passed. Vote results<https://gnso.icann.org/sites/default/files/policy/2024/vote-result/gnso-cou…> Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

**Starting in 15 minutes | Meeting Invitation | GNSO Council Meeting | Thursday, 15 February 2024
by Terri Agnew 15 Feb '24

15 Feb '24

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 15 February 2024 at 21:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/6oAvEQ Check your time zone: http://tinyurl.com/42vy5duf [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/42vy5duf__;!!PtGJab4!_logVnSK…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Passcode: f!Ym9!npfN If joining Zoom via Zoom App the following will be required: Webinar ID: 922 8356 5389 Passcode: 6981311025 Or One tap mobile : +13462487799,,92283565389#,,,,*6981311025# US (Houston) +16699006833,,92283565389#,,,,*6981311025# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/adGHfYeA3T [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/adGHfYeA3T__;!!PtGJab4!9…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/8IAvEQ> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

FYI: FW: [Ext] NEW: Join the Board for a Special ICANN79 Prep Week Session
by Terri Agnew 15 Feb '24

15 Feb '24

FYI: [https://r20.rs6.net/on.jsp?ca=1968e606-b3dd-4d43-96d1-602897c08b25&a=112202…] Thursday, 15 February 2024 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents ICANN79 · NEW: Join the Board for a Special ICANN79 Prep Week Session · NEW: ICANN79 Policy Outlook Report · ICANN79 Schedule Now Available · ICANN79 Prep Week Schedule Now Available · ICANN79 Zoom Backgrounds Information Sharing · NEW: Ten Things to Do in Puerto Rico · NEW: Request for Proposal: ICANN Support Applicant Review Panel Action Items · NEXT WEEK🔥 ACTION ITEM: Calling for NextGen@ICANN Applications for ICANN80 · 🔥 ACTION ITEM: Apply Now for ICANN Leadership Positions Public Comment · NEW: Review of the Draft Applicant Support Program (ASP) Handbook – New gTLD Program · Draft NCAP Study 2 Report and Responses to Questions Regarding Name Collisions · Phase 1 Final Report of the EPDP on Internationalized Domain Names · Proposed Language for Draft Sections of the Next Round Applicant Guidebook · Proposed Top-Level Domain String for Private Use · String Similarity Review Guidelines ICANN79 Prep Week Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Zoom Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> ICANN79 Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> ICANN79 Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> NEW: Join the Board for a Special ICANN79 Prep Week Session During the session, Board members will host three separate breakout rooms, each covering a different topic. Date: Wednesday, 21 February, at 16:30–17:30 UTC. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Information Sharing NEW: Ten Things to Do in Puerto Rico We look forward to greeting the ICANN community in San Juan for the upcoming Community Forum. ICANN selects these meeting locations because the Internet is a global network and our aim is to make it easier for volunteers to participate and to ensure our work represents the entire world. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> NEW: Request for Proposal: ICANN Support Applicant Review Panel ICANN seeks to engage experienced and competent suppliers who can carry out a fair, efficient, consistent, and reliable process to assess ASP applicants in advance of the New gTLD Program: Next Round, anticipated to open in Q2 2026. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Action Items NEXT WEEK 🔥 ACTION ITEM: Calling for NextGen@ICANN Applications for ICANN80 ICANN wants to hear from university students living and studying in the African region who are interested in the future of the Internet and in participating in the ICANN80 Policy Forum. ICANN80 is scheduled to be held in Kigali, Rwanda, from 10–13 June 2024. Deadline: 23 February 2024 Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> 🔥 ACTION ITEM: Apply Now for ICANN Leadership Positions Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the policy development and technical coordination of the Internet's unique identifiers. Deadline: 15 March 2024 at 23:59 UTC Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Public Comment NEW: Review of the Draft Applicant Support Program (ASP) Handbook – New gTLD Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Open for Submissions: 12 February 2024 Closed for Submissions: 02 April 2024 Draft NCAP Study 2 Report and Responses to Questions Regarding Name Collisions [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Open for Submissions: 19 January 2024 Closed for Submissions: 28 February 2024 Phase 1 Final Report of the EPDP on Internationalized Domain Names [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Open for Submissions: 23 January 2024 Closed for Submissions: 12 March 2024 Proposed Language for Draft Sections of the Next Round Applicant Guidebook [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Open for Submissions: 01 February 2024 Closed for Submissions: 19 March 2024 Proposed Top-Level Domain String for Private Use [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Open for Submissions: 24 January 2024 Closed for Submissions: 21 March 2024 String Similarity Review Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> Open for Submissions: 07 February 2024 Closed for Submissions: 27 March 2024 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…>. Volume 6, Issue 13 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…> | Next Issue: Monday, 19 February 2024 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001UQwUNzmCvkx8ehhJ…>

1 0

Re: [council] Summary of domain name renewal and expiration educational resources (Feb Council Agenda Item 6)
by Caitlin Tubergen 14 Feb '24

14 Feb '24

Dear Councilors, Please find an updated attachment. Apologies for the additional email. Kind regards, Caitlin From: council <council-bounces(a)gnso.icann.org> on behalf of Caitlin Tubergen via council <council(a)gnso.icann.org> Reply-To: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Wednesday, February 14, 2024 at 10:07 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: Brian Gutterman <brian.gutterman(a)icann.org> Subject: [council] Summary of domain name renewal and expiration educational resources (Feb Council Agenda Item 6) Dear Councilors, Further to Agenda Item 6 for Thursday’s Council meeting, Next Steps for Consideration of Expired Domain Deletion Policy (“EDDP”) and Expired Registration Recovery Policy (“ERRP”), please find a summary of the current educational materials on domain name renewal and expiration attached. Brian Gutterman from ICANN org will be providing an overview of the materials during the Council meeting on Thursday. Kind regards, Caitlin

1 0

2nd UPDATE - added 9.7 - Update on diacritic study request| Re: Proposed Agenda | GNSO Council Meeting | Thursday, 15 February 2024
by Terri Agnew 14 Feb '24

14 Feb '24

Hi all, Another item has been added in AOB: 9.7 - Update on diacritic study request. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: liaison6c <liaison6c-bounces(a)gnso.icann.org> on behalf of Terri Agnew via liaison6c <liaison6c(a)gnso.icann.org> Reply-To: Terri Agnew <terri.agnew(a)icann.org> Date: Tuesday, February 6, 2024 at 5:00 PM To: 陳曼茹 Manju Chen <manju(a)nii.org.tw> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [liaison6c] UPDATED - added 9.6 - CCOICI Survey Reminder| Re: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 15 February 2024 HI all, We have added this item in AOB: 9.6 - CCOICI Survey Reminder. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: 陳曼茹 Manju Chen <manju(a)nii.org.tw> Date: Monday, February 5, 2024 at 8:40 PM To: Terri Agnew <terri.agnew(a)icann.org> Cc: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] Re: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 15 February 2024 Hi all, I'd like to add CCOICI survey as an AOB to the Agenda. It'd be a brief introduction of the survey and a reminder for all to discuss your response within your SG/Cs. I did suggest it in the Council Meeting Agenda Planning [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> document, but it was not picked up probably because I added too late. Thank you! Best, Manju On Tue, Feb 6, 2024 at 5:09 AM Terri Agnew via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear all, Please find below the final proposed agenda for the GNSO Council Meeting taking place on Thursday, 15 February 2024 at 21:00 UTC for 2 hours This has been posted on the agenda wiki page<https://community.icann.org/x/6oAvEQ>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO Draft GNSO Council Agenda 15 February 2024 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/8IAvEQ. This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> v3.5, updated on 15 March 2023. 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 on Thursday, 15 February 2024 at 21:00 UTC: http://tinyurl.com/42vy5duf [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/42vy5duf__;!!PtGJab4!99g_M5Ib…> 13:00 Los Angeles; 16:00 Washington DC; 21:00 London; 22:00 Paris; 00:00 Moscow (Friday); 08:00 Melbourne (Friday) GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (5 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council Meeting on 21 December 2023 were posted on 02 January 2024 Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council Meeting on 18 January 2023 were posted on 02 February 2024 Item 2: Opening Remarks / Review of Projects & Action List (0 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.com/v3/__https:/gnso.icann.org/en/council/project__;!!Pt…> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Confirm Leadership of Standing Selection Committee (“SSC”) * Confirm GNSO-Nominated ICANN Fellowship Program Mentor Item 4: COUNCIL VOTE - Registration Data Accuracy (20 minutes) The Registration Data Accuracy (RDA) Scoping Team was initiated by the GNSO Council in July 2021 per the formation instructions [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>. The Scoping Team was tasked with considering a number of accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations are to help inform the team’s deliberations and development of recommendations to the GNSO Council on whether any changes are recommended to improve accuracy levels, and, if so, how and by whom these changes would need to be developed (for example, if changes to existing contractual requirements are recommended, a PDP or contractual negotiations may be necessary to effect a change). The Scoping Team completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up<https://mm.icann.org/pipermail/council/2022-September/025950.html> to the Council on 5 September 2022. In its write up, the Scoping Team suggested moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3). ICANN org provided an update to the Council during the 20 April meeting [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/gx322OsdypGMHjYVM…>. During its meeting on 20 June 2023, the Council voted to extend the deferral of the consideration of recommendations #1 and #2, pending resolution of recommendation #3 (pausing the work on proposals that require access to registration data until there is clarity from ICANN org on if/how it anticipates the requesting and processing of registration data to be undertaken in the context of measuring accuracy). On 19 October 2023, ICANN org provided an update<https://mm.icann.org/pipermail/council/2023-October/027397.html> on Registration Data Accuracy efforts, and the Council discussed the update during its 16 November 2023 meeting. During that meeting, some Councilors noted that, barring (i) completion of the Data Processing Agreement, (ii) implementation of the NIS2 directive, or (iii) publication of the Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study, it may not be the appropriate time to reconvene the Accuracy Scoping Team. Now that six months have passed since the Council’s deferral of the accuracy scoping work, the Council will need to consider next steps. Here, the Council will vote on deferring the consideration of the accuracy scoping work for an additional six months or potentially sooner if there is a passage of a significant event, e.g., completion of the Data Processing Agreement, implementation of the NIS2 directive, or publication of the INFERMAL study. 4.1 - Introduction of Topic (Greg DiBiase, GNSO Council Chair) 4.2 - Council Vote (Voting Threshold: Simple Majority) 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Update on SubPro Small Team Progress (20 minutes) In March 2023, the ICANN Board approved the majority of the recommendations contained in the Final Report on the new gTLD Subsequent PDP, but also placed some recommendations into a pending status. The Council convened a small team that worked collaboratively with the ICANN Board to resolve all pending recommendations. While the majority of the pending recommendations were able to be adopted by the ICANN Board, recommendations across six Topics were non adopted by the ICANN Board. With the primary task of addressing the pending recommendations now complete, the Council has tasked the Small Team Plus with an updated assignment form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1yDgWIwKZqKk0…>. The Small Team Plus has committed to a work plan [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1IhxKi0dvkS-a…> to address the recommendations not adopted by the Board. Following that plan, the Small Team has completed initiation steps (i.e., developed background materials, preliminary Supplemental Recommendation language, and issued a call for volunteers for the Small Team Plus). The Small Team Plus has come to preliminary Supplemental Recommendation language (i.e., stable text) for most of the six Topic. Here, the Council will receive an update on the progress of the Small Team Plus. 5.1 - Introduction of Topic (Paul McGrady, Small Team Plus Lead) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Next Steps for Consideration of Expired Domain Deletion Policy (“EDDP”) and Expired Registration Recovery Policy (“ERRP”) (15 minutes) The GNSO Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the EDDP and the ERRP. In November 2020, given concerns about its capacity and no known issues with the policies, the Council agreed to delay the request for the Policy Status Report (PSR) for a period of 24 months. After 24 months had passed, the Council reconsidered whether it was an appropriate time to request a Policy Status Report. To that end, in July 2022, the Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. ICANN org shared a report<https://mm.icann.org/pipermail/council/2022-November/026164.html> from Contractual Compliance colleagues on 1 November 2022, and GNSO Councilors from the Registrar Stakeholder Group shared feedback from registrars on previous Council calls. During its meeting on 17 November 2022<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>, representatives from ICANN org’s Contractual Compliance Team provided a briefing of the report<https://mm.icann.org/pipermail/council/2022-November/026164.html>, and the Council briefly considered potential next steps. Following its review of the report, the Council agreed that both the EDDP and ERRP may benefit from further work, though the timing for the work requires further consideration. In particular, as the Compliance report noted, the language of the policy is ambiguous in parts and has caused confusion for registrants. As the ERRP was implemented in part to ensure that “expiration-related provisions in typical registration agreements are clear and conspicuous enough” and to ensure that “adequate notice exists to alert registrants of upcoming expirations,” the continuing registrant confusion warrants further consideration. Additionally, some of the existing language has become obsolete due to intervening data protection law requirements and will require updates. To that end, the Council requested further information from ICANN org on what expiration-related educational materials are currently published and whether additional information can be provided (whether as registrant educational material referenced in Section 4.3 or elsewhere on ICANN’s website). The Council noted receipt of this information would be helpful to the Council in determining if updates to these materials or additional material in other forms could be helpful to combat the ongoing registrant confusion. Here, the Council will receive an update from ICANN org on the published materials. 6.1 - Introduction of Topic (Nacho Amadoz, Council Vice-Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - ICANN79 Preparation (20 minutes) Pre-ICANN79 GNSO Policy Webinar: * Monday, 26 February 2024 at 21:00 UTC Note: Mandatory for GNSO Council members During ICANN79, the GNSO Council has the following meetings and events scheduled (times listed in AST): Saturday, 2 March * 09:00-10:00 - IDNs EPDP Team Working Session * 13:15-14:30 - Transfer Policy Review PDP Working Group Session 1 of 2 * 15:00-16:00 - Transfer Policy Review PDP Working Group Session 2 of 2 * Time TBD: GNSO Council dinner Sunday, 3 March * 09:00-10:00 - GNSO Working Session 1 of 2 * 10:30-12:00 - GNSO Working Session 2 of 2 * 13:15-14:30 - GNSO Working Session 3 of 3 Monday, 04 March * 15:00-16:00 Joint ICANN Board and GNSO Council Tuesday, 05 March * 17:30-18:30 - GNSO Council Informal meeting [closed] Wednesday, 6 March * 09:00-10:00 - Joint GNSO Council & GAC * 10:30-12:00 - SubPro Supplemental Recommendations Community Consultation * 13:15-15:15- GNSO Council Meeting Thursday, 7 March * 09:00-10:00 - GNSO Council SubPro Small Team Plus Meeting * 15:00-16:00 - GNSO Council Wrap-Up During its Strategic Planning Session the Council agreed to conduct a triannual detailed review of the Program Management Tool. The action item coming from the SPS provided, “During a session at ICANN79, Council to prepare for a careful review of work captured in the Program Management Tool (PMT) that will conclude or initiate prior to the next AGM, or continue beyond the next AGM. Paul McGrady to coordinate with staff to plan for this inaugural effort.” Here, the Council will receive an overview of the current block schedule and plan for its in-person meetings. 7.1 - Introduction of Topic (Greg DiBiase, GNSO Council Chair) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL UPDATE: Draft NCAP Study 2 Report (15 minutes) The Name Collision Analysis Project Discussion Group (NCAP) is currently seeking input on its draft Study 2 report [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/name-collisio…> and responses to a series of questions from the ICANN Board regarding name collisions as outlined in resolution 2017.11.02.30<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> and reaffirmed in resolution 2021.03.25.13<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…>. The draft Study 2 report [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/name-collisio…> is structured to guide the reader through the methodology and significant findings of three pivotal research studies, as well as the analysis of the NCAP Discussion Group's extensive work activities. This material is what informs the eleven strategic recommendations provided at the end of the report. One of the key recommendations is the establishment of a new workflow, the Name Collision Risk Assessment Workflow, designed to enhance the assessment process of new generic top-level domains (gTLDs). This recommendation underscores the NCAP Discussion Group’s belief that name collisions should be approached not merely as a technical challenge but as a critical risk management issue. Here, the Council will receive an overview of the draft Study 2 report [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/name-collisio…> and have the opportunity to ask questions. 8.1 - Introduction of Topic (Greg DiBiase, GNSO Council Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: ANY OTHER BUSINESS (20 minutes) 9.1 - ccNSO & GAC Liaison updates (every three months) 9.2 - Board letter on Closed Generics 9.3 - Standing Predictability Implementation Review Team (“SPIRT”) Charter Drafting Team Update 9.4 - Status Update on Council Requests 9.5 - Update from Contracted Party House Abuse Subgroup’s Meeting with the Non-Commercial Stakeholder Group 9.6 - CCOICI Survey Reminder 9.7 - Update on diacritic study request. _______________________________ 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… [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> References for Coordinated Universal Time of 21:00 UTC Local time between November and March in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ [timeanddate.com]<https://urldefense.com/v3/__https:/www.timeanddate.com/time/change/__;!!PtG…> for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PST) UTC-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EST) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CET) UTC+1 22:00 Moscow, Russia (MSK) UTC+3 00:00 Singapore (SGT) UTC+8 05:00 Melbourne, Australia (AEDT) UTC+11 08:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.com/v3/__http:/www.timeanddate.com/__;!!PtGJab4!99g_M5Ib…> and http://tinyurl.com/42vy5duf [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/42vy5duf__;!!PtGJab4!99g_M5Ib…> _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Summary of domain name renewal and expiration educational resources (Feb Council Agenda Item 6)
by Caitlin Tubergen 14 Feb '24

14 Feb '24

Dear Councilors, Further to Agenda Item 6 for Thursday’s Council meeting, Next Steps for Consideration of Expired Domain Deletion Policy (“EDDP”) and Expired Registration Recovery Policy (“ERRP”), please find a summary of the current educational materials on domain name renewal and expiration attached. Brian Gutterman from ICANN org will be providing an overview of the materials during the Council meeting on Thursday. Kind regards, Caitlin

1 0

Re: [council] Motion re: Deferral of Data Accuracy Scoping Team work
by Terri Agnew 14 Feb '24

14 Feb '24

Hi Greg, Thank you for submitting this. We now have it on the GNSO Council motions wiki page<https://community.icann.org/x/9oAvEQ>. @Councilors, reminder this will need someone to second it, please let us know on the council mailing list. Thank you ever so much! Kind regards, Terri Policy Team Supporting the GNSO From: council <council-bounces(a)gnso.icann.org> on behalf of "DiBiase, Gregory via council" <COUNCIL(a)gnso.icann.org> Reply-To: "DiBiase, Gregory" <dibiase(a)amazon.com> Date: Monday, February 5, 2024 at 2:00 PM To: "COUNCIL(a)GNSO.ICANN.ORG" <COUNCIL(a)gnso.icann.org> Subject: [council] Motion re: Deferral of Data Accuracy Scoping Team work Dear Councilors, Please see the attached motion re: Deferral of Data Accuracy Scoping Team work. This vote will be held during the February meeting. Thanks, Greg

3 3