Page History
...
Per Article 18 of ICANN Bylaws
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:
...
(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].
...
(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:
...
(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:
...
(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.
...
(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:
...
(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) Two representatives Three representatives who are associated with ccTLD(b) One non-ccNSO ccTLD representative who is associated with a ccTLD registry operator that is not a representative of the ccNSO, appointed by the ccNSO; it managers, appointed by the ccNSO from its ccTLD registry operator representatives; 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 consult with the regional ccTLD ccNSO Council reaches out to all ccTLD managers directly and or through regional ccTLD organizations (i.e., AfTLD, APTLD, LACTLD, and CENTR) in making its appointmentseeking volunteers;
(cb) Two representatives appointed by the Registries Stakeholder Group;
(dc) One representative appointed by the Registrars Stakeholder Group;
(ed) One representative appointed by the Commercial Stakeholder Group;
(fe) One representative appointed by the Non-Commercial Stakeholder Group;
(gf) One representative appointed by the GAC;
(hg) One representative appointed by the SSAC;
(ih) One representative appointed by the RSSAC;
(ji) One representative appointed by the ALAC;
(kj) One liaison appointed by the CSC;
(lk) One liaison who may be appointed by the ASO; and
(ml) One liaison who may be appointed by the IAB.
(nm) The IFRT shall also include an unlimited number of non-member, non-liaison participants.
(on) 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.
...
(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.
...
(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.
...
(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.
