Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Deck of Cards
idUpdates


Card
defaulttrue
idDevelopments
labelSHOW ME

Developments in 2021-2024 on:


Card
idPost_2023_ODA
labelNext Steps for New gTLD Round

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

2024

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

  • 6 Mar: GNSO SubPro Small Team held a community consultation session during ICANN79, on the SubPro Supplemental Recommendations.
  • 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.


Card
idAddSubPro
labelADDITIONAL WORK ON SUBSEQUENT PROCEDURES

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. 


Card
idConsensus_Policy
labelON MODIFYING GTLD CONSENSUS POLICIES

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

2022

2021


Card
idTRP
labelTransfer 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

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
idIDN
labelInternationalized Domain Names EPDP

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.


Card
idRDA_Scoping
labelRegistration 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
idSSAD
labelTemp Spec for Registration Data / SSAD ODP / RDRS

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


...

January 2024 - October 2024 Reports

Anchor
A-24-0304
A-24-0304
24-03 04 GNSO COUNCIL MEETING #3 (AT ICANN 78, MAR 2024) #4 (APR 2024)                        (go up to Directory) 

Deck of Cards
idApr2024


Card
idShow_Apr2024
labelSHOW ME

GNSO Council Meeting #4 of 2024 held on 18 Apr 2024 

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


Card
idAgenda_Apr2024
labelAGENDA

GNSO Council Meeting #4 of 2024 held on 18 Apr 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
    • GNSO Council Review of the GAC Communiqué
    • GNSO Council Small Team Guidance Document
    • Confirmation of Standing Predictability Implementation Review Team (SPIRT) Charter Drafting Team Leadership (Chair - Nitan Walia; Vice-chair - Alan Greenberg; GNSO Council liaison - Anne Aikman-Scalese)
  • Item 4: COUNCIL VOTE - Deferral of Policy Status Report Request - Expiration Policies
  • Item 5: COUNCIL DISCUSSION - Diacritics in Latin Script
  • Item 6: COUNCIL VOTE - SubPro Supplemental Recommendations
  • Item 7: COUNCIL DISCUSSION - New gTLD Auction Proceeds Cross Community Working Group - Auction Proceeds (CCWG-AP) - Proposed Update to Recommendation 7
  • Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar
  • Item 9: Update on Status of Privacy and Proxy Services Accreditation Implementation
  • Item 10: ANY OTHER BUSINESS
    • 10.1 - Update on ICANN80 planning and GNSO Draft schedule

    • 10.2 - Replacement of Council representative to the Continuous Improvement Program Community Coordination Group (CIP-CCG)

    • 10.3 - Upcoming Sessions/Updates on the Registration Data Request System (RDRS) 

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


Card
idMOI_Apr2024
labelMATTERS OF INTEREST

Matters of interest to ALAC/At-Large

  • Item 1: Administrative Matters
    • Minutes of the GNSO Council Meeting on 15 February 2024 were posted on  02 March 2024
    • Minutes of the GNSO Council Meeting on 06 March 2024 were posted on 23 March 2024
  • Item 4: COUNCIL DISCUSSION - Reaction to Program Management Tools Discussion
    • During Council’s recent Strategic Planning Session (SPS), Council Leadership and GNSO Support Staff provided an overview of the available program management tools to educate new councilors on what tools are available and how to best utilize them. Council agreed to do a comprehensive and detailed review of the program management tools on a tri-annual basis. The Council agreed the tri-annual cadence aligned with the current ICANN conference schedule, and the first of these reviews was conducted during the Council’s Working Session at ICANN79.
    • Having performed a comprehensive review of the program management suite of tools during its working session, Council will now discuss lessons learned and potential suggestions for the next review at the ICANN80 working session.
  • Item 5: COUNCIL DISCUSSION - Council Engagement with PDP Working Group Chairs
    • During the Council’s 2023 Strategic Planning Session, the Council agreed that updates from PDP Working Group Chairs and Council liaisons should be more purpose-driven. 
    • In discussing this, GNSO Support Staff provided background information on the GNSO Policy Webinar. Specifically, the webinars began in 2018 and were designed to provide the Council with an opportunity to directly engage with PDP chairs regarding the progress of their working groups. This engagement previously took place at ICANN meetings during GNSO working sessions; however, when the ICANN meeting schedule was shortened, these interactions were moved to a webinar format in an effort to allow the engagement to continue.
    • After receiving this background information, some Councilors noted that if the purpose is for the Council to hear frank updates from Working Group Chairs, the webinar should be for Councilors rather than a larger community update. Additionally, Councilors reviewed the list of questions provided to Working Group Chairs in an effort to better understand Working Group progress and potential challenges (if any). 
    • Councilors attended the webinar, in its updated form, prior to ICANN79, and Council will discuss if the updates to the webinar format helped make the interactions more purpose driven or if further updates may be needed.
  • Item 6: COUNCIL DISCUSSION - Update on Contracted Party House Abuse Subgroup Meetings with the Non-Commercial Stakeholder Group
    • In February 2022, Council formed a small team of interested Council members to consider what policy efforts, if any, Council should consider undertaking to support the efforts already underway in the different parts of the community to tackle DNS abuse. 
    • The DNS Abuse Small Team preliminarily concluded that there is not enough information available to warrant further policy work at this time. Following the update from the DNS Abuse Small Team, Council representatives from the Registrar Stakeholder Group commented on the productive dialogue between Contracted Parties and the ICANN Community with respect to DNS Abuse and committed to continuing the dialogue with interested groups.
    • To that end, on 23 January 2024, the Registrar Stakeholder Group and the Registries Stakeholder Group DNS Abuse Subgroups met with the Non-Commercial Stakeholder group as the first in a planned series of outreach sessions to the ICANN Community regarding pain points with respect to DNS Abuse. The discussion touched on potential recommendations for solutions and potential future work.
    • Council will receive an update on this meeting and subsequent discussions with other groups.
  • Item 7: COUNCIL DISCUSSION - Response to Update from ICANN org Implementation Update and interaction with ICANN Board
    • During Council’s Working Session, ICANN org provided an overview of the implementation status of the projects that are currently in implementation. These include:

      • Privacy and Proxy Services Accreditation Implementation (PPSAI)

      • Preventative and Curative Rights Protections for Intergovernmental Organizations (IGOs)/International Non-Governmental Organizations (INGOs)

      • New gTLD Subsequent Procedures PDP

    • In addition, during Prep Week, the ICANN Board held a community engagement session where a question was posed that is relevant to the GNSO Council: how do we handle situations where it becomes clear that community-developed gTLD policies adopted by the Board are superseded by subsequent events or are otherwise not able to, or can no longer, resolve the problems they were designed to address
    • Council will have an opportunity to discuss the update from ICANN org and ICANN Board engagement session to determine next steps, if any.
  • Item 9: ANY OTHER BUSINESS
    • 9.1 - GNSO Chair Election Timeline Announcement
    • 9.2 - Updated Small Team Guidelines
    • 9.3 - Standing Predictability Implementation Review Team (“SPIRT”) Charter Drafting Team Update


Card
idMeetDeets_Apr2024
labelMEETING DETAILS

GNSO Council Meeting #4 of 2024 held on 18 Apr 2024 at 21:00 UTC: https://tinyurl.com/2xcnuymd 

14:00 Los Angeles; 17:00 Washington DC; 22:00 London; 23:00 Paris; 00:00 Moscow (Friday); 07:00 Melbourne (Friday)

GNSO Council Meeting Remote Participation: Zoom link

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


Card
idMeet_Apr2024
labelMEETING RECORD

Records of 18 Apr 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


Card
idSumRep_Apr2024
labelREPORT

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

1. Consent Agenda

  • Council resolved to adopt the Communications Small Team Final Report.




Anchor
A-24-03
A-24-03
24-03 GNSO COUNCIL MEETING #3 (AT ICANN 78, MAR 2024)                           (go up to Directory) 

Deck of Cards
idMar2024


Card
idShow_Mar2024
labelSHOW ME

GNSO Council Meeting #3 of 2024 held on 6 Mar 2024 during ICANN 79, and including a Council Wrap-up Session on 7 Mar 2024


Card
idAgenda_Mar2024
labelAGENDA

GNSO Council Meeting #3 of 2024 held on 6 Mar 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
  • Item 4: COUNCIL DISCUSSION - Reaction to Program Management Tools Discussion
  • Item 5: COUNCIL DISCUSSION - Council Engagement with PDP Working Group Chairs
  • Item 6: COUNCIL DISCUSSION - Update on Contracted Party House Abuse Subgroup Meetings with the Non-Commercial Stakeholder Group
  • Item 7: COUNCIL DISCUSSION - Response to Update from ICANN org Implementation Update and interaction with ICANN Board 
  • Item 8: Selection and Timeline of Next GNSO Liaison to the Governmental Advisory Committee
  • Item 9: ANY OTHER BUSINESS
    • 9.1 - GNSO Chair Election Timeline Announcement
    • 9.2 - Updated Small Team Guidelines
    • 9.3 - Standing Predictability Implementation Review Team (“SPIRT”) Charter Drafting Team Update
    • 9.4 - Open Mic

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


Card
idMOI_Mar2024
labelMATTERS OF INTEREST

Matters of interest to ALAC/At-Large

  • Item 1: Administrative Matters
    • Minutes of the GNSO Council Meeting on 18 January 2023 were posted on 02 February 2024
    • Minutes of the GNSO Council Meeting on 15 February 2024 were posted on  02 March 2024
  • Item 4: COUNCIL DISCUSSION - Reaction to Program Management Tools Discussion
    • During Council’s recent Strategic Planning Session (SPS), Council Leadership and GNSO Support Staff provided an overview of the available program management tools to educate new councilors on what tools are available and how to best utilize them. Council agreed to do a comprehensive and detailed review of the program management tools on a tri-annual basis. The Council agreed the tri-annual cadence aligned with the current ICANN conference schedule, and the first of these reviews was conducted during the Council’s Working Session at ICANN79.
    • Having performed a comprehensive review of the program management suite of tools during its working session, Council will now discuss lessons learned and potential suggestions for the next review at the ICANN80 working session.
  • Item 5: COUNCIL DISCUSSION - Council Engagement with PDP Working Group Chairs
    • During the Council’s 2023 Strategic Planning Session, the Council agreed that updates from PDP Working Group Chairs and Council liaisons should be more purpose-driven. 
    • In discussing this, GNSO Support Staff provided background information on the GNSO Policy Webinar. Specifically, the webinars began in 2018 and were designed to provide the Council with an opportunity to directly engage with PDP chairs regarding the progress of their working groups. This engagement previously took place at ICANN meetings during GNSO working sessions; however, when the ICANN meeting schedule was shortened, these interactions were moved to a webinar format in an effort to allow the engagement to continue.
    • After receiving this background information, some Councilors noted that if the purpose is for the Council to hear frank updates from Working Group Chairs, the webinar should be for Councilors rather than a larger community update. Additionally, Councilors reviewed the list of questions provided to Working Group Chairs in an effort to better understand Working Group progress and potential challenges (if any). 
    • Councilors attended the webinar, in its updated form, prior to ICANN79, and Council will discuss if the updates to the webinar format helped make the interactions more purpose driven or if further updates may be needed.
  • Item 6: COUNCIL DISCUSSION - Update on Contracted Party House Abuse Subgroup Meetings with the Non-Commercial Stakeholder Group
    • In February 2022, Council formed a small team of interested Council members to consider what policy efforts, if any, Council should consider undertaking to support the efforts already underway in the different parts of the community to tackle DNS abuse. 
    • The DNS Abuse Small Team preliminarily concluded that there is not enough information available to warrant further policy work at this time. Following the update from the DNS Abuse Small Team, Council representatives from the Registrar Stakeholder Group commented on the productive dialogue between Contracted Parties and the ICANN Community with respect to DNS Abuse and committed to continuing the dialogue with interested groups.
    • To that end, on 23 January 2024, the Registrar Stakeholder Group and the Registries Stakeholder Group DNS Abuse Subgroups met with the Non-Commercial Stakeholder group as the first in a planned series of outreach sessions to the ICANN Community regarding pain points with respect to DNS Abuse. The discussion touched on potential recommendations for solutions and potential future work.
    • Council will receive an update on this meeting and subsequent discussions with other groups.
  • Item 7: COUNCIL DISCUSSION - Response to Update from ICANN org Implementation Update and interaction with ICANN Board
    • During Council’s Working Session, ICANN org provided an overview of the implementation status of the projects that are currently in implementation. These include:

      • Privacy and Proxy Services Accreditation Implementation (PPSAI)

      • Preventative and Curative Rights Protections for Intergovernmental Organizations (IGOs)/International Non-Governmental Organizations (INGOs)

      • New gTLD Subsequent Procedures PDP

    • In addition, during Prep Week, the ICANN Board held a community engagement session where a question was posed that is relevant to the GNSO Council: how do we handle situations where it becomes clear that community-developed gTLD policies adopted by the Board are superseded by subsequent events or are otherwise not able to, or can no longer, resolve the problems they were designed to address
    • Council will have an opportunity to discuss the update from ICANN org and ICANN Board engagement session to determine next steps, if any.
  • Item 9: ANY OTHER BUSINESS
    • 9.1 - GNSO Chair Election Timeline Announcement
    • 9.2 - Updated Small Team Guidelines
    • 9.3 - Standing Predictability Implementation Review Team (“SPIRT”) Charter Drafting Team Update


Card
idMeetDeets_Mar2024
labelMEETING DETAILS

GNSO Council Meeting #3 of 2024 held on 6 Mar 2024 at 17:15 UTC http://tinyurl.com/yc8h56uu  

09:15 Los Angeles; 12:15 Washington DC; 17:15 London; 18:15 Paris; 20:15 Moscow; 04:15 Melbourne (Thursday)

Please check the ICANN79 Schedule for both in-person and remote participation details.

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


Card
idMeet_Mar2024
labelMEETING RECORD

Records of 6 Mar 2024 Meeting


Card
idSumRep_Mar2024
labelREPORT

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

1. Consent Agenda

2. DNS Abuse

  • GNSO - GAC Bilateral agenda, where GNSO was asked on the status of the GNSO Council Small Team on DNS Abuse. We were able to clarify that the Small Team is not wound up but merely kept in abeyance until such time that Council had access to useful data which could inform a decision on whether gaps exists and how might those gaps be addressed. 

Action by ALAC Liaison

    •  Justine Chew to liaise with CPH on a DNS Abuse mitigation outreach opportunity with At-Large.

3. Next Round of New gTLD

  • Council was informed that the Council Small Team Plus on Pending Subsequent Pending (SubPro) Recommendations (Small Team Plus) had conducted its Community Consultation during ICANN79 as planned, to socialize the Small Team Plus's work on the supplemental recommendations to address the rationale provided by the ICANN Board in declining to approve/adopt 10 (original) SubPro PDP recommendations covering 6 topics. 
  • No comment or objection was received by the Small Team Plus during that ICANN79 session, so, the Small Team Plus is now able to refer the supplemental recommendations to the Council for approval in Council's April 2024 meeting. 

4. Privacy and Proxy Services Accreditation Implementation (PPSAI)

  • Council acknowledged that the Implementation Review Team tasked with implementation of PPSAI recommendations that were adopted by the ICANN Board back in 2016, has been reactivated. 
  • Question was asked if any or all of those recommendations are still fit for purpose given the introduction of GDPR and other newer developments since 2016, and whether this IRT might be compelled to try and implement outdated recommendations.
  • The conclusion reached was that the IRT should be given the opportunity to review those recommendations and state if any one which are no longer fit for purpose, so that the right party (eg GNSO Council to take remedial steps to perhaps re-conduct a policy development process to update those recommendations).
  • This is an example of the need for Topic 2 in the recent Board Consultation during ICANN79 Prep Week with the Community.

5. General Operations of GNSO/GNSO Council

Council discussed and/or noted following:


...