*31 Jul: ICANN Board Chair announces the New gTLD Program: Next Round Implementation Plan which (re-)establishes a target for the the next Applicant Guidebook to be finalized in May 2025, and which then enables the application round to open in Q2 2026 (with the goal of April 2026), noting that any delays to the timeline of the Policy Implementation work stream will cause delays to the opening of the round.

*27 Jul: ICANN Board resolves at a special meeting to acknowledges receipt of a draft New gTLD Program: Next Round Implementation Plan from ICANN org and plans to publish the plan on or before 31 July 2023.

25 Jul: GNSO Council submitted an updated ICANN77 Deliverable Workplan & Timeline SubPro Related Activities to provide further clarity to its 15 Jun submission
15 Jun: GNSO Council submitted its ICANN77 Deliverable Work plan & Timeline SubPro Related Activities as requested by the ICANN Board in its 16 Mar resolution
5 Jun: GNSO Council holds extraordinary meeting to discuss completion of outstanding SubPro-related work.
22 May: GNSO Council meets with the ICANN Board on pending SubPro recommendations.
4 May: GNSO Council holds extraordinary meeting to discuss the Proposal of SubPro Small Team Triage Exercise and determine next steps on the 38 pending recommendations.
23 Mar: GNSO Council received letter from GAC in respect of GAC input on GAC Priority Topics relative to SubPro Recommendations marked as "pending"
22 Mar: GNSO Chair sends letter to ICANN Board and Sally Costerton noting Council's appreciation on progress made during recent weeks and at ICANN76 towards "getting things done".
21 Mar: GNSO Council constitutes a Council Small Team to conduct Council triage for the 38 Pending SubPro Outputs, comprising Anne Aikman-Scalese (NCA), Bruna Martins dos Santos (NCSG), Jeff Neuman (GNSO Liaison to SubPro ODP), Justine Chew (ALAC Liaison to GNSO), Nacho Amados (RySG), Paul McGrady (NCA-NCPH), Sebastien Ducos (RySG), Stephanie Perrin (NCSG), Susan Payne (IPC) and Tomslin Samme-Nlar (NCSG).
16 Mar: GNSO Council receives letter from ICANN Board in respect of Board's action on SubPro Final Report

*16 Mar: ICANN Board resolves during its Board Meeting at ICANN76 to adopt the SubPro Outputs in Section A of its "Scorecard on Subsequent Procedures PDP" (Scorecard); marking 38 Outputs in Section B of the Scorecard as "pending" and noting ongoing community discussions relating to Topic 17: Applicant Support, Topic 23: Closed Generics, and Topic 25: Internationalized Domain Names (IDNs), as well as additional dependencies concerning specific Review Team Recommendations, the Name Collision Analysis Project Study 2 Report (NCAP2), and other items noted in Section C of the Scorecard.

Card

id	AddSubPro
label	ADDITIONAL WORK ON SUBSEQUENT PROCEDURES

Additional Work on Subsequent Procedures – TO MONITOR THIS for ALAC/At-Large participation.

2023

31 Jul - 11 Sep: GGP Applicant Support Guidance Recommendation Initial Report out for public comment

2022

21 Nov: GGP on Applicant Support kicks off.
20 Oct: Mike Silber was confirmed by Council as the Chair for the GGP.
25 Aug: Council resolved unanimously to initiate the GGP using a "Representative + Observers" WG model with each SG/C/AC to be invited to nominate a representative. The GGP will start with Applicant Support first, with the possibility of adding further topics down the line.
12 Aug: Council is expected to consider and vote on a new version of the GGP on Application Support. In brief, this version of the GPP on Application Support proposes as follows:
- A (smaller) Working Group employing a “Representative + Observers” model, to conduct and conclude its work, and oversight activities, in an efficient/effective manner while allowing for inclusive community participation. GNSO Council retains oversight, as with any GNSO WG.
- Each AC/SG, ASO and ccNSO may appoint 1 Member to the WG, who are expected to represent the view of their appointing organization and may be called on to provide the official position of their appointing
  organization and will be responsible for participating in GGP consensus calls. Appointing organizations may replace their Member(s) at their discretion.
- Members must either possess a level of expertise in previous deliberations and/or knowledge that may have been lacking during those initial deliberations.
- The WG has the flexibility/discretion to rely on Subject Matter Experts (SMEs) in specific fields to aid in deliberations for certain tasks, but these SMEs will not be considered as Members of the WG.
- The GNSO Liaison to the ODP may serve as an non-voting member of the WG to advise on issues discussed within the SubPro PDP.
21 Jul: Council considered a late proposed amendment to the substantive motion to establish a GGP to work just on Applicant Support. The amendment received some support and it was decided to defer this issue to Council's August 2022 meeting to allow opportunity to incorporate supported element(s) into the substantive motion for Council's consideration.
15 Jun: Council to proceed with a motion in its Jul meeting to establish a GGP to work just on Applicant Support through a Steering Committee (of a representative+observer model) with ultimate oversight by Council. This GGP is the proposed mechanism to address SubPro Implementation Guidance 17.5, which suggests the creation of a dedicated IRT and it be charged “with developing implementation elements of the Applicant Support Program. In conducting its work, the Implementation Review Team should revisit the 2011 Final Report of the Joint Applicant Support Working Group as well as the 2012 implementation of the Applicant Support program.” This dedicated IRT was to be charged with making substantive decisions on outreach activities and allocation of scarce resources (e.g., when there are more qualified applicants than available funds), among other activities.
19 May: Council to explore (intersessionally) the Draft New gTLD Subsequent Procedures GNSO Guidance Process (GPP) Initiation Request.
5 May: Council received a Draft New gTLD Subsequent Procedures GNSO Guidance Process (GPP) Initiation Request for its consideration. This will likely be discussed at Council's May 2022 meeting.
9 Mar: Based on GNSO SubPro ODP Liaison update - Question set #2, Council discussed options for the way forward to deal with a number of areas possibly considered as incomplete in terms policy-development: including on Applicant Support, SPIRT, challenges and appeals. But Council has yet to determine the mechanism to adopt.

Card

id	CGs
label	CLOSED GENERICS

RE: Closed Generics, specifically

2023

24 Aug: Council update on status of Closed Generics
15 Jul: Comments on Draft framework for Closed Generics due
End May: Draft framework for Closed Generics expected to be delivered to the ALAC, GAC, GNSO and other SOACs for community input.
11 Mar: (CG) GNSO-GAC-ALAC Dialogue face-to-face meeting
31 Jan: (CG): GNSO-GAC-ALAC Dialogue face-to-face meeting.

2022

2 Sep: (CG): Council leadership initiates selection by SGs for their representatives for the dialogue.
9 Aug: (CG): ALAC receives invitation to formally join GNSO and GAC as parties to the Dialogue on Closed Generics.
21 Jul: (CG): Still awaiting convening of the Dialogue, which is inter alia subject to the identification/nomination of representatives from the GNSO and GAC.
29 Jun: (CG): Council has sent a letter to the Board and the GAC relaying its recommendations on the GAC-GNSO Dialogue; cc-ed to ALAC Chair, appending the Jun 2022 report of the Council Small Team on Closed Generics.
15 Jun: (CG): Council has agreed to relay its recommendations to the Board and GAC as the next step leading to the start of the GAC-GNSO Dialogue, with ALAC participation.
19 May (CG): Council Chair Philippe Fouquart received a reply from Maarten Botterman to Council's 27 Apr letter; inter alia encourages GAC and Council to confer on the question of ALAC's participation in the consultative process.
5 May (CG): Council's reconstituted Small Team now comprises Paul McGrady (NCA-Non CPH), Kurt Pritz (RySG), Manju Chen (NCSG), Jeff Neuman (GNSO Liaison to GAC), Justine Chew (ALAC Liaison to GNSO), Greg Dibiase (RrSG), Desiree Miloshevic (NCA-CPH), and Marie Pattulo (CSG); also Council leadership comprising Philippe Fouquart, Sebastien Ducos, and Tomslin Samme-Nlar.
27 Apr (CG): Council replied to the ICANN Board, accepting the invitation for a facilitated dialogue with the GAC on Closed Generics.
- In its reply, Council noted there being no SubPro recommendation to change current policy on Closed Generics, the approach for the immediate next round of New gTLD applications would be out of harmony with GAC Advice on Closed Generics (namely that closed generics ought to serve a public interest goal).
- Council stated that Council will pursue next steps for the dialogue (a) on the basis of the Board having asked that its facilitated dialogue be limited to making Closed Generics available with restrictions, including for eg. that they serve a public interest goal; (b) subject to mutual agreement with the GAC on conditions for that dialogue.
- Council also noted to the Board, NCSG's opposition to the limited dialogue party approach.
- (NB. The earlier convened Council small team will now be reconstituted with a larger/more representative membership of Councillors to develop conditions for the dialogue)
22 Apr (GC): GAC responded to the Board's 6 Mar and 10 Mar letters, raising points on the ICANN Org's Framing Paper.
6 Apr (CG): Council CGs Framing Paper Small Team convened with narrow remit of "proposing to Council next steps in responding to the Board proposal (i.e., whether or not the Council is open to working with the GAC on developing a framework for closed generics)" – Council to decide.
30 Mar (CG): Board replied to GAC's 10 Mar letter, acknowledging GAC’s willingness to have ALAC participate in the consultation process; encourages GAC and GNSO Council to consider this matter as part of the discussions regarding the proposed dialogue.
15 Mar (CG): Council to convene small team to review the ICANN Org's framework paper regarding the Board-facilitated dialogue between GNSO-GAC, and to suggest next steps.
10 Mar (CG): Further to the 7 Mar correspondence, the Board forwarded ICANN Org's Framing Paper for the dialogue on Closed Generics.
10 Mar (CG): GAC replied to the Board's 6 Mar letter, agreeing to participate in dialogue and welcomed participation from the At-Large Advisory Committee (ALAC) in this consultation process.
6 Mar (CG): ICANN Board wrote to the GAC and Council requesting for facilitated dialogue on way forward with Closed Generics (CG).

Card

default	true
id	DNS_Abuse
label	ON DNS ABUSE

Potential Council next steps regarding DNS abuse – TO MONITOR THIS and ENSURE ALAC input is understood.

2023

29 Jun: Council replies to RrSG, RySG, Contractual Compliance and DNSAI on Bulk registrations.
15 May: Council's small team shared its initial feedback regarding the input received on the issue of bulk registrations.

* 25 Apr: ICANN announced its funding of a new project called Inferential Analysis of Maliciously Registered Domains (INFERMAL) to explore drivers of malicious domain name registrations.

20 Apr: Council has determined that this small team should continue its work reviewing the replies received from RySG, RrSG, ICANN Contractual Compliance and DNS Abuse Institute to the two 6 Jan letters. This Council small team now has a refreshed membership of Thomas Rickert, Mark Datysgeld, Wisdom Donkor, Theo Geurts, Sebastien Ducos, Greg DiBiase, Tomslin Samme-Nlar, Paul McGrady, Nacho Amadoz and Justine Chew.

* 19 Apr: Justine's 4th presentation on a summary of the replies below

13 Mar: RrSG reply re: Bulk Registrations
7 Mar: CPH (RySG & RrSG) reply re: Targeted contractual amendments
3 Mar: RySG reply re: Bulk Registrations
27 Feb: DNSAI reply re: Bulk Registrations
23 Feb: ICANN Contractual Compliance reply re: Bulk Registrations
6 Jan: GNSO Council letters (borne out of the work of the GNSO Council Small Team on DNS Abuse) have been distributed and posted:
- The DNS Abuse - Targeted contractual amendments letter to RrSG & RySG
- The DNS Abuse – Bulk Registrations letter to RrSG, RySG, DNSAI, ICANN Contractual Compliance

2022

15 Dec: Leadership of Council's small team on DNS abuse has prepared the draft letter to the Contracted Parties for Council's approval, per the small team's Recommendation #4
17 Nov: Council has accepted the small team's report, containing 4 recommendations, delivered on 10 October. For more specific details on the recommendations and action, refer to the 17 Nov Special Summary Report.
20 Oct: Council acknowledged the Small Team's report and recommendations; acquiesced to the Small Team regrouping to work on Recommendation #4 (drafting of letter to Contracted Parties).
10 Oct: Small Team's final report and recommendations were submitted to GNSO Council for consideration.
21 Sep: Small Team's draft report and recommendations were presented and discussed at ALAC-GNSO meeting at ICANN75.

*17 Aug: Justine's 3rd Presentation to CPWG on Small Team deliberations on comments received from SGs/Cs/DNSAI; + discussion on draft report

4 Aug: Small Team completes deliberation on comments received from outreach exercise and moves onto producing their report

*20 Jul: Justine's 2nd Presentation to CPWG on Small Team deliberations on comments received from ALAC, GAC, SSAC

16 Jun: Small Team conducts meeting at ICANN 74
2 Jun: Small Team begins review of responses from Contractual Compliance.

*25 May: Justine's 1st Presentation to CPWG on responses from Contractual Compliance

19 May: Small Team completes review of comments received from outreach to ALAC, GAC, SSAC and DNSAI, as well as SGs (RySG) and Cs (BC).
20 Apr: ALAC input to 7 Mar letter considered by Small Team and well received, in general.
6 Apr: Input received from BC. Small Team met, to proceed with info gathering from Contractual Compliance in respect of action to do with DNS Abuse vis a vis Contracted Parties. Still awaiting input from other SG/Cs.
4 Apr: Small Team received responses from ALAC, GAC, SSAC and DNSAI to 7 Mar letters. Small Team to meet 6 Apr.
18 Mar: Reply date for 7 Mar letter to ALAC extended to 4 Apr.
7 Mar: Council issued letters to ALAC, GAC, SSAC and the DNS Abuse Institute (DNSAI) to seek input on what DNS abuse issues are best mitigated via policy development specifically, if any, as a mechanism to help determine the Council’s next steps on DNS abuse; to reply by 21 Mar. Input to be sought from each SG also. More respondents may be approached at a later date.
9 Feb: Small Team initial meeting. Updates to be provided at Council Meeting #2 of 2022.
4 Feb: Council small team (comprising Thomas Rickert, Mark Datysgeld, Wisdom Donkor, Maxim Alzoba, Sebastien Ducos, Greg DiBiase, and Justine Chew, also Philippe Fouquart, Tomslin Samme-Nlar, and Paul McGrady) set to begin work on 9 Feb.

2021

28 Oct: A Council small team (comprising Thomas Rickert, Mark Datysgeld, Wisdom Donkor, Kristian Ormen, Maxim Alzoba, Sebastien Ducos) to draft potential GNSO Council next steps regarding DNS abuse.

Card

default	true
id	Consensus_Policy
label	ON MODIFYING GTLD CONSENSUS POLICIES

ICANN Org Discussion paper on Modifying gTLD Consensus Policies – TO MONITOR THIS and assess for ALAC input opportunities.

2022

4 May: ICANN Org (GDS) met with Council and SG/C Chairs to progress ongoing discussions on the Oct 2021 Discussion Paper on Modifying gTLD Consensus Policies (Zoom Recording). Discussions to continue.
25 Apr: Council received a GNSO-sec-developed Discussion Paper on suggested Tracking & Coordination of PDP Improvements
6 Apr: Exchanges between Council and GDS ongoing.
20 Jan: Council to approach ICANN Org on efficient way to address concerns raised in Discussion Paper.
NB. Council small team has expanded (now comprises John McElwaine, Maxim Alzoba, Stephanie Perrin, Antonia Chu, Thomas Rickert, Steve DelBianco, Chris Disspain, Susan Mohr, Sebastien Ducos, and Owen Smigelski)

2021

28 Oct: A Council small team (comprising John McElwaine, Maxim Alzoba, Stephanie Perrin, Antonia Chu, Thomas Rickert and possibly others) to review the Discussion Paper on Modifying gTLD Consensus Policies and develop a draft response.

Card

id	TRP
label	Transfer Policy Review PDP

Transfer Policy Review Policy Development Process (TPR-PDP)

2023

11 Jan: In the course of Phase 1 work conducted to date, the WG discovered that certain Phase 2 topics must be addressed before Phase 1 recommendations can be fully developed. As a result, the PDP leadership team alerts Council to Project Change Request (PCR) to update its work plan to consolidate all work into a single phase and change the order in which topics are considered. This will impact the timeline for key deliverables.

2022

21 Jun - 16 Aug: WG conducts public comment for its Phase 1A Initial Report

2021

16 Dec: Council approved a Project Change Request (PCR) to update charter topics considered in Phase 1 of the TPR-PDP by moving the topic of NACK (rejection of transfer request) of an unauthorized transfer to Phase 1a scope from Phase 2.
May: WG begins meeting
Feb: Council initiated the two-phased Transfer Policy Review PDP

Card

id	IDN
label	Internationalized Domain Names EPDP

Internationalized Domain Names EPDP

2023

20 Jul: GNSO Council received a revised project plan from the IDNs EPDP Working Group which shaves 13 months off the earlier timeline. The key milestones for this EPDP are now as follows:
- Phase 1 Final Report remains expected to be delivered to Council in Nov 2023
- Council then considers this Phase 1 Final Report and decides on the adoption of report and recommendations
- Phase 2 Initial Report is expected to be published for public comment in Apr 2024 (vs May 2025 earlier)
- Phase 2 Final Report is expected to be delivered to Council in Oct 2024 (vs Nov 2025 earlier)
- Council then considers this Phase 2 Final Report and decides on the adoption of report and recommendations
- Assumptions for this revised project plan must hold for the EPDP to meet the new milestone dates:
  - Progress to be achieved via multiple sessions during ICANN78 (similar to ICANN77)
  - A planned F2F workshop scheduled for early Dec 2023
  - No change to the EPDP Charter / scope of quarter questions
14 Jun: GNSO Council received the latest project plan from the IDNs EPDP Working Group, which provides that:
- Phase 1 Final Report is expected to be delivered to Council in Nov 2023
- Council then considers this Phase 1 Final Report and decides on the adoption of report and recommendations
- Phase 2 Initial Report is expected to be published for public comment in May 2025
- Phase 2 Final Report is expected to be delivered to Council in Nov 2025
- Council then considers this Phase 2 Final Report and decides on the adoption of report and recommendations
- The IDNs EPDP WG is already taking steps to improve its timeline to expedite completion of its work well ahead of the Nov 2025 target
25 May: GNSO Council received a presentation from the EPDP Chair in response to the ICANN Board's request to Council noted in the Board's 16 Mar letter to Council.
16 Mar: GNSO Council receives letter from ICANN Board in respect of Board's action on SubPro Final Report; item 4 pertains to the work of the IDNs EPDP.

2022

17 Nov: Council approved the EPDP's Project Change Request (PCR). With this PCR, the EPDP seeks to facilitate the implementation planning of the New gTLD Subsequent Procedures by bifurcating its work into two phases, with Phase 1 covering topics related to top-level IDN gTLD definition and variant management, and Phase 2 covering issues pertaining to second-level IDN variant management, which also requires a timeline extension due to the diversity and complexity of IDN issues, additional data collection needs, review of ICANN org input for draft recommendations, and public comment-related processes. The timeline now contemplated is:
- Publish Phase 1 Initial Report for Public Comment by April 2023
- Submit Phase 1 Final Report to the GNSO Council by November 2023
- Publish Phase 2 Initial Report for Public Comment by April 2025
- Submit Phase 2 Final Report to the GNSO Council by November 2025
10 Oct: Council is alerted to an impending Project Change Request (PCR) which seeks significant changes to the EPDP's project plan.

* 22 Sep: ICANN Board has approved the IDN Guidelines version 4.1 except the deferred guidelines 6a, 11, 12, 13, 18 and associated Additional Notes, and directed these to be published as IDN Guidelines version 4.1 and to supersede version 3.0.

20 Jan: Council to send letter to ICANN Board responding to the Board’s 20 Oct letter regarding the IDN Implementation Guidelines v4.0.

2021

16 Dec: Council Leadership to draft a response to the ICANN Board’s 20 Oct letter regarding the IDN Implementation Guidelines v4.0.
18 Nov: Council has yet to discuss its approach for the response to the ICANN Board’s 20 Oct letter regarding the IDN Implementation Guidelines v4.0.
Aug: The Expedited Policy Development Process on Internationalized Domain Names (EPDP on IDNs) commenced work on its Charter Questions.

Card

id	RDA_Scoping
label	Registration Data Accuracy Scoping Team

Registration Data Accuracy (RDA) Scoping Team

2023

20 Jul: Council resolved to extend deferral of consideration of recommendations #1 and #2 of the Registration Data Accuracy Scoping Team write up for another six months or at an earlier date if the DPA negotiations have been completed before six months have passed and/or there is feedback from ICANN org if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy.
20 Apr: Council considered the RDA Scoping Team Survey Summary Results and ICANN org's 14 Mar input.
14 Mar: ICANN org replies to Council's 1 Dec 2022 letter for an update on outstanding issues related to registration data accuracy and the pending work of the Registration Data Accuracy Scoping Team.

2022

1 Dec: Council sent letter to ICANN org requesting an update on outstanding issues related to registration data accuracy and the pending work of the Registration Data Accuracy Scoping Team.
17 Nov: Council adopted recommendation #3 and deferred consideration of recommendations #1 and #2 as contained in the Scoping Team's write up to the Council of 5 September 2022. For more specific details on the recommendations and action, refer to the 17 Nov Special Summary Report.
10 Oct: The Scoping Team has completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up to the Council on 5 September 2022. In the write up, the group is suggesting moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3). Council is seeking a new Chair for the Scoping Team.
10 May: The RDA Scoping Team submitted a Project Change Request (PCR) to Council.

18 Nov 2021

Council received notice that the ICANN Board has selected two Board members to serve as liaisons to this Registration Data Accuracy Scoping Team. They are Becky Burr and Harald Alvestrand (alternate).
Council has acknowledged the Registration Data Accuracy - Scoping Team (RDA_ST) Project Plan

Card

id	SSAD
label	Temp Spec for Registration Data / SSAD ODP

Temporary Specification for gTLD Registration Data / System for Standardized Access/Disclosure Operational Design Phase (SSAD ODP); See: https://www.icann.org/ssadodp for more official info

2023

22 Mar: GNSO Chair sends letter to ICANN Board and Sally Costerton noting Council's appreciation on progress made during recent weeks and at ICANN76 towards "getting things done".
11 Mar: GNSO EPDP Phase 2 (SSAD) - Implementation of Whois Disclosure System at ICANN76 - Whois Disclosure System (WDS) now known as Registration Data Request Service (RDRS).
6 Mar: Council receives ICANN Board's reply to Council's 17 Nov 2022 letter on Council’s recommendations for how to proceed with the WHOIS Disclosure System (WDS).
27 Feb: ICANN Board adopted a resolution directing ICANN org to proceed to develop and launch the WDS as soon as possible. The Board also authorized the use of the Supplemental Fund for the Implementation of Community Recommendations to support this work. In addition, the Board has directed ICANN org to continue to engage with the Phase 2 Small Team throughout the development and operation of the System, and ensure periodic publication of the collected usage data, once operational.

2022

17 Nov: Council sent letter to ICANN Board alerting on Council’s recommendations for how to proceed with the WHOIS Disclosure System (WDS).
17 Nov: Council accepted the EPDP Phase 2 small team findings and recommendations as outlined in the small team's addendum and confirmed that pending the implementation and subsequent running of the Whois Disclosure System (WDS) for a period of up to two (2) years, the SSAD recommendations should remain paused for consideration by the ICANN Board.
Oct: Council is to further discuss next steps on the Whois Disclosure System (WDS) in November.
Sep-ICANN75: Attention on SSAD has now been redirected to ICANN Org's proposal for the Whois Disclosure System (WDS). Design for this WDS was published prior to ICANN75 and ICANN org provided a presentation of the system design to the EPDP Phase 2 small team during ICANN75. Subsequently, the small team and Council held initial discussions amongst themselves, as well as with the Board during their joint session on Tuesday. The Council discussed during its meeting on Wednesday and the small team met informally on Thursday of ICANN75.
Mar: Council Small Team seated (comprising Members: Paul McGrady, Sebastien Ducos, Marc Anderson, Stephanie Perrin, John McElwaine, Olga Cavalli, Thomas Rickert, Laureen Kapin (GAC- shared membership), Chris Lewis-Evans (GAC- shared membership), Alan Greenberg, Sarah Wyld, Steve DelBianco, Becky Burr, Steve Crocker, Philippe Fouquart (GNSO Council Observing) , Tomslin Samme Nlar (GNSO Council Observing); and Alternates: Gregory DiBiase).
1 Feb: GNSO Council Chair invited GNSO SG/Cs, ALAC, GAC to nominate their EPDP Phase 2 representatives for a Council Small Team led by Sebastien Ducos to analyse the SSAD ODA to develop recommendations on next steps. On 4 Feb, the ALAC Chair nominated Alan Greenberg (being one of the 2 ALAC EPDP Phase 2 representatives) for this Council Small Team.
27 Jan: Council and ICANN Board Consultation on SSAD ODP
18 Jan: SSAD ODP Project Update Webinar #5
12 Jan: A follow up discussion is held for Council and and GNSO-appointed EPDP Phase 2 members to discuss next steps ahead of Council's meeting with the ICANN Board on 27 January on concerns around financial sustainability of the SSAD (wiki)
5 Jan: A 4 Jan 2022 summary paper was circulated to Council members ahead of a 12 Jan call

2021

20 Dec: A closed session is held for Council and GNSO-appointed EPDP Phase 2 members only with the SSAD ODP Project Team focusing on the SSAD Cost Model information (presentation)
16 Dec: Council did not discuss GAC's letter of 15 Dec 2021 to Council regarding SSAD ODP
3 Dec: ICANN's SSAD and Governmental Accreditation Authorities Webinar
18 Nov: ICANN Webinar: SSAD ODP Project Update Webinar #4 on the Business Process Design
2 Nov: ICANN Update: Contractual Compliance and Identity Verification Methodology
28 Oct: ICANN72 Webinar: SSAD ODP Project Update #3
24 Sep: ICANN Webinar: SSAD ODP Project Update #2
13 Jul: ICANN Webinar: SSAD ODP Project Update

...

2023 Jan | Feb | Mar | Apr | Extra_May | May | Extra_Jun | Pre-ICANN77_Bilateral | Jun | Jul | Aug | Sep | Bilateral@ICANN78 | Oct | Nov | Dec

...

January 2023 - December 2023 Reports

Anchor

	A-23-0809
	A-23-0809

GNSO COUNCIL MEETING #8 #9 (AUG SEP 2023) (go up to Directory)

Deck of Cards

id	Aug2023Sep2023

Card

id	Show_Aug2023Sep2023
label	SHOW ME

GNSO Council Meeting #8 #9 of 2023 held on 24 Aug 2023 21 Sep 2023

Card

id	Agenda_Aug2023Sep2023
label	AGENDA

GNSO Council Meeting #8 #9 of 2023 held on 24 Aug 21 Sep 2023

Full Agenda | Documents Agenda | Documents | Motions

Item 1: Administrative Matters
Item 2: Opening Remarks / Review of Projects List and Action Item List.
Item 3: Consent Agenda
- Approval of the 2023 Customer Standing Committee (CSC) Slate
Item 4: COUNCIL VOTE - SubPro Small Team Clarifying Statement
Item 5: COUNCIL DISCUSSION - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements
Item 6: COUNCIL DISCUSSION - Chartering the Standing Predictability Implementation Review Team (“SPIRT”)
Item 7: COUNCIL DISCUSSION - SubPro Pending Recommendations - Expected Non-Adoption
Item 8: COUNCIL DISCUSSION - Closed Generics
Item 9: AOB
- 9.1 Update from NIS2 Outreach Team
- 9.2 ICANN78 Planning
- 9.3 Discussion Paper on .Quebec
- 9.4 Grant Program Implementation update to Chartering Organizations

For notes on highlighted items click on MATTERS OF INTEREST tab above

Card

id	MOI_Aug2023Sep2023
label	MATTERS OF INTEREST

Matters of interest to ALAC/At-Large

Item 1: Administrative Matters
- Minutes of the GNSO Council meeting on 20 July were posted on 06 August 2023.
Item 3: Consent Agenda

Card

id	Meet_Sep2023temp
label	MEETING DETAILS

GNSO Council Meeting #9 of 2023 held on 21 Sep 2023 at 21:00 UTC:

GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09

If joining Zoom via Zoom App the following will be required:

Webinar ID: 978 9162 7902
Passcode: 9844091488

Non-Council members are welcome to attend the call as listen-only observers.

Card

id	Meet_Sep2023
label	MEETING RECORD

Records of 21 Sep 2023 Meeting

Audio Recording
Zoom Recording (includes chat and visual and rough transcript. To access the rough transcript, select the Audio Transcript tab)
Transcript
Minutes

Card

id	SumRep_Sep2023
label	SPECIAL REPORT

Special Summary Report of 21 Sep 2023 Meeting to ALAC

For brevity, I will just highlight a few things here. For some of the issues, you can glean a wider perspective from GNSO Council Sep 2023 Matters of Interest and/or from GNSO Council Sep 2023 Meeting Records.

Anchor

	A-23-08
	A-23-08

GNSO COUNCIL MEETING #8 (AUG 2023) (go up to Directory)

Deck of Cards

id	Aug2023

Card

id	Show_Aug2023
label	SHOW ME

GNSO Council Meeting #8 of 2023 held on 24 Aug 2023

Card

id	Agenda_Aug2023
label	AGENDA

GNSO Council Meeting #8 of 2023 held on 24 Aug 2023

Full Agenda | Documents | Motions

Item 1: Administrative Matters
Item 2: Opening Remarks / Review of Projects List and Action Item List.
Item 3: Consent Agenda
- Approval of the 2023 Customer Standing Committee (CSC) Slate
Item 4: COUNCIL VOTE - SubPro Small Team Clarifying Statement
Item 5: COUNCIL DISCUSSION - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements
Item 6: COUNCIL DISCUSSION - Chartering the Standing Predictability Implementation Review Team (“SPIRT”)
Item 7: COUNCIL DISCUSSION - SubPro Pending Recommendations - Expected Non-Adoption
Item 8: COUNCIL DISCUSSION - Closed Generics
Item 9: AOB
- 9.1 Update from NIS2 Outreach Team
- 9.2 ICANN78 Planning
- 9.3 Discussion Paper on .Quebec
- 9.4 Grant Program Implementation update to Chartering Organizations

For notes on highlighted items click on MATTERS OF INTEREST tab above

Card

id	MOI_Aug2023
label	MATTERS OF INTEREST

Matters of interest to ALAC/At-Large

Item 1: Administrative Matters
- Minutes of the GNSO Council meeting on 14 June were posted on 01 July 2023.
- Minutes of the GNSO Council meeting on 20 July were posted on 06 August 2023.
Item 3: Consent Agenda
- Approval of the 2023 Customer Standing Committee (CSC) Slate - In accordance with Section 17
- Approval of the 2023 Customer Standing Committee (CSC) Slate - 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. The Council approves the full slate of members and liaisons, noting that the SSAC has declined to appoint a liaison.
- The ALAC's Liaison for term 2023-2025 is Holly Raiche, with the alternate being Ejikeme Egbuogu
Item 4: COUNCIL VOTE - SubPro Small Team Clarifying Statement
- During its informal session at ICANN76 and the subsequent Council meeting, Council discussed and agreed to task a small team of interested councilors to review the recommendations that the Board placed in a pending status and suggest to the full Council how the underlying concerns that caused the pending status can be best addressed (i.e., a limited triage exercise).
- Since ICANN76, the Council SubPro Small Team has met several times and has completed a comprehensive review of the issues chart, with Board member input on why the Board placed specific recommendations into a pending status. Council discussed the main output of that triage effort, the proposed paths forward for each pending recommendation, during an Extraordinary Meeting on 4 May. During that meeting, Council agreed to further task the small team with taking interim steps (e.g., provision of clarifying information, developing speaking points) in order to support the Council’s dialogue with the ICANN Board on 22 May. Council debriefed after the dialogue with the ICANN Board and discussed next steps.
- During ICANN77 Day 0 Session, Council heard from members of the Board regarding the Board’s views on potential “landing spots” on the pending recommendations. Following this discussion, the Small Team has drafted clarifying statements for items in landing spot one (“Provision of Clarifying Statement to the Board”). During its meeting in July, Council received an update from the Small Team on the proposed clarifying statement.
- 24 Aug update: I have just been informed that the Board has requested more time because "[t]he Board would like to propose a small tweak to the language [in the clarifying statements for Recommendations 9.1, 9.4, 9.8, 9.9, 9.10, 9.12, 9.13, 30.1, 31.16 and 31.17 (all regarding the enforceability of PICs and RVCs) to ensure that it is crystal clear". Hence the recommendations where there is an expectation that the GNSO Council can resolve the ICANN Board concerns via a Clarifying Statement are now:
  - Topic 3: Applications Assessed in Rounds - Recommendations 3.1, 3.2, 3.5, 3.6, 3.7
    - The SubPro Final Report recommendation envisions that “the next application procedure should be processed in the form of a round” and “Application procedures must take place at predictable, regularly occurring intervals without indeterminable periods of review”. However, the GNSO Council confirms its willingness to engage with the ICANN Board to explore a shared vision for the long-term evolution of the program, which could be materially different than what is envisioned for the next round of the New gTLD Program in the Topic 3 recommendations.
  - Topic 6: Registry Service Provider Pre-Evaluation - Recommendation 6.8
    - The GNSO Council confirms its understanding of the Implementation Review Team (IRT) Principles & Guidelines that state that, “the IRT is convened to assist staff in developing the implementation details for the policy to ensure that the implementation conforms to the intent of the policy recommendations.” The Council therefore recognizes that ICANN org will be responsible for establishing the fees charged for the RSP pre-evaluation program, in consultation with the IRT, as is consistent with the roles and responsibilities captured in the IRT Principles & Guidelines. The language used in Recommendation 6.8 is not intended to alter the respective roles and responsibilities of staff and the IRT.
  - Topic 9: Registry Voluntary Commitments / Public Interest Commitments - Recommendation~~s 9.1, 9.4, 9.8, 9.9, 9.10, 9.12, 9.13~~, 9.15
    - Recommendations 9.1, 9.4, 9.8, 9.9, 9.10, 9.12, 9.13 - The GNSO Council confirms that in respect to any new Public Interest Commitments (PICs) and Registry Voluntary Commitments (RVCs), PICs/RVCs entered into must be contractually enforceable, and in respect of RVCs, enforceability is determined by both ICANN org and the applicant. And further, the Council observes that among the purposes of PICs / RVCs is to address public comments, in addressing strings deemed highly sensitive or related to regulated industries, objections, whether formal or informal, GAC Early Warnings, GAC Consensus Advice, and/or other comments from the GAC.
    - Recommendation 9.15: The GNSO Council confirms that this recommendation does not require any implementation nor creates any dependencies for the Next Round of the New gTLD Program.
  - Topic 26: Security and Stability - Recommendation 26.9
    - The GNSO Council confirms that the “any level” language referenced in the recommendation should be interpreted to only be in respect of domain names that are allocated by the registry operator.
  - Topic 29: Name Collision - Recommendation 29.1
    - The GNSO Council believes that Recommendation 29.1 can be adopted by the Board on the understanding that it does not need to be acted on until such time any next steps for mitigating name collision risks are better understood out of the Name Collision Analysis Project (NCAP) Study 2.
  - ~~Topic 30: GAC Consensus Advice and GAC Early Warning - Recommendation 30.7~~
    - ~~Please see the Council’s clarifying statement for Recommendations 9.1, 9.4, 9.8, 9.9, 9.10, 9.12, 9.13.~~
  - ~~Topic 31: Objections - Recommendations 31.16, 31.17~~
    - ~~Please see the Council’s clarifying statement for Recommendations 9.1, 9.4, 9.8, 9.9, 9.10, 9.12, 9.13.~~
  - Topic 34: Community Applications - Recommendation 34.12
    - The GNSO Council confirms its recommendation that terms included in the contract between ICANN org and the CPE Provider regarding the CPE process must be subject to public comment. This recommendation however is not intended to require ICANN org to disclose any confidential terms of the agreement between ICANN org and the CPE Provider.
  - Topic 35: Auctions - Recommendations 35.3, 35.5
    - The GNSO Council confirms that the references to private auctions in Recommendations 35.3 and 35.5 merely acknowledge the existence of private auctions in 2012 and should NOT be seen as an endorsement or prohibition of their continued practice in future rounds of the New gTLD Program. The Council notes that there were extensive discussions on the use of private auctions in the SubPro working group. To the extent that draft recommendations were developed as to private auctions, these did not receive consensus support in the working group but did receive strong support with significant opposition.
- Council will vote on the clarifying statement to be submitted to the ICANN Board.
Item 5: COUNCIL DISCUSSION - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements
- The GNSO Framework for Continuous Improvement Pilot was initiated in June 2021 to determine whether the framework, as outlined here, could serve as an approach for dealing with the various projects that are focused on improvements to GNSO processes and procedures.
- The CCOICI tasked the GNSO Statement of Interest (SOI) Task Force to address the following questions:
  1. Is the original objective of the SOI, as stated in the BGC WG Report, still valid? If not, why not and what should the current objective be?
  2. Based on the response to question 1), is the requested information to be provided as part of the SOI still fit for purpose? If not, why not, and what would need to be changed to make it fit for purpose?
  3. Are there any further measures that should be considered from an enforcement / escalation perspective, in addition or instead of those already included in the requirements?
- The CCOICI submitted to Council for consideration its Recommendations Report following its review of the Recommendations Report submitted to the CCOICI by the GNSO Statement of Interest Task Force based on their review of the GNSO Statement of Interest (SOI) Requirements as well as their review of the input received in response to the public comment forum.
- Council will receive an overview of the CCOICI Recommendations Report on the SOI Requirements.
Item 6: COUNCIL DISCUSSION - Chartering the Standing Predictability Implementation Review Team (“SPIRT”)
- In its Final Report, the Subsequent Procedures Working Group recommended “the formation of a Standing Predictability Implementation Review Team (‘SPIRT’) (Pronounced ‘spirit’) to serve as the body responsible for reviewing potential issues related to the Program, to conduct analysis utilizing the framework, and to recommend the process/mechanism that should be followed to address the issue (i.e., utilize the Predictability Framework). The GNSO Council shall be responsible for oversight of the SPIRT and may review all recommendations of the SPIRT in accordance with the procedures outlined in the GNSO Operating Procedures and Annexes thereto.”
- Council will hear on the issue of SPIRT chartering.
Item 7: COUNCIL DISCUSSION - SubPro Pending Recommendations - Expected Non-Adoption
- Further to Item 4: SubPro Small Team Clarifying Statement which addressed 22 of 38 SubPro recommendations marked as "pending", the Council SubPro Small Team has also looked at proposing paths for the remaining 16 recommendations the Board is not expected to adopt.
- Council will hear an update on the proposed path. In addition, the small team is requesting Council for further instructions now that it has reached the solution building stage; as well as input on whether or not it is time to invite the GAC to participate more formally in the small team's work and how that would work practically.
Item 8: COUNCIL DISCUSSION - Closed Generics
- In March 2022, the ICANN Board requested that the GAC and GNSO Council consider engaging in a facilitated dialogue to develop a framework for further GNSO policy work on the issue of Closed Generics. The GAC and GNSO Council agreed to the Board’s suggestion and each appointed six participants for the dialogue. One participant and one alternate from the ALAC were also appointed. Should the GAC-GNSO facilitated dialogue result in an agreed framework, the agreements will be further developed through the appropriate GNSO policy process.
- Following an initial, informal meeting at ICANN75 in Kuala Lumpur, the dialogue participants have since been meeting regularly via Zoom and held a substantive two-day face-to-face meeting in Washington, D.C. in late January 2023. The dialogue is hoping to deliver a draft framework around the end of April 2023 to the ALAC, GAC, GNSO and other SOACs for community input. At this stage, groups are expected to have approximately four weeks to review the document.
- During its meeting at ICANN76, the ICANN Board passed a resolution adopting a substantial portion of the outputs from the New gTLD Subsequent Procedures PDP, setting in motion the start of the implementation process for the next round of new gTLDs. As part of the resolution, the Board established deadlines for key deliverables that will impact the development of the implementation plan.
- The GNSO Chair, GAC Chair, and ALAC Chair plan to send a separate communication to the ICANN Board that reflects the decision they took and, as stated in the letter, expressing the collective view that:
  - (1) closed generic gTLDs should not be viewed as a dependency for the next round;
  - (2) until there is community-developed policy, the Board should maintain the position from the 2012 round (i.e., any applications seeking to impose exclusive registry access for "generic strings" to a single person or entity and/or that person's or entity's Affiliates (as defined in Section 2.9(c) of the Registry Agreement) should not proceed; and
  - (3) should the community decide in the future to resume the policy discussions, this should be based on the good work that has been done to date in the facilitated dialogue.
- Council will discuss the current state of work and the proposed communication to the Board.
Item 9: AOB
- 9.1 Update from NIS2 Outreach Team
- 9.2 ICANN78 Planning
- 9.3 Discussion Paper on .Quebec
  - Discussion Paper about “.québec” Challenges
  - ALAC correspondence on DotQuebec
- 9.4 Grant Program Implementation update to Chartering Organizations

Card

id	Meet_Aug2023temp
label	MEETING DETAILS

GNSO Council Meeting #8 of 2023 held on 24 Aug 2023 at 13:00 UTC: https://tinyurl.com/2h2mdzcd.

06:00 Los Angeles; 09:00 Washington DC; 14:00 London; 15:00 Paris; 16:00 Moscow; 07:00 Melbourne

GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09

If joining Zoom via Zoom App the following will be required:

Webinar ID: 978 9162 7902
Passcode: 9844091488

Non-Council members are welcome to attend the call as listen-only observers.

id	Meet_Aug2023
label	MEETING RECORD

Records of 24 Aug 2023 Meeting

Audio Recording
Zoom Recording Recording (includes chat and visual and rough transcript. To access the rough transcript, select the Audio Transcript tab)
Transcript
Minutes

Card

id	SumRep_Aug2023
label	SPECIAL REPORT

Special Summary Report of 24 Aug 2023 Meeting to ALAC

For brevity, I will just highlight a few things here. For some of the issues, you can glean a wider perspective from GNSO Council Jul Aug 2023 Matters of Interest and/or from GNSO Council Jul Aug 2023 Meeting Records.

Anchor

	A-23-07
	A-23-07

GNSO COUNCIL MEETING #7 (JUL 2023) (go up to Directory)

...

Content

Space Tools

Versions Compared

Old Version 500

New Version 501

Key

January 2023 - December 2023 Reports