Versions Compared

Key

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

...

Deck of Cards
idOct2023


Card
idShow_Oct2023
labelSHOW ME

GNSO Council Meeting #10 of 2023 held on 25 and 26 Oct 2023 during ICANN78


Card
idAgenda_Oct2023
labelAGENDA

GNSO Council Meeting #10 of 2023 held on 25 Oct 2023 during ICANN 78, over 2 parts, and including a Council Wrap-up Session on 26 Oct 2023:

Under Part 1 Agenda

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 VOTE - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements 
  • Item 5: COUNCIL DISCUSSION - Optional Topics for Potential Council Response
    • (i) Pilot Holistic Review Revised Draft Terms of Reference 
    • (ii) Proposed Process for the Retirement of Non-Policy Recommendations 
    • (iii) Continuous Improvement Program Community Coordination Group (CIP-CCG)
  • Item 6: COUNCIL DISCUSSION - GNSO Liaison to the Governmental Advisory Committee (GAC) Annual Report
  • Item 7: COUNCIL DISCUSSION - Diacritics Issue in Latin Script
  • Item 8: ANY OTHER BUSINESS
    • 8.1 – Farewell to outgoing Councilors

    • 8.2 – Update - Open Contracted Party House DNS Abuse Calls

    • 8.3 – GNSO Framework for Continuous Improvement Pilot Review

    • 8.4 – Open microphone (Continuation of anniversary session discussion / input)

Under Part 2 Agenda

Full Agenda

  • Item 1: Seating of the 20222023-2023 2024 Council
    INCOMING COUNCILORS:
    • Jennifer ChungSOI Registries Stakeholder Group (RySG)
    • Lawrence Olawale-RobertsSOI Commercial Stakeholder Group (CSG - BC)
    • Damon AshcroftSOI Commercial Stakeholder Group (CSG - IPC)
    • Taiwo Peter AkinremiSOI Non-commercial Stakeholder Group (NCSG)
  • Item 2. Election of the Chair
    • One nomination was received for this position from Gregory DiBiase of the Contracted Party House. Gregory circulated his candidate statement to the GNSO Council on 5 October 2023.
  • Item 3. Election of GNSO Council Vice Chair 2022-2023
    • Non-Contracted Party House - Tomslin Samme- TBDNlar

    • Contracted Party House - TBD

  • Item 4. ANY OTHER BUSINESS
    • TBD
    • Nacho Amadoz

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


Records of 25 and 26 Oct 2023 Meetings at ICANN78

Card
idMOI_Oct2023
labelMATTERS OF INTEREST

Matters of interest to ALAC/At-Large

  • Item 1: Administrative Matters
    • Minutes of the GNSO Council meeting on 24 August 2023 were posted on 09 September 2023.

    • Minutes of the GNSO Council Meeting on 21 September 2023 were posted on 08 October 2023.

  • Item 3: Consent Agenda
    • Confirmation of Appointment of Ashley Heineman as GNSO-appointed Co-Chair of the IANA Naming Function Review Team
  • Item 4: COUNCIL VOTE - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements 
    • The GNSO Framework for Continuous Improvement Pilot was initiated in June 2021 to determine whether the framework, as outlined here, could serve as an approach for dealing with the various projects that are focused on improvements to GNSO processes and procedures.

    • The CCOICI tasked the GNSO Statement of Interest (SOI) Task Force to address the following questions:

      1. Is the original objective of the SOI, as stated in the BGC WG Report, still valid? If not, why not and what should the current objective be?
      2. Based on the response to question 1), is the requested information to be provided as part of the SOI still fit for purpose? If not, why not, and what would need to be changed to make it fit for purpose?
      3. Are there any further measures that should be considered from an enforcement / escalation perspective, in addition or instead of those already included in the requirements?
    • During the meeting in August 2023, CCOICI Chair Manju Chen presented an overview of the CCOICI Recommendations Report on the SOI Requirements, but the vote on the recommendations was ultimately deferred in last month's Council meeting due to some last minute concerns from the CPH.
    • As it turned out, no changes are being proposed to the CCOICI Recommendations and Council will proceed with the vote on these recommendations as they are written - which maintains the ability to exempt participants from declaring in their GNSO SOI who they represented whenever they participated in a PDP in case of professional ethical obligations preventing complications. The motiononly requires a simple majority for it to be carried.
  • Item 5: COUNCIL DISCUSSION - Optional Topics for Potential Council Response

(i) Pilot Holistic Review Revised Draft Terms of Reference 

    • The ICANN Board is currently seeking the community's input on the proposed Pilot Holistic Review Revised Draft Terms of Reference. This is an update to the first version posted for Public Comment in August 2022 and has been modified to reflect community input. The primary focus of the Pilot Holistic Review Draft Terms of Reference (ToR) is to address the four primary issues raised during the first Public Comment proceeding:
      • The scope of Holistic Review is unclear
      • There is a lack of independent examination in the Holistic Review
      • There is a lack of identified dependencies
      • The community might not have the ability to support the Pilot Holistic Review work
    • The ToR Development Team also shortened and revised the ToR document to include more direct language and clearer deliverables.
    • Considering the potential implications on the ICANN structures and work, the Board is seeking input on whether the revised Draft ToR seems fit for purpose, and whether it sufficiently addresses the issues identified in the first Public Comment proceeding.
    • The following questions are designed to aid responders in formulating their views:
      1. Do you support the Pilot Holistic Review Revised Terms of Reference as drafted?
      2. Does the Pilot Holistic Review Revised Terms of Reference sufficiently address the four primary issues identified in the first Public Comment proceeding?
      3. Does the Pilot Holistic Review Revised Terms of Reference sufficiently clarify the deliverables for the Pilot Holistic Review?
      4. Do you support the next steps for the Pilot Holistic Review (as noted below)?
    • For more background information, Councilors are invited to listen to the webinar on this topic. 
    • Deadline for feedback is 27 November 2023.

(ii) Proposed Process for the Retirement of Non-Policy Recommendations 

    • To implement the Board-approved Third Accountability and Transparency Review (ATRT3) Recommendation 5, and considering the numerous times the ATRT3 Final Report stresses the procedural gap of not having a process to retire approved recommendations, ICANN org is proposing a process for the retirement of community-developed Board-approved non-policy recommendations in exceptional cases and according to specific criteria. 
    • Non-policy recommendations refer to community recommendations developed outside of a policy development process, such as Specific Reviews or Cross-Community Working Groups. The process will be publicly documented in the planning prioritization framework, and referenced in relevant documentation, such as the revised version of the Operating Standards for Specific Reviews. 
    • Council will discuss the Proposed Process and determine whether input on the proposed process is needed. 
    • The deadline for input is 30 November 2023

(iii) Continuous Improvement Program Community Coordination Group (CIP-CCG)

    • The Third Accountability and Transparency Review (ATRT3) Recommendation 3.6 calls for Organizational Reviews to be evolved into a Continuous Improvement Program (CIP). The recommendation to create a Continuous Improvement Program states that ICANN org shall work with each Supporting Organization (SO), Advisory Committee (AC) and their stakeholder groups, and the Nominating Committee (NomCom) to establish a Continuous Improvement Program. It will include an annual satisfaction survey of members/participants, and a regular assessment, including a summary of continuous improvements published at least every three years. 
    • As the ICANN Community considers the implementation of ATRT3 Recommendation 3.6 as it relates to each community structure and for the ICANN Community overall, the CIP Community Coordination Group is intended to serve as a forum to exchange best practices, lessons learned, as well as for sharing information and progress related to already existing community continuous improvement activities. The representatives in the CIP-CCG will share best practices and collaborate on community-wide implementation of ATRT3 Recommendation 3.6, while relaying information back to their constituencies to inform the process and voice decisions. 
    • ICANN org plans to proceed with the approach outlined in its letter by the end of November; however, if there are objections, concerns, or further feedback/questions, input is due by 30 November 2023.
  • Item 7: COUNCIL DISCUSSION - Diacritics Issue in Latin Script
    • PointQuébec, CORE Association, and the At-Large Advisory Committee raised an issue to the GNSO Council attention with regard to the challenge affecting future applied-for strings in the Latin script containing diacritics that may be confusingly similar to ASCII strings and are non-variants. 
    • 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, is widely recognized by users as its “equivalence” and may be determined to be confusingly similar (i.e., in which case, it would not pass the String Similarity Review).
    • One notable example of this problem known to the ICANN community is the string “québec”. PointQuébec Inc, the Registry of .quebec, has long held an interest in applying for this string, but it may face challenges obtaining it. PointQuébec regards the string “.québec” a necessity for serving the French speaking community in Quebec, Canada. Quebec is the only province in Canada whose sole official language is French; 71.2% of Quebecers are first language francophones. In the 2012 round, PointQuébec was advised not to apply for “.québec” due to considerations for technical readiness and financial predictability for an IDN gTLD. Hence it applied for the ASCII string without diacritics “.quebec” first, but has been waiting to submit an application for the IDN string in the next round.
    • A similar problem could happen to other existing Registries that currently manage ASCII gTLDs but may wish to apply for their IDN equivalence that are not deemed as allocatable variant labels according to the RZ-LGR. Future applicants may also be affected by this challenge.

    • To consider the development of an exception procedure for handling the consequence of String Similarity Review and create a potential path for future applications such as the “.québec” string, a GNSO Policy Development Process is likely the necessary avenue to do so. Understanding the seriousness of the issue and the potential harm to the interests or needs of the intended language committees, the GNSO Council agrees that requesting an Issue Report to thoroughly research and scope the problem is the appropriate step forward. The Issue Report will serve as the basis for launching a dedicated PDP on this topic, should the GNSO Council consider this path in the future. 

  • Item 8: ANY OTHER BUSINESS
    • 8.1 – Farewell to outgoing Councilors

    • 8.2 – Update - Open Contracted Party House DNS Abuse Calls

    • 8.3 – GNSO Framework for Continuous Improvement Pilot Review

    • 8.4 – Open microphone (Continuation of anniversary session discussion / input

Card
idMeet_Oct2023
labelMEETING RECORD

25 Oct 2023, Session 1

25 Oct 2023, Session 2

26 Oct 2023 (Council Wrap-up)

  • ANY OTHER BUSINESS
    • 8.1 – Farewell to outgoing Councilors

    • 8.2 – Update - Open Contracted Party House DNS Abuse Calls

    • 8.3 – GNSO Framework for Continuous Improvement Pilot Review

    • 8.4 – Open microphone (Continuation of anniversary session discussion / input


Card
idMeet_Oct2023
labelMEETING RECORD

Records of 25 and 26 Oct 2023 Meetings at ICANN78

25 Oct 2023, Session 1

25 Oct 2023, Session 2

26 Oct 2023 (Council Wrap-up)



Card
idSumRep_Oct2023
labelSPECIAL REPORT

Special Summary Report of 25 and 26 Oct 2023 Meetings 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 Oct 2023 Matters of Interest and/or from GNSO Council Oct 2023 Meeting Records.

1. GNSO Council Leadership 2023/2024

  • Greg DiBiase, Tomslin Samme-Nlar and Nacho Amadoz, were elected by acclamation as GNSO Chair, GNSO Council Vice-Chair (NCPH), and GNSO Council Vice-Chair (CPH), respectively.

2. Diacritics Issue in Latin Script

  • Following a staff presentation and after much discussion, Council settled on asking for a Study (and not an Issues Report as Councilors did not want to potentially trigger a subsequent PDP) in order to be able to make a better informed decision on subsequent next step.

3.  DNS Abuse Mitigation by Contracted Party House (CPH)

  • The CPH (i.e. the Registry SG and Registrar SG) has opened their meetings, and plan to invite SOACs to share information with them, to inform on projects and develop possible inputs to such meeting.

    Action by ALAC Liaison

    •  As the ALAC's designated contact point, to liaise with CPH on such outreach opportunities.

4. GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements 

  • In August, Council received an overview of the CCOICI Recommendations Report on the SOI Requirements which concluded that no consensus was reached on the ability to exempt participants from declaring in their GNSO SOI who they represented whenever they participated in a PDP in case of professional ethical obligations preventing complications. Although it was recommended that the GNSO SOI format be updated to form two parts (see below), the existing SOI language which allows for the exemption was to remain as is. Further, it is proposed that the SOI be organised into 2 parts:
    • a) General Statement of Interest which contains general information about a participant (parent).
    • b) Activity Specific Statement of Interest which contains information that is provided specific to the activity, for example, motivation for participation (child)
  • The vote to adopt these CCOICI recommendations was withdrawn at Council's Sep 2023 meeting as CPH were not prepared to vote on the one recommendation, as written, to retain the exemption. Hence this matter went back to the CCOICI for further consideration. CCOICI could not come to agreement to change the relevant recommendation.
  • Following this, the vote to adopt these CCOICI recommendations was put without any amendment at this Council meeting, requiring only a simple majority to pass.
  • The vote failed, with the CPH voting nay and the NCPH voting yay. As a result, none of the CCOICI recommendations were adopted. No change to the GNSO SOI is effected.

5. Topics for Potential Council Response

Card
idSumRep_Oct2023
labelSPECIAL REPORT

Special Summary Report of 25 and 26 Oct 2023 Meetings 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 Oct 2023 Matters of Interest and/or from GNSO Council Oct 2023 Meeting Records
  • .


Anchor
A-23-10B
A-23-10B
ALAC-GNSO COUNCIL BILATERAL MEETING (AT ICANN78, OCT 2023)        (go up to Directory) 

...

Deck of Cards
idSep2023


Card
idShow_Sep2023
labelSHOW ME

GNSO Council Meeting #9 of 2023 held on 21 Sep 2023


Card
idAgenda_Sep2023
labelAGENDA

GNSO Council Meeting #9 of 2023 held on 21 Sep 2023

Full Agenda  |  Documents  | Motions

  • Item 1: Administrative Matters
  • Item 2: Opening Remarks / Review of Projects List and Action Item List
  • Item 3: Consent Agenda (none)
  • Item 4: COUNCIL VOTE (Withdrawn) - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements
  • Item 5: COUNCIL VOTE - Charter for Registration Data Request Service (RDRS) Standing Committee to help inform the next steps on the SSAD policy recommendations
  • Item 6: COUNCIL VOTE (Deferred) -  SubPro Clarifying Statement on Registry Voluntary Commitments (RVCs) and Public Interest Commitments (PICs) 
  • Item 7: COUNCIL DISCUSSION - SubPro Small Team Updated Assignment Form
  • Item 8: ICANN78 Planning 
    • Sat, 21 Oct, 13:15-14:30 CEST - Joint At-Large & GNSO meeting
  • Item 9: Cross Community Working Group - Auction Proceeds Response
  • Item 10: ANY OTHER BUSINESS
    • 10.1 GNSO Prep Week Webinar - Tue, 10 Oct at 13:00 UTC
    • 10.2 Planning for GNSO Council Strategic Planning Session
    • 10.3 ccNSO [& GAC] Liaison updates
    • 10.4 Review of CCOICI pilot
    • 10.5 IGO next steps
    • 10.6 WS2 Community Coordination Group (CCG) 
    • Ad hoc 10.7 Confusing Similarity / IDN in Latin Script

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


Card
idMOI_Sep2023
labelMATTERS OF INTEREST

Matters of interest to ALAC/At-Large

  • Item 1: Administrative Matters
    • Minutes of the GNSO Council meeting on 20 July were posted on 06 August 2023.
    • Minutes of the GNSO Council meeting on 24 August were posted on 09 September 2023.
  • Item 4: COUNCIL VOTE (Withdrawn) - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements
    • The GNSO Framework for Continuous Improvement Pilot was initiated in June 2021 to determine whether the framework, as outlined herecould serve as an approach for dealing with the various projects that are focused on improvements to GNSO processes and procedures.
    • The CCOICI tasked the GNSO Statement of Interest (SOI) Task Force to address the following questions:

      1. Is the original objective of the SOI, as stated in the BGC WG Report, still valid? If not, why not and what should the current objective be?
      2. Based on the response to question 1), is the requested information to be provided as part of the SOI still fit for purpose? If not, why not, and what would need to be changed to make it fit for purpose?
      3. Are there any further measures that should be considered from an enforcement / escalation perspective, in addition or instead of those already included in the requirements?
    • The CCOICI submitted to  Council for consideration its Recommendations Report following its review of the Recommendations Report submitted to the CCOICI by the GNSO Statement of Interest Task Force based on their review of the GNSO Statement of Interest (SOI) Requirements as well as their review of the input received in response to the public comment forum.
    • Council received an overview of the CCOICI Recommendations Report on the SOI Requirements at their Aug meeting and will vote on this vide a motion that only requires a simple majority for it to be carried.
  • Item 5: COUNCIL VOTE - Charter for Registration Data Request Service (RDRS) Standing Committee to help inform the next steps on the SSAD policy recommendations
    • In Sep 2022, ICANN org published a WHOIS Disclosure System (System) Design Paper based on the "proof of concept" approach outlined by the Small Team.

    • Council then informed the ICANN Board on 17 November 2022 that Council unanimously accepted the Addendum to the Preliminary Report (Addendum) prepared by the Small Team and supported the implementation of the System, after which on 27 Feb 2023, the ICANN Board directed ICANN org to “proceed to develop and launch the System as soon as possible”. The ICANN Board also “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". 

    • In Mar 2023, 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”.

    • Council has received the small team's proposed charter for a Registration Data Request Service (RDRS) Standing Committee (to help inform the next steps on the SSAD policy recommendations) and will vote on this charter that only requires a simple majority for it to be carried.

  • Item 6: COUNCIL VOTE (Deferred) -   SubPro Clarifying Statement on Registry Voluntary Commitments (RVCs) and Public Interest Commitments (PICs)
    • During its informal session at ICANN76 and the subsequent Council meeting, Council discussed and agreed to task a small team of interested councilors to review the recommendations that the Board placed in a pending status and suggest to the full Council how the underlying concerns that caused the pending status can be best addressed (i.e., a limited triage exercise).
    • Since ICANN76, the Council SubPro Small Team has met several times and has completed a comprehensive review of the issues chart, with Board member input on why the Board placed specific recommendations into a pending status. Council discussed the main output of that triage effort, the proposed paths forward for each pending recommendation, during an Extraordinary Meeting on 4 May. During that meeting, Council agreed to further task the small team with taking interim steps (e.g., provision of clarifying information, developing speaking points) in order to support the Council’s dialogue with the ICANN Board on 22 May. Council debriefed after the dialogue with the ICANN Board and discussed next steps. 
    • During ICANN77 Day 0 Session, Council heard from members of the Board regarding the Board’s views on potential “landing spots” on the pending recommendations. Following this discussion, the Small Team has drafted clarifying statements for items in landing spot one (“Provision of Clarifying Statement to the Board”).
    • During its meeting in July, Council received an update from the Small Team on the proposed clarifying statement and during its August meeting, Council approved a clarifying statement for a number of pending recommendations, though it removed text in the Clarifying Statement relating to the enforceability of PICs and RVCs and holding this over to a future Clarifying Statement, pending further feedback from the ICANN Board. Additional feedback was delivered to the small team and subsequently considered.
    • The Small Team worked on the second Clarifying Statement relating specifically to the enforceability of PICs and RVCs (but should be read as complementary to the relevant pending recommendation(s) and should be considered jointly with the recommendations for the purposes of implementation), which Council had expected to vote on (vide a motion that only requires a simple majority for it to be carried).
    • As it turned out, this second Clarifying Statement remains a work in progress and hence required that the Council vote be deferred.
  • Item 7: COUNCIL DISCUSSION - SubPro Small Team Updated Assignment Form
    • During its informal session at ICANN76 and the subsequent Council meeting, Council discussed and agreed to task a small team of interested councilors to review the recommendations that the Board placed in a pending status and suggest to the full Council how the underlying concerns that caused the pending status can be best addressed (i.e., a limited triage exercise).
    • Since ICANN76, this the Council SubPro Small Team has, as part of the limited triage exercise, worked on and drafted the first Clarifying Statement and second Clarifying Statement for Council's consideration.
      • The first Clarifying Statement had been approved by Council in its Aug meeting and subsequently submitted to the ICANN Board on 5 Sep. 
      • The ICANN Board has on 10 Sep resolved to, among other things, adopt 12 SubPro Outputs with the 5 Sep GNSO Council Clarifying Statement.
      • The second Clarifying Statement had been planned to be voted on by Council at this meeting but was withdrawn.
    • As the triage exercise is now complete, the Small Team’s assignment form has been updated to reflect the updated assignment regarding how the non-adopted recommendations should be handled, e.g., supplemental recommendation, Section 16, etc.  Council will hear an update on the proposed updated assignment form.
  • Item 8: ICANN78 Planning 
    • A Joint At-Large & GNSO meeting is scheduled for Sat, 21 Oct, 13:15-14:30 CEST, the agenda for which is still in planning.
  • Item 9: Cross Community Working Group - Auction Proceeds Response
    • On 17 Jul 2023, Xavier Calvez sent a written update on the progress of ICANN org’s implementation of the Cross Community Working Group’s - Auction Proceeds (CCWG-AP) Final Report.  The update noted the implementation work will result in the launch of the ICANN Grant Program at the end of the first quarter of 2024. The program will distribute the 2012 New gTLD Program Auction Proceeds in line with the recommendations, as adopted by the ICANN Board in June 2022.
    • As implementation progresses, ICANN org has considered organizing a meeting, with former members of the CCWG-AP, should any of the former members be interested and available to participate. This will help to ensure that implementation preserves the intent of the group’s recommendations.
    • Council will discuss a response to this message. Specifically, the Council is asked to consider if it is comfortable with former CCWG-AP members engaging in a conversation with ICANN org or whether the discussion should be conducted differently.


Card
idMeet_Sep2023
labelMEETING RECORD

Records of 21 Sep 2023 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_Sep2023
labelSPECIAL REPORT

Special Summary Report of 21 Sep 2023 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 Sep 2023 Matters of Interest and/or from GNSO Council Sep 2023 Meeting Records.

1. GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements 

  • Last month, Council received an overview of the CCOICI Recommendations Report on the SOI Requirements which concluded that no consensus was reached on the ability to exempt participants from declaring in their GNSO SOI who they represented whenever they participated in a PDP in case of professional ethical obligations preventing complications. Although it was recommended that the GNSO SOI format be updated to form two parts (see below), the existing SOI language which allows for the exemption was to remain as is. Further, it is proposed that the SOI be organised into 2 parts:
    • a) General Statement of Interest which contains general information about a participant (parent).
    • b) Activity Specific Statement of Interest which contains information that is provided specific to the activity, for example, motivation for participation (child)
  • Just prior to this Council meeting, the vote to adopt these CCOICI recommendations was withdrawn as CPH were not prepared to vote on the one recommendation, as written, to retain the exemption. Hence this matter now goes back to the CCOICI for further consideration and, hopefully, resolution.

2. Charter for Registration Data Request Service (RDRS) Standing Committee

  • The GNSO Council EPDP Phase 2 Small Team's work has wrapped up - since their final task in guiding the design of the Registration Data Request Service (RDRS) (formerly known as the SSAD - System for Standardized Access/Disclosure to Registration Data) has concluded - and ICANN org is slated to launch the RDRS in November. 
  • Given this, the focus moves towards monitoring of ICANN org's implementation of the RDRS and how well it will function.  To facilitate this, Council is transitioning the EPDP Phase 2 Small Team into the RDRS Standing Committee, and Council has approved the Charter for this Standing Committee.
    • Impact for ALAC: ALAC retains a member seat by virtue of having had a member on the EPDP Phase 2 Small Team, along with an alternate.

3. New gTLD Program Next Round / Subsequent Procedures 38 Pending Recommendations 

  • As reported at the At-Large CPWG 20 Sep call, the GNSO Council SubPro Small Team had been working towards recommending a Second Clarifying Statement for Council approval. This Second Clarifying Statement was aimed at clarifying and resolving the ICANN Board's concerns on the group of 10 SubPro Outputs associated with the use, and hence, enforceability, of PICs/RVCs (i.e. SubPro Recommendations 9.1, 9.4, 9.8, 9.9, 9.10, 9.12, 9.13, 30.1, 31.16 and 31.17).
  • At the time Council met, this Second Clarifying Statement is subject to further work by the Small Team and hence required that a Council vote on it be deferred to Council's October meeting.
  • In parallel, also as reported at the At-Large CPWG 20 Sep call, the ICANN Board held a recent workshop where the Board resolved to, per its Scorecard;
    • Section A, adopt 7 SubPro Outputs with no further concern;
    • Section B, adopt 12 SubPro Outputs with the 5 Sep GNSO Council Clarifying Statement (i.e the First Clarifying Statement);
    • Section C, NOT adopt 7 SubPro Outputs at this this time, with given rationales; and
    • Section D, consider adopting 10 SubPro Outputs with the provision of the pending GNSO Council Second Clarifying Statement, and to continue discussing a remaining 3 SubPro Outputs with the GNSO Council SubPro Small Team with a goal of resolving them via the clarification mechanism.
  • Given the above development out of the Board workshop, the Small Team's assignment form (i.e. charter) required a revision to reflect the updated assignment regarding how the non-adopted recommendations should be handled. Council considered and approved this Small Team updated assignment form. 
  • The updated assignment form expands participation in the Small Team to each GNSO Stakeholder Group and Constituency, and each Advisory Committees (mainly ALAC and GAC), to elect to put forward one subject matter expert (SME) plus alternate to help inform the Small Team's final assignment #7 (which is to develop proposed Supplemental Recommendations or develop proposed modifications through GNSO's section 16 process).
    • Impact for ALAC: ALAC will be invited to appoint a SME and an alternate to the Small Team. These appointments may be changed from time to time to facilitate the relevant SME's participation to the different the topics being addressed. For avoidance of doubt, these appointments do not affect my participation as an existing member of the Small Team.

4. ICANN78 Joint Meeting of the At-Large and GNSO

  • A call for additions/changes to the proposed topics of SubPro Updates, RDRS and .quebec was made to Councilors.
  • The plan is to revisit this list of proposed topics in a fortnight for finalization.

5.  Cross Community Working Group - Auction Proceeds Response

  • Council is in favour of responding to Xavier Calvez's written update on the progress of ICANN org’s implementation of the Cross Community Working Group’s - Auction Proceeds (CCWG-AP) Final Report, noting that there is a bigger procedural issue going on regarding how changes to a working group’s recommendations should occur. The next step is to put together a draft response to Xavier Calvez with some of the Councilors' concerns and circulate it on the GNSO Council mailing list.

6. Confusing Similarity / IDN in Latin Script

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


...