Developments in 2021-2023 on:

• Additional Work on Subsequent Procedures (including re: Applicant Support; Closed Generics)
• Subsequent Procedures Operational Design Phase (SubPro OD) & Subsequent Procedures Operational Design Assessment (SubPro ODA)
• Potential Council next steps regarding DNS abuse
• 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)

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

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. 

RE: Closed Generics, specifically

2023

• 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).

Subsequent Procedures Operational Design Phase (SubPro ODP) and Subsequent Procedures Operational Design Assessment (SubPro ODA);  See: https://www.icann.org/subpro-odp for more official info.

2023 - Post ODA

• 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.

   *12 Mar: Subsequent Procedures: Issues and Next Steps at ICANN76

   *1 Mar: SubPro ODP Status Update at ICANN76 Prep Week

2023 - ODA

• 28 Feb: ICANN Board Chair replies to GNSO Chair's letter of 20 Jan on GNSO Council review and input for the SubPro ODA
• 28 Feb: ICANN Board and GNSO Joint Meeting on SubPro discussion.
• 16 Feb: GNSO Council to prepare for a joint meeting with the Board. 
• 20 Jan: GNSO Chair letter on the SubPro ODA input sent to ICANN Board Chair
• 19 Jan: Council Small Team on SubPro ODA prepares input concentrating on identifying areas of ICANN org analysis that may not be true to the intent of the SubPro Final Report, as well as developing impressions of Option 2 contained in the ODA. Given the tight timelines, there will not be adequate time for the small team to provide draft input to Council by it January meeting. Accordingly, the expectation is that the input, delivered on [date], shall be sent to the Board, but include the caveat that it was not formally adopted by Council.

2022

• 15 Dec: Council constitutes a Small Team comprising Anne Aikman-Scalese (NCA), Jeff Neuman (GNSO Liaison to SubPro ODP), Thomas Rickert (ISCP), Sebastien Ducos (RySG), Susan Payne (IPC) and Justine Chew (ALAC Liaison to GNSO) to establish if there were questions or clarifications needed to be relayed to the ICANN Org SubPro Team; and likely comments to be relayed to the ICANN Board.

   *14 Dec: ICANN org (SubPro ODP Team) to host a community webinar on the SubPro ODA on Wed 14 Dec 2022 at 13:00–15:00 and 20:00–22:00 UTC

   *12 Dec: SubPro ODP Team delivers SubPro ODA to ICANN Board

• 8 Dec: SubPro ODP Team blogs on Work Track 9: Overarching Considerations 
• 7 Dec: SubPro ODP Team to conduct a SubPro ODA GNSO Council Specific Webinar (prior to release of the ODA)
• 7 Dec: SubPro ODP Team blogs on Work Track 8: Finance 
• 2 Dec: SubPro ODP Team blogs on Work Track 7: Resource Staffing, Logistics 
• 12 Nov: GNSO SubPro ODP Liaison update - Relay of Question set #6

   *8 Nov: SubPro ODP Team releases Assumptions Subsequent Procedures ODP v.6

• 2 Nov: SubPro ODP Team blogs on Work Track 6: Communications and Outreach

   *14 Oct: SubPro ODP Team releasesSubPro ODP Community Status Update #4 (last of four planned updates). The output of this ODP (i.e. the ODA - Operational Design Assessment)  is now expected to be completed on 9 Nov and delivered to the ICANN Board on 12 Dec.

• 6 Sep: SubPro ODP Team blogs on Work Track 5: Vendor Procurement

   *15 Aug: SubPro ODP Team releases SubPro ODP Community Status Update #3 (the 3rd of four planned updates) which refers to Assumptions Subsequent Procedures ODP v.5. The last update is scheduled for 15 Oct.

• 25 Aug: GNSO SubPro ODP Liaison submits Question set #5 REPLY
• 2 Aug: GNSO SubPro ODP Liaison update - Reminder on Question set #5
• 29 Jul: GNSO SubPro ODP Liaison submits Question set #4 REPLY
• 20 Jul: GNSO SubPro ODP Liaison update - Question set #4 finalization and Relay of Question set #5
  • Question set #5 sought clarity on the Predictability  Framework
• 12 Jul: SubPro ODP Team blogs on Work Track 4: Systems & Tools
• 8 Jul: GNSO SubPro ODP Liaison submits Question set #3 REPLY
• 30 Jun - 15 Jul: Council Small Team comprising Jeff Neuman (GNSO Liaison to SubPro ODP), Paul McGrady (NCA-Non CPH), Justine Chew (ALAC Liaison to GNSO), Desiree Miloshevic (NCA-CPH), and Flip Petillion (IPC) worked on replies to Question set #4.
• 30 Jun: Question set #3 REPLY finalized
• 26 May: SubPro ODP Team blogs on Work Track 3: Operational Readiness
• 26 May: GNSO SubPro ODP Liaison submits Question set #2 REPLY

   *25 May: SubPro ODP Team releases Assumptions Subsequent Procedures ODP v.4

• 19 May: GNSO SubPro ODP Liaison update - Relay of Question set #4 and SubPro Topic Assumptions
  • Question set #4 sought clarity on 10 topics

   *16 May: SubPro ODP Team releases SubPro ODP Community Status Update #2, the 2nd of four planned updates. The next update is scheduled for 15 Aug.

• 12 Apr: GNSO SubPro ODP Liaison update - Relay of Question set #3
  • Question set #3 sought clarity on String Similarity

   *29 Apr: SubPro ODP Team releases Assumptions Subsequent Procedures ODP v.3  

   *28 Mar: SubPro ODP Team releases SubPro ODP Community Status Update #1, the 1st of four planned updates. The next update is scheduled for 16 May.

   *23 Mar: SubPro ODP Team releases Initial & Overarching Assumptions Subsequent Procedures ODP v.2

   *28 Feb: SubPro ODP Team releases Initial Assumption Subsequent Procedures ODP v.1

• 14 Feb: GNSO SubPro ODP Liaison update - Relay of Question set #2
  • Question set #2 sought clarity on the Dedicated IRT for Application Support Program
• 25 Jan: GNSO SubPro ODP Liaison update #5 - Third call with ICANN's SubPro ODP Team
• 21 Jan: GNSO SubPro ODP Liaison submits Question set #1 REPLY
• 18 Jan: SubPro ODP Team blogs on SubPro ODP Work Tracks 
• 9 Jan: GNSO SubPro ODP Liaison update #4 - Second call with ICANN's SubPro ODP Team
• 3 Jan: Actual SubPro ODP Launch date

2021

• 20 Dec:  ICANN org announces that ICANN GDS has informed ICANN Board that it is beginning this ODP in January 2022.
• 16 Dec:  Council mainly considered the process for SubPro ODP interactions between the GNSO ODP Liaison and the ICANN Org's SubPro ODP Team - Councillors are meant to take suggested responses of the GSNO ODP Liaison to SubPro ODP Team's preliminary questions (Question Set #1) back to their respective SG/C for feedback to enable finalization and timeous relay of agreed responses to the SubPro ODP Team. ICANN Org has a public archive of engagement on the topic. 
• 1 Dec: SubPro ODP Team blogs on answers to questions regarding the SubPro ODP
• 1 Dec: GNSO SubPro ODP Liaison update #3 - First call with GDS (ICANN's SubPro ODP Team)
• 22 Nov: GNSO SubPro ODP Liaison update #2. ICANN Org is still in internal project organization mode although GDD has posed a first set of questions to the GNSO ODP Liaison, Jeff Neuman. Formal kick-off of the ODP only expected at end of Nov 2021, thereafter proceeds for an approximate 10 months.
• 18 Nov: GNSO SubPro ODP Liaison update - Relay of Question set #1
  • Question set #1 sought clarity on (i) Applications Assessed in Rounds, (ii) RVCs & PICs, specifically on DNS Abuse Mitigation (iii) Applicant Reviews, and (iv) Auctions.
• 16 Nov: GNSO SubPro ODP Liaison update #1

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

2023

   * TBD: Justine's update to CPWG on Small Team deliberations on 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. 

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 EPDP

2023

• 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

• 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

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 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