July 2021 - council - lists.icann.org

FW: [Ext] Monday, 19 July 2021
by Andrea Glandon July 19, 2021

July 19, 2021

[https://r20.rs6.net/on.jsp?ca=6bdc322d-1725-4274-9152-9959d4199944&a=112202…] Monday, 19 July 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. 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=001PtPppMfOKa7GmfXm…> Table of Contents Webinars · TOMORROW: "The UN, the EU, and Your Business, What Comes Next?" Webinar · THURSDAY: DNS Security Threat Mitigation Program Webinar · NEXT WEEK: FY23 IANA Functions and PTI Planning Webinar · REMINDER: ITI Update: Register Now for ICANN Public Comment Submission Training Webinars Information Sharing · TODAY: Request for Information on Identity Verification Methods for SSAD Closes Today · THURSDAY: Community Input Needed: SSAD ODP Questionnaire · NEW: ICANN72 to be Virtual Annual General Meeting, ICANN73 Planning Update · NEXT WEEK: Ninth Africa DNS Forum to Take Place Virtually 27-28 July 2021 · REMINDER: Nomination Period Opens for Dr. Tarek Kamel Award for Capacity Building · REMINDER: Request for Early Input - GNSO Transfer Policy Review PDP Working Group · REMINDER: APIGA 2021 Application Period Is Now Open · REMINDER: Nominations for NextGen@ICANN Mentor Positions Now Open Public Comment · NEXT WEEK: Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A · Proposed Renewal of the .AERO Registry Agreement [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> · NEW: Proposal for Greek Root Zone Label Generation Rules Webinars TOMORROW: "The UN, the EU, and Your Business, What Comes Next?" Webinar On Tuesday, 20 July 2021 at 16:00 UTC, the ICANN org North America Engagement team will host a webinar related to deliberations on how the infrastructure layer of the Internet is governed that are happening at the United Nations (UN) and within the European Union (EU). These discussions and proposed actions could affect the business sector. Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. THURSDAY: DNS Security Threat Mitigation Program Webinar ICANN will host a webinar on Thursday, 22 July 2021 at 16:00 UTC to provide the ICANN community with updates on its DNS Security Threat Mitigation Program, community-facing initiatives, Domain Abuse Activity Reporting System (DAAR), and Domain Name Security Threat Information Collection and Reporting (DNSTICR) project. Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. NEXT WEEK: FY23 IANA Functions and PTI Planning Webinar ICANN invites the community to join one of two public webinars to discuss planning for the fiscal year 2023 (FY23) Operating Plan and Budget (OP&B) for delivering the Internet Assigned Numbers Authority (IANA) functions. The webinar will explain the planning process, the proposed operational priorities for FY23, timelines, and key assumptions. ICANN welcomes the community's questions and comments. Webinar 1 | Tuesday, 27 July 2021 | 00:00 UTC | Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> Webinar 2 | Tuesday, 27 July 2021 | 16:00 UTC | Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> The annual OP&B for the IANA functions has two components: a budget and operating plan for Public Technical Identifiers (PTI), the ICANN affiliate that performs the IANA functions, which outlines the planned activities and resources to deliver the core IANA functions. The second component includes the PTI budget plus additional programs and costs that the ICANN organization incurs overseeing and enabling the IANA functions. In addition to the webinars, the community has further opportunity to participate in this planning process. The draft plans will be put out for Public Comment in September before being considered for formal adoption in late 2021. REMINDER: ITI Update: Register Now for ICANN Public Comment Submission Training Webinars ICANN org will hold a series of training webinars outlining the new Public Comment submission process. During these sessions, our teams will provide the ICANN community with step-by-step instructions on how to draft and publish a Public Comment submission and outline how to manage your current and past submissions. You are encouraged to ask questions throughout these webinars to ensure you are well-prepared to use this improved feature. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> Webinar 1 | Tuesday, 3 August 2021 | 14:00 UTC | Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> Webinar 2 | Wednesday, 4 August 2021 | 21:00 UTC | Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> Information Sharing TODAY: Request for Information on Identity Verification Methods for SSAD Closes Today ICANN org announced [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> that it has now opened the Request for Information (RFI) to better understand what may be commercially available in the marketplace to deliver some or all of the System for Standardized Access/Disclosure to Non-Public Registration Data (SSAD), including existing methods for identity verification. The RFI overview document can be viewed here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. Indications of interest are to be submitted to ssad-odp-rfi(a)icann.org<mailto:ssad-odp-rfi@icann.org> with the following information, upon which access will be provided to the RFI: · Name of the organization · Name of the contact · Email address of the contact The RFI will be open until 23:59 UTC on Monday, 19 July 2021. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> THURSDAY: Community Input Needed: SSAD ODP Questionnaire ICANN has launched the System for Standardized Access/Disclosure (SSAD) Operational Design Phase (ODP) Community Questionnaire to help determine how many potential users are expected to use the SSAD and the anticipated volume of requests if it is implemented. The questionnaire will play a critical role in assessing the feasibility and associated risks, costs, and resources required in the potential deployment of SSAD. ICANN org is looking for participation from community members who request nonpublic domain name registration data. The questionnaire [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> will be open until Thursday, 22 July (23:59 UTC). For questions, please contact jane.sexton(a)icann.org<mailto:jane.sexton@icann.org> or isabelle.colas(a)icann.org<mailto:isabelle.colas@icann.org>. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> NEW: ICANN72 to be Virtual Annual General Meeting, ICANN73 Planning Update ICANN72 will convene as a Virtual Annual General Meeting due to the continuing impacts of the COVID-19 pandemic. The health and safety of the ICANN community and staff is always a top priority, and as such, holding ICANN72 as an in-person or hybrid meeting would not be feasible by its scheduled date. The resolution and full rationale from the ICANN Board of Directors can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. NEXT WEEK: Ninth Africa DNS Forum to Take Place Virtually 27-28 July 2021 The ninth Africa DNS Forum will be held virtually Tuesday and Wednesday, 27-28 July 2021 with the theme of "Evolving the DNS Ecosystem in Africa." The Africa DNS Forum is organized by the Africa Top Level Domains Organization (AFTLD), the Africa Registrar Association (AfRegistrar), and ICANN. The 2021 edition will take place as a two-day virtual event open to stakeholders in the African domain name industry. Sessions will cover topics including the evolution of the DNS ecosystem in the region, national and regional DNS Forum initiatives, emerging technical issues, financing and insurance in the DNS business, and compliance in the domain name industry. Participants will be able to join sessions through Zoom, and view through YouTube and Facebook streaming. To register, click here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. REMINDER: Nomination Period Opens for Dr. Tarek Kamel Award for Capacity Building ICANN org opened a one-month nomination period for the Dr. Tarek Kamel Award for Capacity Building. Please submit your nominations via this nomination form [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> by 23:59 UTC on Monday, 2 August 2021. Any additional information in support of nominations or questions about the award process may be submitted via email to kamelaward(a)icann.org [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. REMINDER: Request for Early Input - GNSO Transfer Policy Review Policy Development Process Working Group The GNSO Transfer Policy Review PDP Working Group requests input from Supporting Organizations, Advisory Committees, Stakeholder Groups, and Constituencies on topics within the PDP charter. The request was sent on Wednesday, 30 June 2021 to ICANN community leaders. A copy of the letter is available here: https://community.icann.org/x/tIT8CQ. Responses to gnso-secs(a)icann.org are requested by Wednesday, 4 August 2021. REMINDER: APIGA 2021 Application Period Is Now Open The 2021 Asia Pacific Internet Governance Academy (APIGA) announced [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> its application period is now open for their virtual program, which will run from Friday, 1 October through Tuesday, 30 November 2021. Sessions will be held once or twice a week to accommodate the schedules of students and young professionals. Participants will be expected to complete preparatory work between sessions. The final day of the academy will be a hybrid event in South Korea. Applications are due by Sunday, 8 August 2021. Please note that a stable Internet connection is required for participation. The application procedure and more information on APIGA can be accessed here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. REMINDER: Nominations for NextGen@ICANN Mentor Positions Now Open The NextGen@ICANN Program seeks nominations for its Mentor Program through Tuesday, 31 August 2021. The community-nominated selection committee will be responsible for overseeing the mentor selection process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…>. Interested community groups should select their respective volunteers and notify deborah.escalera(a)icann.org<mailto:deborah.escalera@icann.org>. Public Comment TODAY: Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> Close Date: Monday, 19 July 2021 Proposed Renewal of the .AERO Registry Agreement [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> Close Date: Monday, 16 August 2021 NEW: Proposal for Greek Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> Close Date: Thursday, 26 Aug 2021 Volume 3, Issue 52 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001PtPppMfOKa7GmfXm…> | Next Issue: Thursday, 22 July 2021

1 0

FW: [soac-chairs] ICANN72 Board Decision 15July Announcement.pdf
by philippe.fouquart＠orange.com July 16, 2021

July 16, 2021

Dear Councillors, Please note the following note issued by the Board. ICANN72 will a be Virtual Annual General Meeting, and if possible by then, ICANN73 should be a hybrid meeting with an in-person component. Regards, Philippe -------- Message d'origine -------- De : David Olive via soac-chairs <soac-chairs(a)icann.org> Date : 16/07/2021 01:43 (GMT+01:00) À : soac-chairs(a)icann.org Cc : Rachel McFadyen <rachel.mcfadyen(a)icann.org>, Sally Newell Cohen <sally.newellcohen(a)icann.org> Objet : [soac-chairs] ICANN72 Board Decision 15July Announcement.pdf Dear SOAC Chair. Attached is an advance notice to the ICANN72 decision by the Board today. Best regards. David Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

Motion to confirm the formation and instructions to the Accuracy Scoping Team
by PAMELALITTLE July 15, 2021

July 15, 2021

Dear Councilors, Please find attached: 1. A motion to confirm the formation and instructions to the Accuracy Scoping Team to be considered at the GNSO Council meeting on 22 July 2021 at 19:00 UTC; and 2. The final version of the formation and instructions to the Accuracy Scoping Team document. Respectfully submitted, Pam Little

3 2

FW: [Ext] Thursday, 15 July 2021
by Julie Bisland July 15, 2021

July 15, 2021

FYI From: ICANN Community Leadership Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, July 15, 2021 at 10:02 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 15 July 2021 [https://r20.rs6.net/on.jsp?ca=3e902335-cbc9-4fbb-8d46-ad4677788c56&a=112202…] Thursday, 15 July 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. 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=0010m9fIewz-CKW0nhe…> Table of Contents Webinars · TUESDAY: "The UN, the EU, and Your Business, What Comes Next?" Webinar · NEXT WEEK: DNS Security Threat Mitigation Program Webinar · NEW: Register for FY23 IANA Functions and PTI Planning Webinar · REMINDER: ITI Update: Register Now for ICANN Public Comment Submission Training Webinars Information Sharing · CLOSES MONDAY: Request for Information on Identity Verification Methods for SSAD Now Open · NEXT WEEK: Community Input Needed: SSAD ODP Questionnaire · NEW: An Update from the NomComRIWG Chairs · NEW: APIGA 2021 Application Period Is Now Open · REMINDER: Ninth Africa DNS Forum to Take Place Virtually 27-28 July 2021 · REMINDER: Nomination Period Opens for Dr. Tarek Kamel Award for Capacity Building · REMINDER: Request for Early Input - GNSO Transfer Policy Review PDP Working Group · REMINDER: Nominations for NextGen@ICANN Mentor Positions Now Open Public Comment · NEXT WEEK: Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A · Proposed Renewal of the .AERO Registry Agreement [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> Webinars TUESDAY: "The UN, the EU, and Your Business, What Comes Next?" Webinar On Tuesday, 20 July 2021 at 16:00 UTC, the ICANN org North America Engagement team will host a webinar related to deliberations on how the infrastructure layer of the Internet is governed that are happening at the United Nations (UN) and within the European Union (EU). These discussions and proposed actions could affect the business sector. Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. NEXT WEEK: DNS Security Threat Mitigation Program Webinar ICANN will host a webinar on Thursday, 22 July 2021 at 16:00 UTC to provide the ICANN community with updates on its DNS Security Threat Mitigation Program, community-facing initiatives, Domain Abuse Activity Reporting System (DAAR), and Domain Name Security Threat Information Collection and Reporting (DNSTICR) project. Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. NEW: Register for FY23 IANA Functions and PTI Planning Webinar ICANN invites the community to join one of two public webinars to discuss planning for the fiscal year 2023 (FY23) Operating Plan and Budget (OP&B) for delivering the Internet Assigned Numbers Authority (IANA) functions. The webinar will explain the planning process, the proposed operational priorities for FY23, timelines, and key assumptions. ICANN welcomes the community's questions and comments. Webinar 1 | Tuesday, 27 July 2021 | 00:00 UTC | Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> Webinar 2 | Tuesday, 27 July 2021 | 16:00 UTC | Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> The annual OP&B for the IANA functions has two components: a budget and operating plan for Public Technical Identifiers (PTI), the ICANN affiliate that performs the IANA functions, which outlines the planned activities and resources to deliver the core IANA functions. The second component includes the PTI budget plus additional programs and costs that the ICANN organization incurs overseeing and enabling the IANA functions. In addition to the webinars, the community has further opportunity to participate in this planning process. The draft plans will be put out for Public Comment in September before being considered for formal adoption in late 2021. REMINDER: ITI Update: Register Now for ICANN Public Comment Submission Training Webinars ICANN org will hold a series of training webinars outlining the new Public Comment submission process. During these sessions, our teams will provide the ICANN community with step-by-step instructions on how to draft and publish a Public Comment submission and outline how to manage your current and past submissions. You are encouraged to ask questions throughout these webinars to ensure you are well-prepared to use this improved feature. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> Webinar 1 | Tuesday, 3 August 2021 | 14:00 UTC | Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> Webinar 2 | Wednesday, 4 August 2021 | 21:00 UTC | Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> Information Sharing CLOSES MONDAY: Request for Information on Identity Verification Methods for SSAD Now Open ICANN org announced [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> that it has now opened the Request for Information (RFI) to better understand what may be commercially available in the marketplace to deliver some or all of the System for Standardized Access/Disclosure to Non-Public Registration Data (SSAD), including existing methods for identity verification. The RFI overview document can be viewed here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. Indications of interest are to be submitted to ssad-odp-rfi(a)icann.org<mailto:ssad-odp-rfi@icann.org> with the following information, upon which access will be provided to the RFI: · Name of the organization · Name of the contact · Email address of the contact The RFI will be open until 23:59 UTC on Monday, 19 July 2021. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> NEW: An Update from the NomComRIWG Chairs The Nominating Committee Review Implementation Working Group (NomComRIWG [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>) is making progress on review recommendations from the second organizational review of the NomCom. Several of the review recommendations have implications for the broader community and for ICANN governance. In particular, two areas of implementation may be of interest to the ICANN community: · The independent examiner's recommendation on rebalancing the NomCom · The design and installation of a new NomCom Standing Committee Rebalancing of the NomCom (Recommendation 10) The NomComRIWG presented its rebalancing proposal in a webinar at ICANN70 and recently met with the Organizational Effectiveness Committee (OEC) to discuss implementation of this recommendation, among others. Based upon its discussion with the OEC, the NomComRIWG developed a summary of community consultation and feedback on implementation for rebalancing the NomCom. Once the summary is finalized, it will be shared with the OEC and posted on the NomCom2 Review wiki workspace. The NomComRIWG's current Implementation Plan [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> for this recommendation proposes a change to the ICANN Bylaws, whereby the GNSO is allocated the same number of NomCom seats as it holds today, but is able to internally determine how those seats are allocated without requiring further change to the ICANN Bylaws. The NomComRIWG's intent with this proposal is to allow the GNSO to continue to evolve the allocation of NomCom delegates in response to the changing composition of GNSO constituencies and stakeholder groups. Nominating Committee Standing Committee Charter (Recommendation 24) The intended purpose of the Standing Committee is to support continuous improvement and increase the effectiveness and efficiency of the Nominating Committee while enhancing the NomCom's transparency and accountability to the overall ICANN community. The Standing Committee will not oversee or participate in the daily work of the NomCom. However, recognizing that the membership of the NomCom changes annually, the Standing Committee is intended to provide continuity across annual NomCom cycles and build the institutional memory of the NomCom. The NomComRIWG is currently working on the next iteration of the Standing Committee charter to further refine the committee's purpose, scope, composition, and terms. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. NEW: APIGA 2021 Application Period Is Now Open The 2021 Asia Pacific Internet Governance Academy (APIGA) announced [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> its application period is now open for their virtual program, which will run from Friday, 1 October through Tuesday, 30 November 2021. Sessions will be held once or twice a week to accommodate the schedules of students and young professionals. Participants will be expected to complete preparatory work between sessions. The final day of the academy will be a hybrid event in South Korea. Applications are due by Sunday, 8 August 2021. Please note that a stable Internet connection is required for participation. The application procedure and more information on APIGA can be accessed here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. NEXT WEEK: Community Input Needed: SSAD ODP Questionnaire ICANN has launched the System for Standardized Access/Disclosure (SSAD) Operational Design Phase (ODP) Community Questionnaire to help determine how many potential users are expected to use the SSAD and the anticipated volume of requests if it is implemented. The questionnaire will play a critical role in assessing the feasibility and associated risks, costs, and resources required in the potential deployment of SSAD. ICANN org is looking for participation from community members who request nonpublic domain name registration data. The questionnaire [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> will be open until Thursday, 22 July (23:59 UTC). For questions, please contact jane.sexton(a)icann.org<mailto:jane.sexton@icann.org> or isabelle.colas(a)icann.org<mailto:isabelle.colas@icann.org>. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> REMINDER: Ninth Africa DNS Forum to Take Place Virtually 27-28 July 2021 The ninth Africa DNS Forum will be held virtually Tuesday and Wednesday, 27-28 July 2021 with the theme of "Evolving the DNS Ecosystem in Africa." The Africa DNS Forum is organized by the Africa Top Level Domains Organization (AFTLD), the Africa Registrar Association (AfRegistrar), and ICANN. The 2021 edition will take place as a two-day virtual event open to stakeholders in the African domain name industry. Sessions will cover topics including the evolution of the DNS ecosystem in the region, national and regional DNS Forum initiatives, emerging technical issues, financing and insurance in the DNS business, and compliance in the domain name industry. Participants will be able to join sessions through Zoom, and view through YouTube and Facebook streaming. To register, click here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. REMINDER: Nomination Period Opens for Dr. Tarek Kamel Award for Capacity Building Today, ICANN org opened a one-month nomination period for the Dr. Tarek Kamel Award for Capacity Building. Please submit your nominations via this nomination form [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> by 23:59 UTC on Monday, 2 August 2021. Any additional information in support of nominations or questions about the award process may be submitted via email to kamelaward(a)icann.org [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. REMINDER: Request for Early Input - GNSO Transfer Policy Review Policy Development Process Working Group The GNSO Transfer Policy Review PDP Working Group requests input from Supporting Organizations, Advisory Committees, Stakeholder Groups, and Constituencies on topics within the PDP charter. The request was sent on Wednesday, 30 June 2021 to ICANN community leaders. A copy of the letter is available here: https://community.icann.org/x/tIT8CQ. Responses to gnso-secs(a)icann.org are requested by Wednesday, 4 August 2021. REMINDER: Nominations for NextGen@ICANN Mentor Positions Now Open The NextGen@ICANN Program seeks nominations for its Mentor Program through Tuesday, 31 August 2021. The community-nominated selection committee will be responsible for overseeing the mentor selection process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…>. Interested community groups should select their respective volunteers and notify deborah.escalera(a)icann.org<mailto:deborah.escalera@icann.org>. Public Comment CLOSES MONDAY: Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> Close Date: Monday, 19 July 2021 Proposed Renewal of the .AERO Registry Agreement [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> Close Date: Monday, 16 August 2021 Volume 3, Issue 51 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0010m9fIewz-CKW0nhe…> | Next Issue: Monday, 19 July 2021

1 0

Interest for the Effectiveness Review of the Customer Standing Committee
by philippe.fouquart＠orange.com July 15, 2021

July 15, 2021

Dear councilors, By the end of August, we will need to appoint our GNSO members for the effectiveness review of the Customer Standing Committee. According to the CSC charter, the effectiveness of the CSC is reviewed two years after the first meeting [2 years, that was back in 2018] and then every three years thereafter (this is now). The method of review will be determined by the ccNSO and GNSO. Our initial thought within the leadership was to replicate the approach we adopted in 2018 and which worked extremely well, both in terms of the small size of the team (2 GNSO + 2 CCs), and the composition with the ccNSO liaison being one member and a RySG member would be another. Last time we did that, however, it so happened that our liaison to the ccNSO Council wasn't from the RySG (I happened to be that liaison at the time). Having discussed this within the leadership, we appreciate this is of interest mostly to the registries, but we don't want to let it go unnoticed if there is an interest from other groups to put forward a member for this CSC effectiveness review team. If you or your group have an interest in taking part, would you please say so by the end of next week? (July 23rd) Thank you. Regards, Philippe https://www.icann.org/public-comments/csc-effectiveness-initial-2019-01-16-… https://community.icann.org/display/ER/Effectiveness+Review+Home _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

FW: EPDP ODP - liaison's communication
by philippe.fouquart＠orange.com July 14, 2021

July 14, 2021

Dear Councilors, It seems that Janis’s message and report as liaison to the SSAD ODP did not make it to the list due to posting restrictions. This will be the basis of the Update from the GNSO Council Liaison, on the agenda for our council call next week. Thanks Janis. Regards, Philippe From: Janis Karklins [mailto:karklinsj@gmail.com] Sent: Saturday, July 10, 2021 8:10 AM To: council(a)gnso.icann.org; FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Subject: EPDP ODP - liaison's communication Dear Councilors, As provided in the Operational Design Phase Concept Paper, the GNSO Council was invited to appoint a liaison “to streamline communications between ICANN Org’s ODP team and the Council should any questions on the substance or intent of recommendations arise.” To that end, below is a short summary of a recent monthly meeting I had with the org’s SSAD ODP team. In the course of its review of the EPDP Phase 2 Final Report, the SSAD ODP Team identified seven assumptions that they wished to discuss with me. The assumptions and my responses to or comments on the assumptions are annexed to this message for your information. I understand that the SSAD ODP Team plans, pending no objection from the GNSO Council, to proceed with its work on the basis of these assumptions and my responses to or comments on the assumptions and they will be used by the ODP Team as it works on an assessment to inform the Board’s review of the EPDP Phase 2 policy recommendations. It is understood that the ODP is not meant to replace the Implementation Review Team and/or the implementation phase. In addition to the attached assumptions, we also discussed the upcoming webinar<https://www.icann.org/en/announcements/details/register-for-the-ssad-odp-pr…> on the status of the ODP, which will take place on Tuesday, 13 July at 1600 UTC. We plan to meet again in early August. I am at your disposal for any clarifications before or during the next Council meeting. Best regards, JK Org Assumptions Liaison Response Recommendation 1.4.3 states that the Accreditation Authority “MUST validate Identity Credentials and Signed Assertions, in addition to the information contained in the request, facilitate the decision to accept or reject the Authorization of an SSAD request.” ICANN org interprets it to mean that the “request” mentioned in this recommendation refers to the accreditation request, and not the nonpublic registration data request. Please confirm that our understanding is correct. Yes. Rec 1 describes accreditation process Recommendation 13.1.4 states that the Central Gateway Manager “MUST respond only to requests for a specific domain name…” whereas the Recommendation 13.3.2 states that the CGM “MUST support the ability of a Requestor to submit multiple domain names in a single request.” Implementation Guidance 13.5 also states “it must be possible for Requestors to submit multiple requests at the same time.” Recommendation 13.1.4 could be interpreted to be in conflict with Recommendation 13.3.2 and Implementation Guidance 13.5 in terms of how many disclosure requests can be included in a single request. ICANN org’s interpretation is that a single request can contain disclosure requests for multiple domain names as long as all the domain names are individually specified in a fully qualified format. In other words, the Central Gateway Manager should not allow any sort of “catch all” requests, such as a request concerning all domain names that have “apple” in the name, or that are owned by a particular registrant. Please confirm that our understanding is correct. Yes. There isn’t contradiction. Multiple name request option should facilitate SSAD work, but multiple should be “reasonable”. It should be determined at the initial stage of implementation, and possibly corrected as a result of experience gained by operating SSAD. Recommendation 10.14 states that “Response Targets and Compliance Targets MUST be reviewed, at a minimum, after every six months in the first year, thereafter annually (depending on the outcome of the first review).” ICANAN org’s interpretation of this recommendation is that such a review is expected to be done across all contracted parties and not review individual contracted parties. This review is meant to be conducted by the GNSO Standing Committee. Yes. In light of 18.2.2 Recommendations 13.3.6 states that the “SSAD MUST be able to save the history of the different disclosure requests…” ICANN org’s interpretation is that this recommendation applies to not only the Central Gateway Manager, but also to other parties, such as the Accreditation Authorities and the Contracted Parties. Please confirm that our understanding is correct. Rec 13 specifically describes Query policy where both CGM and CP are involved. Rec 15 requires logging (and saving) info on Accreditation. Recommendation 14.2 states that “Requestors of the SSAD data should primarily bear the costs of maintaining this system,” whereas the Recommendation 14.4 states that the “SSAD SHOULD NOT be considered a profit-generating platform for ICANN or the contracted parties. Funding for the SSAD should be sufficient to cover costs…” ICANN org’s interpretation of these recommendations is that the SSAD user fees should cover the operating cost of only the Accreditation Authorities, Identity Providers, and Central Gateway Manager, and does not cover any costs that contracted parties may incur. Please confirm that our understanding is correct. One should separate development and running costs of SSAD. Running costs consist of accreditation and query. These also can be separated. Query costs should be predominantly covered by requestors and not be source of profit neither by ICANN Org or CPs. Hence, fees should cover cost of both involved, but be reasonable. ICANN and CPs may decide to subsidize SSAD running activity as it is part of smooth functioning of DNS. May be mentioned in webinar Recommendation 2 lays out the requirements for governmental accreditation authorities, but it does not indicate whether government entities requiring access to non-public gTLD registration data may only be accredited via these governmental accreditation authorities. Footnote 13 seems to limit the Intergovernmental Organizations (IGOs) to only use the hosting country’s Accreditation Authority. ICANN org’s interpretation is that governmental entities are required to use an Accreditation Authority from their country/territory. This means, if there are no such Accreditation Authorities established within their country/territory, those entities cannot be accredited via the Accreditation Authority that is to be established for non-governmental entities. Please confirm that our understanding is correct. Yes, it is right. Governments either can organize accreditation within their jurisdiction, or pool resources and entrust an IGO to organize it for number of countries. Nevertheless, there should be full technical compatibility of respective accreditation systems. Recommendations 7.1.1 states that “Requestors MAY also submit data verification requests on the basis of Registered Name Holder (RNH) consent that has been obtained by the Requestor (and is at the sole responsibility of that Requestor), for example to validate the RNH’s claim of ownership of a domain name registration, or contract with the Requestor.” ICANN org’s interpretation is that the given the parenthetical of “and is at the sole responsibility of that Requestor.” Please confirm that our understanding is correct. Not sure what is meant by “request on the basis of RNH consent is automatically approved”. Requestor needs to provide Identity Credential and Signed Assertions. If accepted, requestor can submit query. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

FOR DISCUSSION: Document for Agenda Item #6 RPM Phase 2, Review of UDRP Next Steps
by Julie Hedlund July 13, 2021

July 13, 2021

Dear GNSO Councilors, On behalf of Council Leadership, pursuant to the Proposed GNSO Council meeting agenda below, please see the attached document for discussion relating to the following agenda item: Item 6: COUNCIL DISCUSSION - Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP Phase 2, Review of UDRP Next Steps Council Leadership requests that Councilors review the attached document for discussion at the next Council meeting. Kind regards, Julie Julie Hedlund, Policy Director From: council <council-bounces(a)gnso.icann.org> on behalf of Michelle DeSmyter via council <council(a)gnso.icann.org> Reply-To: Michelle DeSmyter <michelle.desmyter(a)icann.org> Date: Monday, July 12, 2021 at 8:39 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Proposed Agenda GNSO Council Meeting - 22 July 2021 at 19:00 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 22 July 2021 at 19:00 UTC. Draft GNSO Council Agenda 22 July 2021 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/cYL8CQ 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 24 October 2019 For convenience: * * * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix * 1 at the end of this agenda. * * * * An excerpt from the Council Operating Procedures defining the absentee voting procedures * is provided in Appendix 2 at the end of this agenda. * GNSO Council meeting held 19:00 UTC Coordinated Universal Time: 19:00 UTC: https://tinyurl.com/ybavc84m [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ybavc84m__;!!PtGJab4!u3v1cUb…> 12:00 Los Angeles; 15:00 Washington; 20:00 London; 21:00 Paris; 22:00 Moscow; (Friday) 05:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/99805526507?pwd=MlRKaTAzdDZIQ3Q1azJsc2JSWXRSZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/99805526507?pwd=MlRKaTAz…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (10 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council meeting on 20 May 2021 were posted on 03 June 2021. Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council meeting on 16 June 2021 were posted on 03 July 2021. Item 2: Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [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) * * * Approval of the Chair for the EPDP on Internationalized Domain Names - Edmon Chung * (SOI<https://community.icann.org/display/gnsosoi/Edmon+Chung+SOI>) * * * * Acknowledgment of the GNSO Council liaison to EPDP on Internationalized Domain Names * - Farrell Folly * * * * Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+22+July+2021> * to adopt the GNSO Review of the GAC ICANN71 Virtual Policy Forum Communiqué for submission to the ICANN Board * Item 4: COUNCIL VOTE - Accuracy Scoping Team (15 minutes) During its October 2020 meeting, the GNSO Council confirmed its intent to launch a scoping team on the topic of accuracy based on a proposal from the previous Council leadership team (see here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>for the proposal). On 4 November 2020, the GNSO Council wrote<https://www.icann.org/en/system/files/correspondence/fouquart-to-swinehart-…> to ICANN org, requesting the preparation of a briefing document outlining both the existing accuracy requirements and programs as well as the impact that GDPR has had on implementing and enforcing the identified requirements and programs. This briefing is intended to inform an accuracy scoping team that the GNSO Council envisioned initiating, which would be tasked with furthering the community’s understanding of the issue and assist in scoping and defining the issue (see here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>). On 10 December 2020, ICANN org responded<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…> to confirm its understanding of the request and to commit to delivering that briefing by 26 February 2021. ICANN org timely delivered the briefing<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…>. In addition to the briefing providing an overview of accuracy requirements and programs and the impact of GDPR on these, ICANN org also included a suggestion that a study to measure accuracy of registration data might be beneficial. In parallel to the request for the briefing, ICANN SO/AC/SG/Cs were requested to start thinking about whether their groups would be interested to participate in a scoping team once created. At or around that time, the BC, ISPCP, RySG, IPC and GAC expressed an interest and identified potential volunteers with relevant knowledge and expertise. The Council discussed this briefing and potential next steps during its Extraordinary Meeting on 08 April 2021. Following the meeting, Council leadership, with the support of the GNSO Support Staff, worked together to develop a set of proposed next steps<https://mm.icann.org/pipermail/council/2021-April/024662.html> for dealing with the topic of accuracy, which was shared on 23 April 2021. Feedback was sought from Councilors by 07 May 2021 and the topic was discussed again during the Council’s May meeting. The Council agreed to convene a small team to refine the proposed next steps, particularly around clarifying the remit of the eventual scoping team. That small team met regularly to clearly document the remit of the scoping team and provided a brief update during the June Council meeting. The small team has reached agreement on the formation and instructions to the scoping team, which it shared<https://mm.icann.org/pipermail/council/2021-July/024851.html> with the Council on 9 July 2021. Here, the Council will vote to confirm the formation and instructions to the Registration Data Accuracy Scoping Team as developed by the Council small team. 4.1 – Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+22+July+2021> (Pam Little, Council vice-chair) 4.2 – Council discussion 4.3 – Council vote (Voting Threshold: simple majority vote of each House) Item 5: COUNCIL DISCUSSION - Operational Design Phase (ODP) on the Standardized System for Access/Disclosure - Update from the GNSO Council Liaison (15 minutes) On 25 March 2021, the ICANN Board launched the Operational Design Phase (ODP) for the System for the Standardized Access/Disclosure to Nonpublic Registration Data (SSAD) policy recommendations as set out in the SSAD ODP Scoping Document<https://www.icann.org/en/system/files/files/ssad-non-public-registration-da…>. As part of the general ODP process, it is recommended that a GNSO Council liaison be appointed, in order to serve as primary contact between the ODP team and Council to facilitate and streamline communications on identified issues that pertain to the intent or substance of the policy recommendations. On 12 April 2021, the Council received a letter<https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-…> from the Board, recommending the appointment of a Council liaison to the ODP. On 20 May 2021, the GNSO Council appointed Janis Karklins, the Chair of the Temporary Specification for gTLD Registration Data Phase 2 Expedited Policy Development Process. Here, the Council will receive an update from the Council liaison to the ODP. 5.1 - Presentation (Janis Karklins) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION - Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP Phase 2, Review of UDRP Next Steps (15 minutes) On 21 January 2021, the GNSO Council approved the recommendations from the Phase 1 Final Report of the GNSO Policy Development Process (PDP) on the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs, covering RPMs applicable to gTLDs launched under the 2012 New gTLD Program. The Council has discussed the need to review the RPMs charter in advance of launching Phase 2 of the PDP, which is focused on the UDRP. Council leadership has considered the best path forward to initiating this work and has shared their thoughts for advancing this effort on [date], which considers a Policy Status Report (PSR) as a possible next step. The leadership team recognizes that a significant amount of time has passed since the 2011 UDRP Issue Report such that it will be helpful to know if new issues or information have emerged that could be relevant to a comprehensive policy review. Leadership also believes that a PSR will support a data-driven policy development effort and will result in a more tightly scoped Charter, that is consistent with the principles of PDP 3.0. Here, the Council will discuss possible next steps, including a PSR for advancing RPMs Phase 2. 6.1 – Introduction of topic (Council leadership) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - IGO Work Track Questions for Council (20 minutes) On 18 April 2019, the Council voted<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+April+20…> to approve recommendations 1-4 of the Final Report from the IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG. The Council also resolved to not approve Recommendation 5 and, ”directs the Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP to consider, as part of its Phase 2 work, whether an appropriate policy solution can be developed that is generally consistent with Recommendations 1, 2, 3 & 4 of the PDP Final Report and: * * * accounts for the possibility that an IGO may enjoy jurisdictional immunity in certain * circumstances; * * * * does not affect the right and ability of registrants to file judicial proceedings in * a court of competent jurisdiction; * * * * preserves registrants’ rights to judicial review of an initial UDRP or URS decision; * and * * * * recognizes that the existence and scope of IGO jurisdictional immunity in any particular * situation is a legal issue to be determined by a court of competent jurisdiction.” * In respect of that resolution, the GNSO Council prepared an Addendum [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> to the RPMs PDP charter to support work related to Recommendation 5 and approved [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> it during its January 2020 Council meeting. During its September 2020 Council meeting, the Council agreed to initiate both the Expressions of Interest process to identify a single, qualified Work Track Chair and issue a call for Members and Observers to join the IGO Work Track. Led by Chris Disspain as the Chair, the Work Track has been meeting since late February of 2021. The Work Track has sought to make meaningful progress within the bounds of the Addendum, with members recognizing that this foundational discussion will influence how the group will work and thus, what its work plan should look like. During its April meeting, the Council received a brief update and acknowledged the work track’s Work Plan<https://community.icann.org/download/attachments/164626455/RPM-IGO-CRWT_Pro…> (April package here<https://community.icann.org/download/attachments/164626455/RPM-IGO-CRWT_Pro…>). In chartering this work, the GNSO Council expected that the work should be completed in an efficient manner and that frequent updates to the Council would be helpful to ensure an effective outcome. The Council has already received updates during the April and May meetings. The Work Track has made steady progress in evaluating recommendation 5 and determining an appropriate policy path forward. According to the work plan, the Work Track is expected to deliver its Initial Report for public comment in early August, but due to the need to migrate the current Public Comment platform on the ICANN org website to a substantially new feature that will be compliant with the Information Transparency Initiative and its requirements, ICANN org needs to impose a moratorium on launching Public Comment proceedings between late July and end August. The Work Track has submitted a Policy Change Request in light of this external factor. With the Work Track nearing a stage where it will be able to publish its Initial Report, notwithstanding the moratorium, it is timely to bring two questions to the Council for their consideration. The first question relates to the fact that the IGO Work Track was originally convened under the auspices of the then-ongoing Review of All Rights Protection Mechanisms (RPM) Policy Development Process (PDP) Working Group, which has since delivered its Final Report to the Council and subsequently approved; planning for Phase 2 of the RPM work is ongoing, which leaves the Work Track without a parent Working Group. The second question relates to the requirements imposed on the Work Track via the Addendum. The Work Track has kept Recommendation #5 (regarding IGO jurisdictional immunity) at the forefront in its work. However, it has concluded that a feasible and appropriate policy solution cannot be crafted simply by looking at that recommendation in isolation. Accordingly, the Work Track is seeking feedback to determine whether the approach and solution are in accordance with the limitations in the addendum. The Work Track leadership and staff have drafted a briefing document to support this agenda item. Here, the Council will discuss the two questions and seek to reach agreement on answers/solutions. 7.1 – Update (John McElwaine, GNSO Council Liaison) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL UPDATE - Update on the Customer Standing Committee and Next Steps for the Council (10 minutes) The GNSO Council will soon have two responsibilities regarding the Customer Standing Committee, per the ICANN Bylaws. The first requirement is that, in accordance with Section 17.2 (d) of the ICANN Bylaw and per the CSC Charter, the full membership of the CSC must be approved by the GNSO Council. This is expected to occur no later than September of 2021. The second responsibility relates to the Customer Standing Committee (CSC) Effectiveness Review, which would represent the second such review. The ICANN Bylaws, Section 17.3 (b) states, "The effectiveness of the CSC shall be reviewed two years after the first meeting of the CSC; and then every three years thereafter. The method of review will be determined by the ccNSO and GNSO and the findings of the review will be published on the Website." The Customer Standing Committee (CSC) was established and conducted its first meeting on 6 October 2016, so the first review needed to take place in 2018. As required, the GNSO and ccNSO established a process to conduct the review, which per the Council’s resolution “concluded that the most practical and efficient path forward is for the ccNSO and GNSO to each appoint two members to conduct the CSC Effectiveness Review that will consider the effectiveness of the CSC in performing its responsibilities as outlined in the CSC Charter and that the findings of the Review, as adopted by both the GNSO and ccNSO Councils, will become an input to the IANA Naming Function Review.” The Council approved [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions*20…> this process in September of 2018. After completing an Initial Report<https://www.icann.org/en/system/files/files/csc-effectiveness-initial-16jan…> and publishing it for public comment, the Final Report<https://community.icann.org/x/VQpIBg> was delivered 05 March 2019; the Council adopted [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions*20…> the Final Report on 13 March 2019. With an October 2016 first meeting for the CSC, the time for the second review of the CSC is October 2021. The GNSO and ccNSO will need to establish the terms of reference for the second review, which may be able to highly leverage the ToR<https://community.icann.org/display/CRT/Terms+of+Reference> from the first review. At a minimum, this second review will need to include a determination whether the recommendations from the first effectiveness review were successfully implemented. Here, the Council will discuss the expectations of the Council as it relates to the two CSC items. 8.1 – Introduction of topic (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: ANY OTHER BUSINESS (5 minutes) 9.1 - Transfer Policy Review PDP - Review of Work Plan<https://community.icann.org/x/MQDQCQ> _______________________________ 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 19:00 UTC Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 12:00 San José, Costa Rica (CST) UTC-6 13:00 New York/Washington DC, USA (EDT) UTC-4 15:00 Buenos Aires, Argentina (ART) UTC-3 16:00 Rio de Janeiro, Brazil (BRST) UTC-3 16:00 London, United Kingdom (GMT) UTC+1 20:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 20:00 Paris, France (CEST) UTC+2 21:00 Moscow, Russia (MST) UTC+3 22:00 Singapore (SGT) (+1day) UTC+8 03:00 Melbourne, Australia (AEDT)(+1day) UTC+11 05:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 31 October 2021, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 7 November 2021 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.com/v3/__http:/www.timeanddate.com/__;!!PtGJab4!u3v1cUbz…> and https://tinyurl.com/ybavc84m [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ybavc84m__;!!PtGJab4!u3v1cUb…>

1 0

GNSO Council Program Suite for 22 July 2021 Meeting
by policy＠bacinblack.com July 13, 2021

July 13, 2021

Dear all, Please find attached links to the latest version of the GNSO Council's Program Suite for the meeting on 22 July 2021. Agenda: * https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+GNSO+ Council+Agenda+22+July+2021 Links to the Program Suite: * Program/Project Management Framework (PPMF): https://community.icann.org/x/0YvzC * Program Management Tool (PMT): https://community.icann.org/x/04vzC * Action/Decision Radar (ADR): https://community.icann.org/x/14vzC * Project List (PL): https://community.icann.org/x/1YvzC * Action Items (AIs): https://community.icann.org/x/RgZlAg * Council Small Teams (CSTs): https://community.icann.org/x/kwANCQ Key Program Suite Structural Changes for this Period: * PMT: The key understanding is that this tool is only as good as the information that is available. For projects and phases that are active today, there's a higher degree of certainty to duration and completion dates, especially for projects that the GNSO Policy team owns. Future work are merely forecasts based on educated guesses, or just plain guesses. As new and more accurate information becomes available, this tool gets updated accordingly. Key updates: * New structure to projects outline as more child projects are connected to the PMT tool. * Extended GNSO3 start based on the Board's resolution to defer and until more information becomes available on ATRT3. * Added a placeholder for the Holistic Review pilot. * Added CSC Effectiveness Review. * Added the COICI - the new standing committee on continuous improvement. * Transfer Policy Review timeline updated based on updated project plan. * ADR: (page 2) and per the Council's resolution to launch the pilot of the continuous improvement framework (COICI), items likely to be within its scope are now decoupled from the ADR range markers until more clarity is obtained on the scope and duration of that work. * PL: added the COICI at the bottom of the projects list. For the time being, the WS2 & GEO reports have been retained until the pilot has concluded or new information forces a change. Key Project Changes for this Period: * Approval to launch Registration Data Accuracy Scoping Team * Approval of ICANN71 GNSO Council response to GAC Communique * IGO Work Track - Project Change Request * RPM - Phase 2: Begin discussion on UDRP Review Next steps * Confirmation of Transfer Policy Review PDP Work Plan * Close of Public Comment on EPDP-P2A * EPDP-IDN 1st meeting expected Key Project Activities for August 2021: * CSC - establish terms of reference for new CSC Effectiveness Review * RPM - Phase 2: Continue discussions on UDRP Review Next steps Thank you. B Berry Cobb GNSO Policy Consultant Principal | <http://bacinblack.com/> BAC in Black Consulting Mob: +1 (720) 839-5735 <https://twitter.com/berrycobb> <https://www.linkedin.com/in/berrycobb/>

1 0

Proposed Agenda GNSO Council Meeting - 22 July 2021 at 19:00 UTC
by Michelle DeSmyter July 13, 2021

July 13, 2021

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 22 July 2021 at 19:00 UTC. Draft GNSO Council Agenda 22 July 2021 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/cYL8CQ This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting held 19:00 UTC Coordinated Universal Time: 19:00 UTC: https://tinyurl.com/ybavc84m 12:00 Los Angeles; 15:00 Washington; 20:00 London; 21:00 Paris; 22:00 Moscow; (Friday) 05:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/99805526507?pwd=MlRKaTAzdDZIQ3Q1azJsc2JSWXRSZz09 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (10 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/sites/default/files/policy/2021/minutes/minutes-gnso…> of the GNSO Council meeting on 20 May 2021 were posted on 03 June 2021. Minutes<https://gnso.icann.org/sites/default/files/policy/2021/minutes/minutes-gnso…> of the GNSO Council meeting on 16 June 2021 were posted on 03 July 2021. Item 2: Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Approval of the Chair for the EPDP on Internationalized Domain Names - Edmon Chung (SOI<https://community.icann.org/display/gnsosoi/Edmon+Chung+SOI>) * Acknowledgment of the GNSO Council liaison to EPDP on Internationalized Domain Names - Farrell Folly * Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+22+July+2021> to adopt the GNSO Review of the GAC ICANN71 Virtual Policy Forum Communiqué for submission to the ICANN Board Item 4: COUNCIL VOTE - Accuracy Scoping Team (15 minutes) During its October 2020 meeting, the GNSO Council confirmed its intent to launch a scoping team on the topic of accuracy based on a proposal from the previous Council leadership team (see here <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…> for the proposal). On 4 November 2020, the GNSO Council wrote<https://www.icann.org/en/system/files/correspondence/fouquart-to-swinehart-…> to ICANN org, requesting the preparation of a briefing document outlining both the existing accuracy requirements and programs as well as the impact that GDPR has had on implementing and enforcing the identified requirements and programs. This briefing is intended to inform an accuracy scoping team that the GNSO Council envisioned initiating, which would be tasked with furthering the community’s understanding of the issue and assist in scoping and defining the issue (see here<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…>). On 10 December 2020, ICANN org responded<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…> to confirm its understanding of the request and to commit to delivering that briefing by 26 February 2021. ICANN org timely delivered the briefing<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…>. In addition to the briefing providing an overview of accuracy requirements and programs and the impact of GDPR on these, ICANN org also included a suggestion that a study to measure accuracy of registration data might be beneficial. In parallel to the request for the briefing, ICANN SO/AC/SG/Cs were requested to start thinking about whether their groups would be interested to participate in a scoping team once created. At or around that time, the BC, ISPCP, RySG, IPC and GAC expressed an interest and identified potential volunteers with relevant knowledge and expertise. The Council discussed this briefing and potential next steps during its Extraordinary Meeting on 08 April 2021. Following the meeting, Council leadership, with the support of the GNSO Support Staff, worked together to develop a set of proposed next steps<https://mm.icann.org/pipermail/council/2021-April/024662.html> for dealing with the topic of accuracy, which was shared on 23 April 2021. Feedback was sought from Councilors by 07 May 2021 and the topic was discussed again during the Council’s May meeting. The Council agreed to convene a small team to refine the proposed next steps, particularly around clarifying the remit of the eventual scoping team. That small team met regularly to clearly document the remit of the scoping team and provided a brief update during the June Council meeting. The small team has reached agreement on the formation and instructions to the scoping team, which it shared<https://mm.icann.org/pipermail/council/2021-July/024851.html> with the Council on 9 July 2021. Here, the Council will vote to confirm the formation and instructions to the Registration Data Accuracy Scoping Team as developed by the Council small team. 4.1 – Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+22+July+2021> (Pam Little, Council vice-chair) 4.2 – Council discussion 4.3 – Council vote (Voting Threshold: simple majority vote of each House) Item 5: COUNCIL DISCUSSION - Operational Design Phase (ODP) on the Standardized System for Access/Disclosure - Update from the GNSO Council Liaison (15 minutes) On 25 March 2021, the ICANN Board launched the Operational Design Phase (ODP) for the System for the Standardized Access/Disclosure to Nonpublic Registration Data (SSAD) policy recommendations as set out in the SSAD ODP Scoping Document<https://www.icann.org/en/system/files/files/ssad-non-public-registration-da…>. As part of the general ODP process, it is recommended that a GNSO Council liaison be appointed, in order to serve as primary contact between the ODP team and Council to facilitate and streamline communications on identified issues that pertain to the intent or substance of the policy recommendations. On 12 April 2021, the Council received a letter<https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-…> from the Board, recommending the appointment of a Council liaison to the ODP. On 20 May 2021, the GNSO Council appointed Janis Karklins, the Chair of the Temporary Specification for gTLD Registration Data Phase 2 Expedited Policy Development Process. Here, the Council will receive an update from the Council liaison to the ODP. 5.1 - Presentation (Janis Karklins) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION - Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP Phase 2, Review of UDRP Next Steps (15 minutes) On 21 January 2021, the GNSO Council approved the recommendations from the Phase 1 Final Report of the GNSO Policy Development Process (PDP) on the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs, covering RPMs applicable to gTLDs launched under the 2012 New gTLD Program. The Council has discussed the need to review the RPMs charter in advance of launching Phase 2 of the PDP, which is focused on the UDRP. Council leadership has considered the best path forward to initiating this work and has shared their thoughts for advancing this effort on [date], which considers a Policy Status Report (PSR) as a possible next step. The leadership team recognizes that a significant amount of time has passed since the 2011 UDRP Issue Report such that it will be helpful to know if new issues or information have emerged that could be relevant to a comprehensive policy review. Leadership also believes that a PSR will support a data-driven policy development effort and will result in a more tightly scoped Charter, that is consistent with the principles of PDP 3.0. Here, the Council will discuss possible next steps, including a PSR for advancing RPMs Phase 2. 6.1 – Introduction of topic (Council leadership) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - IGO Work Track Questions for Council (20 minutes) On 18 April 2019, the Council voted<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+April+20…> to approve recommendations 1-4 of the Final Report from the IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG. The Council also resolved to not approve Recommendation 5 and, ”directs the Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP to consider, as part of its Phase 2 work, whether an appropriate policy solution can be developed that is generally consistent with Recommendations 1, 2, 3 & 4 of the PDP Final Report and: * accounts for the possibility that an IGO may enjoy jurisdictional immunity in certain circumstances; * does not affect the right and ability of registrants to file judicial proceedings in a court of competent jurisdiction; * preserves registrants’ rights to judicial review of an initial UDRP or URS decision; and * recognizes that the existence and scope of IGO jurisdictional immunity in any particular situation is a legal issue to be determined by a court of competent jurisdiction.” In respect of that resolution, the GNSO Council prepared an Addendum<https://gnso.icann.org/sites/default/files/file/field-file-attach/rpms-char…> to the RPMs PDP charter to support work related to Recommendation 5 and approved<https://gnso.icann.org/en/council/resolutions/2020#202001> it during its January 2020 Council meeting. During its September 2020 Council meeting, the Council agreed to initiate both the Expressions of Interest process to identify a single, qualified Work Track Chair and issue a call for Members and Observers to join the IGO Work Track. Led by Chris Disspain as the Chair, the Work Track has been meeting since late February of 2021. The Work Track has sought to make meaningful progress within the bounds of the Addendum, with members recognizing that this foundational discussion will influence how the group will work and thus, what its work plan should look like. During its April meeting, the Council received a brief update and acknowledged the work track’s Work Plan<https://community.icann.org/download/attachments/164626455/RPM-IGO-CRWT_Pro…> (April package here<https://community.icann.org/download/attachments/164626455/RPM-IGO-CRWT_Pro…>). In chartering this work, the GNSO Council expected that the work should be completed in an efficient manner and that frequent updates to the Council would be helpful to ensure an effective outcome. The Council has already received updates during the April and May meetings. The Work Track has made steady progress in evaluating recommendation 5 and determining an appropriate policy path forward. According to the work plan, the Work Track is expected to deliver its Initial Report for public comment in early August, but due to the need to migrate the current Public Comment platform on the ICANN org website to a substantially new feature that will be compliant with the Information Transparency Initiative and its requirements, ICANN org needs to impose a moratorium on launching Public Comment proceedings between late July and end August. The Work Track has submitted a Policy Change Request in light of this external factor. With the Work Track nearing a stage where it will be able to publish its Initial Report, notwithstanding the moratorium, it is timely to bring two questions to the Council for their consideration. The first question relates to the fact that the IGO Work Track was originally convened under the auspices of the then-ongoing Review of All Rights Protection Mechanisms (RPM) Policy Development Process (PDP) Working Group, which has since delivered its Final Report to the Council and subsequently approved; planning for Phase 2 of the RPM work is ongoing, which leaves the Work Track without a parent Working Group. The second question relates to the requirements imposed on the Work Track via the Addendum. The Work Track has kept Recommendation #5 (regarding IGO jurisdictional immunity) at the forefront in its work. However, it has concluded that a feasible and appropriate policy solution cannot be crafted simply by looking at that recommendation in isolation. Accordingly, the Work Track is seeking feedback to determine whether the approach and solution are in accordance with the limitations in the addendum. The Work Track leadership and staff have drafted a briefing document to support this agenda item. Here, the Council will discuss the two questions and seek to reach agreement on answers/solutions. 7.1 – Update (John McElwaine, GNSO Council Liaison) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL UPDATE - Update on the Customer Standing Committee and Next Steps for the Council (10 minutes) The GNSO Council will soon have two responsibilities regarding the Customer Standing Committee, per the ICANN Bylaws. The first requirement is that, in accordance with Section 17.2 (d) of the ICANN Bylaw and per the CSC Charter, the full membership of the CSC must be approved by the GNSO Council. This is expected to occur no later than September of 2021. The second responsibility relates to the Customer Standing Committee (CSC) Effectiveness Review, which would represent the second such review. The ICANN Bylaws, Section 17.3 (b) states, "The effectiveness of the CSC shall be reviewed two years after the first meeting of the CSC; and then every three years thereafter. The method of review will be determined by the ccNSO and GNSO and the findings of the review will be published on the Website." The Customer Standing Committee (CSC) was established and conducted its first meeting on 6 October 2016, so the first review needed to take place in 2018. As required, the GNSO and ccNSO established a process to conduct the review, which per the Council’s resolution “concluded that the most practical and efficient path forward is for the ccNSO and GNSO to each appoint two members to conduct the CSC Effectiveness Review that will consider the effectiveness of the CSC in performing its responsibilities as outlined in the CSC Charter and that the findings of the Review, as adopted by both the GNSO and ccNSO Councils, will become an input to the IANA Naming Function Review.” The Council approved<https://gnso.icann.org/en/council/resolutions#201809> this process in September of 2018. After completing an Initial Report<https://www.icann.org/en/system/files/files/csc-effectiveness-initial-16jan…> and publishing it for public comment, the Final Report<https://community.icann.org/x/VQpIBg> was delivered 05 March 2019; the Council adopted<https://gnso.icann.org/en/council/resolutions#201903> the Final Report on 13 March 2019. With an October 2016 first meeting for the CSC, the time for the second review of the CSC is October 2021. The GNSO and ccNSO will need to establish the terms of reference for the second review, which may be able to highly leverage the ToR<https://community.icann.org/display/CRT/Terms+of+Reference> from the first review. At a minimum, this second review will need to include a determination whether the recommendations from the first effectiveness review were successfully implemented. Here, the Council will discuss the expectations of the Council as it relates to the two CSC items. 8.1 – Introduction of topic (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: ANY OTHER BUSINESS (5 minutes) 9.1 - Transfer Policy Review PDP - Review of Work Plan<https://community.icann.org/x/MQDQCQ> _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 19:00 UTC Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 12:00 San José, Costa Rica (CST) UTC-6 13:00 New York/Washington DC, USA (EDT) UTC-4 15:00 Buenos Aires, Argentina (ART) UTC-3 16:00 Rio de Janeiro, Brazil (BRST) UTC-3 16:00 London, United Kingdom (GMT) UTC+1 20:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 20:00 Paris, France (CEST) UTC+2 21:00 Moscow, Russia (MST) UTC+3 22:00 Singapore (SGT) (+1day) UTC+8 03:00 Melbourne, Australia (AEDT)(+1day) UTC+11 05:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 31 October 2021, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 7 November 2021 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/ybavc84m

1 0

RPM IGO CRWT: Project Change Request + June 2021 Project Package
by policy＠bacinblack.com July 12, 2021

July 12, 2021

Dear GNSO Council, On behalf of the IGO WT leadership team, please find attached a Project Change Request (PCR) for delivery of the Initial and Final Reports. On page 2 of the project package (linked below) you will see that the task for delivering the Initial Report for public comment on 3 August 2021 was downgraded to a red condition. This is a signal that the WT will miss its committed deliverable date. The rationale for missing the date is due to ICANN Org's deployment of the new Information Transparency Initiative Public Comment platform. This unforeseen event is because the legacy public comment platform will not accept new public comment proceedings or posting of public comment reports until the migration is completed. The key dates of the platform moratorium are 20 July - 30 August. As part of the PCR, you will also find attached a proposed timeline. Delivery of the Initial Report will change from 3 August to 7 September and the Final Report deliverable date is now 21 December 2021. The extra five weeks will not go unused, as The IGO WT will use this extra time to strengthen its report prior to public comment. Link to IGO WT's 30 June 2021 Project Package: https://community.icann.org/x/FwDQCQ 1. Page 01 - Summary timeline 2. Page 02 - Project Sitrep - an extract from the Council's Project List 3. Page 03 - Group roster 4. Page 04 - Group attendance for plenary 5. Page 05 - Work and activity metrics 6. Page 06 - Project Plan, Gannt chart 7. Page 07 - Work plan & Action items for the period Please let me know if you have any questions. Thank you B Berry Cobb GNSO Policy Consultant Principal | BAC in Black Consulting <http://bacinblack.com/> Mob: +1 (720) 839-5735 <https://twitter.com/berrycobb> <https://www.linkedin.com/in/berrycobb/>

1 0