Dear IFR2 Review Team; My colleagues in Legal have provided the below information on the topic of the ability for the IFR2 to provide suggested updates to the IANA Naming Function Contract. You may remember this was a specific question that came up on one the IFR2 meetings a few weeks ago. We’ll add this to the agenda for tomorrow’s IFR2 meeting and Sam Eisner will join us for the discussion and to answer questions you might have. The scope of the IFR’s work is set out at Article 18, Section 18.3 of the ICANN Bylaws. As it relates to the IANA Naming Function Contract, the relevant scope includes: 18.3(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; and [related] 18.3(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 In addition, other recommendations from the IFR could result in a need to amend the IANA Naming Function Contract as part of the proper implementation path, but that is a separate issue from the IFR team’s review of the Contract. We understand that IFRT has been dedicating significant time and careful effort to a review of the Contract, including identification of sections for which the IFR suggests the text could be clarified or more preferred language could be used, yet not necessarily fall into the areas of accounting for the needs of the direct customers/community or addressing systemic issues. These proposed redline clarifications might not appropriately be the subject of a unilateral amendment that can result from the IFR outputs. For these clarification items, while they may not be “formal” outputs of the IFR, ICANN org welcomes the suggestions of the IFRT on areas for ICANN and PTI to jointly evaluate to see if a mutually negotiated amendment might be appropriate. As the IFRT’s work also could result in proposed changes that are appropriately the subject of the unilateral amendment after the IFR process completes, the ICANN and PTI teams look forward to engaging with the IFRT to identify the language that could address the issues uncovered by the IFRT, so that any updates are clear and consistent with the other language of the Contract. Please let us know if you have further questions. Best, Jennifer -- Jennifer Bryce Project Manager, Office of the Chief Technology Officer (OCTO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>