Confirmation of Appointment of Ashley Heineman as GNSO-appointed Co-Chair of the IANA Naming Function Review Team

Submitted by Greg DiBiase

Seconded by Tomslin Samme-Nlar

  1. Whereas, on 16 September 2018, the first IANA Naming Function Review (IFR) was convened by the ICANN Board, in compliance with Article 18 of the ICANN Bylaws, which states: "The Board, or an appropriate committee thereof, shall cause periodic and/or special reviews (each such review, an "IFR") of PTI's performance of the IANA naming function against the contractual requirements set forth in the IANA Naming Function Contract and the IANA Naming Function SOW to be carried out by an IANA Function Review Team ("IFRT") established in accordance with Article 18."
  2. Whereas, Section 18.8(d) of the ICANN Bylaws requires both the GNSO and ccNSO Councils to appoint co-chairs to the IFRT.
  3. Whereas, on 18 September 2023, Ashley Heineman, who was appointed by the Registrar Stakeholder Group pursuant to Section 18.7(c) of the Bylaws, volunteered to serve as the Co-Chair of the IFRT.

Resolved,

  1. The GNSO Council accepts Ashley Heineman’s appointment as the Co-Chair of the IANA Function Review Team and thanks her for her willingness to serve.


Motion to adopt the recommendations of the Council Committee for Overseeing and Implementing Continuous Improvement in relation to the review of the GNSO Statement of Interest (SOI) requirements

Submitted by Manju Chen

Seconded by Osvaldo Novoa 

Whereas,

  1. The CCOICI tasked the GNSO Statement of Interest (SOI) Task Force (TF) to address the following questions:
  • 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?
  • 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?
  • 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?

     2. The TF commenced its deliberations in February 2022, submitting the TF Recommendations Report to the CCOICI on 27 April 2023. As the TF was not able to achieve full consensus on one essential element of its recommendations, namely whether there should be an exemption for those prevented by professional ethical obligations to disclose who they are representing in a specific effort, it recommended the CCOICI take on responsibility for resolving this specific issue as all other recommendations had achieved full consensus.

    3. The CCOICI took up this issue in May of 2023 and considered it in detail as outlined in Annex A of the CCOICI Recommendations Report. As the CCOICI was not able to resolve the different positions on the exemption language, the CCOICI agreed to revert to the current, existing exemption language in the SOI to allow the Council to consider all the other recommendations as outlined in section 2 and 3 of the CCOICI Recommendations Report. These recommendations achieved full consensus of the TF as well as the CCOICI.

    4. The CCOICI submitted its Recommendations Report to the GNSO Council on 14 August 2023.

    5. The GNSO Council considered the CCOICI Recommendations Report during its August 2023 meeting.

Resolved,

  1. The GNSO Council adopts the recommendations as outlined in section #2 (SOI Recommendations) and #3 (Proposed Updates to the GNSO Operating Procedures), with the caveat that the proposed updates to the GNSO Operating Procedures will not be implemented until resolved #2 and #3 have been completed.
  2. The GNSO Council requests that the GNSO Policy Development Support Staff develop a proposed implementation plan for these recommendations, recognising that exploring the technical options as well as the transition needs careful consideration.
  3. The GNSO Council will consider the proposed implementation plan and as part of that consideration confirm when the proposed updates to the GNSO Operating Procedures are expected to take effect.
  4. The GNSO Council thanks the members of the GNSO SOI TF as well as the CCOICI for its work.




  • No labels
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers