October 2022 - council - lists.icann.org

FYI: [Ext] ICANN and PTI Publish Audited Financial Statements for FY22
by Devan Reed 31 Oct '22

31 Oct '22

FYI [https://r20.rs6.net/on.jsp?ca=e602499a-2555-4b17-98e3-21c6cea42331&a=112202…] Monday, 31 October 2022 ICANN Community 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. 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=001jf8eltCdiKHmJJAN…> Table of Contents Information Sharing · NEW: ICANN and Partners: Celebrating 10 Years of the Africa DNS Forum · NEW:Two Years of Supporting DNSSEC Deployment in Africa and the Middle East · NEW: ICANN Participation in LACNIC 38 and LACNOG 2022 · NEW: ICANN and PTI Publish Audited Financial Statements for FY22 · NEW: OECD Reports on DNS and Routing Security Provide Blueprint for Policymakers · REMINDER: RPM Implementation Review Team: Call for Volunteers · REMINDER: Introducing the ICANN for Beginners Virtual Program · REMINDER: Call for Nominations Begins for ICANN Academy 2023 Leadership Program · REMINDER: ICANN Launches Fiscal Year 2024 Additional Budget Request Process Public Comment · CLOSES TODAY: Universal Acceptance Roadmap for Domain Name Registry and Registrar Systems · Pilot Holistic Review Draft Terms of Reference · Not-for-Profit Operational Concerns Constituency Charter Amendments · Proposed Updates to the GNSO Operating Procedures · Proposed Amendments to the Base gTLD RA and RAA to Add RDAP Contract Obligations · Draft IANA and PTI FY24 Operating Plan and Budgets · Proposed Amendments to the SLA for the IANA Numbering Services · Registration Data Consensus Policy for gTLDs · Initial Report on the Second CSC Effectiveness Review Information Sharing NEW: ICANN and Partners: Celebrating 10 Years of the Africa DNS Forum The Africa Domain Name System (DNS) Forum, held in Nairobi, Kenya, on 5–6 October 2022, attracted more than 200 participants. This marked the 10th year of this multistakeholder DNS industry event. Over the years, the DNS Forum has evolved to become an annual destination for stakeholders in the domain name industry in Africa, organized by Africa Top Level Domains Organization, the Africa Registrar Association, and the Internet Corporation for Assigned Names and Numbers (ICANN). Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> NEW: Two Years of Supporting DNSSEC Deployment in Africa and the Middle East The Domain Name System (DNS) is a critical service on the Internet. As more and more attacks exploit DNS vulnerabilities, security is increasingly a concern. ICANN has been supporting DNS Security Extensions (DNSSEC) deployment for many years through various initiatives and capacity-building programs. Such efforts have intensified over the past two years with the regionalization of its technical engagement coverage. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> NEW: ICANN Participation in LACNIC 38 and LACNOG 2022 After two and half years of the pandemic, I had the opportunity to participate in person, along with members from Office of the Chief Technology Officer (OCTO) at the Internet Corporation for Assigned Names and Numbers (ICANN), in the Latin American and Caribbean (LAC) Internet Addresses Registry (LACNIC 38) and the LAC Group of Network Operators (LACNOG 2022), held jointly from 3 to 7 October in Santa Cruz, Bolivia. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> NEW: ICANN and PTI Publish Audited Financial Statements for FY22 On 25 October 2022 the Internet Corporation for Assigned Names and Numbers (ICANN) published its audited consolidated financial statements and Public Technical Identifiers (PTI) published its audited financial statements for the fiscal year (FY) ending 30 June 2022. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> NEW: OECD Reports on DNS and Routing Security Provide Blueprint for Policymakers The Organization for Economic Cooperation and Development (OECD) has published a paper [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> on the Domain Name System (DNS), "Security of the Domain Name System (DNS): An Introduction for Policy Makers," and a paper [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> on routing security, "Routing Security: BGP Incidents, Mitigation Techniques and Policy Actions." Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> REMINDER: RPM Implementation Review Team: Call for Volunteers ICANN org is seeking volunteers to participate in an Implementation Review Team (IRT) to assist in the implementation of the policy recommendations from the Phase 1 work of the Policy Development Process (PDP) Working Group on the Review of All Rights Protection Mechanisms (RPMs) in All Generic Top-Level Domains (gTLDs). Read the announcement here. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> All relevant information for this IRT will be posted on the dedicated wiki page [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…>. REMINDER: Introducing the ICANN for Beginners Virtual Program The ICANN for Beginners Virtual Program comprises a series of interactive webinars to provide an overview of the global Internet ecosystem. The program will also guide newcomers on how to join the ICANN community. The first webinar "ICANN for Beginners: An Introduction" will be held during two time slots (you only need to register for one of the webinars): · Wednesday, 2 November 2022 at 14:00 UTC Click here to register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> · Thursday, 3 November 2022 at 06:00 UTC Click here to register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> · Registration closes on Tuesday, 1 November 2022 For enquiries, please email: beginners(a)icann.org [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> REMINDER: Call for Nominations Begins for ICANN Academy 2023 Leadership Program ICANN has issued a call for nominations for the 2023 Leadership Program to be held 9-10 March 2023 in Cancún, Mexico, which is just prior to ICANN76. The ICANN organization will reach out to the Supporting Organization, Advisory Committee, and Stakeholder Group chairs for nominations, and a registration link will be sent directly to individuals who are nominated. The deadline for nomination is Thursday, 10 November 2022. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> REMINDER: ICANN Launches Fiscal Year 2024 Additional Budget Request Process The ABR Process reflects potential ICANN community activities that are not already included in the annual ICANN operating plan and budget. The ABR process helps the ICANN Board and ICANN organization (org) better understand and develop resources for present and future ICANN community needs. More information about the FY24 ABR Process can be found on this workspace [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…>. ICANN org will host an informational webinar on Thursday, 08 December 2022, at 16:00 UTC. Please register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Public Comment CLOSES TODAY: Universal Acceptance Roadmap for Domain Name Registry and Registrar Systems [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 31 August 2022 Closed for submissions date: 31 October 2022 Pilot Holistic Review Draft Terms of Reference [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 30 August 2022 Closed for submissions date: 10 November 2022 Not-for-Profit Operational Concerns Constituency Charter Amendments [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 04 October 2022 Closed for submissions date: 14 November 2022 Proposed Updates to the GNSO Operating Procedures [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 09 September 2022 Closed for submissions date: 14 November 2022 Proposed Amendments to the Base gTLD RA and RAA to Add RDAP Contract Obligations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 06 September 2022 Closed for submissions date: 14 November 2022 Draft IANA and PTI FY24 Operating Plan and Budgets [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 15 September 2022 Closed for submissions date: 17 November 2022 Proposed Amendments to the SLA for the IANA Numbering Services [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 13 September 2022 Closed for submissions date: 18 November 2022 Registration Data Consensus Policy for gTLDs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 24 August 2022 Closed for submissions date: 21 November 2022 Initial Report on the Second CSC Effectiveness Review [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> Open for submissions date: 14 September 2022 Closed for submissions date: 01 December 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…>. Volume 4, Issue 79 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…> | Next Issue: Thursday, 03 November 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001jf8eltCdiKHmJJAN…>

1 0

GNSO Council Absence Notification Form: Swsw
by GNSO Council via ICANN 30 Oct '22

30 Oct '22

Full Name of Officer: مراد مروان صالح السعايده Officer Email Address: Mrwansaydh4(a)gmail.com Date Prepared: 30 October 2022 GNSO Organization: Registries Stakeholder Group Officer Position or Title: Swsw Name of Absent Councilor: Swsw Voting Remedy: Voting Direction Voting Direction Information Reason(s) for or condition(s) leading to the remedy: Swsw Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: Swsw Date upon which the remedy will expire or terminate: 30 November 2022 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s).Yes By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0

GNSO Council Absence Notification Form: Swsw
by GNSO Council via ICANN 30 Oct '22

30 Oct '22

Full Name of Officer: مراد مروان صالح السعايده Officer Email Address: Mrwansaydh4(a)gmail.com Date Prepared: 28 November 2022 GNSO Organization: Non-Commercial Users Constituency Officer Position or Title: Swsw Name of Absent Councilor: Swsw Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Swsw Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: Swsw Date upon which the remedy will expire or terminate: 31 October 2022 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). Yes Full Name of GNSO Councilor Serving as Voting Proxy: مرادمروان صالح السعايده By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0

FYI: FW: [Ext] REGISTER for the ICANN for Beginners Virtual Program NOW!
by Terri Agnew 27 Oct '22

27 Oct '22

FYI [https://r20.rs6.net/on.jsp?ca=4f5e231c-ffa5-497d-9dcb-3cdaf669632b&a=112202…] Thursday, 27 October 2022 ICANN Community 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. 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=001tb1r3QaQE06pckBK…> Table of Contents Information Sharing · NEW: Update on the ICANN Independent Review Process Standing Panel Composition · NEW: Chair’s Blog: Highlights From the September Board Workshop · REMINDER: RPM Implementation Review Team: Call for Volunteers · REMINDER: Introducing the ICANN for Beginners Virtual Program · REMINDER: Call for Nominations Begins for ICANN Academy 2023 Leadership Program · REMINDER: ICANN Launches Fiscal Year 2024 Additional Budget Request Process Public Comment · LAST CALL: Universal Acceptance Roadmap for Domain Name Registry and Registrar Systems · Pilot Holistic Review Draft Terms of Reference · Not-for-Profit Operational Concerns Constituency Charter Amendments · Proposed Updates to the GNSO Operating Procedures · Proposed Amendments to the Base gTLD RA and RAA to Add RDAP Contract Obligations · Draft IANA and PTI FY24 Operating Plan and Budgets · Proposed Amendments to the SLA for the IANA Numbering Services · Registration Data Consensus Policy for gTLDs · Initial Report on the Second CSC Effectiveness Review Information Sharing NEW: Update on the ICANN Independent Review Process Standing Panel Composition Since March, we have been meeting regularly. You can follow our progress on this [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>wiki [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>, although much of the substance of our work will remain confidential in light of the personal details and backgrounds that we are reviewing. On the wiki [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>, you can also see the terms of engagement of the various participants in this process, as well as the terms of reference for our work. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> NEW: Chair’s Blog: Highlights From the September Board Workshop ICANN75 was the first hybrid AGM since the onset of the global pandemic. The energy and engagement of the ICANN Community was palpable and exciting! Prior to the AGM, the Board came together for a hybrid workshop 15–18 September, led by former Board Chair Maarten Botterman. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> REMINDER: RPM Implementation Review Team: Call for Volunteers ICANN org is seeking volunteers to participate in an Implementation Review Team (IRT) to assist in the implementation of the policy recommendations from the Phase 1 work of the Policy Development Process (PDP) Working Group on the Review of All Rights Protection Mechanisms (RPMs) in All Generic Top-Level Domains (gTLDs). Read the announcement here. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> All relevant information for this IRT will be posted on the dedicated wiki page [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>. REMINDER: Introducing the ICANN for Beginners Virtual Program The ICANN for Beginners Virtual Program comprises a series of interactive webinars to provide an overview of the global Internet ecosystem. The program will also guide newcomers on how to join the ICANN community. The first webinar "ICANN for Beginners: An Introduction" will be held during two time slots (you only need to register for one of the webinars): · Wednesday, 2 November 2022 at 14:00 UTC Click here to register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> · Thursday, 3 November 2022 at 06:00 UTC Click here to register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> · Registration closes on Tuesday, 1 November 2022 For enquiries, please email: beginners(a)icann.org [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> REMINDER: Call for Nominations Begins for ICANN Academy 2023 Leadership Program ICANN has issued a call for nominations for the 2023 Leadership Program to be held 9-10 March 2023 in Cancún, Mexico, which is just prior to ICANN76. The ICANN organization will reach out to the Supporting Organization, Advisory Committee, and Stakeholder Group chairs for nominations, and a registration link will be sent directly to individuals who are nominated. The deadline for nomination is Thursday, 10 November 2022. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> REMINDER: ICANN Launches Fiscal Year 2024 Additional Budget Request Process The ABR Process reflects potential ICANN community activities that are not already included in the annual ICANN operating plan and budget. The ABR process helps the ICANN Board and ICANN organization (org) better understand and develop resources for present and future ICANN community needs. More information about the FY24 ABR Process can be found on this workspace [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>. ICANN org will host an informational webinar on Thursday, 08 December 2022, at 16:00 UTC. Please register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Public Comment LAST CALL: Universal Acceptance Roadmap for Domain Name Registry and Registrar Systems [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 31 August 2022 Closed for submissions date: 31 October 2022 Pilot Holistic Review Draft Terms of Reference [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 30 August 2022 Closed for submissions date: 10 November 2022 Not-for-Profit Operational Concerns Constituency Charter Amendments [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 04 October 2022 Closed for submissions date: 14 November 2022 Proposed Updates to the GNSO Operating Procedures [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 09 September 2022 Closed for submissions date: 14 November 2022 Proposed Amendments to the Base gTLD RA and RAA to Add RDAP Contract Obligations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 06 September 2022 Closed for submissions date: 14 November 2022 Draft IANA and PTI FY24 Operating Plan and Budgets [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 15 September 2022 Closed for submissions date: 17 November 2022 Proposed Amendments to the SLA for the IANA Numbering Services [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 13 September 2022 Closed for submissions date: 18 November 2022 Registration Data Consensus Policy for gTLDs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 24 August 2022 Closed for submissions date: 21 November 2022 Initial Report on the Second CSC Effectiveness Review [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> Open for submissions date: 14 September 2022 Closed for submissions date: 01 December 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>. Volume 4, Issue 78 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…> | Next Issue: Monday, 31 October 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001tb1r3QaQE06pckBK…>

1 0

Re: [council] GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO
by Marika Konings 27 Oct '22

27 Oct '22

Dear All, Thank you again for your participation in the discussion on the next steps for the different PDP Improvements. The tracker has been updated in line with the discussion and posted on the dedicated wiki page for this effort: https://community.icann.org/x/e4OLD. We’ll keep you posted as we start work on the next steps for the different items. Best regards, Marika From: council <council-bounces(a)gnso.icann.org> on behalf of Marika Konings via council <COUNCIL(a)GNSO.ICANN.ORG> Reply to: Marika Konings <marika.konings(a)icann.org> Date: Tuesday, 25 October 2022 at 12:11 To: "Demetriou, Samantha" <sdemetriou(a)verisign.com>, Ashley Heineman <aheineman(a)godaddy.com>, Johan Helsingius <julf(a)Julf.com>, "Cole, Mason (Perkins Coie)" <MCole(a)perkinscoie.com>, Lori Schulman <lschulman(a)inta.org>, "wuknoben(a)gmail.com" <wuknoben(a)gmail.com>, Benjamin Akinmoyeje <benakin(a)gmail.com>, Raoul Plommer <plommer(a)gmail.com>, "COUNCIL(a)GNSO.ICANN.ORG" <COUNCIL(a)GNSO.ICANN.ORG> Cc: Andrea Glandon <andrea.glandon(a)icann.org>, Brenda Brewer <brenda.brewer(a)icann.org> Subject: [council] GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO Sent on behalf of Sebastien Ducos **************** Dear All, Based on the survey results<https://community.icann.org/download/attachments/206144128/PDP%20Improvemen…> and the subsequent discussion during the ICANN75 session, the Council leadership team is recommending moving forward with the following PDP Improvements as outlined in the table below. Please note that the proposed next steps represent an incremental step – once this step has been implemented, there will be another opportunity for the GNSO community to consider how to proceed. For the upcoming meeting, Council leadership suggests focusing on those next steps that Council or SG/C Chairs do not support so we can focus on those during the meeting and start moving forward with items that do not raise any concerns. As such, please flag in advance of the meeting which items you would like to discuss further. As a reminder, the meeting is scheduled for Wednesday 25 October at 19.00 UTC. The first half of the meeting will be dedicated to the PDP Improvements discussion, the second half will focus on the next steps concerning the Standing Committee on ICANN Budget and Operations (SCBO). On behalf of Council leadership, Sebastien Improvement Next Step Who is responsible for next step #1 - Enable a process during the PDP to share relevant information and analysis on potential impacts to existing policies, to support consideration by PDP working groups (define this process as part of the GDS liaison role) Council to review Guidelines for GDS Liaisons to PDPs and determine whether anything further is needed to consider this improvement complete GNSO Council #2 - The Council should consider sharing with the ICANN Board when certain items are expected to move from Council to Board to facilitate advance planning by the ICANN Board Derive from the project list and ADR items expected to be delivered to the ICANN Board in the coming year. In combination with sharing its SPS report, the Council communicates to the Board which items are expected to be forwarded to the ICANN Board for its consideration during that year to allow the ICANN Board to anticipate as part of its planning when it may need to consider GNSO policy recommendations. GNSO Staff Support Team GNSO Council #3 - Following adoption of a PDP Final Report by the GNSO Council, schedule a meeting with the ICANN Board to allow the GNSO Council, with the assistance of the PDP Chair(s), to present the Final Report and recommendations to the ICANN Board and allow for Q & A. An invitation has been sent to the ICANN Board to provide a briefing on the IGO Curative Rights EPDP recommendations. Proposed presentation / slides are to be shared in advance of the meeting with the Board to ensure that it is a neutral representation of the results and does not interfere with independent review. Following meeting, debrief with Council & GNSO appointed Board members to determine if this was helpful and/or whether it should be continued Council & GNSO Appointed Board members #4 - Add to the charter template a general or specific provision / question regarding consideration of impact on existing consensus policies Staff support team to create for Council review proposed addition for charter template that would highlight the expectation that a PDP WG is to consider the impact of its recommendation on existing consensus policies. Review proposed addition (note, the template can always be modified as needed to ensure that it is fit for purpose, including calling out specific existing policies that should be factored in) GNSO Staff Support Team GNSO Council #5 - Include in the Final Report template a section to address any direct or indirect implications for existing policies, to support full consideration by the PDP working groups and the GNSO Council. This may include implementation guidance where appropriate. Staff support team to include in the Final Report template a section to address any direct or indirect implications for existing Policies. Inclusion of this section by a PDP Team will be linked to any charter requirement in this regard. Review proposed addition to Final Report template Staff Support Team GNSO Council #6 - Consider if/how the role of the Board liaison of a PDP can contribute to more effective communication. This could, for example, be done by communicating clearly at the outset of a PDP the expected role of the Board liaison. Include link to Board Liaison guidelines in charter template so that if Board liaison is included as part of the charter, the role and expectations can be considered in the context of the review of the charter Review proposed update to charter template GNSO Staff Support Team GNSO Council #7 - Update CPIF to note that as part of implementing a new policy, ICANN org and the IRT review updates to other policies and incorporate as part of the implementation plan Requests GDS to provide an indication of possible timing & consultation of such updates to the CPIF (note, last round of updates were made in 2018 and involved consultation with the GNSO Council / community – the communication should confirm that the expectation is that the same approach would be used). Council Leadership #8 - Review of Policy & Implementation Recommendations Provide further detail on what a policy status review (PSR) would be expected to cover and confirm that a PSR does not mean that a review is initiated but it allows Council to consider whether or not a review is appropriate, and what should be considered as part of a review, if initiated. Review PSR details and decide if/how to proceed. GNSO Staff Support GNSO Council #9 – Review of the Operational Design Phase Develop straightforward survey that can be used to solicit input from the GNSO Council liaison to the SSAD ODP as well as the small team that was tasked to review the ODP to document its findings so that these can be shared when the review takes place after the second ODP completes. Review proposed survey. Notify the Council Liaison to the SubPro ODP that there will be the expectation to provide input on the experience with the ODP so that he can prepare and document his findings accordingly. GNSO Staff Support Team GNSO Council Council Leadership

1 0

Recordings | GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO | 26 Oct 2022
by Terri Agnew 26 Oct '22

26 Oct '22

Dear all, Please find below the audio recording, zoom recording (audio, visual, rough transcript) and zoom chat of the GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO held on Wednesday, 26 October 2022 at 19:00 UTC. Audio only: https://icann.zoom.us/rec/play/jOq1S2_OspuJ1CFQUVj8Lx2j_3n77JewrLGOf4RzuNk0… Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/share/g1qPnAgtSuaOcTpfR5x9SkA3Ecq2u4Jd6uofFDp2mmt… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Thank you. With kind regards, Terri --- Terri Agnew Policy Operations Specialist (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

**Starting in 15 minutes | Meeting Invite - GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO
by Terri Agnew 26 Oct '22

26 Oct '22

**Starting in 15 minutes Dear all, Please see the details below for the GNSO Council & SG/C Chairs call to discuss PDP Improvements & Next Steps Standing Committee on ICANN Budget and Operations (SCBO) taking place on Wednesday, 26 October 2022 at 19:00 UTC for 90 minutes. For other time zones: https://tinyurl.com/vndva5y5 <https://urldefense.com/v3/__https:/tinyurl.com/vndva5y5__;!!PtGJab4!9l6ayf7…> Please click the link below to join the webinar: https://icann.zoom.us/j/95188120788?pwd=WnRXWW52dVZ3T2ZUdFhzc1lkVlM3QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/95188120788?pwd=WnRXWW52…> Passcode: Zx9DKcpc$L Audio only: Webinar ID: 951 8812 0788 Passcode: 4945336565 International numbers available: https://icann.zoom.us/u/aYEpTXpjp [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/aYEpTXpjp__;!!PtGJab4!9l…> Thank you. Kind regards, Julie -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO
by Marika Konings 26 Oct '22

26 Oct '22

Sent on behalf of Sebastien Ducos **************** Dear All, Based on the survey results<https://community.icann.org/download/attachments/206144128/PDP%20Improvemen…> and the subsequent discussion during the ICANN75 session, the Council leadership team is recommending moving forward with the following PDP Improvements as outlined in the table below. Please note that the proposed next steps represent an incremental step – once this step has been implemented, there will be another opportunity for the GNSO community to consider how to proceed. For the upcoming meeting, Council leadership suggests focusing on those next steps that Council or SG/C Chairs do not support so we can focus on those during the meeting and start moving forward with items that do not raise any concerns. As such, please flag in advance of the meeting which items you would like to discuss further. As a reminder, the meeting is scheduled for Wednesday 25 October at 19.00 UTC. The first half of the meeting will be dedicated to the PDP Improvements discussion, the second half will focus on the next steps concerning the Standing Committee on ICANN Budget and Operations (SCBO). On behalf of Council leadership, Sebastien Improvement Next Step Who is responsible for next step #1 - Enable a process during the PDP to share relevant information and analysis on potential impacts to existing policies, to support consideration by PDP working groups (define this process as part of the GDS liaison role) Council to review Guidelines for GDS Liaisons to PDPs and determine whether anything further is needed to consider this improvement complete GNSO Council #2 - The Council should consider sharing with the ICANN Board when certain items are expected to move from Council to Board to facilitate advance planning by the ICANN Board Derive from the project list and ADR items expected to be delivered to the ICANN Board in the coming year. In combination with sharing its SPS report, the Council communicates to the Board which items are expected to be forwarded to the ICANN Board for its consideration during that year to allow the ICANN Board to anticipate as part of its planning when it may need to consider GNSO policy recommendations. GNSO Staff Support Team GNSO Council #3 - Following adoption of a PDP Final Report by the GNSO Council, schedule a meeting with the ICANN Board to allow the GNSO Council, with the assistance of the PDP Chair(s), to present the Final Report and recommendations to the ICANN Board and allow for Q & A. An invitation has been sent to the ICANN Board to provide a briefing on the IGO Curative Rights EPDP recommendations. Proposed presentation / slides are to be shared in advance of the meeting with the Board to ensure that it is a neutral representation of the results and does not interfere with independent review. Following meeting, debrief with Council & GNSO appointed Board members to determine if this was helpful and/or whether it should be continued Council & GNSO Appointed Board members #4 - Add to the charter template a general or specific provision / question regarding consideration of impact on existing consensus policies Staff support team to create for Council review proposed addition for charter template that would highlight the expectation that a PDP WG is to consider the impact of its recommendation on existing consensus policies. Review proposed addition (note, the template can always be modified as needed to ensure that it is fit for purpose, including calling out specific existing policies that should be factored in) GNSO Staff Support Team GNSO Council #5 - Include in the Final Report template a section to address any direct or indirect implications for existing policies, to support full consideration by the PDP working groups and the GNSO Council. This may include implementation guidance where appropriate. Staff support team to include in the Final Report template a section to address any direct or indirect implications for existing Policies. Inclusion of this section by a PDP Team will be linked to any charter requirement in this regard. Review proposed addition to Final Report template Staff Support Team GNSO Council #6 - Consider if/how the role of the Board liaison of a PDP can contribute to more effective communication. This could, for example, be done by communicating clearly at the outset of a PDP the expected role of the Board liaison. Include link to Board Liaison guidelines in charter template so that if Board liaison is included as part of the charter, the role and expectations can be considered in the context of the review of the charter Review proposed update to charter template GNSO Staff Support Team GNSO Council #7 - Update CPIF to note that as part of implementing a new policy, ICANN org and the IRT review updates to other policies and incorporate as part of the implementation plan Requests GDS to provide an indication of possible timing & consultation of such updates to the CPIF (note, last round of updates were made in 2018 and involved consultation with the GNSO Council / community – the communication should confirm that the expectation is that the same approach would be used). Council Leadership #8 - Review of Policy & Implementation Recommendations Provide further detail on what a policy status review (PSR) would be expected to cover and confirm that a PSR does not mean that a review is initiated but it allows Council to consider whether or not a review is appropriate, and what should be considered as part of a review, if initiated. Review PSR details and decide if/how to proceed. GNSO Staff Support GNSO Council #9 – Review of the Operational Design Phase Develop straightforward survey that can be used to solicit input from the GNSO Council liaison to the SSAD ODP as well as the small team that was tasked to review the ODP to document its findings so that these can be shared when the review takes place after the second ODP completes. Review proposed survey. Notify the Council Liaison to the SubPro ODP that there will be the expectation to provide input on the experience with the ODP so that he can prepare and document his findings accordingly. GNSO Staff Support Team GNSO Council Council Leadership

4 3

Re: [council] [Ext] RE: GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO
by Marika Konings 25 Oct '22

25 Oct '22

Thanks, Anne. Please find some responses to your questions in blue below. Best regards, Marika From: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com> Date: Tuesday, 25 October 2022 at 19:53 To: Marika Konings <marika.konings(a)icann.org>, "Demetriou, Samantha" <sdemetriou(a)verisign.com>, Ashley Heineman <aheineman(a)godaddy.com>, Johan Helsingius <julf(a)Julf.com>, "Cole, Mason (Perkins Coie)" <MCole(a)perkinscoie.com>, Lori Schulman <lschulman(a)inta.org>, "wuknoben(a)gmail.com" <wuknoben(a)gmail.com>, Benjamin Akinmoyeje <benakin(a)gmail.com>, Raoul Plommer <plommer(a)gmail.com>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: Andrea Glandon <andrea.glandon(a)icann.org>, Brenda Brewer <brenda.brewer(a)icann.org> Subject: [Ext] RE: GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO Thank you, Marika. Regarding Recommendation #1, my recollection is that the GDS Guidelines for GDS Liaisons to PDPs is quite thorough. Could you please send these around again via link or pdf before tomorrow’s meeting? A concern here is that participation by the Liaison should be active and timely. In the past, we have had active participation but I believe there may have been reluctance to provide too much concrete input because the Working Group had not reached a final conclusion during its deliberations as to where the policy development was headed. This is a bit of a “chicken and egg” problem. I’m sure Karen Lentz could be helpful in providing comments as to how the GDS Liaison can deal with that dynamic. What we absolutely must avoid is late-breaking advice from GDS as to whether policies under discussion can be executed or not. The feasibility of any policy under discussion by the WG needs to be addressed at the policy development stage. Otherwise, this improvement could become a “roadblock”. Here is the link to the GDS Guidelines: https://mm.icann.org/pipermail/council/attachments/20220919/fa2e1ac6/Guidel… Regarding Recommendation #2 as to Council sharing anticipated time frames with the Board. Can we be more specific as to what is required of Council in connection with adopting this improvement? The verb, “consider” is pretty vague. Do we mean that Council should “endeavor to share time frames with the Board as early as possible”? This is how this improvement was formulated in the 2021 SPS meeting report from which this improvement stems. Maybe this additional context is helpful: “Status and next steps of GNSO policy recommendations post-Council adoption - The Council should explore how it can assist in keeping the ball rolling once policy recommendations leave the Council – for example, the Council could be more proactive in asking the ICANN Board and ICANN org about expected timing / timelines as well as how it can assist in making sure things move forward. In addition, the Council should consider sharing with the ICANN Board when certain items are expected to move from Council to Board to facilitate advance planning by the ICANN Board.” (from the SPS Meeting Report) Recommendation #3 looks solid and attainable to me. Recommendation #4 – As I commented in the survey, it would be unfair for the Chair and WG members to be tasked with identifying all policies that might be affected by their work on a specific PDP. If staff identifies the policies that need to be reviewed by the WG in advance, that is a task that is well-defined and attainable. A “general” instruction to the PDP Working Group to “identify other policies that are affected” is unworkable. In addition to staff identification of possible implications, would it not be incumbent on the GDS Liaison to raise any new or late-breaking effects on existing policies as the work progresses in the WG and to bring that question to the attention of the WG Chairs? Could we say that (1) existing policies to be reviewed by the WG should be specifically identified and (2) WG should also review any existing policies that are identified by the GDS Liaison as needing to be analyzed in the course of the WG’s Deliberations? Recommendation #5 – For the WG to include in the Final Report “any direct or indirect” effect on existing policies. Again, this is overly broad in scope. If a particular policy has been identified in the Charter as requiring review OR if the GDS Liaison has identified an existing policy that is affected, then it makes sense to require the Working Group to address that in the Final Report. As we all know, policy development and implementation is an ongoing and iterative process. We should not be creating obligations on the Working Group that lend themselves to getting mired down in processes that ultimately should be handled at the IRT level. Recommendation #6 re Role of Board Liaison to the PDP looks good to me. Recommendation #7 – not sure how we can approve this without knowing the future of the Operational Design Phase. When you update the Consensus Policy Implementation Framework as recommended, how do you account for the possible duplication of effort if the PDP Outcomes have already been reviewed by ICANN Org in the Operational Design Phase? For example, you now have an Operational Design Assessment that will be coming from ICANN Org on the Sub Pro Recommendations. If you update the CPIF as recommended here, does that mean ICANN Org comes back again at the IRT phase and does additional assessments? How would the amendment to the CPIF interact with the ODP and ODA process created by the Board which is still being assessed? It seems to me that this Recommendation is subject to and has to be put on hold until Recommendation 9 is accomplished – #9 is Review of ODP process. Note that the proposed next step is only about asking about a possible timeline for future updates to the CPIF. Recommendation #8 – Review of the Policy Status Report details certainly makes sense. How do we fit this work into the list of priorities? Is this a Small Team assignment for Council? (Maybe I don’t understand the proposed execution of this improvement. If so, I apologize.) The proposed next step is for staff to further detail what a Policy Status Report would entail, so that the Council can review if would like the staff support team to move forward with the PSR. This is not expected to be a long document just a high level overview but it is of course up to the Council to decide if it would need to form a small team to review this. Recommendation #9 – Review of ODP - Support this one and believe that the proposed survey should be expanded to a wide audience in the community. Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image002.png@01D8E8B1.373B05A0] From: council <council-bounces(a)gnso.icann.org> On Behalf Of Marika Konings via council Sent: Tuesday, October 25, 2022 3:10 AM To: Demetriou, Samantha <sdemetriou(a)verisign.com>; Ashley Heineman <aheineman(a)godaddy.com>; Johan Helsingius <julf(a)Julf.com>; Cole, Mason (Perkins Coie) <MCole(a)perkinscoie.com>; Lori Schulman <lschulman(a)inta.org>; wuknoben(a)gmail.com; Benjamin Akinmoyeje <benakin(a)gmail.com>; Raoul Plommer <plommer(a)gmail.com>; council(a)gnso.icann.org Cc: Andrea Glandon <andrea.glandon(a)icann.org>; Brenda Brewer <brenda.brewer(a)icann.org> Subject: [council] GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO [EXTERNAL] ________________________________ Sent on behalf of Sebastien Ducos **************** Dear All, Based on the survey results<https://community.icann.org/download/attachments/206144128/PDP%20Improvemen…> and the subsequent discussion during the ICANN75 session, the Council leadership team is recommending moving forward with the following PDP Improvements as outlined in the table below. Please note that the proposed next steps represent an incremental step – once this step has been implemented, there will be another opportunity for the GNSO community to consider how to proceed. For the upcoming meeting, Council leadership suggests focusing on those next steps that Council or SG/C Chairs do not support so we can focus on those during the meeting and start moving forward with items that do not raise any concerns. As such, please flag in advance of the meeting which items you would like to discuss further. As a reminder, the meeting is scheduled for Wednesday 25 October at 19.00 UTC. The first half of the meeting will be dedicated to the PDP Improvements discussion, the second half will focus on the next steps concerning the Standing Committee on ICANN Budget and Operations (SCBO). On behalf of Council leadership, Sebastien Improvement Next Step Who is responsible for next step #1 - Enable a process during the PDP to share relevant information and analysis on potential impacts to existing policies, to support consideration by PDP working groups (define this process as part of the GDS liaison role) Council to review Guidelines for GDS Liaisons to PDPs and determine whether anything further is needed to consider this improvement complete GNSO Council #2 - The Council should consider sharing with the ICANN Board when certain items are expected to move from Council to Board to facilitate advance planning by the ICANN Board Derive from the project list and ADR items expected to be delivered to the ICANN Board in the coming year. In combination with sharing its SPS report, the Council communicates to the Board which items are expected to be forwarded to the ICANN Board for its consideration during that year to allow the ICANN Board to anticipate as part of its planning when it may need to consider GNSO policy recommendations. GNSO Staff Support Team GNSO Council #3 - Following adoption of a PDP Final Report by the GNSO Council, schedule a meeting with the ICANN Board to allow the GNSO Council, with the assistance of the PDP Chair(s), to present the Final Report and recommendations to the ICANN Board and allow for Q & A. An invitation has been sent to the ICANN Board to provide a briefing on the IGO Curative Rights EPDP recommendations. Proposed presentation / slides are to be shared in advance of the meeting with the Board to ensure that it is a neutral representation of the results and does not interfere with independent review. Following meeting, debrief with Council & GNSO appointed Board members to determine if this was helpful and/or whether it should be continued Council & GNSO Appointed Board members #4 - Add to the charter template a general or specific provision / question regarding consideration of impact on existing consensus policies Staff support team to create for Council review proposed addition for charter template that would highlight the expectation that a PDP WG is to consider the impact of its recommendation on existing consensus policies. Review proposed addition (note, the template can always be modified as needed to ensure that it is fit for purpose, including calling out specific existing policies that should be factored in) GNSO Staff Support Team GNSO Council #5 - Include in the Final Report template a section to address any direct or indirect implications for existing policies, to support full consideration by the PDP working groups and the GNSO Council. This may include implementation guidance where appropriate. Staff support team to include in the Final Report template a section to address any direct or indirect implications for existing Policies. Inclusion of this section by a PDP Team will be linked to any charter requirement in this regard. Review proposed addition to Final Report template Staff Support Team GNSO Council #6 - Consider if/how the role of the Board liaison of a PDP can contribute to more effective communication. This could, for example, be done by communicating clearly at the outset of a PDP the expected role of the Board liaison. Include link to Board Liaison guidelines in charter template so that if Board liaison is included as part of the charter, the role and expectations can be considered in the context of the review of the charter Review proposed update to charter template GNSO Staff Support Team GNSO Council #7 - Update CPIF to note that as part of implementing a new policy, ICANN org and the IRT review updates to other policies and incorporate as part of the implementation plan Requests GDS to provide an indication of possible timing & consultation of such updates to the CPIF (note, last round of updates were made in 2018 and involved consultation with the GNSO Council / community – the communication should confirm that the expectation is that the same approach would be used). Council Leadership #8 - Review of Policy & Implementation Recommendations Provide further detail on what a policy status review (PSR) would be expected to cover and confirm that a PSR does not mean that a review is initiated but it allows Council to consider whether or not a review is appropriate, and what should be considered as part of a review, if initiated. Review PSR details and decide if/how to proceed. GNSO Staff Support GNSO Council #9 – Review of the Operational Design Phase Develop straightforward survey that can be used to solicit input from the GNSO Council liaison to the SSAD ODP as well as the small team that was tasked to review the ODP to document its findings so that these can be shared when the review takes place after the second ODP completes. Review proposed survey. Notify the Council Liaison to the SubPro ODP that there will be the expectation to provide input on the experience with the ODP so that he can prepare and document his findings accordingly. GNSO Staff Support Team GNSO Council Council Leadership ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

1 0

Post Oct Council meeting - Motion vs Letter as ODA response to the Board
by Sebastien＠registry.godaddy 25 Oct '22

25 Oct '22

Dear All, as mentioned during last week’s Council meeting, the Council will need to consider how to communicate its views to the ICANN Board in relation to the Whois Disclosure System. One option is to do this via a motion, which is the standard way in which the Council takes and confirms an action. Another option could be to do this via a letter, similar to how the Council’s perspective have been shared on other topics in relation to this conversation such as the ODA and the preliminary report of the EPDP Phase 2 team. In order to determine the preferred path forward, the Council may want to consider the following: * Motion – as this is not an action that is called out in the Bylaws, the threshold for the motion to pass would be a simple majority vote of each House. The voting results are recorded and publicly available. The results of the vote would be communicated immediately to the ICANN Board for its review and consideration. * Letter – a Council letter is typically agreed to in the form of non-objection. Unless a letter is drafted, agreed and considered as part of the November Council meeting, there may be some additional time needed after the November Council meeting to draft this letter and obtain non-objection from the Council to send it. You will have seen that a draft motion was already shared for review prior to the last Council meeting. The approach taken in that motion is that the Council would adopt the conclusions of the EPDP Phase 2 small team that are recorded in the addendum (which is in the process of being finalized). My assumption is that a letter would follow a similar path by either calling out certain elements in the letter which would serve as the vehicle to transmit the addendum. As at this stage, the EPDP Phase 2 small team is working on the assumption that, at a minimum, there will be support from all GNSO SG/Cs for the addendum recommending moving forward with the Whois Disclosure System. Although there is no requirement to do so, a motion is the method by which the Council documents its actions and directions to the ICANN Board. As such, for accountability and transparency reasons, and recognizing that this is requesting the ICANN Board and ICANN org to commit resources to this effort, I would personally suggest following the motion path here. If there is a strong view that a letter is preferred, I am happy to be convinced otherwise, but I hope we can spend our energy on considering the substance of the matter instead of getting distracted by procedural options. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_3031963986] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

2 1