Per Article 18 of ICANN Bylaws (as of 1 January 2023)
Section 18.1. IANA NAMING FUNCTION REVIEW
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, as follows:
(a) Regularly scheduled periodic IFRs, to be conducted pursuant to Section 18.2 below ("Periodic IFRs"); and
(b) IFRs that are not Periodic IFRs, to be conducted pursuant to Section 18.12 below ("Special IFRs").
Section 18.2. FREQUENCY OF PERIODIC IFRS
(a) The first Periodic IFR shall be convened no later than [1 October 2018].
(b) Periodic IFRs after the first Periodic IFR shall be convened no less frequently than every five years, measured from the date the previous IFRT for a Periodic IFR was convened.
(c) In the event a Special IFR is ongoing at the time a Periodic IFR is required to be convened under this Section 18.2, the Board shall cause the convening of the Periodic IFR to be delayed if such delay is approved by the vote of (i) a supermajority of the ccNSO Council (pursuant to the ccNSO's procedures or, if such procedures do not define a supermajority, two-thirds (2/3) of the ccNSO Council's members) and (ii) a GNSO Supermajority. Any decision by the ccNSO and GNSO to delay a Periodic IFR must identify the period of delay, which should generally not exceed 12 months after the completion of the Special IFR.
Section 18.3. IFR RESPONSIBILITIES
For each Periodic IFR, the IFRT shall:
(a) Review and evaluate the performance of PTI against the requirements set forth in the IANA Naming Function Contract in relation to the needs of its direct customers and the expectations of the broader ICANN community, and determine whether to make any recommendations with respect to PTI's performance;
(b) Review and evaluate the performance of PTI against the requirements set forth in the IANA Naming Function Contract and IANA Naming Function SOW;
(c) Review the IANA Naming Function SOW and determine whether to recommend any amendments to the IANA Naming Function Contract and IANA Naming Function SOW to account for the needs of the direct customers of the naming services and/or the community at large;
(d) Review and evaluate the openness and transparency procedures of PTI and any oversight structures for PTI's performance, including reporting requirements and budget transparency;
(e) Review and evaluate the performance and effectiveness of the EC with respect to actions taken by the EC, if any, pursuant to Section 16.2, Section 18.6, Section 18.12, Section 19.1, Section 19.4, Section 22.4(b) and Annex D;
(f) Review and evaluate the performance of the IANA naming function according to established service level expectations during the IFR period being reviewed and compared to the immediately preceding Periodic IFR period;
(g) Review and evaluate whether there are any systemic issues that are impacting PTI's performance under the IANA Naming Function Contract and IANA Naming Function SOW;
(h) Initiate public comment periods and other processes for community input on PTI's performance under the IANA Naming Function Contract and IANA Naming Function SOW (such public comment periods shall comply with the designated practice for public comment periods within ICANN);
(i) Consider input from the CSC and the community on PTI's performance under the IANA Naming Function Contract and IANA Naming Function SOW;
(j) Identify process or other areas for improvement in the performance of the IANA naming function under the IANA Naming Function Contract and IANA Naming Function SOW and the performance of the CSC and the EC as it relates to oversight of PTI; and
(k) Consider and assess any changes implemented since the immediately preceding IFR and their implications for the performance of PTI under the IANA Naming Function Contract and IANA Naming Function SOW.
Section 18.4. IFR REQUIRED INPUTS
In conducting an IFR, the IFRT shall review and analyze the following information:
(a) Reports provided by PTI pursuant to the IANA Naming Function Contract and/or IANA Naming Function SOW during the IFR period being reviewed, any portion of which may be redacted pursuant to the Confidential Disclosure Framework set forth in the Operating Standards in accordance with Section 4.6(a)(vi);
(b) Reports provided by the CSC in accordance with the CSC Charter during the IFR period being reviewed;
(c) Community inputs through public consultation procedures as reasonably determined by the IFRT, including, among other things, public comment periods, input provided at in-person sessions during ICANN meetings, responses to public surveys related to PTI's performance under the IANA Naming Function Contract and IANA Naming Function SOW, and public inputs during meetings of the IFRT;
(d) Recommendations for technical, process and/or other improvements relating to the mandate of the IFR provided by the CSC or the community; and
(e) Results of any site visit conducted by the IFRT, which shall be conducted in consultation with ICANN (i) upon reasonable notice, (ii) in a manner so as to not affect PTI's performance under the IANA Naming Function Contract or the IANA Naming Function SOW and (iii) pursuant to procedures and requirements reasonably developed by ICANN and reasonably acceptable to the IFRT. Any such site visit shall be limited to matters reasonably related to the IFRT's responsibilities pursuant to Section 18.3.
Section 18.5. IFR RESULTS AND RECOMMENDATIONS
(a) The results of the IFR are not limited and could include a variety of recommendations or no recommendation; provided, however, that any recommendations must directly relate to the matters discussed in Section 18.3 and comply with this Section 18.5.
(b) Any IFRT recommendations should identify improvements that are supported by data and associated analysis about existing deficiencies and how they could be addressed. Each recommendation of the IFRT shall include proposed remedial procedures and describe how those procedures are expected to address such issues. The IFRT's report shall also propose timelines for implementing the IFRT's recommendations. The IFRT shall attempt to prioritize each of its recommendations and provide a rationale for such prioritization.
(c) In any case where a recommendation of an IFRT focuses on a service specific to gTLD registry operators, no such recommendation shall be made by the IFRT in any report to the community (including any report to the Board) if opposition to such recommendation is expressed by any IFRT member appointed by the Registries Stakeholder Group. In any case where a recommendation of an IFRT focuses on a service specific to ccTLD registry operators, no such recommendation shall be made by the IFRT in any report to the community (including any report to the Board) if opposition to such recommendation is expressed by any IFRT member appointed by the ccNSO.
(d) Notwithstanding anything herein to the contrary, the IFRT shall not have the authority to review or make recommendations relating to policy or contracting issues that are not included in the IANA Naming Function Contract or the IANA Naming Function SOW, including, without limitation, policy development, adoption processes or contract enforcement measures between contracted registries and ICANN.
Section 18.6.Recommendations to Amend the IANA Naming Function contract, iana naming function SOW or CSC charter
(a) The IFRT may recommend, among other things to the extent reasonably related to the IFR responsibilities set forth in Section 18.3, amendments to the IANA Naming Function Contract, IANA Naming Function SOW and/or the CSC Charter. The IFRT shall, at a minimum, take the following steps before an amendment to either the IANA Naming Function Contract, IANA Naming Function SOW or CSC Charter is proposed:
(i) Consult with the Board (such consultation to be conducted in parallel with other processes set forth in this Section 18.6(a)) and PTI;
(ii) Consult with the CSC;
(iii) Conduct a public input session for ccTLD and gTLD registry operators; and
(iv) Seek public comment on the amendments that are under consideration by the IFRT through a public comment period that complies with the designated practice for public comment periods within ICANN.
(b) A recommendation of an IFRT for a Periodic IFR that would amend the IANA Naming Function Contract or IANA Naming Function SOW shall only become effective if, with respect to each such recommendation (each, an "IFR Recommendation"), each of the following occurs:
(i) The IFR Recommendation has been approved by the vote of (A) a supermajority of the ccNSO Council (pursuant to the ccNSO's procedures or, if such procedures do not define a supermajority, two-thirds (2/3) of the ccNSO Council's members) and (B) a GNSO Supermajority;
(ii) After a public comment period that complies with the designated practice for public comment periods within ICANN, the Board has approved the IFR Recommendation; and
(iii) The EC has not rejected the Board's approval of the IFR Recommendation pursuant to and in compliance with Section 18.6(d).
(c) If the Board (x) rejects an IFR Recommendation that was approved by the ccNSO Council and GNSO Council pursuant to Section 18.6(b)(i) or (y) does not resolve to either accept or reject an IFR Recommendation within 45 days of the later of (1) the date that the condition in Section 18.6(b)(i) is satisfied or (2) the expiration of the public comment period contemplated by Section 18.6(b)(ii), the Secretary shall provide a Board Notice to the EC Administration and the Decisional Participants, which Board Notice shall enclose a copy of the applicable IFR Recommendation. ICANN shall post the Board Notice, along with a copy of the notification(s) sent to the EC Administration and the Decisional Participants, on the Website promptly following the delivery of the Board Notice to the EC Administration and the Decisional Participants.
(i) ICANN shall, at the direction of the EC Administration, convene a Rejection Action Community Forum (as defined in Section 2.3(a) of Annex D), which Rejection Action Community Forum shall be conducted in accordance with Section 2.3 of Annex D, to discuss the Board Notice; provided, that, for purposes of Section 2.3 of Annex D, (A) the Board Notice shall be treated as the Rejection Action Supported Petition, (B) the EC Administration shall be treated as the Rejection Action Petitioning Decisional Participant (and there shall be no Rejection Action Supporting Decisional Participants (as defined in Section 2.2(d)(i) of Annex D) and (C) the Rejection Action Community Forum Period shall expire on the 21st day after the date the Secretary provides the Board Notice to the EC Administration and the Decisional Participants.
(ii) No later than 45 days after the conclusion of such Rejection Action Community Forum Period, the Board shall resolve to either uphold its rejection of the IFR Recommendation or approve the IFR Recommendation (either, a "Post-Forum IFR Recommendation Decision").
(A)If the Board resolves to approve the IFR Recommendation, such IFR Recommendation will be subject to Section 18.6(d).
(B)For the avoidance of doubt, the Board shall not be obligated to change its decision on the IFR Recommendation as a result of the Rejection Action Community Forum.
(C)The Board's Post-Forum IFR Recommendation Decision shall be posted on the Website in accordance with the Board's posting obligations as set forth in Article 3.
(d) Promptly after the Board approves an IFR Recommendation (an "IFR Recommendation Decision"), the Secretary shall provide a Board Notice to the EC Administration and the Decisional Participants, which Board Notice shall enclose a copy of the IFR Recommendation that is the subject of the IFR Recommendation Decision. ICANN shall post the Board Notice, along with a copy of the notification(s) sent to the EC Administration and the Decisional Participants, on the Website promptly following the delivery of the Board Notice to the EC Administration and the Decisional Participants. The EC Administration shall promptly commence and comply with the procedures and requirements specified in Article 2 of Annex D.
(i) An IFR Recommendation Decision shall become final upon the earliest to occur of the following:
(A)(1) A Rejection Action Petition Notice is not timely delivered by the Rejection Action Petitioning Decisional Participant to the Secretary pursuant to and in compliance with Section 2.2(c) of Annex D or (2) a Rejection Process Termination Notice is delivered by the EC Administration to the Secretary pursuant to and in compliance with Section 2.2(c) of Annex D, in which case the IFR Recommendation Decision shall be final as of the date immediately following the expiration of the Rejection Action Petition Period relating to such IFR Recommendation Decision;
(B)(1) A Rejection Action Supported Petition is not timely delivered by the Rejection Action Petitioning Decisional Participant to the Secretary pursuant to and in compliance with Section 2.2(d) of Annex D or (2) a Rejection Process Termination Notice is delivered by the EC Administration to the Secretary pursuant to and in compliance with Section 2.2(d) of Annex D, in which case the IFR Recommendation Decision shall be final as of the date immediately following the expiration of the Rejection Action Petition Support Period relating to such IFR Recommendation Decision; and
(C)(1) An EC Rejection Notice is not timely delivered by the EC Administration to the Secretary pursuant to and in compliance with Section 2.4 of Annex D or (2) a Rejection Process Termination Notice is delivered by the EC Administration to the Secretary pursuant to and in compliance with Section 2.4(c) of Annex D, in which case the IFR Recommendation Decision shall be final as of the date immediately following the expiration of the Rejection Action Decision Period relating to such IFR Recommendation Decision.
(ii) An IFR Recommendation Decision that has been rejected by the EC pursuant to and in compliance with Article 2 of Annex D shall have no force and effect, and shall be void ab initio.
(e) For the avoidance of doubt, Section 18.6(d) shall not apply when the Board acts in a manner that is consistent with an IFR Recommendation unless such IFR Recommendation relates to an IANA Naming Function Separation Process as described in Article 19.
(f) Timelines for implementing any amendments to the IANA Naming Function Contract or IANA Naming Function SOW shall be reasonably agreed between the IFRT, ICANN and PTI.
(g) A recommendation of an IFRT that would amend the CSC Charter shall only become effective if approved pursuant to Section 17.3(d).
Section 18.7. COMPOSITION OF IFR TEAMS
Each IFRT shall consist of the following members and liaisons to be appointed in accordance with the rules and procedures of the appointing organization:
(a) Three representatives who are associated with ccTLD managers, appointed by the ccNSO Council. Representatives need not be associated with a ccNSO member. The ccNSO Council should use an inclusive process, which is open to all ccTLD managers, independent of their membership to the ccNSO. It is strongly recommended that the ccNSO Council reaches out to all ccTLD managers directly and or through regional ccTLD organizations (i.e., AfTLD, APTLD, LACTLD, and CENTR) in seeking volunteers;
(b) Two representatives appointed by the Registries Stakeholder Group;
(c) One representative appointed by the Registrars Stakeholder Group;
(d) One representative appointed by the Commercial Stakeholder Group;
(e) One representative appointed by the Non-Commercial Stakeholder Group;
(f) One representative appointed by the GAC;
(g) One representative appointed by the SSAC;
(h) One representative appointed by the RSSAC;
(i) One representative appointed by the ALAC;
(j) One liaison appointed by the CSC;
(k) One liaison who may be appointed by the ASO; and
(l) One liaison who may be appointed by the IAB.
(m) The IFRT shall also include an unlimited number of non-member, non-liaison participants.
(n) The IFRT shall not be a standing body. A new IFRT shall be constituted for each IFR and the IFRT shall automatically dissolve following the end of the process for approving such IFRT's IFR Recommendations pursuant to Section 18.6.
Section 18.8. MEMBERSHIP; ELECTION OF CO-CHAIRS, AND LIAISONS
(a) All candidates for appointment to the IFRT as a member or liaison shall submit an expression of interest to the organization that would appoint such candidate as a member or liaison to the IFRT, which shall state: (i) why the candidate is interested in becoming involved in the IFRT, (ii) what particular skills the candidate would bring to the IFRT, (iii) the candidate's knowledge of the IANA functions, (iv) the candidate's understanding of the purpose of the IFRT, and (v) that the candidate understands the time necessary to participate in the IFR process and can commit to the role.
(b) Members, liaisons and participants of the IFRT shall disclose to ICANN and the IFRT any conflicts of interest with a specific complaint or issue under review. The IFRT may exclude from the discussion of a specific complaint or issue any member deemed by the majority of IFRT members to have a conflict of interest. The co-chairs of the IFRT shall record any such conflict of interest in the minutes of the IFRT.
(c) To the extent reasonably possible, the appointing organizations for the IFRT members and liaisons shall work together to achieve an IFRT that is balanced for diversity (including functional, geographic and cultural) and skill, and should seek to broaden the number of individuals participating across the various reviews; provided, that the IFRT should include members from each ICANN Geographic Region, and the ccNSO and Registries Stakeholder Group shall not appoint multiple members who are citizens of countries from the same ICANN Geographic Region.
(d) The IFRT shall be led by two co-chairs: one appointed by the GNSO from one of the members appointed pursuant to clauses (c)-(f) of Section 18.7 and one appointed by the ccNSO from one of the members appointed pursuant to clauses (a)-(b) of Section 18.7.
(e) The PTI Board shall select a PTI staff member to serve as a point of contact to facilitate formal lines of communication between the IFRT and PTI. The Board shall select an ICANN staff member to serve as a point of contact to facilitate formal lines of communication between the IFRT and ICANN.
(f) Liaisons to the IFRT are not members of or entitled to vote on any matters before the IFRT, but otherwise are entitled to participate on equal footing with members of the IFRT.
(g) Other participants are entitled to participate in the IFRT, but are not entitled to vote.
(h) Removal and Replacement of IFRT Members and Liaisons
(i) The IFRT members and liaisons may be removed from the IFRT by their respective appointing organization at any time upon such organization providing written notice to the Secretary and the co-chairs of the IFRT.
(ii) A vacancy on the IFRT shall be deemed to exist in the event of the death, resignation or removal of any IFRT member or liaison. Vacancies shall be filled by the organization that appointed such IFRT member or liaison. The appointing organization shall provide written notice to the Secretary of its appointment to fill a vacancy, with a notification copy to the IFRT co-chairs. The organization responsible for filling such vacancy shall use its reasonable efforts to fill such vacancy within one month after the occurrence of such vacancy.
Section 18.9. MEETINGS
(a) All actions of the IFRT shall be taken by consensus of the IFRT, which is where a small minority may disagree, but most agree. If consensus cannot be reached with respect to a particular issue, actions by the majority of all of the members of the IFRT shall be the action of the IFRT.
(b) Any members of the IFRT not in favor of an action (whether as a result of voting against a matter or objecting to the consensus position) may record a minority dissent to such action, which shall be included in the IFRT minutes and/or report, as applicable.
(c) IFRT meetings, deliberations and other working procedures shall be open to the public and conducted in a transparent manner to the fullest extent possible.
(d) The IFRT shall transmit minutes of its meetings to the Secretary, who shall cause those minutes to be posted to the Website as soon as practicable following each IFRT meeting. Recordings and transcripts of meetings, as well as mailing lists, shall also be posted to the Website.
Section 18.10. COMMUNITY REVIEWS AND REPORTS
(a) The IFRT shall seek community input as to the issues relevant to the IFR through one or more public comment periods that shall comply with the designated practice for public comment periods within ICANN and through discussions during ICANN's public meetings in developing and finalizing its recommendations and any report.
(b) The IFRT shall provide a draft report of its findings and recommendations to the community for public comment. The public comment period is required to comply with the designated practice for public comment periods within ICANN.
(c) After completion of the IFR, the IFRT shall submit its final report containing its findings and recommendations to the Board. ICANN shall thereafter promptly post the IFRT's final report on the Website.
Section 18.11. ADMINISTRATIVE AND OPERATIONAL SUPPORT
ICANN shall provide administrative and operational support necessary for each IFRT to carry out its responsibilities, including providing and facilitating remote participation in all meetings of the IFRT.
