Page History

Developments in 2021-2024 on:

• Next Steps for New gTLD Round (post 2022/2023 Subsequent Procedures Operational Design Assessment (SubPro ODA))
• Additional Work on Subsequent Procedures (including re: Applicant Support)
• Modifying gTLD Consensus Policies
• Transfer Policy Review Policy Development Process (TPR-PDP)
• Internationalized Domain Names Expedited Policy Development Process (IDNs-EPDP)
• Registration Data Accuracy (RDA) Scoping Team
• Temporary Specification for gTLD Registration Data / System for Standardized Access/Disclosure Operational Design Phase (SSAD ODP)

Next Steps for a New gTLD Round 2023-2024 (post Subsequent Procedures Operational Design Assessment (SubPro ODA))  

2024

• 22 Feb: ICANN79 Prep Week session on the SubPro supplemental recommendations developed by the GNSO SubPro Small Team Plus.

     *1 Feb: ICANN org initiates public comment proceeding for input on proposed language for 7 sections of the Applicant Guidebook (AGB) for the New gTLD Program: Next Round.

2023 - Post ODA

    *7 Dec: ICANN Board initiates Public Interest Commitments/Registry Voluntary Commitments Consultation, issuing their Draft Implementation Framework for Content-Related Registry Commitments.

    *21 Nov: ICANN Board previews Public Interest Commitments/Registry Voluntary Commitments Consultation

    *26 Oct: ICANN Board resolves during its regular Board Meeting to adopt the Scorecard: Subsequent Procedures dated 26 October 2023 (the "October 2023 Scorecard"), comprising:

• • Section A, which details the recommendations that the Board adopts with the second Clarifying Statement.
  • Section B, which details the recommendations that the Board does not adopt (Recommendations 32.1, 32.2 and 32.10) because they are not in the best interests of the ICANN community or ICANN, including a Board statement and rationale for each of the Outputs, per Bylaws Annex A, Section 9.

and directed ICANN org, to commence the implementation work related to the recommendations adopted by the Board in Section A of the October 2023 Scorecard, and to consider the recommendations and the second Clarifying Statement jointly for the purpose of implementation and operation of the New gTLD Program: Next Round.

• 21 Oct: GNSO Council transmitted to the ICANN Board its "New gTLD Subsequent Procedures Pending Recommendations - GNSO Council Second Clarifying Statement" (Second Clarifying Statement) developed by the SubPro Small Team to address the Board's concerns on 10 pending Outputs around the enforceability of Public Interest Commitments (PICs) and Registry Voluntary Commitments (RVCs).

   *10 Sep: ICANN Board resolves during its regular Board Meeting to adopt the Scorecard: Subsequent Procedures dated 10 September 2023 (the "September 2023 Scorecard"), comprising:

• • Section A which details the Outputs that the Board adopts: Recommendations 16.1, 18.4, 19.1, and 19.3; also input on implementation of Recommendations 30.4, 30.5 and 30.6 post discussion with GAC. 
  • Section B, which details the Outputs that the Board adopts with the "New gTLD Subsequent Procedures Pending Recommendations - GNSO Council Clarifying Statement" transmitted to the Board on 5 September 2023 that provide relevant context to these Outputs; Affirmation with Modification 3.1, Recommendations 3.2, 3.5, 3.6, 3.7, 6.8, 9.15, 26.9, 29.1, 34.12, 35.3 and 35.5.
  • Section C, which details the Outputs that the Board does not adopt, including a Board statement and rationale for each of the Outputs, per Bylaws Annex A, Section 9a, because they are not in the best interests of the ICANN community or ICANN: Recommendations 9.2, 17.2, 18.1, 18.3, 22.7, 24.3, and 24.5.
  • Section D, which details the recommendations that remain pending following this Board action, i.e. Recommendations 9.1, 9.4, 9.8, 9.9, 9.10, 9.12, 9.13, 30.7, 31.16, and 31.17 (all relating to the enforceability of PICs and RVCs), and  32.1, 32.2, and 32.10 (all relating to the proposed Challenge & Appeal mechanisms).

and directed ICANN org to commence the implementation work related to the Outputs adopted by the Board in Section A of the September 2023 Scorecard, taking into account the noted Board considerations regarding recommendations 18.4, 30.4 and 30.6.

See my 14 Jun 2023 Council Meeting summary report for a distillation of (selected) SubPro Output context and Board concerns

• 5 Sep: GNSO Council transmitted to the ICANN Board its "New gTLD Subsequent Procedures Pending Recommendations - GNSO Council Clarifying Statement" (Clarifying Statement) developed by the SubPro Small Team to address the Board's concerns on the pending Outputs.

   *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 to the ICANN Board an updated ICANN77 Deliverable Workplan & Timeline SubPro Related Activities to provide further clarity to its 15 Jun submission
• 15 Jun: GNSO Council submitted to the ICANN Board 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; and directed ICANN org to commence implementation work related to Section A.

Additional Work on Subsequent Procedures  

2024

• 18 Jan: GNSO Council resolves to submit the GGP Applicant Support Guidance Recommendation Final Report  to the ICANN Board for approval.

2023

• 21 Dec: GNSO Council adopts the GGP Applicant Support Guidance Recommendation Final Report .
• 25 Sep: ICANN org publishes the Public Comment Summary Report on the GGP Applicant Support Guidance Recommendation Initial Report.
• 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. 

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. 

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

Internationalized Domain Names Expedited Policy Development Process (IDNs-EPDP)

2024

• 18 Jan: GNSO Council resolves to submit the IDNs EPDP Phase 1 Final Report to the ICANN Board for approval.

2023

• 21 Dec: GNSO Council adopts the IDNs EPDP Phase 1 Final Report containing 69 policy recommendations on topics related to top-level IDN gTLD definition and variant management.
• 6-8 Dec: IDNs EPDP had their F2F workshop in Kuala Lumpur.
• 8 Nov: GNSO Council receives the IDNs EPDP Phase 1 Final Report with a full consensus designation on all 69 recommendations on topics related to top-level IDN gTLD definition and variant management.
• 14 Sep: GNSO Leadership relays GNSO Council Guidance Statement on ".québec” to the EPDP Team.
• 24 Aug: At the GNSO Council meeting, the GNSO Chair led the commentary on this issue which essentially concluded that the issue of .quebec (TLD) not being a variant of “.québec” did not require an immediate resolution and one that did not squarely sit in the remit of the Expedited Policy Development Process on Internationalized Domain Names (EPDP on IDNs). The letter from the ALAC Chair to the GNSO Chair on this issue was referred to also.
• 17 Aug: GNSO Leadership circulated the 22 Jun 2023 letter from ALAC Chair to the GNSO Chair regarding the Latin script LGR and .québec issue
• 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 Jul: GNSO Leadership received a communication from the EPDP Chair regarding 4 public comments related to creating an exceptional process by which the existing registry operator for .quebec could apply “.québec” in a future gTLD round ("the .québec issue") being out of scope of the IDN EPDP and its Charter, and referred the comments to the GNSO Council for consideration and action as determined appropriate.
• 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.

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

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 / Registration Data Request Service (RDRS)

2024

  * 24/25 Jan:  ICANN runs webinars to provide usage data on the RDRS and answer any questions about the service which handles requests for access to nonpublic registration data related to generic top-level domains (gTLDs).

2023

  * 28 Nov: ICANN launches theRegistration Data Request Service (RDRS)

• 21 Sep: Council adopted the EPDP Phase 2 small team's proposed charter for a Registration Data Request Service (RDRS) Standing Committee, which is expected to replace the EPDP Phase 2 small team shortly.
• 8 Sep: Council received the small team's proposed charter for aRegistration Data Request Service (RDRS) Standing Committeeto help inform the next steps on the SSAD policy recommendations.
• 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".
• 15 Mar: GNSO Council instructed the small team to continue working with ICANN org on the implementation of the System as well as “provide the Council with a recommendation on the approach and format through which, following implementation of the system, data should be reviewed and analyzed to help inform subsequent decisions on how to proceed with the SSAD recommendations”.
• 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.
• 13 Sep: ICANN org published a WHOIS Disclosure System (System) Design Paper based on the "proof of concept" approach outlined by the Small Team.
• 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 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

GNSO Council Meeting #2 of 2024 held on 15 Feb 2024

• Agenda
• Matters of Interest
• Meeting Details
• Meeting Record
• Special Summary Report

GNSO Council Meeting #2 of 2024 held on 15 Feb 2024 

Full Agenda  |  Documents  |  MotionsAgenda  |  Documents  |  Motions

• Item 1: Administrative Matters
• Item 2: Opening Remarks / Review of Projects List and Action Item List. 
• Item 3: Consent Agenda
  • Confirm Leadership of Standing Selection Committee (“SSC”)
  • Confirm GNSO-Nominated ICANN Fellowship Program Mentor
• Item 4: COUNCIL VOTE - Registration Data Accuracy
• Item 5: COUNCIL DISCUSSION - Update on SubPro Small Team Progress
• Item 6: COUNCIL DISCUSSION - Next Steps for Consideration of Expired Domain Deletion Policy (“EDDP”) and Expired Registration Recovery Policy (“ERRP”) 
• Item 7: COUNCIL DISCUSSION - ICANN79 Preparation
• Item 8: COUNCIL UPDATE: Draft NCAP Study 2 Report 
• Item 9: ANY OTHER BUSINESS 
  • 9.1 - ccNSO & GAC Liaison updates (every three months)
  • 9.2 - Board letter on Closed Generics
  • 9.3 - Standing Predictability Implementation Review Team (“SPIRT”) Charter Drafting Team Update
  • 9.4 - Status Update on Council Requests
  • 9.5 - Update from Contracted Party House Abuse Subgroup’s Meeting with the Non-Commercial Stakeholder Group
  • 9.6 - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) survey

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

Matters of interest to ALAC/At-Large

• Item 1: Administrative Matters
  • Minutes of the GNSO Council Meeting on 21 December 2023 were posted on 02 January 2024
  • Minutes of the GNSO Council Meeting on 18 January 2023 were posted on 02 February 2024
• Item 3: Consent Agenda
  • Confirm Leadership of Standing Selection Committee (“SSC”)
  • Confirm GNSO-Nominated ICANN Fellowship Program Mentor
• Item 4: COUNCIL VOTE - Registration Data Accuracy
  • Following Council's discussion last month and seeing as (i) completion of the Data Processing Agreement (DPA) is pending. (ii) implementation of the NIS2 directive, and  (iii) publication of the Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study is still pending (targeted for Sep 2024), Council will vote on deferring the consideration of the accuracy scoping work for an additional six months or potentially sooner if there is a passage of a significant event, e.g., completion of the Data Processing Agreement, implementation of the NIS2 directive, or publication of the INFERMAL study .  
• Item 5: COUNCIL DISCUSSION - Update on SubPro Small Team Progress
  • In March 2023, the ICANN Board approved the majority of the recommendations contained in the Final Report on the new gTLD Subsequent PDP, but also placed some recommendations into a pending status. The Council convened a small team that worked collaboratively with the ICANN Board to resolve all pending recommendations. While the majority of the pending recommendations were able to be adopted by the ICANN Board, recommendations across six Topics were not adopted by the ICANN Board.
  • With the primary task of addressing the pending recommendations now complete, the Council has tasked the Small Team Plus with an updated assignment form. The Small Team Plus has committed to a work plan to address the recommendations not adopted by the Board. Following that plan, the Small Team has completed initiation steps (i.e., developed background materials, preliminary Supplemental Recommendation language, and issued a call for volunteers for the Small Team Plus). The Small Team Plus has come to preliminary  Supplemental Recommendation language (i.e., stable text) for most of the six Topics.
  • Council will receive an update on the progress of the Small Team Plus.
• Item 6: COUNCIL DISCUSSION - Next Steps for Consideration of Expired Domain Deletion Policy (“EDDP”) and Expired Registration Recovery Policy (“ERRP”) 
  • Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the EDDP and the ERRP. In November 2020, given concerns about its capacity and no known issues with the policies, the Council agreed to delay the request for the Policy Status Report (PSR) for a period of 24 months. After 24 months had passed, the Council reconsidered whether it was an appropriate time to request a Policy Status Report.
  • In considering a Nov 2022 ICANN org report, Council agreed that both the EDDP and ERRP may benefit from further work, though the timing for the work requires further consideration. In particular, as the Compliance report noted, the language of the policy is ambiguous in parts and has caused confusion for registrants. As the ERRP was implemented in part to ensure that “expiration-related provisions in typical registration agreements are clear and conspicuous enough” and to ensure that “adequate notice exists to alert registrants of upcoming expirations,” the continuing registrant confusion warrants further consideration. Additionally, some of the existing language has become obsolete due to intervening data protection law requirements and will require updates.
  • To that end, Council requested further information from ICANN org on what expiration-related educational materials are currently published and whether additional information can be provided (whether as registrant educational material referenced in Section 4.3 or elsewhere on ICANN’s website). The Council noted receipt of this information would be helpful to the Council in determining if updates to these materials or additional material in other forms could be helpful to combat the ongoing registrant confusion.

  • Council will receive an update from ICANN org on the published materials. 

• Item 7: COUNCIL DISCUSSION - ICANN79 Preparation
  • Pre-ICANN79 GNSO Policy Webinar: 
    • Monday, 26 February 2024 at 21:00 UTC

Note: Mandatory for GNSO Council members

• • During ICANN79, the GNSO Council has the following meetings and events scheduled (times listed in AST):

Saturday, 2 March

• • • 09:00-10:00 - IDNs EPDP Team Working Session 
    • 13:15-14:30 - Transfer Policy Review PDP Working Group Session 1 of 2
    • 15:00-16:00 - Transfer Policy Review PDP Working Group Session 2 of 2
    • Time TBD: GNSO Council dinner

Sunday, 3 March

• • • 09:00-10:00 - GNSO Working Session 1 of 2
    • 10:30-12:00 - GNSO Working Session 2 of 2
    • 13:15-14:30 - GNSO Working Session 3 of 3

Monday, 04 March

• • • 15:00-16:00 Joint ICANN Board and GNSO Council

Tuesday, 05 March

• • • 17:30-18:30 - GNSO Council Informal meeting [closed]

Wednesday, 6 March

• • • 09:00-10:00 - Joint GNSO Council & GAC
    • 10:30-12:00 - SubPro Supplemental Recommendations Community Consultation
    • 13:15-15:15- GNSO Council Meeting

Thursday, 7 March

• • • 09:00-10:00 - GNSO Council SubPro Small Team Plus Meeting
    • 15:00-16:00 - GNSO Council Wrap-Up
  • During its Strategic Planning Session, Council agreed to conduct a triannual detailed review of the Program Management Tool. The action item coming from the SPS provided, “During a session at ICANN79, Council to prepare for a careful review of work captured in the Program Management Tool (PMT) that will conclude or initiate prior to the next AGM, or continue beyond the next AGM. Paul McGrady to coordinate with staff to plan for this inaugural effort.”
  • Council will receive an overview of the current block schedule and plan for its in-person meetings.
• Item 9: ANY OTHER BUSINESS 
  • 9.3 - Standing Predictability Implementation Review Team (“SPIRT”) Charter Drafting Team Update

GNSO Council Meeting #2 of 2024 held on 15 Feb 2024 at 21:00 UTC: http://tinyurl.com/42vy5duf 

13:00 Los Angeles; 16:00 Washington DC; 21:00 London; 22:00 Paris; 00:00 Moscow (Friday); 08:00 Melbourne (Friday)

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

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

Records of 15 Feb 2024 Meeting

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

Special Summary Report of 15 Feb 2024 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 Jan 2024 Matters of Interest and/or from GNSO Council Jan 2024 Meeting Records.

GNSO Council Meeting #1 of 2024 held on 18 Jan 2024

• Agenda
• Matters of Interest
• Meeting Details
• Meeting Record
• Special Summary Report

GNSO Council Meeting #1 of 2024 held on 18 Jan 2024 

Full Agenda  |  Documents  |  Motions

• Item 1: Administrative Matters
• Item 2: Opening Remarks / Review of Projects List and Action Item List. 
• Item 3: Consent Agenda
  • Recommendations Report for GNSO Guidance Process (“GGP”) for Applicant Support
  • Recommendations Report for EPDP on Internationalized Domain Names Phase 1 Final Report
• Item 4: COUNCIL DISCUSSION - SubPro Small Team Update on Non-Adopted Recommendations
• Item 5: COUNCIL DISCUSSION - Communications Small Team Follow-up Conversation
• Item 6: COUNCIL DISCUSSION - Council Engagement with PDP Working Group Chairs 
• Item 7: COUNCIL DISCUSSION - Registration Data Accuracy
• Item 8: ANY OTHER BUSINESS 

  • 8.1 Update on ICANN79 planning and GNSO Draft schedule

  • 8.2 Update from SO/AC Roundtable

  • 8.3 Update on Diacritic Study Request

  • 8.4 Update on PPSAI Implementation (GDS will provide update)

  • 8.5 Expected Standards of Behavior

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

Matters of interest to ALAC/At-Large

• Item 1: Administrative Matters
  • Minutes of the GNSO Council Meeting on 16 November 2023 were posted on 01 December 2023.
  • Minutes of the GNSO Council Meeting on 21 December 2023 were posted on 02 January 2024
• Item 3: Consent Agenda
  • Recommendations Report for GNSO Guidance Process (“GGP”) for Applicant Support
  • Recommendations Report for EPDP on Internationalized Domain Names Phase 1 Final Report
• Item 4: COUNCIL DISCUSSION - SubPro Small Team Update on Non-Adopted Recommendations
  • Since ICANN76 this Council small team has worked collaboratively with the ICANN Board to resolve 38 pending recommendations from the Subsequent Procedures PDP WG. While the majority of these pending recommendations were able to be adopted by the ICANN Board, 10 recommendations across six Topics were not adopted by the ICANN Board.
  • Having addressed most of the pending recommendations, Council then tasked an expanded small team, called the Small Team Plus, with an updated assignment form. The Small Team Plus has committed to a work plan to address the 10 recommendations not adopted by the Board. Following that plan, the Small Team initiated first steps (i.e., developed background materials, preliminary Supplemental Recommendation language, and issued a call for volunteers for the Small Team Plus). The Small Team Plus has begun developing Supplemental Recommendation language, beginning with Recommendation 17.2, Applicant Support, according to the above-mentioned work plan and has continued to make further progress.  
  • Council will receive an update on the Small Team Plus's work.
• Item 7: COUNCIL DISCUSSION - Registration Data Accuracy
  • The Registration Data Accuracy (RDA) Scoping Team was initiated by Council in July 2021 per the formation instructions. The Scoping Team was tasked with considering a number of accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations are to help inform the team’s deliberations and development of recommendations to Council on whether any changes are recommended to improve accuracy levels, and, if so, how and by whom these changes would need to be developed (for example, if changes to existing contractual requirements are recommended, a PDP or contractual negotiations may be necessary to effect a change). 
  • The Scoping Team completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up to Council on 5 September 2022. In its write up, the Scoping Team suggested moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3).
  • ICANN org provided an update to Council during the 20 April meeting. During its meeting on 20 June 2023, Council voted to extend the deferral of the consideration of recommendations #1 and #2, pending resolution of recommendation #3 (pausing the work on proposals that require access to registration data until there is clarity from ICANN org on if/how it anticipates the requesting and processing of registration data to be undertaken in the context of measuring accuracy). 
  • On 19 October 2023, ICANN org provided an update on Registration Data Accuracy efforts, and Council discussed the update during its 16 November 2023 meeting. During that meeting, some Councilors noted that, barring (i) completion of the Data Processing Agreement, (ii) implementation of the NIS2 directive, or (iii) publication of the Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study, it may not be the appropriate time to reconvene the Accuracy Scoping Team. Now that six months have passed since Council’s deferral of the accuracy scoping work, Council will need to consider next steps. 
  • Council will consider whether a further deferral is appropriate or if other next steps are timely e.g., the consideration of the Scoping Team’s recommendations 1 and 2.
• Item 8: ANY OTHER BUSINESS 
  • 8.3 Update on Diacritic Study Request

GNSO Council Meeting #1 of 2024 held on 18 Jan 2024 at 05:00 UTC: http://tinyurl.com/y3a7xhu3 

 21:00 Los Angeles (Wednesday); 00:00 Washington DC; 05:00 London; 06:00 Paris; 08:00 Moscow; 16:00 Melbourne

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

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

Records of 18 Jan 2024 Meeting

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

Special Summary Report of 18 Jan 2024 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 Jan 2024 Matters of Interest and/or from GNSO Council Jan 2024 Meeting Records.

1. Consent Agenda

• Council resolved to approve both the Recommendations Report for the GGP on Applicant Support and the Recommendations Report for the EPDP on Internationalized Domain Names (IDNs) for transmission to the ICANN Board. Correspondence to the Board completed on 18 Jan.

2. SubPro Small Team Update on Non-Adopted Recommendations

• Supplemental Recommendations on (a) confusingly similar singular-plural strings (Recs 23.3 and 23.5) are being refined/finalized; and (b) Waiver of RA Spec 11 3(a) & 3(b) for single registrant TLDs (Rec 9.2) is stable.
• Work of the Small Team Plus continues on (c) covenant not to sue (Recs 18.1 and 18.3) tied with (d) challenge/appeal mechanisms (Recs 32.1, 32.2 and 32.10)
• Work of the Small Team Plus expected to conclude - in terms of Supplemental Recommendations - before ICANN79, in time for the planned community consultation session at ICANN79. Thereafter, depending on any substantial community input received, Council plans to vote on the entire package of Supplementation Recommendations covering 10 non-adopted recommendations (i.e. 17.2, 22.7, 23.3, 23.5, 9.2, 18.1, 18.3, 32.1, 32.2, 32.10)  at its April meeting. (For info on the 10 non-adopted recommendations, see: slide no. 3 of my SubPro Update #5 to CPWG on 8 Nov 2023)

Action by ALAC Liaison

• •  Justine Chew To update ALAC/CPWG on the package of Supplemental Recommendations to be discussed at ICANN79 (on the Wed).
  •  Justine Chew To alert ALAC/CPWG on any GNSO session planned for ICANN79 Prep Week to discuss the GNSO SubPro PDP Supplemental Recommendations

3. Registration Data Accuracy (RDA) & RDA Scoping Team

• By way of recap, the RDA Scoping Team was initiated by Council in July 2021 per the formation instructions, andtasked with considering a number of accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations are to help inform the team’s deliberations and development of recommendations to Council on whether any changes are recommended to improve accuracy levels, and, if so, how and by whom these changes would need to be developed (for example, if changes to existing contractual requirements are recommended, a PDP or contractual negotiations may be necessary to effect a change). 
• The Scoping Team completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up to Council on 5 September 2022. In its write up, the Scoping Team had suggested moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3).
• However, a number of factors which remain pending to-date have led Council to defer further work in this area. 
  • At Council's Jun 2023 meeting, Council voted to defer for 6 months, consideration of a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) pending resolution of recommendation #3 (pausing the work on proposals that require access to registration data until there is clarity from ICANN org on if/how it anticipates the requesting and processing of registration data to be undertaken in the context of measuring accuracy). 
  • At Council's Nov 2023 meeting, Council revisited this area of work and noted that, barring (i) completion of the Data Processing Agreement (DPA), (ii) implementation of the NIS2 directive, or (iii) publication of the Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study, it may not be the appropriate time to reconvene the Accuracy Scoping Team.  
  • Given that (i) the DPA is not yet ready (confirmed by ICANN org staff) (ii) the NIS2 directive has not yet been implemented, and (iii) publication of the Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study is still pending (targeted for Sep 2024), Council declined to take further action at this point.  

4. Diacritic Study Request

• GNSO Council Leadership is still reviewing a draft request prepared by Councilor Mark Datysgeld on the Diacritic Study and will report back to Council in due course.
• As a reminder, this request for a Diacritic Study is concerned with how to deal with existing ASCII TLDs which have a version with diacritics which are NOT considered as variants of each other accordingly to established Label Generation Rules (for eg. quebec and québec).   

Action by ALAC Liaison

• •  Justine Chew To alert ALAC/CPWG when the draft Diacritic Study Request is ready for Council's comment.

5. Privacy-Proxy Services Accreditation Issues (PPSAI) Implementation

• There are Board-approved PPSAI recommendations which have yet to be implemented as focus has been prioritized towards the implementation of the EPDP on Temp Spec Phase 1 recommendations instead thus far. However ICANN Org's GDS (Global Domains & Strategy) is now developing a work plan to actively work on implementing these PPSAI recommendations with input from the previous GNSO PDP on PPSAI members (by email).
• Next update will be available at ICANN79; but the work plan will only be ready at the end of Q1, 2024.