Page History

GNSO Council Meeting #6 of 2024 held on 12 June 2024 

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

GNSO Council Meeting #6 of 2024 held on 12 Jun 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 Aspirational Statement (WITHDRAWN)
• Item 4: COUNCIL VOTE - Request for Policy Status Report - Expiration Policies
• Item 5: COUNCIL DISCUSSION - Accuracy Check-in
• Item 6: COUNCIL DISCUSSION - Standing Predictability Implementation Review Team (“SPIRT”) Draft Charter
• Item 7: COUNCIL DISCUSSION - ICANN org Implementation Update - Second-Level International Governmental Organizations (IGO) Protections
• Item 8: COUNCIL UPDATE - Update on the Internet Governance Forum Support Association (“IGFSA”)
• Item 9: COUNCIL DISCUSSION: Updated Work from Council Strategic Planning Session (“SPS”)
• Item 10: Any Other Business
  • 10.1 - ccNSO Liaison update (tentative)
    • Joint Meeting: ccNSO & GNSO Councils on 11 July 2024
  • 10.2 - PPSAI Call for Volunteers
  • 10.3 - Open Mic

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

Matters of interest to ALAC/At-Large (updated on 14 May)

• Item 1: Administrative Matters
  • Minutes of the GNSO Council Meeting on 18 April 2024 were posted on 03 May 2024.
  • Minutes of the GNSO Council Meeting on 16 May 2024 were posted on 01 June  2024.
• Item 4: COUNCIL VOTE - Request for Policy Status Report - Expiration Policies
  • Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the Expired Domain Name Deletion Policy (“EDDP”) and the Expired Registration Recovery Policy (“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 PSR. 
  • Before voting whether to further defer the request, Council agreed that it would be helpful to consult with both registrars and ICANN org to assist in determining whether there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. 
  • During its 16 May 2024 meeting, Council discussed the option of adding the PSR request to ICANN org’s queue of work instead of deferring the request for two years, noting the PSR analysis should be completed but not as an urgent priority.
  • Council will vote to request ICANN org to deliver a PSR in one (1) year or to confirm that work on the PSR has begun and deliver an updated estimate on when the PSR should be delivered, in one (1) year. (voting threshold: simple majority)
• Item 5: COUNCIL DISCUSSION - Accuracy Check-in
  • 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 before making a recommendation 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). 
  • 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.  Council voted to extend the deferral of the Accuracy Scoping Team’s recommendations by another six months during its meeting on 15 February 2024. During this meeting, Council agreed to check in on the progress of these items during its June 2024 meeting.
  • Council will discuss the status of accuracy discussions and consider ICANN org’s proposed next steps for addressing the charter topics and informing further community discussions, factoring in the legal as well as resource limitations that exist. Specifically, ICANN org suggested (1) providing historical data via ICANN’s existing audit program and (2) engaging with contracted parties on current European ccTLD identity verification practices.
• Item 6: COUNCIL DISCUSSION - Standing Predictability Implementation Review Team (“SPIRT”) Draft Charter
  • Council enlisted a Drafting Team to develop a draft charter for the SPIRT, which is a standing implementation review team recommended in the New gLTD gTLD Subsequent Procedures Final Report. 

  • When relevant issues arise during the course of the New gTLD Program that may need to be addressed, the Standing Predictability Implementation Review Team (“SPIRT”) will utilize the Predictability Framework. The GNSO Council shall be responsible for oversight of the SPIRT.

  • In developing the draft charter, the Drafting Team considered elements such as the composition of the SPIRT, how issues are raised to the SPIRT procedurally, the operating principles and decision-making of the SPIRT, et.al. The New gTLD Subsequent Procedures Final Report included an annex that provides detailed guidance on how the SPIRT should operate. 
  • Council will received an update receive a presentation on the draft charter from its liaison to the Charter Drafting Team.
• Item 8: COUNCIL UPDATE - Update on the Internet Governance Forum Support Association (“IGFSA”)
  • The Internet Governance Forum Support Association is an independent membership association established in September 2014 to support the United Nations Internet Governance Forum (IGF) and to provide financial and other support for National and Regional IGFs (NRIs) around the world. 
  • The IGFSA will provide an overview of its mission and recent work to Council.

GNSO Council Meeting #6 of 2024 held on 12 Jun 2024 at 11:45 UTC: https://tinyurl.com/yeykc7fm 

04:45 Los Angeles; 07:45 Washington DC; 12:45 London; 13:45 Paris; 14:45 Moscow; 21:45 Melbourne

GNSO Council Meeting Remote Participation: refer to ICANN80 Schedule - Zoom link to be shared 24 hours in advance

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

Records of 12 Jun 2024 Meeting

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

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

1. Consent Agenda

• The agenda item (along with a vote) on the GNSO Council Aspirational Statement was withdrawn.

2. 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 before making a recommendation 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). 
• 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.  Council voted to extend the deferral of the Accuracy Scoping Team’s recommendations by another six months during its meeting on 15 February 2024. During this meeting, Council agreed to check in on the progress of these items during its June 2024 meeting.
• Council considered the status of accuracy discussions and the need to better inform the ICANN community, especially the GAC, on the factors around the legal as well as resource limitations that are holding Council from future action. 
• TO BE UPDATED AFTER THE COUNCIL WRAPUP SESSION.

3. Standing Predictability Implementation Review Team (“SPIRT”) Draft Charter 

• The formation of the Standing Predictability Implementation Review Team (SPIRT, pronounced as 'SPIRIT') is the result of Recommendation 2.1 of the New gTLD Subsequent Procedures Final Report, a recommendation that the Board has since adopted.
• The role of the SPIRT is to serve as the body responsible for reviewing potential issues which may arise during the course of the New gTLD Program (Next Round and beyond) application and evaluation processes AFTER the next Applicant Guidebook (AGB) has been approved by the Board, by conducting analysis utilizing the Predictability Framework, and to recommend the process/mechanism that should be followed to address those issues. The Predictability Framework is found in Annex E of the New gTLD Subsequent Procedures Final Report and it provides detailed guidance on how the SPIRT should operate.
• Council received a presentation on the draft charter from its liaison to the Charter Drafting Team which touched on several key aspects being discussed by the Drafting Team working group: composition of the SPIRT, how issues are raised to the SPIRT procedurally, the operating principles and decision-making of the SPIRT, etc, while considering the Predictability Framework.
• Work continues at the Drafting Team working group level.

4. Deferral of Policy Status Report Request - Expiration Policies

• Council had previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the Expired Domain Name Deletion Policy (“EDDP”) and the Expired Registration Recovery Policy (“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, Council reconsidered whether it was an appropriate time to request a PSR.
• In July 2022, Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. 

• In making its decision whether to request to a PSR at this time, Council consulted: 

  1. Registrars, who were asked to flag substantial issues with the policies that would warrant a near-term request for PSR and did not note any issues
  2. ICANN Compliance, who provided a write-up, noting confusion with key terms in the policy and persistent registrant confusion with the auto-renew grace period and aftermarket activities, et al.
  3. ICANN org Registrant Program, which provided a catalog of the available educational resources on domain name expiration and renewal (Brian Gutterman’s update at Council)
• Council then determined that the EDDP and ERRP seem to have been implemented as intended and imminent policy work is not needed at this time, and so, considered to pursue a PSR on the Expiration Policies in two years' time, or earlier, if a need is determined and it is requested.
• Primarily at the request of IPC, this decision for a deferral of the PSR was deferred yet again, to Council's Jun 2024 meeting. IPC's belief that the request for a PSR should proceed now since it would take some time for it to be actioned by ICANN org staff, and IPC had wanted a bit more time to shore up its representation on this issue.
• After much deliberation, Council has now resolved to request ICANN org to deliver a PSR in one (1) year or to confirm that work on the PSR has begun and deliver an updated estimate on when the PSR should be delivered, in one (1) year. 

5. Internet Governance Forum Support Association (“IGFSA”)

• Council received a presentation on the mission and work of the Internet Governance Forum Support Association which is an independent membership association established in September 2014 to support the United Nations Internet Governance Forum (IGF) and to provide financial and other support for National and Regional IGFs (NRIs) around the world. 
• This is an outreach by the IGFSA, asking for Councilors to help create awareness of IGFSA to garner support for its activities and to grow IGFSA's organisational and individual membership.
• Note: The At-Large will receive a similar outreach presentation at the ICANN80 At-Large Leadership Wrap Up Session.

GNSO Council Meeting #5 of 2024 held on 16 May 2024 

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

GNSO Council Meeting #5 of 2024 held on 16 May 2024 (updated on 15 May)

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 Liaison to the Governmental Advisory Committee
  • Council Response to Board Letter on CCWG Auction Proceeds Recommendation 7
• Item 4: COUNCIL VOTE - Request for Preliminary Issue Report for Diacritics in Latin Script
• Item 5: COUNCIL DISCUSSION - Deferral of Policy Status Report Request - Expiration Policies
• Item 6: COUNCIL DISCUSSION - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (“CCOICI”) Pilot Survey Results
• Item 7: COUNCIL DISCUSSION - Intellectual Property Constituency Request for Reconsideration
• Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar
• Item 9: GNSO Council Aspirational Statement 

• Item 10: Any Other Business

  • 10.1 - Update on ICANN80 planning and GNSO Draft schedule

  • 10.2 - ccNSO & GAC Liaison updates (every three months)

  • 10.3 - SPS Action Item Updates: Recommendation Reports and GNSO Liaisons to WGs

  • 10.4 - Call for Volunteers - Privacy and Proxy Services Accreditation Implementation Review Team (PPSAI)

  • 10.5 - Transfer Policy Review Working Group participation (see letter)
  • 10.6 - Pre-ICANN80 GNSO Policy Webinar on Tuesday, 21 May at 21:00 UTC - Note: GNSO Councilor Attendance is mandatory
  • 10.7 - Informal meeting with ICANN Board on Monday, 20 May at 13:00 UTC

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

Matters of interest to ALAC/At-Large (updated on 15 May)

• Item 1: Administrative Matters
  • Minutes of the GNSO Council Meeting on 06 March 2024 were posted on 23 March 2024.
  • Minutes of the GNSO Council Meeting on 18 April 2024 were posted on 03 May 2024.
• Item 4: COUNCIL VOTE - Request for Preliminary Issue Report for Diacritics in Latin Script
  • Council was made aware of a potential issue whereby future applied-for strings in the Latin script containing diacritics may be confusingly similar to ASCII strings, are non-variants, and the same entity wishes to operate both strings.
  • For background, an applied-for IDN gTLD string in the Latin script containing diacritics, which is NOT an allocatable variant label of the base ASCII string (existing or applied-for) according to RZ-LGR, are sometimes seen as equivalents. In some instances however, the base ASCII string is seen as a workaround and not necessarily “correct”. The base ASCII string and the Latin diacritic string may be determined to be confusingly similar (i.e., in which case, the strings would be placed in a contention set or if an existing gTLD is involved, the applied-for label would not pass the String Similarity Review).

  • During the GNSO Council Meeting at ICANN78 in Hamburg on 25 October 2023, Council received a detailed briefing on this issue and agreed to request a study from ICANN org to help inform Council on the issue of diacritics in Latin Script. Prior to the request being made to ICANN org, the org volunteered to investigate what mechanism or mechanisms might be appropriate to address this issue.

  • Following the discussion during its April 2024 meeting, Council discussed requesting a Preliminary Issue Report on diacritics in the Latin Script. On [date], the request for an Issue Report was circulated to the Council mailing list.

  • Council will vote to request ICANN org to deliver a Preliminary Issue Report on diacritics in the Latin Script.
• Item 5: COUNCIL DISCUSSION - Deferral of Policy Status Report Request - Expiration Policies
  • Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the Expired Domain Name Deletion Policy (“EDDP”) and the Expired Registration Recovery Policy (“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 PSR.
  • In July 2022, Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. 

  • In making its decision whether to request to a PSR at this time, Council consulted: 

    1. Registrars, who were asked to flag substantial issues with the policies that would warrant a near-term request for PSR and did not note any issues
    2. ICANN Compliance, who provided a write-up, noting confusion with key terms in the policy and persistent registrant confusion with the auto-renew grace period and aftermarket activities, et al.
    3. ICANN org Registrant Program, which provided a catalog of the available educational resources on domain name expiration and renewal (Brian Gutterman’s update at Council)
  • Council then determined that the EDDP and ERRP seem to have been implemented as intended and imminent policy work is not needed at this time. Accordingly, the GNSO Council will reconsider a PSR on the Expiration Policies in two years time, or earlier, if a need is determined and it is requested.
  • Council will discuss whether to consider a PSR on the Expiration Policies in two years.
• Item 7: COUNCIL DISCUSSION - Intellectual Property Constituency Request for Reconsideration
  • On 22 November 2023, the Intellectual Property Constituency (IPC) filed a Request for Reconsideration  of the ICANN Board Resolutions 2023.10.26.11 and 2023.10.26.122, regarding (i) the actions and inactions that led to:
    • (a) the ICANN Board’s public comment of 6 December 2018 on the Initial Report of the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP),
    • (b) the organization of the public comment phase on the Proposed Final Report of the New gTLD Auction Proceeds Cross Community Working Group,
    • (c) the ICANN Board Resolutions 2022.06.12.13 to 2022.06.12.16 , and (ii) the actions and inactions involving the implementation of the ICANN Grant Giving Program.
  • Council will hear an update on the Request for Consideration and discuss potential next steps for the Council, if any.
• Item 10: Any Other Business
  • 10.4 - Call for Volunteers - Privacy and Proxy Services Accreditation Implementation Review Team (PPSAI)
  • 10.7 - Informal meeting with ICANN Board on Monday, 20 May at 13:00 UTC

GNSO Council Meeting #5 of 2024 held on 16 May 2024 at 05:00 UTC: https://tinyurl.com/4dthynkr  

22:00 Los Angeles (Wednesday); 01:00 Washington DC; 22:00 London; 06:00 Paris; 08:00 Moscow; 15:00 Melbourne 

GNSO Council Meeting Remote Participation: Zoom link

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

Records of 16 May 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 16 May 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 May 2024 Matters of Interest and/or from GNSO Council May 2024 Meeting Records.

1. Consent Agenda

• Council resolved to adopt the revised Description of the role of GNSO Liaison to the Governmental Advisory Committee.
• Council resolved to approved the ICANN Board’s Proposed Amendment to remove the phrase “from the Independent Project Applications Panel” from the Cross-Community Working Group on Auction Proceeds Recommendation 7.

2. Diacritics in Latin Script

• The issue of diacritics in Latin script is not a new one. It first originated, resulting from the 2012 Round, when the registry operator for .Quebec opted to apply for the non-diacritic .quebec label in favour of the label with diacritic “.québec”, but they did not pursue any "formal" remedy to the challenge of also obtaining the “.québec” TLD until more recently, when 4 public comments were submitted in response to the GNSO Call for Public Comments to the Phase 1 Initial Report of the IDNs EPDP in Apr 2023.
• In Jul 2023, GNSO Leadership received a communication from the IDNs-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 IDNs-EPDP and its Charter, and referred the comments to the GNSO Council for consideration and action as determined appropriate.
• On 17 Aug 2023, GNSO Leadership circulated the 22 Jun 2023 letter from ALAC Chair to the GNSO Chair regarding the Latin script LGR and .québec issue.
• On 24 Aug 2023, Council discussed this issue and, the then GNSO Chair 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 IDNs-EPDP.
• On 23 Sep 2023, the then Council Chair again addressed the issue of accents and diacritics in Latin languages that could be deemed confusingly similar to existing strings or other applications, and suggested chartering something with a narrow scope to ensure that this topic does not slide elsewhere into the string similarity discussion and ensure that solutions are found that match requirements imposed on variants.  ICANN org staff clarified that next steps from the staff perspective would be for Council to request an Issues Report.

• On 25 Oct 2023, Council received a detailed briefing on this issue and agreed to request a study from ICANN org to help inform the GNSO Council on the issue of diacritics in Latin Script. Prior to the request being made to ICANN org, the org volunteered to investigate what mechanism or mechanisms might be appropriate to address this issue. Since then, Council had for several months deferred discussing a way forward to address the issue as GNSO support staff had indicated that a proposal for a solution was being worked on which might alleviate the need for a study request which Council had been mooting earlier.

• The issue finally returned to Council's agenda in Apr 2024, where after much discussion, Council concluded that GNSO support staff's suggested way forward was neither feasible nor desirable (see my Apr 2024 report), and as a result, Council reinforced its agreement to request an Issue Report on diacritics in Latin script. Since this could only be actioned through a Council resolution, it was agreed that Council would vote on such a motion in its May 2024 meeting.
• Hence at this meeting, Council resolved to adopt the request for an an Issues Report, and directs staff to create the Report.

3. IPC's Request for Reconsideration (RfR) on the Board's Proposed Bylaws Updates to Limit Access to Accountability Mechanisms

• This is regarding the Board Accountability Mechanisms Committee's (BAMC) dismissal of IPC's RfR on the basis that IPC was not a party harmed by the Board's Proposed Bylaws Updates to Limit Access to Accountability Mechanisms.
• NOTE: While the GNSO Council did not support the Board's proposal but the ALAC did, the issue being contended here, is the principle that an ICANN community group can be found to have no standing (i.e. has been unable to show harm suffered) for something that has yet to be implemented.
• Council discussed possible next steps to counter the BAMC dismissal, noting that the gravity and implications of grounds for this dismissal, including the possibility of involving other members of the ICANN Community in next steps.

4. Deferral of Policy Status Report Request - Expiration Policies

• Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the Expired Domain Name Deletion Policy (“EDDP”) and the Expired Registration Recovery Policy (“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 PSR.
• In July 2022, Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. 

• In making its decision whether to request to a PSR at this time, Council consulted: 

  1. Registrars, who were asked to flag substantial issues with the policies that would warrant a near-term request for PSR and did not note any issues
  2. ICANN Compliance, who provided a write-up, noting confusion with key terms in the policy and persistent registrant confusion with the auto-renew grace period and aftermarket activities, et al.
  3. ICANN org Registrant Program, which provided a catalog of the available educational resources on domain name expiration and renewal (Brian Gutterman’s update at Council)
• Council then determined that the EDDP and ERRP seem to have been implemented as intended and imminent policy work is not needed at this time, and so, considered to pursue a PSR on the Expiration Policies in two years' time, or earlier, if a need is determined and it is requested.
• Primarily at an IPC Councilor's request, this decision for a deferral of the PSR was deferred yet again, to Council's Jun 2024 meeting. IPC's belief that the request for a PSR should proceed now since it would take some time for it to be actioned by ICANN org staff, and IPC wanted a bit more time to shore up its representation on this issue.  There was no objection to deferring the vote to Council's next meeting.