Page History

GNSO Council Meeting #7 of 2022 held on 21 Jul 2022 

• Agenda
• Matters of Interest
• Meeting Records
• Special Summary Report

GNSO Council Meeting #7 of 2022 held on 21 Jul 2022

Full Agenda  |  Motions 

• Item 1: Administrative Matters
• Item 2: Opening Remarks / Review of Projects & Action List
• Item 3: Consent Agenda
• Item 4: COUNCIL VOTE - Initiation of the GNSO Guidance Process on Applicant Support
• Item 5: COUNCIL DISCUSSION - Policy Status Report for the Expired Domain Deletion Policy and the Expired Registration Recovery Policy - Next Steps
• Item 6: COUNCIL DISCUSSION - PDP Improvements Tracker - Review of Format 
• Item 7: COUNCIL DISCUSSION - Council Commitments Document 
• Item 8: ANY OTHER BUSINESS

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

Matters of interest to ALAC/At-Large

• Item 1: Administrative Matters

  • Minutes of the GNSO Council meeting on 19 May 2022 were posted on 03 June 2022.

  • Minutes of the GNSO Council meeting on 15 June 2022 were posted on 01 July 2022

• Item 3: Consent Agenda 
  • Confirmation of the Recommendations Report to the ICANN Board regarding adoption of recommendations 1-5 contained in the Final Report from the EPDP on Specific Curative Rights Protections for IGOs. 
    
    • The resolved portion of the motion to be voted on reads, "The GNSO Council approves the Recommendations Report and instructs the GNSO Secretariat to transmit the report to the ICANN Board and communicate the outcomes from the GNSO Council’s decisions as appropriate."
• Item 4: COUNCIL VOTE - Initiation of the GNSO Guidance Process on Applicant Support
  • In the course of Council's consideration of the ICANN Org SubPro ODP Team's work in February 2022 - and although specifically about the topic of Applicant Support at that point - broader procedural concerns arose about whether the level of substantive work receommended by SubPro to be conducted by an IRT, would be beyond the commonly understood scope of the IRT.
  • Council agreed to explore finding avenues to complete that level of substantive work in advance of the expected IRT that would be convened upon ICANN Board adoption of the SubPro Outputs. The potential model to address this work is the GNSO Guidance Process. ICANN org staff worked with Jeff Neuman and Council leadership to prepare a draft GGP Initiation request, which was shared on Council list on 4 May 2022.
  • The potential GGP was discussed further during the Council’s June meeting, with general agreement it should be limited to the singular topic of Applicant Support. There was however discussion that additional topics should be able to be added to the existing GGP, at the discretion of the Council.
  • The updated GGP, with Applicant Support as the only topic, was shared with the Council on 13 July 2022.
  • Council to discuss and vote on the initiation of the GNSO Guidance Process on Applicant Support, which to be carried requires a Voting threshold of an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House)

• • • The resolved portion of the motion to be voted on reads, 

1. The GNSO Council approves the GNSO Guidance Process Initiation Request and initiates the GGP.
2. The GNSO Council directs staff to:

a. communicate the results of this motion to the GNSO SG/Cs as well as ICANN SO/ACs and invite them to identify Members for the Steering Group following the Steering Group composition described in the initiation request;
b. communicate the results of this motion to the ICANN Org GDS Team and invite them to identify at least one (1) staff liaison for the Steering Group; and
c. launch a call for expressions of interest seeking interested candidates to Chair the Steering Group.

Action by ALAC Liaison

• •  To monitor initiation of the request for the GNSO Guidance Process (GGP), and to ensure role for ALAC/At-Large in resulting process.

    See TAB under 'POST GNSO COUNCIL MEETING DEVELOPMENTS' section for easier tracking. 

• Item 5: COUNCIL DISCUSSION - Policy Status Report for the Expired Domain Deletion Policy and the Expired Registration Recovery Policy - Next Steps
  • During the Council’s meeting in November 2020, it voted to approve a deferral for the request of a Policy Status Report (PSR) for the Expired Domain Deletion Policy (EDDP) and the Expired Registration Recovery Policy (ERRP). The EDDP defines a uniform delete practice that registrars must follow at the time of domain name expiry, as well as specific requirements for registrar handling of expired names that are subject to a UDRP dispute. The ERRP sets minimum renewal notification requirements for registrars before and after domain names expire, as well as certain requirements for renewal and restoration of expired domain names. In taking this action, the Council was careful to note that it recognized the importance of the PSR for these two expiration related Consensus Policies, but did not see the PSR as urgent at that time. After approximately 1.5 years, the potential PSR has again risen to the 0-1 month range of the Action Decision Radar.
  • Council must consider again whether a PSR is necessary and if it is timely to request a PSR from ICANN org’s Global Domains and Strategy (GDS) function. Council could consider interim steps prior to determining whether a full PSR is needed, such as reviewing ICANN Compliance data and/or requesting an update on expiration related complaints from ICANN Compliance, to help determine if there are known issues with either of the two policies.
  • Council to discuss appropriate next steps for the potential PSR for the EDDP and ERRP.

Action by ALAC Liaison

• •  To review for direct relevant to end-user (registrants), and to inform if need arises for a role for ALAC/At-Large in any resulting process. 
    
    
• Item 6: COUNCIL DISCUSSION - PDP Improvements Tracker - Review of Format
  • During the ICANN73 wrap up, the Council discussed a number of parallel conversations that have emerged since implementing PDP 3.0, identifying other aspects of the PDP where improvements could be considered. Council discussed the discussion paper and agreed that to better understand the concept, it would be helpful to have an example of what the tracker may look like. A draft of the PDP Improvements Tracker was prepared and discussed during the Council’s June meeting. While substantive review of the items in the tracker will take place in the near future, this agenda item is to help ensure that the format of the tracker meets the needs of the Council; a series of six questions are included in the PDP Improvements Tracker for consideration by the Council, to help make that determination.
  • Council will continue its review of the proposed format of the GNSO PDP Improvements tracker

Action by ALAC Liaison

• •  To review for direct relevant to At-Large, and to inform if need arises for a role for ALAC/At-Large in any resulting process. Answer: No. 

• Item 8: ANY OTHER BUSINESS
  • 8.1 – Last call for input on the Council’s response to SubPro Question Set #4

Action by ALAC Liaison

• •  Participated in the Council Small Team on SubPro Questions Set #4

See TAB under 'POST GNSO COUNCIL MEETING DEVELOPMENTS' section for easier tracking.

• • 8.2 – ICANN75 Planning

Action by ALAC Liaison

• •  To establish if there is a need for an ALAC-GNSO Bilateral Meeting at ICANN75 

Records of 21 Jul 2022 Meeting

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

Special Summary Report of 21 Jul 2022 Meeting to ALT-PLUS

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

1. GNSO Guidance Process (GGP) on Applicant Support 

• Council discussed the draft GGP Initiation Request to establish a GGP to start with Applicant Support using a Steering Committee (of a representative+observer model) with ultimate oversight by Council, given that it received a proposed amendment to the said GPP from Kurt Pritz (RySG), primarily regarding the composition of the Steering Committee.
• Discussion revealed some support for a smaller Steering Committee (or Small Team) which does not require strict representation from GNSO SGs/Cs but may also invite participation from beyond GNSO (ALAC and GAC who have significant interest in the topic) and still call upon any required expertise referred to in the SubPro Outputs. 
• Council deferred voting on the submitted motion to its Aug meeting to allow opportunity to rework the GPP Initiation Request to take into account points from the discussion.

2. Policy Status Report for the Expired Domain Deletion Policy and the Expired Registration Recovery Policy 

• Council agree to pursue a light approach to a request for the Policy Status Report (PSR) for the Expired Domain Deletion Policy (EDDP) and the Expired Registration Recovery Policy (ERRP), by first requesting for ICANN Compliance data and/or requesting an update on expiration related complaints from ICANN Compliance, and feedback from the RrSG on the EDDP and ERRP, to help determine if there are known issues with either of the two policies.
• These 2 policies affect registrants, so, further understanding is needed on whether At-Large's involvement is needed and if so, in what form.

3. SubPro ODP

• Council received the ICANN org SubPro ODP Team's question set #5